Skip to main content

stripe

Software Engineer

South San Francisco, CA$156.8k–$235.2kfull-timemidAdded today

About this role

Stripe seeks a Software Engineer to build and maintain financial infrastructure platforms that manage risk while delivering excellent user experiences. You'll transform business challenges into scalable solutions, collaborate across teams, and ensure production systems remain secure and performant.

What you'll do

  • Develop platforms and solutions to minimize financial and regulatory risk
  • Transform business requirements into scalable engineering solutions
  • Partner with engineering, product, policy, legal, operations, and data science teams
  • Diagnose and resolve production issues across services and tech stack layers
  • Enhance engineering standards, improve tooling, and identify emerging risk patterns

What they're looking for

  • Python, Java, or Ruby development
  • Scalable systems design and maintenance
  • Production issue troubleshooting across multiple services
  • SQL and data visualization
  • Business requirements translation to technical designs
  • Cross-functional collaboration
  • Financial or regulatory domain knowledge (preferred)

Benefits

  • Equity
  • Company bonus or sales commissions
  • 401(k) plan
  • Medical, dental, and vision coverage
  • Wellness stipends
  • 50% remote work flexibility
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

  • Describe a time you identified and resolved a production issue that spanned multiple services—how did you approach debugging across the stack?
  • Walk us through how you've translated ambiguous business requirements into clear system designs.