Cursor

Software Engineer, Billing

Rol remoto de Teams con fit claro de ubicación del candidato.

Publicado12 mar 2026

Países elegibles2 países aceptados

Señal de seniorityNivel abierto

Modelo de trabajoRemoto

Ubicaciones aceptadas para candidatos

AustraliaEstados Unidos

Resumen del rol

Software Engineer, Billing

Requisitos y responsabilidades

Contenido del rol extraído en secciones para revisar más rápido.

What you’ll do

Implement usage and billing systems changes end-to-end, from updates in the UI and raw usage events at the edge to invoiced amounts in Stripe, including the metering pipeline, aggregation logic, entitlement enforcement, and ledger.
Evolve our ledger system that serves as the source of truth for customer balances, credits, overages, and adjustments — with the correctness guarantees that financial systems require.
Integrate deeply with Stripe including subscriptions, usage records, invoices, webhooks, and edge cases like mid-cycle plan changes, prorations, and failed payment recovery.
Build billing APIs and internal tooling that product, finance, and customer success teams depend on to query customer state, issue credits, and investigate billing anomalies.
Improve observability across the billing pipeline — metering lag, reconciliation discrepancies, invoice accuracy — so the team can quickly detect and debug billing regressions.
Partner with product, infrastructure, and finance teams to ship new pricing models with confidence and minimal operational risk.
You will own usage & limits across the product family, payments (stripe + daily jobs), grants & promotions, ledger, and internal data insights. You will be a technical authority on billing correctness and scale.
You will not own tax compliance, or general finance infrastructure unless it intersects directly with the billing system.
You will not be a backend generalist who contributes to billing occasionally. This is the core of your scope.
Revenue accuracy is part of the job, but the goal is to build systems with enough correctness and observability that billing is boring — not to manually reconcile every edge case.

You may be a fit if

You’ve shipped a usage-based billing system in production and have opinions on metering architecture, idempotency, and exactly-once semantics.
You’ve integrated deeply with Stripe, understand its data model, and have dealt with erroring webhooks.
You’ve built or maintained a financial ledger and understand why it’s required.
You care about correctness and making sure customer’s don’t have to manually review their invoices.
You can hold the tension between "move fast" and "do not lose revenue or trust."
You feel comfortable shipping features end-to-end - scaling up infrastructure to tweaking a UI component.

Roles similares