The interview consisted of 45 minutes of coding, followed by 10 to 15 minutes of me asking questions about Stripe.
The questions were pasted into a CoderPad session. You could either use CoderPad to work or share your screen and use your own environment. You were encouraged to use the language you are most comfortable with. Tests should also be written, covering primary and edge cases. You did not need to grind LeetCode or similar sites for this interview.
I felt the interview went well. I explained my thought process clearly to the interviewer, asked good clarifying questions about the prompts, debugged tests when they failed for unexpected reasons, and apparently even taught the interviewer some things about Ruby they weren't previously aware of. However, I was still rejected with no real feedback as to what I missed or didn't do.
Iterating through items in a string to find matches in a collection, in a specific order.
The following metrics were computed from 1 interview experience for the Stripe Backend / API Engineer role in San Francisco, California.
Stripe's interview process for their Backend / API Engineer roles in San Francisco, California is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Stripe's Backend / API Engineer interview process in San Francisco, California.