Stripe is hiring a Backend/API Engineer, Money as a Service in Tech — United Kingdom. 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 Organization
Company context from the listing:
Money as a Service (MaaS) oversees a diverse portfolio of Stripe's core platforms and services. Our Stripe Treasury suite helps users manage and move their funds with ease, providing the robust financial infrastructure and tools they need to power their businesses on a global scale.
Team Matching: exact team matching for one of the subteams within this org will begin during final stages. Please note we may also consider you for different orgs based on your experience, location, etc.
What you’ll do
Day-to-day scope for the Backend/API Engineer, Money as a Service as described in the posting:
We’re looking for Backend Engineers who want to make an impact on managing money at a global scale with a passion for building ergonomic APIs. You’ll play a key role in extending our foundational Money Management APIs and services powering our Treasury products globally.
Responsibilities
Day-to-day scope for the Backend/API Engineer, Money as a Service as described in the posting:
- Scope, design, build, and maintain APIs, services, and large-scale systems that reliably and efficiently handle billions of money movement requests
- Debug and solve critical production issues across services and multiple levels of the stack
- Mentor engineers to help them grow
- Collaborate with stakeholders across the company to build new features at large-scale, while improving internal engineering standards, tooling, and processes
- Collaborate effectively in a distributed and hybrid team, maintaining open communication and strong connections with colleagues
Who you are
Experience and skills the team lists as required:
The listing frames the Backend/API Engineer, Money as a Service 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 industry software engineering experience (does not include internships nor includes co-ops)
- Strong coding skills in any programming language (we understand new languages can be learned on the job so our interview process is language agnostic)
- Strong collaboration skills, can work across workstreams within your team and contribute to your peers’ success
- Have the ability to thrive on a high level of autonomy, responsibility, and think of yourself as entrepreneurial
- Interest in working as a generalist across varying technologies and stacks to solve problems and delight both internal and external users
Preferred Qualifications
Experience and skills the team lists as required:
- Experience with large-scale financial tracking systems
- Good understanding and practical knowledge in cloud based services (e.g. gRPC, GraphQL, Docker/Kubernetes, cloud services such as AWS, etc.)
Build a standout application
For the Backend/API Engineer, Money as a Service 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.