AO
AceOffer
Stripe logo

Stripe Interview Questions

Reconstructed from 405 verified candidate reports across 70 questions. Jan 2025 – Sep 2026.

This page is a live view of every Stripe interview question AceOffer has indexed — pulled from real candidate reports, not invented from job descriptions or one founder’s memory. Every question shows how many times it’s been reported and when it was last seen. The catalog gets a refresh pass every month.

405
candidate reports
70
distinct questions
7
round types
Monthly
refresh cadence

Key facts

  • •70 distinct Stripe interview questions indexed
  • •405 candidate reports across the catalog
  • •Most reported: Bike Map — 46× (last seen August 2026)
  • •Reports span Jan 2025 – Sep 2026
  • •Refreshed monthly · last updated September 2026

Browse Stripe interviews by topic

Coding Interview QuestionsSystem Design Interview QuestionsBehavioral Interview QuestionsInterview Process & Rounds

The Stripe loop, from candidate reports

Stripe's loop is built from its own round types rather than LeetCode. Reports describe an online assessment on some loops, one technical screen, and a virtual onsite. The assessment, reported by new-grad, intern and experienced candidates alike, is a single long multi-part problem on HackerRank of about 60 minutes. The technical screen is one multi-part coding problem, most often shipping cost, payment-to-invoice matching or business data verification. A full-time onsite is usually four or five rounds: a programming exercise; an Integration round inside a cloned repository, where Bike Map is the most-reported question in the catalog; a Bug Squash round that asks you to fix failing tests in an unfamiliar library, most often a modified Mako template engine; a system design round; and a behavioral or hiring-manager round. Intern loops report two onsite rounds, and some L2 loops report no system design. From spring 2026, several reports say the programming round, and on some loops the screen, became an AI coding round using HackerRank's built-in assistant. Most coding-style rounds come in parts that build on each other, and more than one candidate reports passing without finishing the last part.

What does Stripe ask in each interview round?

Stripe interviews span 7 distinct round types, broken down below. Counts reflect distinct questions per round, not number of times asked. Frequencies on individual question cards show how many candidates reported getting that specific question.

The technical screen and the onsite programming exercise: one business problem in parts that build on each other. Shipping cost, the subscription email scheduler, business data verification and payment-invoice matching lead the reports.
31 questions

Most-reported: Shipping Cost Calculator (36×)
One long multi-part problem on HackerRank, about 60 minutes, reported on new-grad, intern and experienced loops. The Jupyter load balancer and the request routing system are the most reported.
14 questions

Most-reported: Jupyter Load Balancer (8×)
Fix failing tests in a modified open-source library. Mako is the long-running repository, requests, Moshi/Jackson and SnakeYAML appear in other loops, and interviewers weigh the debugging process as well as the fixes.
9 questions

Most-reported: Mako Template Engine (27×)
Design at the API and data-model level. The ledger, a metric counter and a feature flag SDK are the most reported.
7 questions

Most-reported: Ledger System (10×)
Hands-on work inside a cloned repository against real files and HTTP APIs. Bike Map dominates; invoice reconciliation against an API and request replay also recur.
6 questions

Most-reported: Bike Map (46×)
A behavioral round and a hiring-manager round: why Stripe, your proudest project, feedback and conflict, and in 2026 reports, how you use AI at work.
2 questions

Most-reported: Behavioral Round (22×)
A coding problem solved with HackerRank's built-in AI assistant, reported from 2026 in place of the programming exercise and on some screens. The transaction rule parser is the reported question.
1 question

Most-reported: Transaction Rule Parser (9×)

Which Stripe interview questions come up most?

These are the Stripequestions reported most across the loops we’ve indexed, sorted by candidate-report frequency.

QuestionRoundReportedLast seen
Bike MapIntegration46×August 2026
Shipping Cost CalculatorCoding36×March 2026
Subscription Email SchedulerCoding31×May 2026
Mako Template EngineBug Squash27×June 2026
Behavioral RoundBehavioral22×August 2026
Business Data Verification (KYC)Coding21×September 2026
Payment–Invoice MatchingCoding18×August 2026
Hiring Manager RoundBehavioral16×August 2026
Account Balance ManagerCoding12×May 2026
BitFont RendererCoding10×May 2026

The full index is below, or browse the Stripe catalog →

Every Stripeinterview question we’ve indexed

All 70, grouped by round and sorted by how often candidates reported them. Each links to the question, its reported follow-up count, and when it was last seen.

Coding (31)

OA (14)

Bug Squash (9)

System Design (7)

Integration (6)

Behavioral (2)

AI Coding (1)

Read two Stripe questions free

Full problem statements, candidate-reported follow-ups, and walkthroughs. No signup needed.

Free previewCoding36× reported
Shipping Cost Calculator

Given an order (a destination country and items with quantities) and a per-country shipping table, return the total cost. Part 2 replaces flat prices with quantity tiers; an interviewer said to assume the tier list is not sorted, and the last tier can have no upper bound; Part 3 adds fixed tiers charged once however many units fall in them. One report warns that if-chains on tier boundaries tangle into edge cases, and one candidate whose first two parts used well-named helpers changed a single helper for Part 3. This is a free preview — full statement, follow-ups, and a worked solution.

Last reported March 2026Read it →
Free previewIntegration46× reported
Bike Map

The Integration round most candidates meet. In a cloned repository, read coordinates from a JSON ride file, POST a map request to a provided API and save the returned image, then add start and end markers and a coloured path built from the ride; some variants add landmarks joined to the nearest point. AI autocomplete must be off, searching documentation is allowed, and the interviewer offers little guidance — reports say the round grades whether you can unblock yourself.

Last reported August 2026Read it →
Free previewBug Squash27× reported
Mako Template Engine

Bug Squash on a modified Mako template engine: run the test suite, find the failing tests, and fix up to three independent planted bugs, the third often framed as a stretch goal. One interviewer acknowledged the missing AST-visitor bug is hard to see. Recorded failures include a Python version that broke the debugger, debugging with print statements until time ran out, and the AST bug itself.

Last reported June 2026Read it →
What passing candidates do
  • •Writing readable, modular code instead of racing to the last part. One report that ended in an offer credits clean naming, structure and edge cases over completion; on the shipping-cost problem, a candidate whose first two parts used well-named helpers only had to change one helper for Part 3.
  • •Working the AI coding round as plan, prompt, review. Candidates who did well formed their own view of the problem before prompting, read the assistant's code closely, and added their own tests. At least one candidate who sketched their own skeleton first was asked why they were not using the AI.
  • •Using a real debugger in Bug Squash. Candidates who debugged Mako with print statements report running out of time. A tip from one rejected candidate: compare a failing test with the passing tests next to it, which usually differ only in their input.
  • •Unblocking yourself in Integration. The round gives you a repository and documentation, not guidance, and reports say it measures how quickly you find your way around unfamiliar code and choose your next step. One rejection's feedback named exactly that.
  • •Designing at the API and data-model level. Reports on the ledger round say it wants API-level detail rather than only a high-level diagram, and it probes idempotency keys and how money is modelled.
Where candidates lose points
  • •Choosing Java. Several reports say the multi-part rounds are very hard to finish with Java's boilerplate; one intern repeated 'do not use Java' three times, and one interviewer said the bar would be higher for a Python candidate.
  • •Spending the round reading. The problem statements are long: candidates on the email scheduler report that reading time left too little time to debug, and data verification reports call the statement too long to finish reading. On invoice matching, misreading the input format cost candidates the later parts.
  • •Bugs in your own test cases. More than one candidate lost many minutes debugging a correct solution against a wrong expected value copied from an earlier test.
  • •An environment that will not run. On Mako, a broken IDE debugger cost some candidates the round: one traced it to a Python version the repository did not support and failed, another fixed only one bug.
  • •Answering staff-level behavioral questions with execution stories. One staff candidate was told the technical rounds were fine but the behavioral answers did not show staff scope.

Get the full Stripe catalog

Every question. Every candidate-reported follow-up. The mistakes that sink people, and what passers do instead. Monthly refresh.

See pricingBrowse free first
More company interview guides
Anthropic Interview Questions→OpenAI Interview Questions→Waymo Interview QuestionsFree→xAI Interview Questions→Perplexity Interview Questions→Mercor Interview QuestionsFree→Palantir Interview Questions→Harvey AI Interview QuestionsFree→Roblox Interview Questions→Zip Interview Questions→Robinhood Interview Questions→Databricks Interview Questions→
Prefer to study first? Free reading guides & references — including the AI Training Papers reading guide.
Is this helpful?