Staff Software Engineer, Monetization Platform

Drata • San Francisco, CA

19h • $200,000 - $271,500 • Hybrid

About The Position

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.

Requirements

• 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, and end-to-end tests, Logging, telemetry, and 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.

Nice To Haves

• Usage-based billing platforms such as Metronome, especially concepts like usage events, billable metrics, products, rate cards, contracts, credits, and programmable invoice workflows.
• Entitlement and monetization platforms such as Stigg, especially entitlements as a system of record for feature access, limits, credits, and 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
• Architected or modernized a billing system that had to support real usage metering, invoice correctness, and flexible commercial models rather than a single static subscription plan.
• Built systems where raw product activity was transformed into durable billing inputs and surfaced in 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 for different customer segments.
• Partnered directly with Finance, Accounting, and RevOps to close gaps between what the product did, what the customer bought, and what the company invoiced.
• Led engineers through ambiguous, cross-functional initiatives where the right answer required balancing correctness, flexibility, speed, and operational simplicity.
• Communicated complex architectural decisions clearly to both technical and non-technical stakeholders.
• Balanced individual contributor depth with mentoring and unblocking other engineers.

Responsibilities

• 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.

Benefits

• Stock equity
• Up to 100% employer-paid premiums for medical, dental, and vision coverage for employees and their dependents
• Comprehensive wellness benefits and healthcare concierge services
• 401(k) plan
• Company-paid life and disability insurance
• Tax-advantaged spending accounts
• Discounted voluntary offerings
• Paid Parental Leave policy
• Kindbody fertility and family-building benefits
• Dedicated leave specialists
• Generous annual stipends for both professional and personal development
• Access to a wide range of internal learning opportunities
• Flexible vacation policy
• Paid holidays

What This Job Offers

• Job Type: Full-time
• Career Level: Senior
• Education Level: No Education Listed