Software Engineer(Internship) applicants have rated the interview process at Stripe with 2.8 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 75% positive. To compare, the company-average is 58.1% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer(Internship) roles take an average of 45 days to get hired, when considering 4 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 4 Glassdoor interviews include:
Presentation: 33%
Phone interview: 33%
One on one interview: 33%
Here are the most commonly searched roles for interview reports -
I applied through an employee referral. The process took 3 weeks. I interviewed at Stripe in Sept 2018
Interview
One of the best interview styles I've witnessed. Applied online with a referral, received a HackerRank challenge. Challenge was pretty simple but different than your typical DS/algorithm question. It was more related to Stripe itself and seemed concentrated on coding style and design. Heard back about two weeks later to set up an phone interview. I was able to schedule my interview only a few days ahead. Phone interview had a similarly-styled question with a follow-up if you complete the first part. Recruiter was kind and attentive. Thought I did pretty well but I received a rejection the next day. Overall the experience was really good - recruiters emailed back within hours when I asked questions and I got feedback from my interview in less than 24 hours.
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.