stripe
Software Engineer, Backend
About this role
Stripe seeks an experienced backend engineer to develop scalable financial infrastructure systems. You'll optimize APIs, build data processing tools, and implement logging systems while collaborating across teams to enhance platform reliability and performance.
What you'll do
- Develop scalable backend systems managing large data volumes aligned with business objectives
- Improve backend performance by integrating frameworks, refactoring APIs, and optimizing databases
- Design tools to ingest and process signals from various sources for partner teams
- Build logging and data visualization systems for backend APIs
- Diagnose and resolve production issues from testing and customer reports
- Implement automated testing suites and CI/CD pipelines to streamline deployment
What they're looking for
- Java, C++, Python, or Ruby
- Scalable systems design and implementation
- RESTful microservices architecture
- Distributed systems
- Production debugging across service layers
- Database optimization
- CI/CD pipelines and automation
- Business requirements translation to technical design
Benefits
- Equity and company bonus opportunities
- 401(k) plan
- Medical, dental, and vision coverage
- Wellness stipends
- 50% telecommuting permitted
- Multiple positions available
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
Likely interview questions
- Describe your experience designing and scaling microservices in a high-transaction environment like payments processing.
- Walk us through how you've debugged a critical production issue affecting multiple services and what you learned.