Stripe Software Engineer Intern Interview Guide
Stripe software engineer intern interview guide: internship OA, team screen and final-day coding, integration and AI rounds, from real candidate reports.
On this page
How to crack Stripe: The Software Engineer Intern interview, from real experiences
Last reviewed: 17 November 2026 · Estimated reading time: 15 min · Audience: First-time internship candidates, beginner-friendly, mixed/global geography
Who wrote this and what it draws on. Researched by Codinzhub from three candidate records for this exact role — one Stripe intern experience with an SF offer and two Codinzhub records (ids 2346 and 1997) — plus six additional Reddit candidate reports (R-INT-1 to R-INT-6) retrieved through an archive. Not written or approved by Stripe. Reports are individual experiences, not a company script, so confirm your own format with your recruiter.
DRAFT. Several rounds still have fewer than five distinct reported questions: OA (4), VO programming (2), integration (1 distinct task) and the AI round (no named question). Team screen/technical coding (5) and the hiring-manager chat (15) now meet the minimum. This is a map of the process and skills, not a complete question bank. Shortfalls and searches are in the checklist at the end.
The 30-second version. Across the reviewed intern accounts (2025–2026, India/Bangalore and San Francisco), the reported path was an online assessment (OA), a technical or "team" screen, and a final day or second stage with programming, integration and — in one report — an AI round that allowed an LLM, then a hiring-manager (HM) chat and an offer or rejection. Coding was multi-part and incremental; one 2026 account described five questions revealed one at a time with increasing difficulty, where simple working code was accepted. Interviewers valued clean, working solutions over clever algorithms. The integration round, where you work in existing code with an API and long documentation, was the round candidates found hardest. Manager chats covered project, motivation and feedback questions. Your best habit: turn a long specification into small, tested helpers under a timer.
Important things to know before the interview
Integration is Stripe's distinctive round. The SF intern's "Bikemap" task gave long library documentation; the candidate made requests, parsed responses and found the docs' examples did not match the needed code (3 of 5 parts done). The Bangalore intern described debugging existing code, integrating APIs and reading documentation fast. Do: build small projects that call an external API and practise reading docs under a clock.
Coding is incremental. Screens gave one problem in parts: solve part 1, add a rule for part 2 while keeping part 1 passing, then part 3. Do: keep parsing, rules and output in separate helpers so a new rule changes one place.
The language note is a candidate report, not a rule. One intern reported that an HR prep document ranked C/C++ lower and suggested Java or JavaScript; another suggested Python or JavaScript because C++ libraries can be complex. They disagree, and no official Stripe page checked says anything about languages. Do: use a language you can parse and test quickly in, and confirm allowed languages with your recruiter. This is not a ban.
Location and route changed the experience. The SF report is a recruiter-driven December timeline with an offer after 10 January; the Bangalore report came via a LinkedIn inmail in August and ended in October rejection; the India off-campus record applied on a portal and waited about two months for an OA link. Anchor expectations to your own channel.
Terms on first use. An OA (online assessment) is a timed test on your own machine, here reported on HackerRank, a browser-based coding-test platform. A VO (virtual onsite) is the final interview day done remotely. BQ (behavioural questions) ask what you have done, not code you write. Integration means making existing code work with an outside service or library. A bug-squash round asks you to find and fix a defect in an unfamiliar codebase; it appears in Stripe reports for other levels but not in any of these three intern accounts. Stack rank is the candidate's phrase for comparing interns as a group after the manager round.
What this guide covers
This guide covers only Stripe's Software Engineer Intern role — not new-grad, SDE, backend, senior or staff roles, which may run similar loops. Evidence comes from 2025 internship cycles with outcomes through January 2026: an SF-offer account, a Bangalore internship and an India off-campus application.
Stripe's careers pages say interns write production software, that the program is competitive with high expectations, and that preferred qualifications include at least one year of university education or equivalent. They publish no fixed round count, question list or cutoff. Everything more specific below is a candidate report or, where labelled, editorial advice. We reviewed candidate accounts for this role; we did not read every account that exists.
Round-by-round breakdown
The stage order below is the order reported across the three accounts. Labels vary by source, so both names are given.
Stage 1: Application, where candidates applied
| Channel | What candidates reported |
|---|---|
| Careers portal | The India off-campus intern (record 2346) applied on Stripe's portal; the OA link arrived about two months later. |
| LinkedIn recruiter inmail | The Bangalore intern (record 1997) was contacted in August 2025 about a summer internship at the Bangalore office. |
| Recruiter-driven / not reported | The SF account starts at the OA in December; the application channel is unstated. |
Referrals, campus drives and contests are not documented for this role in the assigned records, so they are not claimed.
Stage 2: Shortlisting, how candidates moved forward
Shortlisting is the step between applying and the first scored round.
- OA invite or scheduling link: about two months after applying (India), six days after the inmail (Bangalore), or an OA dated 1 December (SF).
- Next-stage scheduling invite: the SF account notes a phone-screen invite the day after the OA; Bangalore notes a Team Screen invite.
- Pre-interview material: the India candidate received a preparation document and questionnaire from HR — the source of the language note above.
No official screening criteria or response-time promise appears in these reports.
Stage 3: Online assessment (OA)
How it works. An early timed screen, reported here on HackerRank. The India candidate described one very hard question and said 17 of 19 test cases passed led to an interview call — one person's result, not a cutoff. None of the three reports names the OA problem, so no question table with real content is possible. An external editorial resource describes a common pattern of one 60-minute practical problem with parsing, maps and state, but that is a pattern, not a reported question from these accounts.
At a glance: Duration — not reported in the assigned records (editorial resource suggests ~60 min; check your invitation). Questions — one hard question in the India report, content not described. Topics — DSA tag only. Examples — none detailed enough to reproduce.
Reported questions — INCOMPLETE (0 of 5)
| Question summary | Skill or pattern | Reported follow-up | Level / scope | Codinzhub question or experience |
|---|---|---|---|---|
| No question content was reported in the assigned records. | Not applicable | Not reported | Intern, 2025, India report | Codinzhub record 2346 (plain text, no URL) |
More questions: the practice section offers general parsing and state-mapping drills; these are analogues, not reported OA questions.
Stage 4: Team screen / technical coding interview
How it works. A live coding screen. Bangalore reported 60 minutes and two problems, focusing on clean, working solutions using core data structures rather than optimal complexity, in JavaScript. SF's 8 December "team screen" was a three-part invoice matching problem. India's interview used two medium questions on a HackerRank link shared during the call, with screen share on Zoom and Google allowed for syntax — a detail reported only by that candidate.
At a glance: Duration — 60 min (Bangalore); not reported elsewhere. Questions — two problems (Bangalore), one multi-part problem (SF), two medium (India). Topics — data structures, parsing, mapping, incremental rules. Examples — invoice matching; a problem like LeetCode Count Mentions Per User.
Reported questions — INCOMPLETE (2 of 5)
| Question summary | Skill or pattern | Reported follow-up | Level / scope | Codinzhub question or experience |
|---|---|---|---|---|
| Match payments to invoices: by ID (handle no match), then by exact amount choosing the earliest-dated invoice, then within an amount "forgiveness" range choosing the earliest date. | Matching, maps, incremental design, tie rules | Three staged parts; interviewer said finishing all three was not required | Intern, SF, Dec 2025 | Codinzhub question record |
| A coding problem the candidate compared to LeetCode's "Count Mentions Per User" (mentions across timestamped events with online/offline states). | Event processing, maps, state | Not reported | Intern, Bangalore, Sep 2025 | Codinzhub record 1997; analogue |
More questions: these two rows are the complete named set we could source for this round.
Stage 5: Final interview day / virtual onsite (VO)
Bangalore reports two one-hour rounds on the final day: a Programming Round and an Integration Round. SF describes a 16 December VO with a programming exercise (45 minutes allotted) and an integration task. These are treated as one stage with two rounds.
Programming round
How it works. Another data-structure-heavy, multi-part exercise. SF called it "the email one" and completed 2 of 3 parts; Bangalore said it was similar to the first screen, again valuing clean working solutions over complexity.
At a glance: Duration — 45 min allotted (SF), one hour (Bangalore). Questions — one multi-part problem (3 parts in SF). Topics — dates, deterministic ordering, rule design. Example — subscription email scheduling.
Reported questions — INCOMPLETE (1 of 5)
| Question summary | Skill or pattern | Reported follow-up | Level / scope | Codinzhub question or experience |
|---|---|---|---|---|
| Given subscription records (customer, start date, length in days), produce every lifecycle email in send-date order, such as a welcome email at the start and an expiration email at the end. | Date arithmetic, sorting with tie rules, extensible rules | More email types in later parts is the natural extension; exact follow-ups not reported | Intern, SF, Dec 2025 | Codinzhub question record |
More questions: none named in the assigned accounts; use the ordering and scheduling practice below.
Integration round
How it works. You work in an existing setup: make HTTP requests, parse responses and read long documentation to find the call you need. The SF candidate found this hardest (3 of 5 parts); Bangalore also named docs and API integration as a weak spot. No other integration task is named in the assigned records.
At a glance: Duration — not reported separately. Questions — one task with multiple parts (5 in SF). Topics — requests, response parsing, docs, debugging. Example — "Bikemap".
Reported questions — INCOMPLETE (1 of 5)
| Question summary | Skill or pattern | Reported follow-up | Level / scope | Codinzhub question or experience |
|---|---|---|---|---|
| "Bikemap" task: use an open library/API from its documentation, make requests, parse the response and adapt the docs' examples to the task. | API integration, parsing, documentation reading | 5 parts total per the candidate; only the general shape is reported | Intern, SF, Dec 2025 | Full experience |
More questions: other Stripe experiences describe integration tasks for other roles; those are not intern questions and are not counted.
Stage 6: Hiring-manager chat and behavioural questions
How it works. A conversational manager round about your projects, teamwork and motivation. The SF candidate found the manager earnest but stern, and was redirected when an answer drifted. This is the one round with enough distinct reported questions to be complete.
At a glance: Duration — not reported. Questions — nine listed by the SF candidate. Topics — projects, teamwork, deadlines, mistakes, judgement, motivation.
Reported questions — COMPLETE (9 of 5)
| Question summary | Skill or pattern | Reported follow-up | Level / scope | Codinzhub question or experience |
|---|---|---|---|---|
| Describe one of your projects. | Project deep dive | Who was on it / role split | Intern, SF, Dec 2025 | Codinzhub behavioural record |
| Who was on that project, and how did you divide the roles? | Ownership / teamwork | Follow-up to project question | Intern, SF, Dec 2025 | Same record |
| Describe a time your voice was not heard. | Disagreement / influence | Candidate drifted and was steered back | Intern, SF, Dec 2025 | Same record |
| How do you set deadlines? | Planning | Not reported | Intern, SF, Dec 2025 | Same record |
| A time when you learned from your mistakes. | Reflection | Not reported | Intern, SF, Dec 2025 | Same record |
| What do you value in your career? | Motivation / values | Not reported | Intern, SF, Dec 2025 | Same record |
| Something you could not resolve by yourself. | Asking for help | Not reported | Intern, SF, Dec 2025 | Same record |
| A situation where you made a quick decision. | Judgement under time | Not reported | Intern, SF, Dec 2025 | Same record |
| Why Stripe? | Company motivation | Not reported | Intern, SF, Dec 2025 | Same record |
More questions: the intern hiring-manager record groups these into a story bank.
Final decision: offer, wait and group comparison
The SF candidate got an HM invite the morning after the VO, chatted on 29 December, and heard nothing until an offer-call email after 10 January. They observed that New York filled first (about 20 interns there, by their Discord estimate) but headcount still existed in December and January; they received an SF offer. They also reported hearing that interns finishing HM within a two-week window are compared as a group before offers — the candidate's own hearsay, not confirmed policy.
Stripe experiences shared on Codinzhub
| College or background | Role and reported outcome | What was asked | Experience |
|---|---|---|---|
| Not stated (SF-offer report) | Software Engineer Intern — offered | Invoice screen; email scheduling and Bikemap integration in VO; nine HM questions | Full experience |
| NIT XX | "swe intern" — rejected (round 2 of 3) | OA with one hard question; interview with two medium questions; content not described | Codinzhub record 2346 (plain text, no URL) |
| Not stated (Bangalore) | Software Engineer Intern — rejected | 60-minute screen; programming + integration on final day | Codinzhub record 1997 (plain text, no URL) |
The Codinzhub next-round playbook
These are editorial recommendations based on what the reports demanded, not claims about what caused an offer.
- OA: practise one long problem in a single file under a ~60-minute timer; separate parsing from rules; test empty input, duplicate IDs, zero amounts, date ties and unknown references.
- Team screen: rehearse explaining while coding (the Bangalore candidate was told to value a clean working solution over complexity); drill map lookups and tie rules; decide your language before the round — one candidate switched mid-process and regretted it.
- Programming round: practise date arithmetic across month/year boundaries and a deterministic order for same-day events.
- Integration round: do one rep with only documentation and a short task; skim doc structure first, then locate the exact call — the Bikemap candidate lost time on the docs/examples mismatch.
- HM chat: prepare distinct stories for a project, a rejected proposal, a deadline, a mistake, unsolved problem, quick decision and career values. A simple STAR structure (Situation, Task, Action, Result) keeps answers short.
Variations within this role
- Location/headcount: SF had a late timeline that still produced an offer and an early-New-York-fill observation; Bangalore came via inmail in August with an October rejection.
- Route: portal application with a two-month wait (India off-campus) versus recruiter inmail (Bangalore) versus recruiter-driven timing (SF).
- Round naming: "Team Screen" (SF/Bangalore), "interview" (India), "VO" for the final day (SF) — labels for similar stages, not proof of one global sequence.
- Language material: only the India record mentions a prep document with a language ranking; no official policy was found.
Do's and don'ts
| Do | Don't | Why it matters |
|---|---|---|
| Confirm allowed languages, tools and round count with your recruiter. | Treat the C/C++ note as an official ban or one timeline as universal. | It is one candidate's report of prep material, and accounts disagree. |
| Keep earlier parts passing when a new rule arrives. | Rewrite the whole solution each part. | Every reported coding task was incremental. |
| Use a date library and state your tie rule. | Hand-count days or leave ordering implicit. | Email scheduling depended on correct dates and order. |
| Read API docs for structure, then find the exact call. | Copy an example that does not fit. | The Bikemap candidate lost time on exactly this. |
| Prepare distinct behavioural stories. | Reuse one story for every question. | Nine different questions came in one manager chat. |
| Dry-run a no-match case and a duplicate by hand. | Only test the sample input. | The invoice task required handling a payment with no match. |
Most-asked topics
"Most asked" means recurring in the three reviewed accounts; the dataset is too small for frequencies or percentages.
| Topic | What it means | Priority | Reported examples | Codinzhub practice |
|---|---|---|---|---|
| Incremental multi-part coding | One problem extended in stages, older behaviour preserved | Recurring in every technical account | Invoice matching, email scheduling | Invoice matching |
| Maps and matching | Storing records by key for fast lookup | Reported in screen and programming rounds | Invoice ID match, amount match, mention counts | Group Anagrams |
| Parsing and record modelling | Turning raw lines into clean data | Across coding and integration rounds | Payment/invoice records, API responses | Invoice matching |
| Ordering and tie rules | Deterministic output when several items qualify | Invoice and email tasks | "Earliest date", same-day emails | Merge Intervals |
| API integration and docs | Calling a service and reading its docs | Both VO accounts | Bikemap | Full experience |
| Behavioural / motivation | Projects, teamwork, mistakes, "Why Stripe" | One manager chat, nine questions | See HM table | HM record |
The question patterns that keep coming back
Pattern 1: The problem grows while you watch
A screen gives part 1, then adds parts 2 and 3 to the same code. The SF invoice task went from ID matching, to exact amount, to a forgiveness range; its programming task had three parts. Recognise it by "builds on part 1" or "still has to support the previous logic". Action: sketch parse, decide and format helpers before coding.
Pattern 2: From a key lookup to a range lookup
Match by exact ID, then exact amount, then any amount inside a tolerance while picking the earliest date. Recognise it by "earliest" or "within ±". Action: use a map for exact keys and a sorted structure for ranges; state whether bounds are inclusive and what breaks a tie.
Pattern 3: Events become a schedule
Subscription records must produce welcome and expiration emails in send-date order, with more types added later. Recognise it by "produce every event in chronological order". Action: generate dated events, sort with an explicit tie rule, and describe rules as data so a new type is a table change.
Pattern 4: Work inside someone else's system
The integration round hands you long documentation and an existing setup. Recognise it by "make a request and parse the response". Action: find the exact endpoint and response shape, get the smallest request working, then extend part by part.
Preparing for the behavioural and company-values round
Prepare for the nine questions in the HM table. Candidates described a conversational but focused style, with the manager redirecting drifting answers. No special Stripe-named values framework appears in this evidence, so do not memorise a slogan.
Build a story bank covering: one project you can explain technically, team and role split, a rejected proposal, a deadline you set, a mistake you owned, a problem you could not solve alone, a fast decision, and your career values. Speak in the first person about your actions, give a result, and add one line of reflection. Keep "Why Stripe?" tied to products or engineering you can actually name.
Practice problems that match the experiences
These are practice analogues, not questions confirmed as Stripe's. The three Codinzhub records are structured versions of questions reported in the SF account and are the closest practice available.
| # | Practice problem | Pattern | Related reported question or variant |
|---|---|---|---|
| 1 | Match Payments to Invoices by ID, Exact Amount, then a Forgiveness Range | Incremental matching, maps, ranges | Structured from the reported invoice screen |
| 2 | Schedule Welcome and Expiration Emails | Dates, ordering, rules | Structured from the reported VO programming task |
| 3 | Internship Hiring-Manager Behavioral | Story bank | The nine reported HM questions |
| 4 | Count Mentions Per User | Events, online/offline state | The Bangalore candidate's example problem |
| 5 | Two Sum | Hash-map lookup | Exact-key matching from invoice part 1 |
| 6 | Group Anagrams | Grouping by a key | Key-based grouping |
| 7 | Design HashMap | Map behaviour | The lookup structure you rely on |
| 8 | Binary Search | Ordered lookup | Finding bounds in a forgiveness range |
| 9 | Merge Intervals | Sorting, overlap, ordering | Range and ordering discipline |
| 10 | LRU Cache | Class design, state | Keeping state consistent as rules change |
How to handle a question you have never seen
- Clarify the contract. Write down entities, operations, output and ordering or "no match" rules; ask about empty input and duplicates.
- Build a tiny example by hand. If you cannot predict a two-row result, your model is not ready.
- State an initial approach. Say what you will store in a map or sorted list and why.
- Find the bottleneck. Is the difficulty parsing, state, a rule or formatting? Name it before editing code.
- Improve the approach. Add a helper or better index, then re-run your tiny example and the given tests.
- Implement, then attack edge cases. Test no-match, a tie, a boundary and a repeated operation.
- Handle follow-ups aloud. Say which helper a new rule changes and confirm old cases still pass.
Why candidates were rejected
No recruiter feedback was quoted in the assigned accounts, so no cause can be stated as fact. The India candidate was rejected after round 2 with no reason recorded. The Bangalore candidate was rejected after the final day and received constructive feedback; they identified integration as their weakest area — the candidate's own interpretation, not an official rubric. The SF candidate received an offer.
Common preparation mistakes (editorial advice, not reported feedback): treating a multi-part problem as separate questions; leaving tie rules and no-match behaviour implicit; reading API docs too slowly; arriving with one reusable behavioural story.
If you remember only five things
- Expect an OA, team screen, final day with programming and integration rounds, and a manager chat — but confirm your own sequence.
- Multi-part coding rewards clean, extendable code more than clever algorithms.
- Integration was the round candidates struggled with most; practise APIs and documentation, not just DSA.
- Use a language you can parse, test and type in quickly; the C/C++ note is one candidate's report of prep material, not a rule.
- Prepare distinct, specific manager-chat stories, including a project deep dive and "Why Stripe".
FAQ
Is the Stripe intern OA one long problem or many?
The assigned records do not name it. One India report mentions a single hard question; an external editorial resource describes a common ~60-minute practical problem with several parts. Treat that as a preparation hint and read your invitation.
Does Stripe ask LeetCode-style questions?
The Bangalore screen emphasised clean working solutions over complexity and used a problem the candidate compared to Count Mentions Per User — one example, not a rule. Practise maps, strings and state, but expect practical, spec-heavy tasks.
Is there system design in the intern loop?
None of the three accounts reports one. Design rounds appear in Stripe reports for other roles and levels, which are out of scope here. Do not assume one.
Which language should I use?
One intern reported a prep document ranking C/C++ lower and suggesting Java or JavaScript; another suggested Python or JavaScript. These are individual reports of prep guidance and they disagree, so confirm allowed languages with your recruiter.
How long are the rounds?
Bangalore reported a 60-minute screen and two one-hour final-day rounds; SF says 45 minutes were allotted for the programming exercise; India gives no duration. These are per-account figures.
Does the process differ by location?
Yes in these reports: SF had recruiter-driven timing, an early New York fill and a later SF offer; Bangalore came through an August inmail with an October rejection; India waited about two months after applying.
How soon will I hear back?
No reliable range. One SF candidate waited from a 29 December manager chat until after 10 January; one India candidate waited about two months for an OA link.
What is a bug-squash round, and will I get one?
It asks you to find and fix a defect in an unfamiliar codebase. It appears in Stripe reports for other levels but in none of the three intern accounts used here, so do not treat it as a confirmed intern round.
About this guide
Researched for Codinzhub from three candidate records for this role (one full experience and two Codinzhub records) plus Stripe's official emerging-talent and internship pages, checked in November 2026. Coverage is 2025 internship cycles with outcomes through January 2026. We searched Reddit for this exact role and found relevant posts, but their full text was inaccessible, so no claims were taken from them. We also checked Medium, Glassdoor, Teamblind and aggregators; one accessible additional account duplicated an existing Codinzhub record. Questions were paraphrased, and multi-part follow-ups were not counted as separate questions. Practice problems were matched by reported skill, never presented as exact Stripe questions. Corrections and new experiences are welcome through Codinzhub's contribution and experience pages.
Processes, round names and formats vary by team, location and year. Your recruiter and invitation are the authority on your current process.
Other company and role guides
These are related Codinzhub guides for nearby roles and companies. They are separate guides, not part of this role's evidence. Each link was checked against the published site.
- Stripe Software Engineer Interview Guide
- Amazon Software Engineer Interview Guide
- Microsoft Software Engineer Interview Guide
Editorial completion checklist
- Separate guide for the exact role and level (Software Engineer Intern only)
- Reddit research completed and recorded privately (searches logged; posts found but inaccessible, no claims taken)
- External research expanded when internal experiences were limited (Medium, Teamblind, Glassdoor, aggregators, official pages)
- At least five actual sourced questions per round — four rounds fall short; see table
- Important company-specific findings checked and highlighted (integration round, incremental coding, scoped C/C++ note, location differences)
- Application and shortlisting sections included
- Do's and don'ts included
- Most-asked topics and recurring patterns included
- Matching practice problems included
- Question-bank practice links verified (three Codinzhub records, seven LeetCode pages)
- SEO metadata and beginner readability reviewed
- Contextual Codinzhub links and related guides verified
- External research/resource links excluded from the public article (no Sources section)
- No calendar-based study plan included
- Remaining gaps documented and draft status accurate — status is DRAFT
| Round | Distinct reported questions | Minimum five met | Remaining gap |
|---|---|---|---|
| Online assessment (OA) | 0 | No | 5 missing; no OA problem named in any assigned record |
| Team screen / technical coding | 2 | No | 3 more needed; Reddit/Glassdoor accounts inaccessible or out of scope |
| Final day — programming round | 1 | No | 4 more needed |
| Final day — integration round | 1 | No | 4 more needed; only "Bikemap" named in intern sources |
| Hiring-manager / behavioural | 9 | Yes | None |
Unresolved facts: five named OA questions; three further team-screen questions; four further programming-round questions; four further integration-round questions; read access to relevant Reddit intern posts; confirmation of whether the prep-document language note reflects any current official guidance.
Keep preparing on Codinzhub
- Stripe interview questions and experiences — OA questions and interview experiences candidates shared for Stripe.
- Browse Stripe online assessment questions — filter the Codinzhub question bank by company.
- Amazon Software Engineer Intern interview guide — the Amazon process, rounds and question patterns.
- Google Software Engineer Intern interview guide — the Google process, rounds and question patterns.
- Microsoft Software Engineer Intern interview guide — the Microsoft process, rounds and question patterns.
- All company interview guides — every guide on the Codinzhub blog.
Search the question bank
The questions from each round above, with practice links for similar problems. Log in to search every question we collected for this role, including questions shared on Codinzhub.
Showing 20 of 35 questions
No question content was reported in the assigned records.
Level: Not reported.
Match payments to invoices: by ID (handle no match), then by exact amount choosing the earliest-dated invoice, then within an amount "forgiveness" range choosing the earliest date.
Level: Three staged parts; interviewer said finishing all three was not required.
A coding problem the candidate compared to LeetCode's "Count Mentions Per User" (mentions across timestamped events with online/offline states).
Level: Not reported.
Given subscription records (customer, start date, length in days), produce every lifecycle email in send-date order, such as a welcome email at the start and an expiration email at the end.
Level: More email types in later parts is the natural extension; exact follow-ups not reported.
"Bikemap" task: use an open library/API from its documentation, make requests, parse the response and adapt the docs' examples to the task.
Level: 5 parts total per the candidate; only the general shape is reported.
Describe one of your projects.
Level: Who was on it / role split.
Who was on that project, and how did you divide the roles?
Level: Follow-up to project question.
Describe a time your voice was not heard.
Level: Candidate drifted and was steered back.
How do you set deadlines?
Level: Not reported.
A time when you learned from your mistakes.
Level: Not reported.
What do you value in your career?
Level: Not reported.
Something you could not resolve by yourself.
Level: Not reported.
A situation where you made a quick decision.
Level: Not reported.
Why Stripe?
Level: Not reported.
Incremental multi-part coding
Level: Recurring in every technical account.
Maps and matching
Level: Reported in screen and programming rounds.
Parsing and record modelling
Level: Across coding and integration rounds.
Ordering and tie rules
Level: Invoice and email tasks.
API integration and docs
Level: Both VO accounts.
Behavioural / motivation
Level: One manager chat, nine questions.
Keep track of what you’ve learned.