Stripe · Software engineer · All levels
Conversational and logistical
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.
Stripe’s published process. Lime marks the stage this round runs.
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.
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.
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.
Stripe's engineering ladder as reported by submitted offers: L1 at entry through L6, with L4 named Staff Engineer, which is what the level labels on these rounds map to.
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.
Conversational but probing
Spoken, collaborative design
One problem, added to part by part
Extend an existing project against unfamiliar libraries
Fix a real bug in a public open source project
A short algorithmic exercise, deliberately not the bar