Stripe Experienced SWE OA and Onsite Questions: 3 Experiences
- Company
- Stripe
- Reports
- 3 interview reports
- Level
- Full-time
- Stages
- OA → Onsite
Stripe experienced SWE reports from November 2026: two OA candidates drew the same request routing question, and one onsite had four rounds.
At a glance
- Process: an online assessment (OA) built around a routing question; report 01 gives HackerRank, 60 minutes and three parts. The onsite in report 02 had four rounds: AI coding, integration, debugging and a hiring manager talk.
- Asked recently: Request Routing System in both OA reports (01, 03); a rule parser written with AI help, the Bikemap integration, a Python bug fix and project questions at the onsite (02).
- Difficulty: all three candidates rated the difficulty average. Both OA candidates said the question itself wasn't hard (01, 03); report 01 found 60 minutes tight and the JavaScript setup confusing.
- Practise first: Request Routing System, Complete a Bikemap Route and JSON Integration, Parse Boolean Rule Expressions
Coverage: Three experienced candidates changing jobs, all for full-time general software engineering roles. The reports went up on November 18 and 19, 2026, and all three list October to December 2026 as the interview period. Two cover the OA (01, 03) and one the onsite (02). None reports a final result.
What came up
The two OA candidates wrote up separately and drew the same routing question (reports 01 and 03). At the onsite, each of the four rounds tested something different.
| Topic | Reports | Last seen |
|---|---|---|
| Request routing | 2 of 3 | Nov 2026 (report date) |
| AI-assisted coding: a rule parser | 1 of 3 | Nov 2026 (report date) |
| API integration and drawing a route | 1 of 3 | Nov 2026 (report date) |
| Debugging a Python project | 1 of 3 | Nov 2026 (report date) |
| Behavioral: past projects, leading, teamwork | 1 of 3 | Nov 2026 (report date) |
Questions we found
Algorithms / Data Structures
| Question | Reports | Last seen |
|---|---|---|
| Request Routing System | 2 | Nov 2026 (report date) |
AI Coding
| Question | Reports | Last seen |
|---|---|---|
| A rule parser, written and tested with AI help (practice) | 1 | Nov 2026 (report date) |
Project Coding
| Question | Reports | Last seen |
|---|---|---|
| Bikemap: ride data, a map API and a drawn route (practice) | 1 | Nov 2026 (report date) |
Behavioral (BQ)
| Question | Reports | Last seen |
|---|---|---|
| A project you worked on, your part and its impact | 1 | Nov 2026 (report date) |
| A project you led | 1 | Nov 2026 (report date) |
| Working closely with other people to get a project done | 1 | Nov 2026 (report date) |
3 detailed candidate timelines, loops, and screens
01: HackerRank OA in JavaScript, three parts in 60 minutes
Report date: November 19, 2026 · Interview period: 2026 Q4 · Role: Software engineer, changing jobs · Degree listed: Master's · Channel: Applied online · Candidate's rating: Negative experience, average difficulty · Result: Not stated (marked as other)
OA (HackerRank, 60 minutes)
- Before the test started, HackerRank asked for the candidate's years of work experience. The candidate wonders whether that number is used to pick questions of different difficulty.
- The question was the routing system one. FastPrep's practice version is Request Routing System. The candidate didn't think the problem was hard, but the time pressure was real: three parts in 60 minutes.
- The candidate wrote in JavaScript, and how results should be printed wasn't made clear up front. By trying things, the candidate found that each operation's result had to go out through
process.stdout.write, one line per operation with a newline at the end. Used to LeetCode, the candidate had never seen this before. - The worst part was a long stretch stuck at 13 of 20 test cases. ES6 syntax turned out not to work there; the spread operator (
...) couldn't be used. The tests were hidden, so the only way to find out was to write test cases by hand during the test.
Result
The candidate marked the result as "other" and gave no detail.
02: Four-round onsite, from AI coding to the hiring manager
Report date: November 19, 2026 · Interview period: 2026 Q4 · Role: Software engineer, changing jobs · Degree listed: Master's · Channel: Referral · Candidate's rating: Positive experience, average difficulty · Result: Waiting
The candidate lists four onsite rounds.
- AI coding. Build a rule parser, using AI to help write and test the code. The candidate doesn't describe the rules or the operators. Once the code was done, the interviewer asked how the candidate judges code the AI produced, and what would have to change to add a new operator later. FastPrep's closest practice is Parse Boolean Rule Expressions.
- Integration: Bikemap. The candidate got ride data and API documentation. The task was to read the coordinates, call a map API and then draw the route. It came in several parts. The early parts went fine; drawing the route took a lot of time spent in the docs and checking the output. The candidate found it nothing like a LeetCode problem; what mattered was reading the requirements carefully and calling the API correctly. Practice it with Complete a Bikemap Route and JSON Integration.
- Debugging. A ready-made Python project with a few failing tests. The job was to find the code behind the failures and fix it. Reading the code took a while, and after the fix the candidate had to walk the interviewer through what changed. The report doesn't name the project, the library or the bug. FastPrep has several Stripe debugging projects, so this round can't be matched to one of them and stays unlinked.
- Behavioral, with the hiring manager. What the candidate did on a project and the impact it had (practice), then experience leading a project and working with other people.
Result
Still waiting to hear back.
03: OA with a proximity routing class
Report date: November 18, 2026 · Interview period: 2026 Q4 · Role: Software engineer, changing jobs · Degree listed: Bachelor's · Channel: Applied online · Candidate's rating: Positive experience, average difficulty · Result: Not stated (marked as other)
The candidate calls this round an OA, while the stage field they picked says video interview.
- The question was the one the candidate calls proximity request routing. It felt like object-oriented coding: write a class and its functions.
- The work was mostly one Router class, split into three parts, with about four different commands in all. The router computes the distance to each data center and returns the nearest one that is healthy and still has capacity. FastPrep's practice version is Request Routing System.
- The candidate found it not hard. In their view, being comfortable with parsing strings, sorting and plugging numbers into a math formula should be enough.
Result
The candidate marked the result as "other" and gave no detail.
Patterns across the reports
- Same OA question, in parts. Two independent OA reports drew the routing question, and both describe it in three parts (01, 03). Report 03 adds the Router class and about four commands; report 01 adds the 60-minute limit and the hidden tests.
Common questions
What is on the Stripe experienced SWE OA?
Both OA reports got the request routing question, in three parts (reports 01 and 03).
How long is the Stripe OA on HackerRank?
Sixty minutes for three parts, in the one report that gives a length (01).
Does the Stripe HackerRank OA support modern JavaScript?
Not fully, in report 01: the spread operator didn't work, and output had to be printed with process.stdout.write, one line per operation.
What rounds are in the Stripe onsite for experienced engineers?
Four in report 02: AI coding, an integration task, a Python debugging task and a behavioral talk with the hiring manager.
What does the Stripe AI coding round ask?
In report 02, a rule parser built with AI help, followed by questions on judging the generated code and adding a new operator.
Other Stripe cohort: the new-grad reports from the same days, a phone screen and an OA, are in Stripe New Grad SWE OA and Phone Screen: 2 Experiences.
Keep practicing
- OA: Request Routing System (reports 01 and 03).
- Onsite: Parse Boolean Rule Expressions and Complete a Bikemap Route and JSON Integration (report 02).
- Behavioral: A project you worked on, your part and its impact, A project you led and Working closely with other people (report 02).
- More Stripe coding questions: the Stripe coding question bank. It needs sign-in.
- More Stripe project rounds: the Stripe project coding bank. It needs sign-in.
- More Stripe behavioral questions: the Stripe behavioral question bank. It needs sign-in.
- Stripe interview page: every Stripe question on one Stripe interview page.
- Hiring insights: the Stripe hiring insights page.
- More firsthand reports: browse the Experience feed.
Sources: Anywhere useful interview info can be found.
Comments
0No comments yet — be the first to share what you know.