Own the double-entry accounting ledger and lead systems for licensing and revenue recognition at Verkada.
Posted by employer 2 days ago
First seen on Joblaze 1 day ago
Last verified on the company career page 1 day ago
Joblaze summary
The Staff Backend Engineer for Verkada's Licensing & Revenue Platform is responsible for managing a double-entry accounting ledger that ensures accurate revenue recognition from licenses. This role requires expertise in financial systems, particularly in areas like billing and revenue recognition, with a strong emphasis on correctness and durability. Ideal candidates will have over eight years of backend development experience, particularly in financial contexts, and should be comfortable collaborating with finance and accounting teams. The position is part of a small, autonomous team that values direct feedback and high standards in execution.
Quick facts
- Is the Staff Backend Engineer - Licensing & Revenue Platform role remote?
- No — this is an on-site role in San Mateo, CA, United States.
- What's the salary range?
- Verkada lists $150,000–$300,000 for this role.
- How much experience is required?
- At least 8 years of relevant experience for this Staff Backend Engineer - Licensing & Revenue Platform role.
- Where is the role based?
- Verkada is hiring for this position in San Mateo, CA, United States.
- What's the tech stack?
- Joblaze extracted these technologies from the posting: Go, Python.
- Does Verkada sponsor work visas for this role?
- Yes — the posting indicates visa sponsorship is available for the right candidate.
- What seniority level is this role?
- Verkada targets staff-level candidates for this position.
- Is this full-time or contract?
- Full-time for this Staff Backend Engineer - Licensing & Revenue Platform role at Verkada.
From the original posting
Who We Are
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).
US Employee Benefits
- Healthcare programs that can be tailored to meet the personal health and financial well-being needs - Premiums are 100% covered for the employee under at least one plan and 80% for family premiums under all plans
- Nationwide medical, vision and dental coverage
- Health Saving Account (HSA) with annual employer contributions and Flexible Spending Account (FSA) with tax saving options
- Expanded mental health support
- Paid parental leave policy & fertility benefits
- Time off to relax and recharge through our paid holidays, firmwide extended holidays, flexible PTO and personal sick time
- Professional development stipend
- Wellness/fitness benefits
- Healthy lunches provided daily
- Commuter benefits
Additional Information
- This role requires U.S. citizenship or permanent residency for FedRAMP compliance, and onsite presence five days per week.
- We want to build an inclusive team. Research consistently shows that candidates from underrepresented groups apply less often than is warranted — if this opportunity is a positive challenge for your career, please apply.
- Verkada sponsors for many other engineering roles — see open positions at https://www.verkada.com/careers/
Estimated Annual Pay Range
$150,000—$300,000 USD
Verkada Is An Equal Opportunity Employer
Standard company text repeated across Verkada's postings is omitted here.