J'ai postulé via la recommandation d'un employé. Le processus a pris 4 semaines. J'ai passé un entretien chez Stripe (San Francisco, CA) en juil. 2021
Entretien
- system design interviews (2 of them)
- technical discussion interview - do a writeup or presentation on a complex problem you solved or project you were on
- adaptability interview focuses on work style, culture fit; is behavioral
- coding interview
the process is very streamlined and typical of other tech companies
J'ai postulé en ligne. J'ai passé un entretien chez Stripe (New York, NY) en avr. 2026
Entretien
An intro screen call with a recruiter, followed by 2 hour-long initial assessment interviews for coding (not leetcode) and system design. After the assessment rounds came a longer loop consisting of an hour-long "integration" coding session involving working with an existing codebase and interacting with external APIs, a 45-minute "adaptability" behavioral session, a 45-minute technical discussion involving presenting and answering questions about a former software project to other software engineers, and finally an hour-long career history discussion with the hiring manager. Overall everyone from the recruiter to the interviewers were very friendly and helpful.
Questions d'entretien [1]
Question 1
Describe a time you disagreed with a colleague about the direction of a project.
started with technical recruiter screen. then scheduled a technical interview (coding and architecture) round. after that is more specific sessions with the team and other non-technical people. process took a little more than a week start to finish and the stated goal was two total weeks
Questions d'entretien [1]
Question 1
architecture problem was around scaling a global system
coding was a series of increasing complexity and requirements
J'ai postulé en ligne. Le processus a pris 3 semaines. J'ai passé un entretien chez Stripe (Toronto, ON) en sept. 2025
Entretien
7 stages.
- Screening call
- initial code challenge
- 4 more code challenges
- behavioural
The 4 code challenges and behavioural are schedules as a panel, all in one day, an hour each, or you can split them into two days. Interviewers seem to be chosen at random, and are not necessarily going to be a part of your team.
I applied for staff developer role, backend, and they for some reason put me through a full stack interview process. One of the challenges I got was about frontend code, which was not supposed to be a part of my process (and my HR representative agreed), but nothing was done to correct this mistake.
Questions d'entretien [1]
Question 1
- consume an api endpoint
- create a formatted report from some raw json data
- reformat some data from one raw format to another, add filtering capabilities
- find a bug in an opensource library
- create Ui element that shows a list of items, add different distinguishing elements to some of the line items.
- discuss a project you worked on in the past, how did you ideate it, pitch it, how did you break it down, minimize risk, what went well, what didnt go well, how did you approach buy-in, stakeholder management, deadlines, delivery.