SWE Intern applicants have rated the interview process at Stripe with 3.1 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 50% positive. To compare, the company-average is 45.8% positive. This is according to Glassdoor user ratings.
Candidates applying for SWE Intern roles take an average of 21 days to get hired, when considering 12 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 SWE Intern according to 12 Glassdoor interviews include:
Phone interview: 40%
One on one interview: 20%
Skills test: 20%
Presentation: 20%
Here are the most commonly searched roles for interview reports -
It was a phone interview and they are friendly and patient. They gave me an HTTP-related question. And it is fairly easy with python. Just using hashmap and list should be enough.
A university recruiter reached out to me on LinkedIn and recommended that I apply. Soon after I did, I received a 90 min HackerRank question. Next, a 1hr technical interview. Then two 1hr back to back technical interviews, and finally a 30min nontechnical interview with an engineering manager. A week an a half later, I had a zoom meeting with the recruiter where we discussed my opinions on the process and they shared interviewer feedback. The whole process took close to two months and 5 hours of interviewing. All of my interviewers were kind and their questions interesting, and I thoroughly enjoyed the process.
Interview questions [1]
Question 1
I won't say any actual questions, but they were rather practical and not the usual leetcode style. Generally they were a mini version of a real plausible task. They involved writing clear, idiomatic code, using real libraries, and were completely open resource — yes, Stack Overflow included. Make sure to explain your work, be open when you don't know something, and ask questions if you need to. They want to know what it would be like to work with you, not whether you can find and implement the most optimized solution in three minutes without hints or debugging. However, I do suggest familiarizing yourself with APIs/HTTP requests beforehand.