Staff Software Engineer, Monetization Platform

Drata is building the trust layer between great companies - automating compliance, managing risk, and helping organizations prove trust continuously as they scale. We're Dratanauts: a global crew of 600+ professionals united by a culture that rewards integrity, ownership, and raising the bar, no matter where in the world we're working from. Why Join the Drata Team? At Drata, you're not maintaining legacy compliance software - you're building the agentic AI platform defining what trust looks like for the next generation of companies. Here's what makes the work itself worth showing up for:

Problems without a playbook: You'll work at the edge of AI and security, building agentic governance, continuous compliance, and real-time trust verification to solve problems that don't have an established answer yet. You're writing it as you go.

Real ownership, not just process: Our values center on owning outcomes and raising the bar, not checking boxes. You're expected to have opinions and back them.

A seat at the table: Your perspective is unique and valued. Open debate and diverse viewpoints are built into how decisions actually get made here, at every level.

Growth at rocketship speed: Drata is scaling fast, which means scope grows fast too. High performers get more ownership, visibility, and experience.

A crew, not just coworkers: Dratanauts consistently describe a "come as you are" culture with sharp, curious people—the kind of team that makes hard problems genuinely fun to solve. See what they say here and follow us on LinkedIn for company news, employee stories, and career updates.

Job Summary:

The Staff Software Engineer, Monetization Platform serves as a technical leader with a primary focus on the systems that turn product usage, subscriptions, credits, commitments, and contracts into accurate customer outcomes and clean financial operations.

This person will architect and evolve the core billing domain for Drata: usage event ingestion, billable metrics, pricing and packaging, invoice generation, entitlement enforcement, and the integrations that connect engineering to Accounting, Finance, RevOps, Salesforce, CPQ, and ERP systems like NetSuite.

They should be equally comfortable designing event-driven systems, shaping commercial flexibility with business stakeholders, and building operationally trustworthy software where correctness, audit-ability, and scale matter. Modern billing is no longer just “charge a credit card once a month” — it is a real-time product control plane that must support evolving pricing models without turning the codebase into a fragile mess.

What you’ll do:

Partner with Product, Finance, Accounting, RevOps, and Engineering leadership to shape Drata’s long-term billing architecture and commercial flexibility across self-serve and enterprise motions.

Design the primitives of a modern billing platform: usage events, billable metrics, products, rate cards, contracts, credits, subscriptions, overages, and invoice workflows.

Architect a system that can accurately meter product usage at scale, transform raw events into billable quantities, and support pricing changes without requiring constant product rework.

Build and evolve the entitlement layer that separates pricing and packaging from product behavior, so feature access, limits, credits, and plan controls are programmable rather than hardcoded.

Work closely with SFDC admins, CPQ owners, and Finance systems stakeholders to ensure quote-to-cash flows are coherent across CRM, product, billing, ERP, and downstream reporting systems.

Ensure billing systems are operationally trustworthy: idempotent event handling, strong reconciliation paths, reliable notifications, auditability, and clear observability for engineers and business teams.

Review architecture and code for billing-related projects to ensure correctness, scale, security, and maintainability while empowering teams to own implementation details.

Troubleshoot the hard problems: invoice discrepancies, usage drift, contract edge cases, entitlement bugs, migration failures, and cross-system data mismatches.

Lead cross-team initiatives such as introducing a usage-based billing foundation, rationalizing packaging models, improving billing developer experience, or migrating from brittle homegrown logic to more composable billing and entitlement systems.

Mentor engineers across teams on domain modeling, distributed systems tradeoffs, financial correctness, and the realities of building software where product behavior and revenue recognition are tightly coupled.

What you’ll bring:

10+ years of experience as a software engineer, including meaningful time owning business-critical backend systems in production.

Deep experience architecting billing, payments, pricing, or quote-to-cash systems for a B2B SaaS company at meaningful scale.