软件工程师，计费
Software Engineer, Billing
我们的使命是自动化编码。我们旅程的第一步是打造最好的工具，供专业程序员使用，结合创新研究、设计和工程。我们的组织结构非常扁平，团队小而人才密集。我们特别喜欢追求真理、充满热情且富有创造力的人。我们享受激烈的辩论、疯狂的想法以及持续交付代码。
关于该职位
我们正在招聘一名软件工程师（计费方向），以推动支持Cursor对数百万开发者和企业团队进行收费和收入对账的系统。
你将负责计费栈的各个方面——使用计量管道、订阅和权限系统、支付集成以及账本层，使计费准确、可扩展且透明。这是一个高度技术性的个人贡献者角色。这不是财务运营岗位，也不是佩戴计费帽子的后端通用工程师。
你将负责
- 从UI更新和边缘的原始使用事件到Stripe中的发票金额，端到端地实现使用和计费系统的变更，包括计量管道、聚合逻辑、权限执行和账本。
- 持续演进我们的账本系统，该系统是客户余额、信用、超额费用和调整的权威来源——并确保符合财务系统所需的正确性保证。
- 深度集成Stripe，包括订阅、使用记录、发票、Webhook，以及中周期计划变更、按比例计算和支付失败恢复等边缘情况。
- 构建计费API和内部工具，产品、财务和客户成功团队依赖这些工具查询客户状态、发放信用和调查计费异常。
- 提升计费流程的可观测性——计量延迟、对账差异、发票准确性——以便团队能够快速检测和调试计费回归问题。
- 与产品、基础设施和财务团队合作，有信心且风险最小地推出新的定价模型。
- 你将负责产品系列中的使用和限制、支付（Stripe + 日常任务）、拨款和促销、账本以及内部数据洞察。你将成为计费正确性和扩展性的技术权威。
- 你不会负责税务合规，或一般的财务基础设施，除非它们直接与计费系统相关。
- 你不会是一个偶尔参与计费的后端通用工程师。这是你的核心职责范围。
- 收入会计
查看英文原文
Our mission is to automate coding. The first step in our journey is to build the best tool for professional programmers, using a combination of inventive research, design, and engineering. Our organization is very flat, and our team is small and talent dense. We particularly like people who are truth-seeking, passionate, and creative. We enjoy spirited debate, crazy ideas, and shipping code.
ABOUT THE ROLE
We're hiring a Software Engineer, Billing to evolve the systems that power how Cursor charges and reconciles revenue across millions of developers and enterprise teams.
You will work across the billing stack — usage metering pipelines, subscription and entitlement systems, payment integrations, and the ledger layer — to make billing accurate, scalable, and transparent. This is a deeply technical IC role. It is not a finance ops role, and it is not a backend generalist role wearing a billing hat.
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.
#LI-DNI