Stripe OA: What It Tests (2026)
- Company
- Stripe
- Level
- Internship
- Stages
- OA
Stripe's online assessment is a coding task split into parts. Nine of 79 reports from 2017 to 2026 give 60 minutes, and 39 problems are listed.
At a glance
- Process: The OA comes right after the application. For interns it is followed by a team screen (16 of the 41 intern accounts from 2025 on that go beyond an application update), then an onsite with coding and integration rounds, then a manager chat. Two reports name HackerRank, a timed coding site, and 27 of 39 problem pages list it. Nine reports give 60 minutes. Details are under OA format and timing below.
- Tests: Of 17 software reports from 2023 on that describe the task, 12 describe a task split into parts (5 of those say the later parts build on the earlier ones), 6 describe commands that change balances or payment state, and 5 describe parsing text or logs. The table under What the OA tests has the counts.
- Difficulty: Scores vary a lot. Two candidates finished with 13 of 13 tests and one called it light on algorithm puzzles. Another passed 11 of 16 and did not move on. FastPrep rates 22 of the 39 problems medium, 9 easy and 7 hard.
- Practise first: Request Routing System (25 sightings), Subscription and Usage-Based Billing Calculator (24) and Deployment Window Scheduler (23).
Coverage: 79 candidate reports from 2017 to Oct 2026 (74 describe the OA or later stages, 5 are application updates only). By period: 47 from 2025 to 2026, 15 from 2023 to 2024, 17 earlier. Seventy-two are software engineering interns, 6 are machine learning engineering interns (3 of them PhD applicants) and 1 is an experienced software engineer. Places named in OA reports: Toronto, Dublin, Bengaluru, Bucharest, Cluj-Napoca, New York and San Francisco. Each candidate is counted once. The 39 OA problems carry 238 dated sightings between Oct 2018 and Nov 2026.
What the OA tests
Most task reports read like small business simulations, not puzzles. You get one story, such as invoices, disputes or fraud rules, and the task grows over several parts. A stateful task keeps a running record, such as account balances, and updates it as each command arrives.
Seventeen software reports from 2023 on describe the task or its parts. Three more describe the OA only in a few words (maps, filesystem work, light on algorithms) and are not in the 17. The rest say only that an OA happened. A report can count in more than one row.
| Topic | Reports (of 17) | Last seen |
|---|---|---|
| Task split into several parts | 12 (5 say later parts build on earlier ones) | Sep 2026 |
| Commands that change balances or payment state | 6 | Nov 2025 |
| Parsing strings, logs and CSV rows | 5 | Autumn 2025 |
| Building and printing a tree | 1 | Mar 2026 |
The problem pages point the same way. Across the 39 problems, 29 carry the hash table tag, 28 simulation, 11 sorting and 10 parsing. Five carry intervals, 4 graph and 1 tree. Harder algorithm topics are rare.
Two other kinds of OA are covered below: one PhD machine learning report with four timed sections, and one experienced-hire report with a single sliding-window question.
OA format and timing
Platform
Two reports name HackerRank: an intern fraud-rules OA (Nov 2025) and the experienced-hire OA (Nov 2026). On the problem pages, 27 of 39 list HackerRank and 12 list no platform. No report or page names another site.
Length and number of parts
- 60 minutes: nine reports, latest Oct 2026. Places: Toronto (2), San Francisco (2), Dublin, Bengaluru and New York, plus 2 reports that give no place.
- About 90 minutes: two reports, a transaction-system task (Nov 2025) and the PhD machine learning OA (Oct 2025).
- Three parts: three reports from Toronto (Sep 2026), Dublin (Apr 2026) and Bengaluru (late 2025), plus one from 2023. The Bengaluru candidate had to finish them in order.
- Four parts: four reports (Oct 2025, Oct 2024, Sep 2024, Aug 2024).
- One question: one report (Nov 2025), a fraud-rules task with 25 tests.
- A Sep 2026 report calls the OA hard, with parts that depend on each other. It does not give a count.
Regions
Reports from Toronto, Dublin, Bengaluru, New York and San Francisco all give 60 minutes, and no report points to a regional difference. Most places have only one or two reports. Cluj-Napoca has one: a multi-part tree task in Mar 2026 with no length given. Bucharest has a four-part parsing OA from Oct 2024.
Scoring and hidden tests
Reports quote test counts, which suggests scoring by tests passed, but no report says so.
- Counts reported: 13 of 13 (two candidates, Jan 2026), a full 600 of 600 with about five minutes left (Dec 2025), 22 of 25 (Nov 2025), 15 of 19 (Oct 2025), 11 of 16 (Nov 2025) and 7 of 10 (Nov 2024).
- The 11 of 16 candidate saw errors pile up as the parts grew and did not move on.
- Three missed tests (Oct 2024) and still an offer. In 2022, a parsing mistake meant zero passing tests, and a manual review still moved the candidate forward.
The reports show no cutoff. The 7 of 10 candidate advanced, while the 11 of 16 candidate did not. One 2018 report says the candidate failed one hidden test and was rejected the next day.
Timing and what comes next
- Application to OA link: about two months (Nov 2025), 7 weeks (Sep to Nov 2025) and about 17 days (Aug to Sep 2024).
- OA to team screen: 7 days (Dec 2025), 9 days (Apr 2025), 25 days (Feb to Mar 2026) and 30 days (Nov to Dec 2025).
- Replies can be fast or silent. One candidate was rejected two days after the OA (Sep 2024). The two 13 of 13 candidates had heard nothing a few days later (Jan 2026).
- Among the 41 intern accounts from 2025 on that go beyond an application update, 16 describe a team screen after the OA, and two more describe a screen without mentioning the OA. Two reports give the screen as 60 minutes and one says 45. Several describe one problem that gains requirements part by part. Thirteen reports then describe an onsite integration round inside unfamiliar code or an API. The manager chat comes last. The first roundup under Keep practicing has the full loops.
Experienced hires
One report covers an experienced software engineer who was referred for a full-time role. The OA was on HackerRank with one question on sliding windows, rated easy. One test case failed and the candidate was still invited to an HR interview (reported Nov 2026).
No report ties that question to a page. Incident Monitor is the only OA problem tagged sliding window, and it carries full-time and new-grad tags. That makes it the closest match, but this is our inference. Sixteen pages carry a full-time tag.
Machine learning intern OA
One PhD machine learning candidate (Oct 2025) described 90 minutes in four timed sections: applied math (2 questions, 5 minutes), statistics (3 questions, 10 minutes), Python data work (1 question, 25 minutes) and PyTorch (1 question, 50 minutes). Unused time carried forward, but finished sections could not be reopened. No problem page matches this test. The four Card Range Obfuscation pages carry "ML Eng" in their titles, but no report ties them to it.
Every OA problem we have
Each problem page lists dated sightings from candidate reports. The Sightings column counts those dated entries, and Last seen is the newest one. They are not report counts.
Most reported in 2026
| Problem | Sightings | Last seen |
|---|---|---|
| Request Routing System | 25 | Nov 2026 |
| Subscription and Usage-Based Billing Calculator | 24 | Nov 2026 |
| Deployment Window Scheduler | 23 | Nov 2026 |
| Financial Account Ledger | 21 | Nov 2026 |
| Incident Monitor | 18 | Nov 2026 |
| Asynchronous Event Processing | 14 | Nov 2026 |
| WebSocket Load Balancer, Parts 1 to 5 | 13 | Sep 2026 |
| Split Tender Part 4, Refunds | 13 | Nov 2026 |
| Split Tender Part 1, Basic Split Tendering | 12 | Nov 2026 |
| Split Tender Part 2, Expiration Dates | 12 | Nov 2026 |
| Split Tender Part 3, Surcharges | 12 | Nov 2026 |
Financial Account Ledger and Split Tender Part 4 are also tagged phone screen, and WebSocket Load Balancer is also tagged onsite. Most of these are command or record streams that you replay in order. Request Routing System sends requests to datacenters by location, capacity and health. Deployment Window Scheduler works with time windows. WebSocket Load Balancer sends connections to the least-loaded of several targets, adding rules in later parts. Split Tender splits one payment across several payment methods.
Seen a few times or once in 2026
| Problem | Sightings | Last seen |
|---|---|---|
| Merchant Fraud Risk Scoring | 5 | Sep 2026 |
| Chat Billing Calculation | 4 | Nov 2026 |
| Payment Approval and Partial Capture | 1 | Oct 2026 |
| Evolving Merchant Clusters and Persistent Pins | 1 | Sep 2026 |
| Directly Linked Users | 1 | Jun 2026 |
| Fraud Ring Size | 1 | Jun 2026 |
| Risky Fraud Ring | 1 | Jun 2026 |
| Count Valid Bitwise Pairs | 1 | Jun 2026 |
| Conditional Group Aggregation | 1 | May 2026 |
| Email Log Processing, Grouping, and Sorting | 1 | May 2026 |
| Build and Render an Organization Role Tree | 1 | Mar 2026 |
The three fraud-ring pages form one sequence, and all three were sighted on the same day. The one tree report (Cluj-Napoca, Mar 2026) matches the last row. Conditional Group Aggregation is a table query task, not a stream of commands.
2024 and 2025
| Problem | Sightings | Last seen |
|---|---|---|
| For All Intents And Purposes, Part 4 | 4 | Apr 2025 |
| For All Intents And Purposes, Part 1 | 3 | Apr 2025 |
| For All Intents And Purposes, Part 2 | 3 | Apr 2025 |
| For All Intents And Purposes, Part 3 | 3 | Apr 2025 |
| Card Range Obfuscation, Part 1 | 2 | Nov 2024 |
| Card Range Obfuscation, Part 2 | 2 | Nov 2024 |
| Card Range Obfuscation, Part 3 | 2 | Nov 2024 |
| Card Range Obfuscation, Part 4 | 2 | Nov 2024 |
| Parse and Filter Chargeback Disputes | 2 | Sep 2024 |
| Transaction Log Metrics | 1 | Dec 2025 |
| Merchant Fraud Thresholds and Disputes | 1 | Nov 2025 |
| Filter Strings and Extract Payment Details | 1 | Mar 2025 |
| Process List of Commands | 1 | Dec 2024 |
| Process Card Transaction Records | 1 | Oct 2024 |
For All Intents And Purposes is the Payment Intent task: it begins with creating and paying intents and ends with refund time limits. One Sep 2024 report describes it as a four-part OA.
Older reports
| Problem | Sightings | Last seen |
|---|---|---|
| Track Invoice Lifecycle and Outstanding USD Balance | 3 | Nov 2019 |
| Capital Loans, Withholding and Direct Repayment | 1 | Aug 2020 |
| Compute Platform Balance with Optional Destinations | 1 | Oct 2018 |
Four 2019 accounts describe the invoice task, and three accounts describe the loan task (Aug 2020, Sep 2021, Oct 2021), which is more than the dated sightings above. Both are command streams, so this style is not new at Stripe. Some reports name work that has no page here, such as a 2023 bank-commands OA with time-ordered transfers, a 2021 dictionary check, and a Nov 2025 transaction system with no details kept.
Common questions
How long is the Stripe OA?
Nine reports say 60 minutes, the latest from Oct 2026. Two say about 90 minutes: a transaction-system task and the PhD machine learning OA.
Is the Stripe OA on HackerRank?
Two reports name HackerRank (Nov 2025 and Nov 2026), and 27 of 39 problem pages list it. No report names a different site.
What is the Stripe WebSocket load balancer question?
The problem page has five parts. You send connection requests to the least-loaded of several targets and handle connect, disconnect and shutdown events, with extra rules added later. It has 13 sightings, the latest in Sep 2026, and carries intern and new-grad tags. Two reports mention a load balancer: one from Oct 2026 that does not say which round, and one Bucharest screen from Oct 2025 that the candidate did not solve in time. Neither confirms it as OA content.
Do you have to pass every Stripe OA test?
No cutoff shows in the reports. A candidate with 7 of 10 tests advanced, and one with 11 of 16 did not.
What is on the Stripe experienced-hire OA?
One report describes a HackerRank OA with a single sliding-window question, rated easy. The details are under Experienced hires above.
What to practise
- Command and record processing in parts: Request Routing System (25 sightings), Subscription and Usage-Based Billing Calculator (24), Financial Account Ledger (21) and Asynchronous Event Processing (14). Task parts appear in 12 of 17 task reports (5 say they build on each other), latest Sep 2026.
- A full multi-part series in order: the four Split Tender pages (12 or 13 sightings each, Nov 2026), or WebSocket Load Balancer (13, Sep 2026).
- Time windows: Deployment Window Scheduler (23, Nov 2026, rated hard).
- Logs and sliding windows: Incident Monitor (18, Nov 2026, rated hard), and Transaction Log Metrics, which one off-campus candidate got as an OA task (autumn 2025).
- Payment state rules: For All Intents And Purposes, Part 1 through Part 4 (3 or 4 sightings, Apr 2025). Stateful tasks appear in 6 of 17 reports.
- The June 2026 graph sequence: Directly Linked Users, Fraud Ring Size and Risky Fraud Ring, each sighted once.
Keep practicing
- Stripe SWE Intern OA and Interview Questions: 46 Experiences: the full intern loops, including the team screen, integration round and manager chat.
- Stripe Experienced SWE HackerRank OA: the one experienced-hire OA report.
- Stripe Dublin SWE Internship Three-Part OA and Stripe Toronto Summer Internship 60-Minute OA: regional OA reports from 2026.
- Stripe SWE Intern Transaction-System OA and Stripe SWE Intern Payment Intent OA: two task-level OA reports.
- Stripe interview page: Stripe coding, design and behavioral questions by stage.
- Stripe hiring insights: hiring timelines and assessment activity for Stripe.
- Stripe OA question bank: the same problems with a code editor (needs sign-in).
- Interview experiences: full candidate reports for other companies.
Comments
0No comments yet — be the first to share what you know.