Public preview and process notes

Stripe Frontend Interview Questions and Process

Stripe describes its process only in general terms, so the frontend loop here comes from people who went through it between 2022 and 2026: a recruiter call, an hour of live coding with an engineer, then four or five onsite interviews built around a bug squash, an integration exercise, a programming exercise, frontend design and a talk with the hiring manager. After the rounds come the questions they reported; the bug squash is open to every reader.

17 reported questionsFrontendAtlas practice set: Coding 2 · Debugging 3 · Concepts 1Full practice set requires Premium

Editorial practice groupings, not verified official interview questions or endorsements.

Stripe’s careers FAQ, linked below, says most 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. The rest comes from candidates: frontend accounts on Taro from 2022 to 2026 written from Canada, the United States, Spain, India, Sweden and Ireland, two Blind threads, a LeetCode post on a 2024 software engineer screen, a 2025 intern account on Medium, and web developer accounts from 2017 and 2018 that add behavioural questions.

What public interview reports describe

A multi-part screen, then an onsite of four or five rounds

The recruiter call runs about 30 minutes. The screen is about an hour with an engineer, in CoderPad or in your own editor, on one exercise in parts or two to four short ones, and several accounts let the candidate pick the language. The onsite, virtual in the 2022 and 2024 accounts, held four or five interviews: a bug squash, an integration exercise, one or more programming exercises, a frontend design discussion and a conversation with the hiring manager.

  • A 2022 account from India found the bug squash and the integration round the hardest, and a commenter on a 2024 Blind thread had a hiring manager interview in place of the bug squash. See the onsite stages
  • Timing varies: three weeks of interviews and two more for an answer in a 2023 account, four weeks from screen to offer in 2022, two weeks for a 2025 senior loop.
  • Accounts from 2022 to 2025 say the tasks are set in realistic work scenarios rather than puzzle-style problems. In 2022 a recruiter told a senior candidate to expect a small, self-contained JavaScript component of the kind a component library holds.

Round decoder

The Stripe bug squash: what the round asks and how it runs

The bug squash is an onsite round in which you fix a bug in a codebase you have not seen. In a 2022 loop that ended in an offer, the code was a fork of a real open-source project with an issue describing the problem and failing test cases: the candidate reproduced the failure, walked the code to the root cause, explained the fix, implemented it and ran the whole test suite.

A 2022 Seattle account describes the same kind of task in a forked open-source repository, and a 2024 Canada account a failing unit test in an existing codebase. A 2022 account from India called this round and the integration round the hardest of the loop.

Position in the loop
One of four or five onsite interviews after the screen; a recruiter’s 2024 plan, posted on Blind, put it second, after the programming exercise.
What you get
An existing repository with a reported bug and failing tests; in two 2022 accounts, a fork of an open-source project.
What you do
Reproduce the failing test, find the root cause, explain the cleanest fix, implement it, then run the full suite, in the order the 2022 candidate with an offer gives.
Environment
In the 2024 account most onsite tasks were cloned from GitHub and worked on in the candidate’s own setup.
Swaps
A commenter on the 2024 Blind thread had a hiring manager interview instead, and a 2025 Barcelona account lists bug fixing among four onsite rounds next to deployment, testing and CI/CD.
Sources
Taro accounts from 2022 (two from the United States, one from India), 2023 (Spain), 2024 (Canada) and 2025 (Spain), and the 2024 Blind thread with the recruiter’s plan, listed at the end of the page.

Reported interview process

Stripe frontend interview process

Stripe's careers FAQ says most processes include a recruiter screen, a technical or skills-based assessment and a series of interviews with the team you would join. Frontend accounts from 2022 to 2026 describe a recruiter call, an hour of live coding with an engineer, then an onsite of four or five interviews: a bug squash, an integration exercise, a programming exercise, frontend design and a conversation with the hiring manager.

The onsite rows rest on a handful of accounts and one recruiter's plan posted on Blind, and the mix changes: one candidate had a hiring manager interview in place of the bug squash, and a 2025 account lists bug fixing, deployment, testing and CI/CD among its four onsite rounds. In 2022 and 2024 accounts the recruiter described each interview in advance, so ask for that description. Sources last checked Nov 2026.

Frontend engineers

StageWhat happensWhoReported by
Recruiter screen About 30 minutes with a recruiter, by phone in the 2025 accounts, on your experience, your motivation and the role. One 2022 loop opened with a chat with the hiring manager about the team instead. Frontend engineersOfficial page and 5 reportsNewest: Frontend engineer, United States · Aug 2025
Technical screen 7 reported questions About 60 minutes of live coding with an engineer, in CoderPad or in your own editor. Accounts from 2022 to 2025 describe one exercise built in parts or two to four short ones, a small UI component in some screens and work on data in others; several let you choose the language, and one 2025 screen ran 40 to 45 minutes on Zoom. A 2026 account lists a separate coding exercise between this screen and the onsite. Practice: React fetch and render a listFrontend engineersOfficial page and 12 reportsNewest: Frontend engineer · Jan 2026
Onsite: bug squash 1 reported question Fix a bug in a codebase you have not seen: reproduce it, find the cause and get the existing tests passing. Two 2022 accounts name a fork of an open-source project, and in 2024 the code was cloned from GitHub and run in the candidate's own environment. A commenter on a 2024 Blind thread had a hiring manager interview in place of this round. Practice: Bug squash an unfamiliar invoicing repoPremium task for this roundFrontend engineers7 public reports, 2022–2025Newest: Frontend developer, Spain · Mar 2025
Onsite: integration 2 reported questions Build a working piece of a feature with tools or an API you are given, reading their documentation as you go. A 2023 account describes integrating two provided tools, and a 2025 intern loop gave a private repository, the API documentation and open internet access. A 2022 account from India rated this round and the bug squash the hardest. Practice: Fetch JSON with a timeout and abortFrontend engineers5 public reports, 2022–2025Newest: Software engineering intern, India · Oct 2025
Onsite: programming exercise 1 reported question A coding exercise with an engineer. A 2022 account from India says its questions were real-life scenarios rather than LeetCode-style problems, and a 2024 virtual onsite held three programming exercises, most cloned into the candidate's own environment. Practice: Parse a query stringFrontend engineers5 public reports, 2022–2024Newest: Frontend engineer (L3) · Nov 2024
Onsite: frontend design 3 reported questions A design discussion, talked through rather than coded, about how you would structure a piece of frontend. Accounts from 2022 to 2024 call it frontend system design, an architecture design discussion or a deep dive into design. Practice: Frontend system design blueprintFrontend engineers5 public reports, 2022–2024Newest: Frontend engineer (L3) · Nov 2024
Onsite: manager conversation A conversation with the hiring manager about your past work, how you work and your goals. A 2022 account describes behavioural and past-experience questions to judge culture fit, and a 2022 Seattle loop counted two behavioural interviews among its five. Practice: Behavioral interview guideFrontend engineers7 public reports, 2022–2025Newest: Software engineering intern, India · Oct 2025

3 more reported questions come from sources that do not name the round.

Technical screen: try React fetch and render a list now, a free task we picked for this round.

Start the free task

Questions from Stripe reports

17 questions candidates reported

The first question is open to read; its answer outline opens with a free account. The others show their topic and what is behind the lock; Premium opens all 16 still locked.

Newest account May 2026

Locked questions are Premium, but you can open one free with an account: one per account, across all company guides.

  1. 1

    Bug in an unfamiliar repository

    Open

    Fix a bug in a codebase you have not seen: in 2024 a failing unit test in an existing codebase; in a 2022 United States account, a fork of a real open-source project with an issue and failing tests, where the candidate reproduced the failure, traced the root cause, explained the cleanest fix, implemented it and ran the whole suite.

    Onsite: bug squashPractical codingFrontend software engineer, Canada · Reported in 4 accounts · Apr 2024

    Practice: Bug squash an unfamiliar invoicing repoPremium task

  2. 2

    Four-digit code entry form

    Premium

    Technical screenUI buildFrontend engineer, United States · Reported in 1 account · Aug 2025

    Behind the lock: the question only.

  3. 3

    Passport validation form

    Premium

    Technical screenUI buildFront-end engineer, Sweden · Reported in 1 account · Sep 2025

    Behind the lock: the question only. Its practice task is free for everyone.

  4. 4

    Nested string parsing

    Premium

    Technical screenAlgorithmFrontend developer, Canada · Reported in 1 account · Sep 2025

    Behind the lock: the question only.

  5. 5

    Sorting and filtering employee records

    Premium

    Technical screenJavaScriptFrontend developer, Spain · Reported in 1 account · Mar 2025

    Behind the lock: the question only.

  6. 6

    Transaction data in a JavaScript object

    Premium

    Technical screenJavaScriptFront-end engineer, Canada · Reported in 1 account · Jul 2025

    Behind the lock: the question and a Premium practice task.

  7. 7

    Ordered list with conditional styles

    Premium

    Technical screenUI buildFront-end developer, Canada · Reported in 1 account · May 2024

    Behind the lock: the question only.

  8. 8

    JSON traversal and manipulation

    Premium

    Technical screenJavaScriptSoftware engineer 2 · Reported in 1 account · Oct 2024

    Behind the lock: the accounts' description (they do not share the prompt) and a Premium practice task.

  9. 9

    Finance-themed algorithm problem

    Premium

    Onsite: programming exerciseAlgorithmFrontend engineer, United States · Reported in 1 account · Mar 2022

    Behind the lock: the accounts' description (they do not share the prompt) only.

  10. 10

    String shortening

    Premium

    Round not statedAlgorithmFrontend software engineer, Canada · Reported in 1 account · Apr 2024

    Behind the lock: the question only.

  11. 11

    String encoding and decoding forms

    Premium

    Round not statedReact buildFrontend engineer · Reported in 1 account · May 2026

    Behind the lock: the question only.

  12. 12

    Async code and loops

    Premium

    Round not statedJavaScriptSenior frontend developer, Canada · Reported in 1 account · Sep 2025

    Behind the lock: the accounts' description (they do not share the prompt) only. Its practice task is free for everyone.

  13. 13

    Calls to Stripe production servers

    Premium

    Onsite: integrationPractical codingFrontend engineer, United States · Reported in 1 account · Mar 2022

    Behind the lock: the question only. Its practice task is free for everyone.

  14. 14

    Files and an external API

    Premium

    Onsite: integrationPractical codingSoftware engineering intern, India · Reported in 1 account · Oct 2025

    Behind the lock: the question only.

  15. 15

    Reusable React tooltip component

    Premium

    Onsite: frontend designFrontend system designFrontend software engineer, Canada · Reported in 1 account · Apr 2024

    Behind the lock: the question and a Premium practice task.

  16. 16

    Frontend design of a Stripe page

    Premium

    Onsite: frontend designFrontend system designFrontend engineer, United States · Reported in 1 account · Mar 2022

    Behind the lock: the accounts' description (they do not share the prompt) and a Premium practice task.

  17. 17

    Design breakdown of a given app

    Premium

    Onsite: frontend designFrontend system designFront-end developer, Canada · Reported in 1 account · Jun 2023

    Behind the lock: the accounts' description (they do not share the prompt) only.

Behavioural questions candidates were asked

Open to everyone: 7 questions from 5 public sources.

  • Talk about a project you are proud of, or projects where you made an impact.Reported in 2 accounts · Dec 2025
  • Explain a project you worked on recently that was difficult.Reported in 1 account · Jun 2017
  • How do you stay up to date with the latest technologies?Reported in 1 account · Jun 2017
  • What does an ideal team look like when working on a project?Reported in 1 account · Oct 2018
  • How do you handle deadlines, and how do you break a task down?Reported in 1 account · Oct 2025
  • How do you work with teammates when the requirements are unclear or keep changing?Reported in 1 account · Oct 2025
  • How do you react when something goes wrong?Reported in 1 account · Oct 2025

How to prepare with this grouping

Start with the bug squash

The bug squash leads because its question is the one open to every reader, and a 2022 account gives the round’s steps in order. The free tasks train the habit of reading code you did not write; the Premium repository is the full rehearsal.

  1. Free now
    Fix an off-by-one in a chunk helper

    A teammate’s helper with a boundary bug: write the failing case before you touch the code, as the 2022 candidate did with the issue’s test.

  2. Free now
    Stop a helper mutating its input

    A second fix in code you did not write, where the existing behaviour has to survive the change.

  3. Free now
    Fetch and render a list with loading, error and empty states

    For the hour-long screen: a small component with honest request states, built while you explain it.

  4. Premium
    Bug squash an unfamiliar invoicing repo

    Five files you have not seen and four bug reports, the shape of the bug squash round.

Published by Stripe

Official preparation pages from Stripe

Stripe publishes these pages itself. They describe the process and expectations in the company's own words; they are not a list of the questions you will be asked, and FrontendAtlas is not affiliated with Stripe.

PageWhat it coversChecked
Careers FAQMost processes include a recruiter screen, a technical or skills-based assessment and a series of interviews with the team the candidate would join.Oct 2026

Preparation FAQ

Common questions about Stripe frontend interviews

What is the bug squash round?

An onsite round in which you fix a bug in a codebase you have not seen; in two 2022 accounts it was a fork of a real open-source project with an issue and failing tests. A 2022 account from India called it and the integration round the hardest parts of the loop.

Which language does the screen use?

Your choice in several accounts: the 2025 screens in Barcelona and San Francisco and a 2024 Toronto screen. A 2025 Canada account calls its screen a JavaScript and React interview. Confirm the language with your recruiter.

Does Stripe publish preparation material?

The careers FAQ describes the process in general terms only. In 2022 and 2024 accounts the recruiter explained each interview in advance, and one told a senior candidate what kind of component the screen would ask for.

Try free challenge View pricing

Sources (25)

The links open with a free account. Create a free accountSign in

Each candidate's account describes one loop, not a fixed format.

  • Stripe: Careers FAQ

    An official page read for the process table, where it describes the Recruiter screen and Technical screen. Process context, not interview content.

  • Taro account, around October 2023

    Frontend engineer, Spain · Oct 2023

    A public account read for the process table, where it describes the Recruiter screen, Onsite: bug squash, Onsite: integration, Onsite: programming exercise, Onsite: frontend design and Onsite: manager conversation.

  • Taro account, around August 2025

    Frontend engineer, United States · Aug 2025

    A public account read for the process table, where it describes the Recruiter screen and Technical screen.

  • Taro account, around March 2025

    Frontend developer, Spain · Mar 2025

    A public account read for the process table, where it describes the Recruiter screen, Technical screen and Onsite: bug squash.

  • Taro account, around July 2025

    Front-end engineer, Canada · Jul 2025

    A public account read for the process table, where it describes the Recruiter screen and Technical screen.

  • Taro account, around March 2022

    Frontend engineer, United States · Mar 2022

    A public account read for the process table, where it describes the Recruiter screen, Technical screen, Onsite: bug squash, Onsite: integration, Onsite: programming exercise, Onsite: frontend design and Onsite: manager conversation.

  • Blind account, July 2024

    Senior developer · Jul 2024

    A public account read for the process table, where it describes the Technical screen.

  • Taro account, September 2025

    Frontend developer, Canada · Sep 2025

    A public account read for the process table, where it describes the Technical screen.

  • LeetCode Discuss account, October 2024

    Software engineer 2 · Oct 2024

    A public account read for the process table, where it describes the Technical screen.

  • Taro account, May 2024

    Front-end developer, Canada · May 2024

    A public account read for the process table, where it describes the Technical screen.

  • Taro account, September 2025

    Front-end engineer, Sweden · Sep 2025

    A public account read for the process table, where it describes the Technical screen.

  • Taro account, around June 2025

    Front-end engineer, Canada · Jun 2025

    A public account read for the process table, where it describes the Technical screen.

  • Taro account, January 2026

    Frontend engineer · Jan 2026

    A public account read for the process table, where it describes the Technical screen.

  • Taro account, around April 2022

    Senior frontend engineer, United States · Apr 2022

    A public account read for the process table, where it describes the Technical screen.

  • Taro account, November 2022

    Front-end developer, India · Nov 2022

    A public account read for the process table, where it describes the Onsite: bug squash, Onsite: integration and Onsite: programming exercise.

  • Blind (recruiter plan) account, November 2024

    Frontend engineer (L3) · Nov 2024

    A public account read for the process table, where it describes the Onsite: bug squash, Onsite: integration, Onsite: programming exercise, Onsite: frontend design and Onsite: manager conversation.

  • Taro account, around April 2022

    Frontend software engineer, United States · Apr 2022

    A public account read for the process table, where it describes the Onsite: bug squash and Onsite: manager conversation.

  • Taro account, around April 2024

    Frontend software engineer, Canada · Apr 2024

    A public account read for the process table, where it describes the Onsite: bug squash, Onsite: programming exercise, Onsite: frontend design and Onsite: manager conversation.

  • Medium account, October 2025

    Software engineering intern, India · Oct 2025

    A public account read for the process table, where it describes the Onsite: integration and Onsite: manager conversation.

  • Taro account, around June 2023

    Front-end developer, Canada · Jun 2023

    A public account read for the process table, where it describes the Onsite: frontend design.

  • Taro account, September 2025

    Senior frontend developer, Canada · Sep 2025

    A public account read for the process table, where it describes the Onsite: manager conversation.

  • Taro account, May 2026

    Frontend engineer · May 2026

    A public account read for one reported question.

  • Taro account, December 2025

    Frontend engineer, Ireland · Dec 2025

    A public account read for a behavioural question.

  • Taro account, June 2017

    Web developer, United States · Jun 2017

    A public account read for two behavioural questions.

  • Taro account, around October 2018

    Web designer and developer, United States · Oct 2018

    A public account read for a behavioural question.