Start free
All Stripe rounds

Stripe · Software engineer · Mid to senior

API / Systems Design

Spoken, collaborative design

What they actually ask

The question shapes this round uses. Larpy does not read these out. It builds each one from your own resume, because the generic version is the one you have already rehearsed.

  • “Design an end-to-end infrastructure service from a one-line requirement, such as a monitoring or metrics service, scoping it yourself before you draw anything.”
  • “Design a public API and its data model, then defend the contract you chose.”
  • “Design a delivery system where the receiver can see an event twice and events can arrive out of order.”
  • “Design a client or service that stays correct when the thing it depends on rejects or drops requests.”

What this round is judged on

  • Problem solving · how effectively you understand the problem and devise a solution for it
  • Design · whether the system is organised with interfaces that are easy to understand
  • Correctness · explicit reasoning about edge and error cases rather than the happy path
  • Communication · you explain your thinking, respond to feedback, and ask when you need more

Where this round sits

Stripe’s published process. Lime marks the stage this round runs.

  1. 01
    Recruiter screen
  2. 02
    Technical / skills-based assessment
  3. 03
    Virtual onsite (the loop)this round
  4. 04
    Debrief and offer
What happens in each stage›
Recruiter screen
Non-technical. Background, motivation, the team and problems you want, level and timeline. Stripe publishes this as the first stage of most of its processes.
Technical / skills-based assessment
A coding round of about an hour, run on a shared editor over video. One problem in several parts, where the interviewer adds the next requirement as you finish the last one.
Virtual onsite (the loop)
Around five rounds of about an hour: a bug squash in an open source codebase, an integration round wiring HTTP calls into an existing project, a systems design conversation, a shorter programming exercise, and a conversation with a manager.
Debrief and offer
Feedback from the loop is collected and the recruiter delivers the outcome. Stripe says timelines vary by role, level and location, and that it tries to work quickly and give clear feedback at every stage.

Sources

Built from what Stripe publishes about its own process. No leaked question lists. The questions you get are generated against your own resume, so they are not from anyone else's interview.

  • companyStripe, Careersstripe.com

    The published stages: most processes include a recruiter screen, a technical or skills-based assessment and a series of interviews with the team you'd be joining, with timelines that vary by role, level and location. Also the traits Stripe names: ownership that extends beyond your own expertise, that you'll fix things that don't belong to you, choosing challenge over comfort, and changing your mind when the evidence shows you were wrong.

  • companyStripe, Careers / Compatibilitystripe.com

    The six operating principles verbatim (Users first, Create with craft and beauty, Move with urgency and focus, Collaborate egolessly, Stay curious, Obsess over talent), the mission phrasing "grow the GDP of the internet", and the expectation that you work outside your domain on problems that did not exist a year ago.

  • companyStripe, On-site interviews for Engineering: What to expect (archived 2017)web.archive.org

    Stripe's own candidate guide: technical interviews simulate the engineering work you'd do day to day, you use whatever language, environment and editor you're most comfortable with on your own laptop, online resources such as docs and Stack Overflow are encouraged, one question is structured around HTTP requests, and one interview has you fix a bug in an open source project. Also the eight dimensions Stripe says it evaluates, and the bar it states as "is this someone we'd actively seek to work with?".

  • companyStripe docs, Idempotent requestsdocs.stripe.com

    Idempotency keys, so a create or update request can be safely repeated after a connection error without performing the operation twice. Background for the retry-safety half of an API design conversation.

  • companyStripe docs, Rate limitsdocs.stripe.com

    That exceeding a limit returns 429 Too Many Requests, and that Stripe tells integrators to retry on an exponential backoff schedule with added randomness to avoid a thundering herd. Background for how a Stripe interviewer expects you to reason about a failing call.

  • companyStripe docs, Paginationdocs.stripe.com

    Cursor-based pagination on Stripe list endpoints via limit, starting_after and ending_before. Background for any walk-the-collection task built against a Stripe-shaped API.

  • companyStripe docs, Webhooksdocs.stripe.com

    That an endpoint can receive the same event more than once, that Stripe does not guarantee events arrive in the order they were generated, and that undelivered events are retried automatically. Background for a delivery-semantics design conversation.

  • reportsRam Patra, Stripe interview for software engineer in Dublinblog.rampatra.com

    A first-hand account naming the same rounds: a multi-part phone screen on a shared editor, then five onsite rounds of about an hour each called Bug Squash, Integration, Design, Programming Exercise and a manager conversation.

Sources last checked . Hiring loops change, so this date is the honest limit on everything above.

Other Stripe rounds