Skip to content
aitrainer.work - AI Training Jobs Platform
Engineering Full-Time
Hercules

Staff Software Engineer, Billing and Monetization (US)

Hercules • San Francisco, CA

Company

Hercules

Annual salary

$200k – $300k/yr

Location

San Francisco, CA

Listed

26d ago

Experience:
2 to 10 years
Workplace:
Hercules is based in San Francisco (Kearny & Bush), and the founding team works in-office. A remote arrangement could be arranged for an exceptional candidate, but it should not be the default.
Equity:
0.01%-0.25%

On-site in San Francisco, CA.

Send us your LinkedIn and CV. If your experience fits, we'll introduce you to the recruiter filling this role.

Apply for a referral →

The recruiter emails you before anything happens and may suggest other jobs that suit you better.

What you'll do

  • Own everything about how Hercules collects money from customers: plans, subscriptions, entitlements, prorations, credits and one-time charges.
  • Design and build the multi-provider payments system. Hercules runs on Stripe today, and you'll add Adyen, PayPal, crypto and local payment methods so customers anywhere can pay in their own currency, while also cutting provider fees.
  • Build and scale usage-based billing for AI credits and Cloud credits, including usage metering, credit drawdown and overage charges, using platforms like Orb or Metronome or a system built in-house.
  • Build Hercules Commerce, the billing and payments features customers use inside their own Hercules apps to charge their customers (similar to Stripe Connect).
  • Make the billing infrastructure fast and reliable at scale, with solid webhook processing, retries and reconciliation as usage and transaction volumes grow. You'll work in TypeScript, Postgres, Redis and Temporal.
  • Work directly with the founders to run pricing and packaging A/B tests, then ship and iterate quickly to grow revenue across hundreds of thousands of users.

What you need

  • We need someone with 4, 10 years of experience as a backend, full-stack or growth engineer on the billing or monetization team of a SaaS or consumer product. You should have integrated at least two payment providers in production, such as Stripe at one company and Adyen or PayPal at another, and built usage-based or credit-based billing on top of subscriptions. You should be comfortable owning a business-critical system end to end at a 7-person startup that moves very fast. You should also have a track record of shipping billing and payments features to real customers and improving them. Bonus points if you've already built a unified multi-provider payments layer, worked with Orb or Metronome, supported international payment methods and currencies, or run pricing experiments.

Common questions

How do I apply for the Staff Software Engineer, Billing and Monetization (US) role at Hercules? +

Use the Apply for a referral button on this page to send us your LinkedIn and CV. If your experience fits, we'll introduce you to the recruiter filling this role. They'll email you to check you're interested, then put you forward for this job or others that suit you better. It's free.

What does this Hercules role pay? +

The listing gives $200k – $300k/yr.

Is this role remote? +

The listing gives the location as San Francisco, CA. Hercules is based in San Francisco (Kearny & Bush), and the founding team works in-office. A remote arrangement could be arranged for an exceptional candidate, but it should not be the default.

Software Engineer interview prep

Questions Software Engineer interviewers often ask. They aren't taken from this listing.

How do you approach designing a system when the requirements are still likely to change?

I design around the parts of the problem I'm confident are stable, like the core data model, and keep the parts most likely to change, like specific business rules, isolated behind clear interfaces. Over-engineering flexibility everywhere just adds complexity to parts of the system that were never going to change.

What's your process for debugging an issue that only reproduces in production, not locally?

I add targeted logging around the suspected area and compare production data or configuration against my local setup, since an issue that's environment-specific usually traces back to a real difference between the two rather than a fundamentally different bug. I avoid making speculative changes without first confirming where the divergence is.

How do you decide when a piece of code needs a test versus when it's low-risk enough to skip?

I prioritize tests for logic with real business consequences if it breaks, or code that's likely to be touched again later by someone unfamiliar with it. Simple, rarely-changed glue code gets less coverage, since the cost of a thorough test there often exceeds the risk it's protecting against.

How do you evaluate a proposed technical solution's trade-offs, like performance versus maintainability?

I start from the actual constraint that matters for this specific system, whether that's genuinely performance-critical or whether maintainability is the bigger long-term cost, rather than defaulting to whichever trade-off I personally prefer. Optimizing for performance the system doesn't need just adds complexity nobody benefits from.

See all 10 Software Engineer interview questions →

Related roles

Hercules

Browse all referral roles

Salaried roles at startups, AI companies and established businesses, all filled by referral. One application covers every role.

See all referral roles →