Stripe's online assessment is a timed HackerRank test that intern and new-grad candidates commonly report early in the process: about 60 minutes for one long, practical problem, often split into parts that extend the same code. It reads less like a puzzle and more like a slice of real work: parse records, track state, apply business rules and print exactly the expected output.
Stripe does not publish the format, so this guide keeps what Stripe says separate from what candidates report, and every candidate detail is a range rather than a promise. One rule holds throughout: the assessment measures your own work, so take it alone, without AI tools or another person, under the conditions in your invitation.
What Stripe officially says
Stripe's careers FAQ, as it read on November 16, 2026, says most hiring processes include a recruiter screen, “a technical or skills-based assessment,” and a series of interviews with the team you would join, and that timelines vary by role, level and location. Its emerging-talent page adds three points for students:
- Internship interview scheduling typically follows local academic calendars.
- Full-time and apprenticeship roles are hired on a rolling basis.
- Stripe recommends applying as early as possible.
What Stripe does not publish: the platform, the number of questions, the time limit, a pass mark, or a candidate AI policy for the assessment. We did not find one on the careers pages we checked. Your invitation is the authority on all of it.
The format, as candidates report it
| Element | What candidates commonly report |
|---|---|
| Who gets it | Mostly intern and new-grad applicants. Prep guides note it goes to some candidates only; experienced hires more often start with a recruiter call and a live technical screen. |
| Platform | HackerRank in the 2024 to 2026 reports we reviewed. |
| Time | About 60 minutes. A December 2025 new-grad report and a 2025 Seattle new-grad report both cite 60. |
| Questions | One long problem, often in two or three parts on one codebase. A 2024 Toronto report describes a two-part question; a 2026 report describes three parts built on one string-parsing solution. |
| Question type | Practical data processing: read input, keep state, apply rules, print exact output. Rarely a classic algorithm puzzle. |
| Difficulty | Seldom algorithmically hard. The challenge is reading a long specification carefully and covering edge cases before the clock runs out. |
These details come from self-reported threads and prep sites, they differ on the number of parts, and Stripe can change the test between cycles. If your invitation says something different, trust the invitation.
Topics, with practice examples
Stripe does not publish its questions and none of the drills below are claimed to be on the test. The first three themes come from candidate reports; the fourth is a closely related practice theme. The drills are ours, sized to a 60-minute window.
| Theme | What it looks like | Practice drill |
|---|---|---|
| CSV-style parsing | Records packed into a delimited string, with later parts extending the same parser | Parse lines of id, merchant, amount and currency; total fees per merchant at a percentage plus a fixed amount, in integer cents |
| State transitions | Sequential commands, some invalid; track state and print a final summary | Model an account that can be opened, funded, frozen and closed, and reject commands that are invalid for the current state |
| Thresholds over events | Merchant fraud rules over transactions and disputes | Flag a merchant once disputes pass a set share of transactions, and test both greater-than and greater-than-or-equal readings |
| Ledgers and notifications (practice) | Balances or messages generated from an event stream | Build a transfer ledger that refuses overdrafts and prints balances sorted by account, then by name |
For classic problems that train the same habits, try Logger Rate Limiter, Time Based Key-Value Store, Design Underground System, Merge Intervals and Group Anagrams. Our Stripe coding interview questions guide covers the practical rounds that follow, which reward the same careful, readable style.
Scoring and the pass bar
HackerRank scores a coding question by the test cases your code passes, and most of those cases are hidden. Our HackerRank assessment guide explains how partial credit, hidden tests and resubmission work. Stripe publishes no cutoff. Candidate anecdotes include people who advanced after strong scores and people rejected despite high scores, so a perfect score is strong evidence but not a guarantee; résumé fit, location, headcount and timing also count.
Hidden tests usually probe unstated assumptions rather than tricks. Check these before you submit:
- Empty input and a single record.
- Duplicate or unknown IDs.
- Output order, including ties.
- Threshold comparisons at the exact boundary.
- Rounding: keep money in integer cents.
- Large inputs that punish a nested scan.
Proctoring and the rules
HackerRank lets each employer choose its integrity settings. Its help center describes a Proctor Mode that flags leaving full-screen, switching tabs or leaving the test window and produces an integrity report afterwards, and it records copy and paste, with pasted content shown in the candidate report. You accept an honor code before the timer starts, and the employer's instructions on that first screen are the rules that apply to you.
Assume no AI tools, no searching for solutions and no second person unless the invitation explicitly allows something. Breaking a stated rule can end a candidacy, and later interviewers may ask you to walk through or extend the code you submitted, which is hard to do with work that is not yours.
A 10-day preparation plan
- Days 1–2: Parsing. Three drills a day: comma-separated lines, key=value pairs and timestamps. Print output in an exact format and diff it against the expected text.
- Days 3–4: State and rules. Build two small simulators from a written specification, such as an account ledger and an order lifecycle. Write test inputs before code.
- Days 5–6: Multi-part drills. Solve part 1, then add part 2 requirements without rewriting. Practice pulling logic into small functions so new rules slot in.
- Day 7: Edge cases. Integer cents versus floats, sorting ties, unknown references and empty input.
- Days 8–9: Full simulations. Two unseen 60-minute problems in HackerRank's sample-test environment, no notes and no searching.
- Day 10: Light review. Re-solve one drill you got wrong, check your setup and reread the rules in your invitation.
What happens after the assessment
Candidates commonly report a live technical screen with practical coding in a shared editor, then a virtual loop that can include coding, an integration round, a bug-squash debugging round, system design at experienced levels, and behavioral or manager conversations. Our guide to the Stripe interview process for engineers walks through those rounds. Response times in reports range from days to weeks, and Stripe does not publish a turnaround. If you are early in your search, the new grad online assessment guide explains how timed, auto-graded tests differ from live rounds.
Where CoPilot Interview fits
CoPilot Interview is an AI interview assistant, and its honest place in Stripe's process is before the assessment, not during it. The assessment is a solo, timed test that measures your own skill, so no assistant, AI tool or second person belongs in it unless the invitation says so in writing. Use the weeks before it instead: the browser demo at /try has 145 interview questions in 10 tracks and scores typed answers out of 10, and the free AI mock interview reads questions aloud and scores your spoken answers out of 10, which is the closest rehearsal for the live technical screen that follows. The free plan gives 15 minutes a day of live help in sessions of up to 15 minutes, with AI mock interviews included. In any live round later, follow your employer's rules; the desktop app runs on Windows 10 and 11 and macOS 12 or later.
Disclosure: CoPilot Interview is our product, so weigh what we say about it accordingly.
Frequently asked questions
Does every Stripe applicant get an online assessment?
No. Reports describe it mainly for intern and new-grad applicants, and Stripe's own FAQ says only that most processes include a technical or skills-based assessment. Experienced candidates more often go from a recruiter call to a live technical screen.
How long is the Stripe online assessment?
Candidates most often report about 60 minutes on HackerRank for one long problem, sometimes in two or three parts. Your invitation states the real limit.
Is the Stripe online assessment LeetCode-style?
Mostly not. Reports describe practical tasks such as parsing transaction records, tracking state and applying rules, where careful reading and edge cases matter more than clever algorithms.
Can I use AI tools or search during the Stripe online assessment?
Not unless the invitation explicitly allows it. Treat it as a solo test with no AI tools, no solution searches and no second person.
What language should I use for the Stripe assessment?
Use the allowed language you parse strings and use maps in most fluently. Reports do not point to a required language; confirm the options in the invitation.
Practice this interview before the real one
The AI mock interview builds questions from your resume and the job description, reads them aloud and scores each spoken answer out of 10. Included on the free plan.
Start a mock interview