Staff Backend Engineer - Licensing & Revenue Platform

About the Role

The Core Licensing & Devices team owns the layer that turns Verkada's licenses into revenue: a double-entry accounting ledger that reconciles every license into daily revenue recognition. This is the system Finance closes the books on and the one auditors trace, so every entry has to be right. As Verkada scales past millions of devices and the business matures toward tighter reporting and audit requirements, this system moves from important to load-bearing.

We're a small, high-trust, high-autonomy team. We give and receive feedback directly, we learn out loud, and we hold a high bar on both execution and written communication.

What You'll Do

• Own the double-entry accounting ledger that reconciles licensing into daily revenue recognition — its accounting model, its invariants, and its correctness guarantees under concurrency, retries, and failure.
• Design and lead the systems behind upmarket licensing: pay-as-you-go metering and billing, fixed-term commitments, and the packaging our enterprise customers buy.
• Build reconciliation and controls that let Finance close the books daily and let auditors trace any recognized dollar back to its source — with the auditability, immutability, and lineage a maturing company requires.
• Partner with Finance, Accounting, Revenue, and Product to turn revenue-recognition policy (ASC 606, deferred revenue, contract modifications, true-ups) into precise, testable system behavior.
• Lead major features end-to-end and bring others along — through design reviews, code reviews, crisp written docs, and direct mentorship.
• Drive operational rigor: strong observability, tight SLOs, low pager noise, and blameless learning when incidents occur.
• Help shape the platform's roadmap toward the company's biggest long-term bets as Verkada scales and matures.

What You Bring

• 8+ years building backend services with strong correctness, consistency, and durability guarantees at scale.
• Depth in financial or transactional systems: ledgers, double-entry accounting, billing, payments, or revenue recognition — you understand why idempotency, exactly-once semantics, immutability, and reconciliation matter, and you've built for them.
• Comfort working shoulder-to-shoulder with Finance and Accounting — or a track record of getting deep in an unfamiliar, high-stakes domain fast.
• Fluency in Python or Go; other backend languages can contribute to your experience, but the interviews will be conducted in one of the above.
• A track record of partnering with Finance, Accounting, or other non-engineering stakeholders, translating policy and ambiguity into systems they can rely on without surprise.
• At the Staff level: the ability to set technical direction across teams, shape shared architecture, and raise the bar on how the org designs and operates critical financial systems.
• Bonus: experience preparing financial systems for audit (SOX or external financial audit).