Stripe · Software engineer · All levels
Recruiter Screen
Conversational and logistical
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.
- “Walk me through your background and what you're working on right now.”
- “What's drawing you to Stripe specifically, and why now?”
- “What kinds of problems or teams are you hoping to work on, and what level do you see yourself at?”
- “What's your timeline, and are you interviewing anywhere else?”
What this round is judged on
- Motivation · genuine pull toward Stripe's mission and the specific team
- Background fit · your experience mapped to the role and level
- Communication · a clear, concise account of what you've built
- Logistics · timeline, location, and process alignment
Where this round sits
Stripe’s published process. Lime marks the stage this round runs.
- 01Recruiter screenthis round
- 02Technical / skills-based assessment
- 03Virtual onsite (the loop)
- 04Debrief 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.
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.
Other Stripe rounds
- Hiring Manager / Behavioral
Conversational but probing
- API / Systems Design
Spoken, collaborative design
- Technical Phone Screen (Practical Coding)
One problem, added to part by part
- Integration Round
Extend an existing project against unfamiliar libraries
- Bug Squash / Debugging
Fix a real bug in a public open source project
- Programming Exercise
A short algorithmic exercise, deliberately not the bar