Full Stack Engineer applicants have rated the interview process at Stripe with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 33% positive. To compare, the company-average is 45.8% positive. This is according to Glassdoor user ratings.
Candidates applying for Full Stack Engineer roles take an average of 2 days to get hired, when considering 3 user submitted interviews for this role. To compare, the hiring process at Stripe overall takes an average of 26 days.
Common stages of the interview process at Stripe as a Full Stack Engineer according to 3 Glassdoor interviews include:
Phone interview: 100%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 1 week. I interviewed at Stripe in Aug 2019
Interview
The interview with the recruiter was very interesting. The problem was the technical interview which had to be pair programming, instead the interviewer was chatting on slack or on the phone and he didn't even notice that I finished writing the code.
Phone screen -> technical interview -> in person interview.
I was told that they do not do LeetCode type questions and instead ask more holistic questions. However on the interview they only asked standard Leetcode questions.
Interview questions [1]
Question 1
LeetCode type question about managing inventory and lookups. 3 phases.
Recruiter told me it was 60% frontend work and there was no frontend interview. Initial recruiter call, then a backend coding interview and then 3 more backend coding interviews and a manager interview.
A 30-minute HR call first.
Then 60-minute technical interview questions in Zoom. 45 out of 60 minutes are for coding.
Then Virtual Onsites: 5 rounds - 4 technical (3 coding + 1 design) + 1 hiring manager call
Interview questions [1]
Question 1
For the first 60-minute technical interview, the problem is a Leetcode-style question, but more like a small task from a real-world application. There are two parts. The first part is straightforward and the second part is a variation that is built on the first part.
Related to objects and array processing.