软件工程师,计费
查看雇主原标题
Software Engineer, BillingCursor (Anysphere) · Remote; 澳大利亚
职位信息来自雇主公开的招聘页面。申请前请务必在雇主官网核实详情。
为什么值得关注?
发现指数 50/100,仅依据与该职位一起存储的证据计算。
- 新的雇主官方职位
- 远程职位
分数构成
- 时效性 (随职位发布时间变化)+18
- 雇主官方来源+15
- 远程职位+8
- 稀有职位+1
- 公司来源健康度+8
该职位未包含:已披露薪资、提及签证担保、提及搬迁、未出现在监控的职位板上。
这些理由来自雇主自己的职位描述与我们核实过的来源检查结果。除了已存储的信号之外,我们不做任何推测。
职位描述
机器翻译我们的使命是实现编码自动化。我们旅程的第一步是为专业程序员打造最好的工具,结合富有创造力的研究、设计和工程。我们的组织非常扁平,团队规模小且人才密集。我们尤其喜欢求真、充满热情和富有创造力的人。我们享受热烈的辩论、疯狂的想法和交付代码。
岗位职责
我们正在招聘一名软件工程师,计费方向,来演进支撑 Cursor 如何向数百万开发者和企业团队收费并核对收入的系统。 你将跨计费技术栈工作——用量计量管道、订阅和权益系统、支付集成以及账本层——使计费准确、可扩展且透明。这是一个深度技术型的个人贡献者角色。它不是财务运营角色,也不是一个披着计费帽子的后端通才角色。 • 端到端地实现用量和计费系统变更,从 UI 更新和边缘侧的原始用量事件,到 Stripe 中的开票金额,包括计量管道、聚合逻辑、权益执行和账本。
• 演进我们的账本系统,它作为客户余额、额度、超额用量和调整的真相来源——并具备财务系统所需的正确性保证。
• 与 Stripe 深度集成,包括订阅、用量记录、发票、webhooks,以及诸如周期中计划变更、按比例计费和支付失败恢复等边缘情况。
• 构建计费 API 和内部工具,供产品、财务和客户成功团队依赖,以查询客户状态、发放额度和调查计费异常。
• 改善整个计费管道的可观测性——计量延迟、对账差异、发票准确性——以便团队能够快速检测和调试计费回归。
• 与产品、基础设施和财务团队合作,以信心和最小运营风险交付新的定价模型。
• 你将负责整个产品家族的用量与限制、支付(stripe + 每日任务)、赠予与促销、账本以及内部数据洞察。你将成为计费正确性和规模方面的技术权威。
• 你不会负责税务合规,或一般财务基础设施,除非它与计费系统直接交叉。
• 你不会是一个偶尔为计费做贡献的后端通才。这是你职责范围的核心。
• 收入准确性是工作的一部分,但目标是构建具备足够正确性和可观测性的系统,让计费变得无聊——而不是手动核对每一个边缘情况。
你可能适合,如果 • 你曾在生产环境中交付基于用量的计费系统,并对计量架构、幂等性和精确一次语义有见解。
• 你曾与 Stripe 深度集成,理解其数据模型,并处理过报错的 webhooks。
• 你曾构建或维护财务账本,并理解为什么需要它。
• 你关心正确性,并确保客户不必手动审查他们的发票。
• 你能在“快速行动”和“不要损失收入或信任”之间保持张力。
• 你能自如地端到端交付功能——从扩展基础设施到调整 UI 组件。
#LI-DNI
以上内容由机器翻译自动生成,可能存在错误;投递前请以雇主原文为准。
查看雇主原文
职位描述
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.
岗位职责
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. • 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