Overview
Stripe's loop is less about algorithm puzzles and more about practical engineering. Besides coding and system design, people report a bug squash round where you fix failing tests in an unfamiliar repo, and an integration round where you build something using an API or library you haven't seen before.
System design questions that candidates report include webhooks, feature flags, rate limiting and metrics or analytics pipelines. Stripe cares a lot about API design, data modeling and what happens when things fail. Recent loops also include an AI programming round where you work with a built-in AI assistant.
Below is what people get asked in each one and what to study.
System design interviews
Questions lean toward infrastructure Stripe runs for itself and its merchants, like webhooks, feature flags, rate limiting and metrics. Expect to get specific about API design, data models and failure handling.
What people get asked
- Build a feature flag platform
- Deliver webhooks to merchants
- Aggregate metrics and analytics events
- Design an API rate limiter
Coding interviews
Coding is practical: multi-part problems that keep adding requirements, plus rounds for debugging, working with an unfamiliar API, and coding with an AI assistant.
What people get asked
- Check transactions against rules
- Convert between currencies
- Build a rate limiter
- Calculate shipping costs
The rest of the process
Your recruiter will walk you through this, but here's the quick version.
| Stage | Length | What happens |
|---|---|---|
| Recruiter screen | 30 min | Your background and the role |
| Technical screen | About 60 min | Usually one practical coding problem in several parts, on HackerRank or a shared editor |
| Coding | About 60 min | A multi-part practical problem, with an eye on tests |
| AI programming | About 60 min | A multi-part problem solved with the platform's built-in AI assistant, while you check what it writes |
| Bug squash | About 60 min | A GitHub repo you've never seen, with failing tests to fix |
| Integration | About 60 min | Build to a set of requirements using an unfamiliar API or library and its docs |
| System design and experience & goals | 2 rounds | A design question, and a manager chat about your background, a hard project, your goals and how you use AI tools |
Sources
We pulled this together from candidates' own write-ups of their interviews. They don't always agree, and things change over time.
- Blind: Stripe SWE L3 loop with AI programming round
- Blind: Bug squash and integration thread with a Stripe interviewer (2022)
- Jointaro: Staff SWE Toronto, webhook design (2023)
- Jointaro: SWE Bengaluru, currency conversion (2025)
- Jointaro: SWE Berlin, rate limiter design (2024)
- Jointaro: SWE San Francisco full loop (2025)
- 1point3acres: Onsite with email subscription, bug fix, reconciliation
Practice Loop is an independent practice tool and isn't affiliated with or endorsed by Stripe.