Skip to main content

stripe

Backend Engineer, Developer & End-user Experience Platform

SEA, SFmidAdded 2 days ago

About this role

Stripe seeks a Backend Engineer to build and maintain APIs and large-scale systems powering global money movement. You'll design ergonomic platforms for balance management and funds accessibility while collaborating across teams to deliver innovative financial infrastructure solutions.

What you'll do

  • Design, build, and maintain APIs and services handling billions of money movement requests at scale
  • Debug and resolve critical production issues across multiple service layers
  • Mentor and support other engineers in their professional growth
  • Collaborate cross-functionally to build new features while improving engineering standards and tooling
  • Work effectively in a distributed, hybrid team environment with strong communication

What they're looking for

  • Backend API design and development
  • Large-scale distributed systems
  • Production debugging and troubleshooting
  • Cloud infrastructure (AWS, Docker, Kubernetes)
  • gRPC or GraphQL
  • Financial systems experience
  • Cross-functional collaboration
  • Mentorship and technical leadership
Apply on the employer's site

Opens the official application on the employer’s site. No login required.

stripe

Stripe builds payment infrastructure and financial services platforms, offering APIs and tools that enable developers and businesses to process transactions, detect fraud, verify identity, and manage security at scale. The company is hiring Backend Engineers, Full Stack Engineers, ML Engineers, AI Engineers, and Security Engineers to develop core platform systems, payment intelligence, customer support infrastructure, and security data platforms.

Website
stripe.com
View all jobs at stripe

Likely interview questions

  • Walk us through your experience designing APIs that handle high transaction volumes. How did you ensure reliability and efficiency?
  • Tell us about a time you debugged a critical production issue affecting multiple services. What was your approach?