Stripe is hiring a Backend Engineer, Payments and Risk in 8582 Optimized Checkout - Eng — US. 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.
Note: if you are an intern, new grad, staff, frontend or fullstack applicant, please do not apply using this link and visit our jobs page for those specific postings.
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:
Payments and Risk
Sub-orgs: Link and OCS, Payments Acceptance, Risk
The Payments organization focuses on developing products and platforms that enable users to accept payments from customers efficiently. This includes building APIs for processing payments, enabling regional, non-card payment options, and extending Stripe's capabilities to make it easy for businesses to accept in-person payments.
Team Matching: Exact team matching for one of the sub-teams 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 Engineer, Payments and Risk as described in the posting:
The listing frames the Backend Engineer, Payments and Risk at Stripe as a hands-on product role. Our team collaborates with many cross-functional teams — from Infrastructure to Product — to deliver innovative solutions that address evolving user needs.
Responsibilities
Day-to-day scope for the Backend Engineer, Payments and Risk as described in the posting:
- 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 Engineer, Payments and Risk 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
- 2+ years of industry software engineering experience (does not include internships or 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
- Ability to thrive with a high degree of autonomy and ownership, with an entrepreneurial mindset
- Interested 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 of cloud-based services (e.g., gRPC, GraphQL, Docker/Kubernetes, AWS, etc.)
Build a standout application
For the Backend Engineer, Payments and Risk 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.