Staff Software Engineer, Monetization Platform

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.
• Strong experience designing APIs and event-driven systems that ingest, validate, aggregate, and reconcile high-volume operational data.
• Strong understanding of modern billing models, including usage-based pricing, subscriptions, prepaid credits, commitments, overages, hybrid packaging, and enterprise-specific commercial terms.
• Experience working directly with Accounting, Finance, RevOps, and GTM systems where data quality, auditability, and timing matter.
• Strong experience integrating with systems like Salesforce, CPQ, NetSuite, payment platforms, and downstream finance/reporting tooling.
• Strong proficiency with JavaScript/TypeScript and object-oriented programming, building and consuming RESTful web services, relational databases, data modeling, and transactional workflows, distributed systems and asynchronous processing, writing unit/integration/end-to-end tests, logging/telemetry/production debugging, Git and modern CI/CD practices, at least one major cloud platform and modern infrastructure tooling.
• A strong product and systems mindset: you can model the commercial domain cleanly, but you also know billing architecture is ultimately customer experience architecture.

Bonus Qualifications

• Usage-based billing platforms such as Metronome (usage events, billable metrics, products, rate cards, contracts, credits, programmable invoice workflows).
• Entitlement and monetization platforms such as Stigg (entitlements as a system of record for feature access, limits, credits, packaging logic).
• Building systems that support both PLG/self-serve and enterprise sales motions on the same technical foundation.
• Audit logs, RBAC, webhooks, durable queues, and other patterns that make billing and monetization systems reliable and debuggable in production.
• AI-assisted development tools.
• Success architecting or modernizing a billing system supporting real usage metering, invoice correctness, and flexible commercial models.
• Built systems transforming raw product activity into durable billing inputs for customer-facing or internal financial workflows.
• Worked through pricing and packaging changes without repeatedly hardcoding logic into application code.
• Supported models like prepaid credits, subscriptions with overage, enterprise commitments, or hybrid contracts.
• Partnered directly with Finance, Accounting, and RevOps to close gaps between product behavior and financial outcomes.