RepostedStripe logo

Stripe · OA → Phone screen → Onsite

In process

Stripe SWE Intern OA and Interview Questions: 46 Experiences

Software engineer · InternshipOct 2026
Shared byjanebeingjane

Stripe intern reports, Apr 2025–Oct 2026: a 60-minute multi-part OA, a three-part screen, then integration, coding and manager rounds; Bikemap came up 5x.

At a glance

  • Process: a 60-minute OA with one problem in dependent parts, a 60-minute screen that adds requirements part by part, an onsite of coding plus integration in an unfamiliar repository or API, then a manager chat (03, 27, 29, 31).
  • Asked recently: multi-part implementation in 21 of 46 accounts and integration, API or file work in 16. Repeated tasks: Bikemap (5), invoice reconciliation and subscription email scheduling (2 each).
  • Difficulty: partial completion was common and not fatal: offers followed 2/3 coding plus 3/3 integration (25) and 3/5 integration parts (29, 31); others were rejected after finishing every screen part (15).
  • Practise first: Bikemap JSON Integration, Invoice / Payment Reconciliation and Email Subscription Scheduler.

Coverage: 43 SWE and 3 PhD ML intern accounts (U.S., Canada, India, Romania, Ireland), Apr 2025 – Oct 2026, including 5 application-only updates. Entries 01–05 are the 2027 cycle, 06–45 the 2026 cycle, 46 a spring 2025 ML process.

What came up

Stripe intern interviews are building exercises: one problem grows over several parts, then an integration round has you work with real APIs, files or a repository.

Topic Reports Last seen
Progressive / multi-part implementation 21 of 46 Oct 2026 (report date)
Integration, API or file work 16 of 46 Sep 2026
Behavioral or past-project discussion 8 of 46 Mar 2026
Data checks, reconciliation or fraud rules 6 of 46 Mar 2026
Server or worker allocation 3 of 46 Oct 2026 (report date)

A candidate can appear in more than one row.

Questions we found

Project Coding

Question Reports Last seen
Bikemap route / JSON integration 5 Mar 2026
Paginated API synchronization 1 Dec 2025

Algorithms / Data Structures

Question Reports Last seen
Invoice / payment reconciliation 2 Mar 2026
Subscription email scheduling 2 Dec 2025
Multipart load balancer 1 Oct 2026 (report date)
CSV-string parsing and queries 1 Jul 2026 (report date)
Organization-role tree rendering 1 Mar 2026
Transaction-log metrics 1 Dec 2025 (report date)
BitFont rendering and compression 1 Dec 2025
Key-value validation 1 Dec 2025
Account-balance coding 1 Dec 2025 (report date)
Converted balance checks 1 Nov 2025
Three-part shipping cost 1 Nov 2025
Progressive transaction-system OA 1 Nov 2025
Merchant fraud thresholds and disputes 1 Nov 2025 (report date)
Worker skills and account assignment 1 Oct 2025 (report date)
Per-key rate limiter 1 Oct 2025 (report date)
Server load-balancer screen (Bucharest) 1 Oct 2025 (report date)
Discount calculation 1 Oct 2025 (report date)

LLD, AI coding and behavioral

Question Reports Last seen
Business KYC verification (LLD) 1 Mar 2026 (report date)
Rule-expression parser (AI coding) 1 Mar 2026
Past projects or internships (BQ) 6 Mar 2026
Teamwork or collaboration (BQ) 4 Dec 2025
Meeting deadlines (BQ) 3 Mar 2026
Why Stripe, disagreements, feedback, quick decisions (BQ) 2 each Mar 2026

46 detailed candidate timelines, loops, and screens

01: Oct 2026 report · New York

No offer. A 60-minute OA led to a three-part team screen. Each part added requirements; edge cases mattered. The task was undisclosed.

02: Oct 2026 report · Load balancer

No offer after completing 2/3 coding parts. The round label, routing rules and output were not retained.

03: Sep 2026 · Toronto

No offer. The loop had a 60-minute/three-part OA, a 60-minute engineer screen, two 45-minute API-design/integration sessions and a manager chat. Tasks were undisclosed. AI was prohibited for this candidate.

04: Sep 2026 report · Dependent OA parts

No offer. A difficult timed assessment had dependent implementation parts; the task and completion count were undisclosed.

05: Sep 2026 · San Francisco

No offer. OA/screen work used maps and practical implementation. Integration supplied an unfamiliar repository and external APIs; operations and endpoints were undisclosed.

06: Apr 2026 report · Dublin

No offer. A 60-minute OA had one implementation question in three parts; the task was undisclosed.

07: Apr 2026 report · Bucharest

No offer. After about a two-week response wait and short HR chat, a US engineer gave two technical tasks. Prompts and completion were undisclosed.

08: Apr 2026 report · San Francisco

No offer. Recruiter and manager chats preceded technical conversations with two engineers; questions were undisclosed.

09: Feb–Apr 2026 · PhD ML

OA Feb 27, screen Mar 24, onsite Apr 10, manager Apr 16; rejected Apr 28. The screen involved strings and a vaguely recalled stock-account domain. Operations and OA/onsite prompts were undisclosed. The candidate explicitly reported no onsite system design or bug squash.

10: Mar 2026 · Cluj-Napoca

No offer. A multipart OA managed and printed a company-role tree; operations, traversal and layout were undisclosed. A behavioral question concerned meeting a deadline.

11: Mar 2026 report · Bengaluru

No offer. Electronic KYC checks were the live low-level-design task and felt similar to the OA. Entities, interfaces and checks were not transcribed.

12: Jan–Mar 2026 · Reconciliation, AI and Bikemap

Offer. An unfinished OA still led to a progressive invoice-reconciliation screen; exact extensions were not supplied. Onsite included an AI-assisted rule-expression parser and Bikemap. The AI round required directing the tool, checking its code and fixing errors. Integration API details were undisclosed. Manager topics: difficult projects, disagreements, feedback, AI use and why Stripe. Interviewers were friendly and offered useful hints.

13: Feb 2026 report · Toronto

A 60-minute summer-intern OA is established; outcome undisclosed. No task was described.

14: Feb 1, 2026 update · Intern holding email

Application update only. A second intern applicant confirmed a similar holding-pattern email. No later decision was shared; cohort inferred.

15: Jan 2026 report · Summer 2026 US

Rejected. Completion: team screen 4/4, pair programming 3/3, integration 2/4. Python with strings, maps and lists; tasks were undisclosed.

16: Jan 2026 report · Unlocking edge cases

No offer. Each completed coding part unlocked another, reused prior code and added edge cases. Domain and completion count were undisclosed.

17: Jan 2026 report · Code quality and ambiguity

No offer. The interview emphasized code quality, product judgment and ambiguity; no prompt or solution was shared.

18: Jan 2026 · US manager-to-offer timing

In a Summer 2026 US discussion, this candidate reported an offer at January’s end, about two weeks after the manager round. Exact days and questions were undisclosed.

19: Jan–Feb 2026 update · Withdrawal

Application update only. An intern applicant interpreted a holding-pattern email as a waitlist, then withdrew for another offer by Feb 1.

20: Jan 2026 · Canada OA, second 13/13

In the Summer 2026 Canada discussion, a Jan 24 reply reported completing the OA the preceding Wednesday: 13/13, no response. Task/platform undisclosed.

21: Jan 2026 · Canada OA, 13/13

In the same Summer 2026 Canada discussion, this candidate received the OA the previous day and completed it on Jan 22: 13/13. They found it not especially algorithm-heavy; task/platform undisclosed. On Jan 26 they still had no interview response.

22: Jan 21, 2026 update · Canada invitation

Application update only. A September applicant had just received an OA. Summer 2026 Canada is thread context; completion was unreported.

23: Jan 21–22, 2026 update · Canada application

Application update only. The author applied in September for Summer 2026 Canada and asked about January OA outreach. Their own invitation or completion was not confirmed.

24: Jan 2026 update · Seattle offer

Application update only. The author reported a recent intern offer and intended to accept. Their own “this summer” reference supports 2026; interview dates, rounds and questions were undisclosed.

25: Dec 2025 · Onsite and manager reschedule

Offer. About 2/3 programming parts and 3/3 integration parts were completed. A manager invitation arrived the next day and was moved to early January. Tasks and manager questions were undisclosed. One application spans the year boundary.

26: Dec 2025 report · Balances and Bikemap

Balance coding was implemented but testing unfinished; operations were not retained. Bikemap used simple.json: print ten coordinates, POST data, read/transform JSON, add specified point colors and POST again. Completion: about 2.5/4 parts. Endpoint/schema/color rules and final operation were not retained. Outcome undisclosed.

27: Nov–Dec 2025 · Off-campus offer

Applied September, screened November, onsite Dec 4; offer. OA: parse transaction logs, filter error codes, calculate latency and success metrics; grammar/formulas undisclosed. Screen: financial records, currency conversion and balance checks with evolving requirements.

Onsite coding scheduled subscription emails; later parts adjusted future emails after plan changes/extensions. Integration fetched authenticated pages, filtered/transformed data and POSTed to another service. Follow-ups: rate limits, idempotency and HTTP failures. Manager: prior internships, teamwork, quick decisions and feedback. Onsite tasks were completed.

28: Dec 2025 · Validation, email and Bikemap

Applied Sep 13; OA invite Nov 3; screen Dec 3; onsite Dec 11; manager Dec 22. Screen: three key-value validation parts, without a retained schema. Onsite: an unspecified email task (2/3) and three-part Bikemap. Invalid/delayed meeting links shortened technical sessions. On Jan 3 the recruiter was away and the candidate still awaited results; OA prompt undisclosed.

29: Dec 2025 report · Summer 2026 offer

Accepted offer. OA: 600/600, five minutes left, progressive implementation/debugging. Screen: through 3a, part of 3b, then pseudocode. Recruiter feedback praised Python fluency, type hints, clean code and edge-case questions.

Onsite coding was scheduled for 60 minutes but allowed about 35: three parts completed, total unknown. Integration added a repository feature using unfamiliar docs: 3/5 parts. Package setup took time. Feedback praised methodical debugging but noted slower debugging and a design quirk that worked for the task and most edge cases. A STAR/Stripe-values manager chat ran 20 minutes over and touched on familiar frameworks and a project. Coding prompts were withheld.

30: Nov–Dec 2025 · Shipping, BitFont and Bikemap

Rejected January 2026. All three shipping-cost screen parts were completed; pricing rules were not retained. Onsite BitFont rendered 2D bitmap characters, compressed/decompressed them, then added another transformation while reusing code. Two parts completed; the last transformation was undisclosed. Bikemap requested map data and added sport/activity points: three parts completed. Manager: past work and teamwork. OA task undisclosed.

31: Dec 2025 · Invoice matching, email and Bikemap

San Francisco offer after Jan 10, 2026. OA Dec 1; screen Dec 8; onsite Dec 16; manager Dec 29. Screen: invoice-ID matching, then earliest equal-amount invoice without an ID, then amount tolerance. All three parts completed; detailed rules came from an older saved note. Onsite: 2/3 email-scheduler parts, 3/5 Bikemap parts. Long docs and examples that did not align cleanly with the task slowed integration. Manager: projects, teamwork, disagreements, deadlines, mistakes, unfinished work, quick decisions, career priorities and why Stripe.

32: Nov 2025 report · San Francisco offer

Accepted offer after OA, screen, two onsite sessions and manager interview. Technical work used classes, strings and API requests; prompts/contracts were not retained.

33: Nov 2025 report · Winter-intern manager

The season label conflicts with the report date. Following a Thursday onsite, a manager invitation arrived the next Wednesday with a short scheduling deadline. The chat felt rushed, with little question time; rejection came the next day. No prompts disclosed.

34: Sep–Nov 2025 · Bengaluru

No offer. The 60-minute OA had three sequential parts. October screen: arrays/maps/strings, two parts coded and the third explained. Onsite coding parsed/cleaned data. Integration used a private repository, API docs, files, requests/responses and repeated debugging. Manager: prior internship work, deadlines, collaboration, ambiguity and ownership. Exact task/API contracts were undisclosed.

35: Nov 2025 · San Francisco OA

No offer. A one-hour assessment involved many variables and state changes; domain, operations and part count were not retained.

36: Nov 2025 · Transaction-system OA

No offer. A roughly 90-minute OA built a simple transaction system in successive parts. Errors accumulated; 11/16 tests passed. Commands/output rules were not retained.

37: Nov 2025 · Expedited scheduling

A Nov 26 reply in the 2026 intern discussion reported a competing offer. Manager and onsite sessions were scheduled together in a partly expedited process. Results from the preceding Friday’s interview were pending; no questions or final outcome disclosed.

38: Nov 2025 report · 2026 intern onsite

On Nov 25, this SWE Intern 2026 applicant said one onsite round felt weaker, but a manager invitation followed a couple of days later. Questions and final outcome undisclosed.

39: Nov 12, 2025 report · 2026 intern fraud OA

Off-campus, no referral; about two months to an OA link received the day before the report. HackerRank: one question, 60 minutes. Merchants map to MCCs with integer/count or decimal/ratio fraud thresholds. Given fraud/non-fraud codes, process CHARGE and DISPUTE; disputes reverse fraudulent charges. Score: 22/25. No update by Nov 17; actual OA day unreported.

40: Oct 2025 report · PhD ML OA

90 minutes: applied math (2 questions/5 minutes), statistics (3/10), Python data/ETL (1/25), PyTorch (1/50). Unused time carried forward; completed sections could not be revisited. The seven prompts were not transcribed.

41: Oct 2025 report · Dublin filesystem work

Coding assessment, filesystem work and past-project questions. File operations, output, round order and outcome were not retained.

42: Oct 2025 report · Per-key rate limiter

Structured season conflicts with the report date. In a 45-minute screen, implement hit(key, timestamp) and allowed(key, timestamp). Fixed or sliding windows were allowed. Discussion: many keys, concurrency, deques/ring buffers, cleanup, bursts, missing keys, out-of-order times, idle gaps and complexity.

43: Oct 2025 report · Worker assignment

Assign duration-bearing tasks to the worker with least assigned workload. Add skills, then prefer a worker with prior work on that account if eligible. A possible fourth part was not reached; ties and competing-match precedence were unclear. Earlier screen: discounts, formula unretained. Integration: HTTP request, endpoint/action unretained. Outcome undisclosed.

44: Oct 2025 OA · CSV and graph/string rounds

Applied August–September; later live-round dates unreported. Rejected after the second live round. All rounds, including the OA, were 60 minutes. OA: four-part string/transaction-flow/LRU-like implementation, 15/19 tests; the analogy does not identify a cache exercise. First live round: parse CSV from one string and answer queries, 2/4 parts coded, third explained. Next: graphs/strings; debugging consumed time. Query rules and graph operation were not retained.

45: Oct 30, 2025 report · Summer 2026 Bucharest

A second-year CS student reached a server-load-balancer screen but did not solve it in time; no offer. No event, load metric or output rule identifies the variant.

46: Apr–May 2025 · PhD ML offer

OA Apr 14, screen Apr 23, onsite coding/ML integration May 1, manager May 2, offer May 5. Practical multipart work used strings, arrays, maps and integers. Prompts undisclosed; working code, readability and tests mattered.

Patterns across the reports

  1. Each part builds on the last. 21 accounts describe multi-part problems where later parts reuse earlier code and add edge cases (01, 16, 27, 31).
  2. Integration means unfamiliar code. Repositories, docs and external APIs slowed several candidates (05, 29, 31, 34).
  3. Partial completion still led to offers. 25, 29 and 31 got offers without finishing every part.

Common questions

What is on the Stripe intern OA?

A 60-minute implementation problem in dependent parts (01, 06, 34); one 2025 OA was about 90 minutes (36), and a fraud OA scored 22/25 tests (39).

What is the Stripe Bikemap question?

An integration task: read a JSON file of coordinates, POST data to an API, transform it and POST again, sometimes adding point colors or activity types (26, 30, 31).

Do you need to finish every part of a Stripe interview?

No fixed rule: offers followed partial completion (25, 29, 31), and a rejection followed full screen completion (15).

What does the Stripe intern manager round ask?

Past projects, teamwork, deadlines, disagreements, feedback, quick decisions and why Stripe (12, 27, 31, 34).

Keep practicing

Sources: Anywhere useful interview info can be found.

0 total reactions. Your reactions: none.
0 comments

Comments

0

No comments yet — be the first to share what you know.