Stripe is hiring a Backend / API Engineer, Metronome (Billing) in 9014 Metronome - R&D — Toronto, Canada. The overview below is synthesized from the employer posting on stripe.com: factual requirements and scope are preserved, but prose is rewritten with editorial context. Verify details and apply via the employer link.
Who we are
About Stripe
Company context from the listing:
Stripe is a financial infrastructure platform for businesses. Millions of companies—from the world's largest enterprises to the most ambitious startups—use Stripe to accept payments, grow their revenue, and accelerate new business opportunities.
About the team
Company context from the listing:
The Revenue and Financial Automation (RFA) team at Stripe is building a modern, revenue-focused, financial management platform for fast-growing, digital-native companies.
Hundreds of thousands of businesses of all sizes and types use Stripe Billing to collect revenue for recurring and one-time payments across a variety of different pricing models—from selling SaaS subscriptions, to orchestrating multi-stage contracts, delivering Usage-Based Billing, and providing recovery and retention tools to prevent customer churn.
What you'll do
Day-to-day scope for the Backend / API Engineer, Metronome (Billing) as described in the posting:
As an engineer on the team, you'll be responsible for shaping and building a suite of products that let our users model and operate their business more efficiently. You'll work on projects that span technologies, systems, and processes where you'll design, build, test, and ship code every day.
Responsibilities
Day-to-day scope for the Backend / API Engineer, Metronome (Billing) as described in the posting:
- Design the next generation of Stripe products to meet the high-growth needs of our company and customers for years to come
- Deliver value through a strong collaborative, user-first approach with stakeholders and customers
- Mentor engineers to help them grow
- Debug and solve critical production issues across services and multiple levels of the stack
Who you are
Experience and skills the team lists as required:
The listing frames the Backend / API Engineer, Metronome (Billing) at Stripe as a hands-on product role. If you meet these requirements, you are encouraged to apply. The preferred qualifications are a bonus, not a requirement.
Minimum requirements
Experience and skills the team lists as required:
- 2–12+ years of experience in backend software development
- Ability to write high-quality code (in programming languages like Go, Java, C/C++, etc.)
- Hands-on experience contributing to or building large-scale distributed systems
- Strong collaboration skills, with the ability to work across work streams within your team and contribute to your peers' success
- Ability to thrive with a high level of autonomy and responsibility, with an entrepreneurial mindset
Preferred qualifications
Experience and skills the team lists as required:
- Familiarity with event-driven architectures
- Experience with subscription management, usage-based billing, or financial reporting systems
- Interest in financial infrastructure and how businesses manage their revenue operations
- Direct leadership and mentorship experience
Build a standout application
For the Backend / API Engineer, Metronome (Billing) at Stripe, reviewers look for concise evidence over buzzwords. Mirror the language of the posting sparingly, quantify support or delivery outcomes, and show how you handled ambiguity, time-zone collaboration and user empathy. Keep your resume to impact, keep your cover note to one page, and link to artifacts — tickets resolved, docs shipped, dashboards owned — that prove you can operate in a fast-moving Web3 team. Prepare to discuss a time you turned a confusing user report into a clear fix and how you measure quality in support and operations.
Web3 hiring values reliability: on-time follow-through, clear writing, and a track record of improving runbooks and tooling. Treat the application as a work sample. For interviews, be ready to walk through how you prioritize across time zones, handle a difficult user, and decide when to escalate versus resolve directly. Show how you document decisions so the next teammate benefits.
In a distributed Web3 org, trust builds through written clarity. Use the cover note to demonstrate it.