> Markdown version of [/jobs/ext/4512062-platform-engineer-billing-systems](https://www.wearedevelopers.com/jobs/ext/4512062-platform-engineer-billing-systems). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Platform Engineer, Billing Systems

- **Company:** Wispr Flow
- **Location:** San Francisco, CA, United States
- **Contract:** Permanent contract
- **Skills:** Artificial Intelligence, Systems Engineering, Design of User Interfaces, Human-Computer Interaction, Stripe, Front End Software Development
- **Published:** November 2, 2026
- **Apply:** https://www.careerbuilder.com/job-details/platform-engineer-billing-systems-san-francisco-ca--309d5d4b-d7e6-4602-9c45-b3dae2e446f4

## About the Role

Billing, Systems Engineering, Artificial Intelligence (AI), User Interface/Experience (UI/UX), Problem Solving Skills, Testing, Pricing, Product Pricing, Product/Service Launch, Stock Keeping Unit (SKU)

## Description

Wispr serves consumers, teams, and enterprises with varying subscriptions, usage limits, seats, bundles, currencies, and payment methods. You'll own the platform beneath every pricing motion, from its core abstractions to its vendor integrations. You'll make it possible to launch new products and pricing quickly without creating operational complexity or risking customer trust.

What you'll do

 * Own the billing platform across consumer and enterprise motions
 * Reconcile state across Stripe, RevenueCat, Sequence, IAP, and future vendors
 * Build abstractions that support new SKUs, bundles, currencies, usage models, and entitlements
 * Handle the operational realities of proration, credits, true-ups, dunning, and invoicing
 * Create testing and observability that catch divergence before customers do

You may be a fit if

 * You've built billing systems across both consumer and enterprise motions
 * You've migrated live pricing or billing systems without customer or revenue impact
 * You've made architecture decisions in this domain and lived with their consequences
 * You know where billing demands rigor and where the system can remain flexible
 * You work effectively with Product, Growth, GTM, and Finance

Frontend, ML, voice, and experience with our exact vendors are not required.