Software Engineer, Monetization Platform

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, Rev Ops, Salesforce, CPQ, and ERP systems like Net Suite.

They should be equally comfortable designing event‑driven systems, shaping commercial flexibility with business stakeholders, and building operationally trustworthy software where correctness, auditability, 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.

• Partner with Product, Finance, Accounting, Rev Ops, 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 home‑grown 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.

• 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, Rev Ops, and GTM systems where data quality, auditability, and timing matter.
• Strong experience integrating with systems like Salesforce, CPQ, Net Suite, payment platforms, and downstream finance/reporting tooling.
• Strong proficiency with:
• JavaScript/Type Script 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…