Revenue Systems Administrator (CRM & GTM Stack)

At UpGuard, we are replacing manual security bottlenecks with AI-driven precision. Fresh off a $75M Series C, we are scaling our infrastructure to process 100 billion risk signals daily. This isn’t just growth; it’s a total reimagining of how the world manages cyber risk.

We build the Cyber Risk Posture Management (CRPM) platform that security teams actually love. By integrating security ratings, threat intel, and agentic AI, we empower organizations to stay ahead of an ever-evolving attack surface.

We aren’t just building another tool; we’re defining a category. We provide the autonomy to ship world-class technology and the resources to do it at a global scale.

Why are we hiring for this role?

We're looking for a builder to join our Revenue Systems team and take ownership of the systems that power our go-to-market motion. This is deliberately not a CRM-specialist role — the successful candidate will have a proven ability to work across the full GTM technology stack. You'll start hands-on administering and improving our tooling, and grow into architectural ownership of how our GTM systems fit together.

We are looking for someone with a strong GTM systems point of view. Someone who can execute cleanly against clear written direction and tell us why one architectural choice beats another. If you think in systems, care about data integrity and access control, and are energized by the idea of AI agents and APIs doing real work inside a CRM, this is for you.

What you'll do

• Administer and improve our GTM stack — day-to-day ownership of our GTM tools: users, objects, fields, workflows, automations, integrations, validation logic, and data hygiene.

• Own access and security at the data layer. Design and enforce granular, field- and property-level access controls using profiles, permission sets, and field-level security — not the UI. As we lean into AI agents and API-driven bulk actions, you'll make sure automated processes respect each user's permission scope at the data layer, where it actually counts.

• Build automation that enforces process — deal-stage gates, handoffs, territory and eligibility logic, and the workflow actions that keep our sales process clean.

• Partner on architecture. Work directly with the Rev Ops team on how our CRM, CPQ/billing, and CS systems integrate — and increasingly drive those decisions yourself as you ramp.

• Work across systems, not just the CRM. Pick up projects in adjacent tools (sales engagement, CS platforms, enrichment, etc.) and apply the same systems thinking regardless of vendor.

• Document what you build — clear SOPs and process documentation for the systems you own.

What will you bring?

• 1–3 years hands-on building and maintaining an object-oriented CRM system. Salesforce and HubSpot experience is ideal, but strong object-model fluency in a comparable system is what matters most.

• Salesforce Administrator certification (or a clear path to it) is a strong plus; HubSpot CRM experience is a strong plus.

• A genuine point of view on CRM architecture. You can articulate why a design choice matters — object relationships, permission models, automation patterns — not just execute a ticket.

• You execute reliably against written instruction and know when to raise a hand with a better idea.

• Deep comfort with the permission model — profiles, permission sets, field-level security, and teams/roles. You understand that the UI is not a security boundary and that API/agent actions run with the authenticated user's permissions.

• A general systems mindset. You'd be comfortable — not lost — if we handed you a Sales Engagement or Customer Success project instead of a Salesforce one.

• An intermediate AI / Claude-specific mindset — you've used LLM tooling meaningfully and think about where agents fit into an ops workflow.

What gives you an edge?

• Comfort with API-based actions and concepts — REST/CRUD, auth, batching, and the idea of code-driven workflow actions.

• Exposure to CPQ/billing tooling, custom code actions, or CRM API integration work.

• Experience supporting a fast-moving SDR/AE org.