What Billing Engineers Actually Build
Billing engineering spans from subscriptions to revenue operations.
Subscription Management
Recurring revenue systems:
- Plan management — Pricing tiers and features
- Subscription lifecycle — Create, upgrade, downgrade, cancel
- Proration — Mid-cycle changes
- Trials — Free trial logic
- Discounts — Coupons, promotions
Invoicing and Payments
Billing customers:
- Invoice generation — Monthly/annual billing cycles
- Tax calculation — Sales tax, VAT, GST
- Payment processing — Integration with gateways
- Dunning — Failed payment recovery
- Credits and refunds — Customer adjustments
Revenue Operations
Financial accuracy:
- Revenue recognition — ASC 606 compliance
- Metered billing — Usage-based pricing
- Reporting — MRR, ARR, churn metrics
- Reconciliation — Matching transactions
- Audit trails — Financial compliance
Billing Technology Stack
Platforms
| Platform | Use Case |
|---|---|
| Stripe Billing | Integrated with Stripe |
| Chargebee | Subscription management |
| Recurly | Subscription billing |
| Zuora | Enterprise billing |
| Custom | Unique requirements |
Key Integrations
- Payment gateways: Stripe, Braintree, Adyen
- Tax: Avalara, TaxJar
- Accounting: QuickBooks, Xero
- CRM: Salesforce, HubSpot
Skills by Experience Level
Junior Billing Engineer (0-2 years)
Capabilities:
- Implement billing features
- Generate invoices
- Handle basic subscription logic
- Support billing queries
- Fix billing bugs
Learning areas:
- Complex proration
- Tax compliance
- Revenue recognition
- System design
Mid-Level Billing Engineer (2-5 years)
Capabilities:
- Design billing systems
- Implement complex scenarios
- Handle tax calculation
- Build reporting systems
- Work with finance team
- Mentor juniors
Growing toward:
- Architecture decisions
- Revenue strategy
- Technical leadership
Senior Billing Engineer (5+ years)
Capabilities:
- Architect billing platforms
- Lead revenue systems
- Handle compliance requirements
- Design scalable billing
- Drive billing strategy
- Mentor teams
Curiosity & fundamentals
Independence & ownership
Architecture & leadership
Strategy & org impact
Interview Focus Areas
Technical Skills
- "How do you handle proration for mid-cycle upgrades?"
- "Explain subscription lifecycle states"
- "How do you calculate and handle taxes?"
- "Design a usage-based billing system"
Business Logic
- "What happens when a payment fails?"
- "How do you handle refunds and credits?"
- "Explain dunning and retry strategies"
Edge Cases
- "A customer upgrades mid-cycle, then cancels. Walk me through the billing."
- "How do you handle currency conversion?"
- "What happens during a subscription with partial months?"
Common Hiring Mistakes
Underestimating Complexity
Billing looks simple until you encounter proration, failed payments, mid-cycle changes, tax edge cases. Engineers who haven't dealt with this complexity struggle.
Ignoring Edge Cases
Billing edge cases are where money is lost or gained incorrectly. Look for engineers who think carefully about corner cases.
Missing Finance Understanding
Billing engineers work with finance teams. Understanding revenue recognition, MRR calculations, and financial reporting helps.
Hiring Pure Backend Engineers
Generic backend skills aren't enough. Billing-specific domain knowledge accelerates impact significantly.
Where to Find Billing Engineers
High-Signal Sources
Billing engineers typically come from SaaS companies with significant billing complexity or billing infrastructure vendors. Stripe (Billing team), Chargebee, Zuora, and Recurly alumni have direct expertise. Also look at high-growth SaaS companies (Salesforce, HubSpot, Atlassian) that have built sophisticated billing systems.
Conference and Community
SaaStr conferences attract revenue operations professionals, including billing engineers. Subscription industry events (Subscribed by Zuora) surface practitioners. Finance and accounting software communities may have billing engineer involvement.
Company Backgrounds That Translate
- Billing platforms: Stripe Billing, Chargebee, Zuora, Recurly—direct expertise
- High-growth SaaS: Salesforce, HubSpot, Atlassian—complex billing needs
- Marketplaces: Airbnb, Uber—multi-party billing (host payouts, driver earnings)
- Usage-based companies: AWS, Snowflake, Datadog—metered billing expertise
- Fintech: Companies with complex pricing and financial operations
Domain Knowledge
Unlike many engineering roles, billing benefits significantly from domain knowledge. Engineers who understand accounting basics (revenue recognition, deferred revenue) and SaaS metrics (MRR, churn) accelerate faster.
Recruiter's Cheat Sheet
Resume Green Flags
- Subscription billing experience
- SaaS billing ownership
- Proration/dunning implementation
- Tax handling experience
- Financial system integration
Resume Yellow Flags
- No billing-specific experience
- Only payment processing
- Cannot discuss edge cases
- No SaaS background
Technical Terms to Know
| Term | What It Means |
|---|---|
| MRR | Monthly Recurring Revenue |
| ARR | Annual Recurring Revenue |
| Proration | Adjusting for partial periods |
| Dunning | Failed payment recovery |
| Churn | Customer cancellations |
| ASC 606 | Revenue recognition standard |