Start free
All Stripe rounds

Stripe · Software engineer · Mid to senior

Integration Round

Extend an existing project against unfamiliar libraries

What this round is judged on

  • Navigating codebases · you can find your way around unfamiliar code and work out what is going on
  • Tools familiarity · you are set up to write code and can actually run it in your chosen environment
  • Correctness · explicit reasoning and tests to check correctness, and whether you consider edge and error cases
  • Programming language familiarity · comfort with the language you chose, and whether your code is idiomatic for it
  • Communication · you explain your thinking clearly, respond to feedback, and ask for help when stuck

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 and from real interview data. 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?".

  • dataJulia Evans, Tell candidates what to expect from your job interviewsjvns.ca

    An engineer who co-edited that guide at Stripe, confirming what it is and what the loop tested in practice: candidates were not interviewed for algorithms expertise, using Stack Overflow during an interview was fine, and the debugging round required a local dev environment able to install a library and run the tests.

  • 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, 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.

  • 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