My experience interviewing at Stripe has surpassed every other company by a wide margin. Every person I spoke and met with was nice, smart, and professional. The recruiters give you just the right amount of preparation material about what the next steps are. Along every step, the recruiters are mindful and respectful of your timing and needs. The entire process consisted of:

1. Recruiter phone screen: 30-minute chat about work experience, what you're looking for, which areas of Stripe you're interested in working on, etc.

2. Technical phone screen: 1-hour coding session to solve a 2-part problem (second part builds on top of the first part) over a video call where you share your screen with an engineer.

3. Recruiter follow up: 30-minute chat about feedback from the phone screen, and if it was positive, an overview of the onsite interviews. The recruiter also talked about a few teams that might be a good match, and you can tell them which one you'd like to interview for. During the onsite, you'll meet with the engineering manager from that team.

4. Onsite: A full day of interviews on 1) building a script/tool that solves a particular problem, 2) creating an UI that handles user input, 3) fixing a bug in a large, unknown codebase (in a language of your choice), 4) solving a coding problem similar in difficulty to the phone screen exercise, and 5) behavioral/cultural interview with an engineering manager. You'll also have lunch (the food is very delicious and healthy) with an engineer, as well as a 15-minute chat with your recruiter.

For both the phone screen and onsite, the technical interviews consisted of working on problems that you may actually face as a Stripe engineer. You won't be asked to solve esoteric questions that appear on CS midterms (space & time complexity, red-black trees, bit manipulation, etc.). Instead, the exercises mirror real-life situations, and you should solve them as such—using docs and StackOverflow, asking clarifying questions, writing tests, and debugging in a REPL as you go. Before you come onsite, you can even set up some boilerplate code so that you don’t waste precious interview time on setting up a project from scratch. Make sure you communicate clearly, ask the right questions, address edge cases, display good coding intuition, and write correct & readable code.

NDA.