Software Engineer(Internship) 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 63% positive. To compare, the company-average is 45.8% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer(Internship) roles take an average of 28 days to get hired, when considering 56 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 Software Engineer(Internship) according to 56 Glassdoor interviews include:
Phone interview: 33%
One on one interview: 25%
Skills test: 17%
Presentation: 13%
Personality test: 4%
Background check: 3%
Other: 3%
IQ intelligence test: 1%
Group panel interview: 1%
Here are the most commonly searched roles for interview reports -
I applied through college or university. The process took 1 week. I interviewed at Stripe in Oct 2018
Interview
1 hour phone interview where they can see you and your computer and you code the solution to a HackerRank style problem and essentially do virtual "whiteboarding". You will be observed by a current engineer and there is also an entry-level engineer observing you. Onsite interview are only 2 interviews long (plus casual lunch interview) for interns.
Interview questions [1]
Question 1
Read in a list of dictionaries and return the dictionary with the largest instance of a key given. Also with additional constraints and edge cases provided.
There was a recruiter call where they told me what to expect for the next couple rounds. I had a call with the hiring manager and technicals with 2 other engineers.
I applied and got an interview offer in about 2 weeks. I interviewed with someone from the US even though i applied for Bucharest. A bit of introduction and HR style questions in the beggining, followed by 2 problems.
The first step is a HackerRank challenge, typically 60 minutes long, consisting of one question broken into 3 parts/sub-tasks. The question is implementation-heavy rather than a typical dynamic programming or graph puzzle.