• Extremely challenging engineering interviews
• Known for being one of the best places to work as an engineer
• Compensation is very high even when compared to other tech companies

The interview process takes 2-4 weeks on average.

Stage 1: A phone screen which is composed of two parts. The initial part is a 30 min chat with a recruiter to go over your resume, work experience and the areas of Stripe that you are interested in. The second part is a technical screen with an engineer which consists of a 60 min coding session to solve a 2-part problem over a screen share in an editor/language of your choice.
Stage 2: A follow-up with the recruiter to schedule and explain the onsite interview. The recruiter also mentions which teams might be a good fit for you, then asks you to decide which team you would like to interview for.
Stage 3: An onsite interview consisting of five parts, a pair programming interview (build a script/tool that solves a particular problem), a bug hunt (fixing a bug in a large unknown codebase - in a language of the your choice), and system design and implementation. In between all of that, there is lunch with an engineer 'lunch buddy' and the last interview is a behavioral/culture interview with the engineering manager.

The interview process takes 4-8 weeks on average.

Stage 1: A take home project
Stage 2-3: Two technical phone screens.
Stage 4: An onsite interview consisting of 6 back to back interviews, each 45 about minutes long.

The interview process takes 4 weeks on average.

Stage 1: A phone screen with HR.
Stage 2: A video conference Interview'with a PM, with a focus on your execution of ideas.
Stage 3: A take home exercise on a generic PM problem, how do you write a solution and communicate that solution to the broader team and senior management => metric x is going down, why, what do you do? draft email to your team and also to the CEO
Stage 4: An onsite consisting of 5 interviews with the following people - an engineering manager, a design manager, a few PMs (product sense), a hiring manager (behavioral, management style and some execution ), a data scientist, as well as a chat with a senior leader at Stripe.

• How would you design and architect a system that developers can use to run validity/correctness checks in production? (involved coding it as well)
• Implement a key-value store with history (through timestamps)
• Given a bug report (on a private Github repo they invite you to), clone the project and try to find the bug and fix it
• (Skype + screen share coding problem) Implement a system to keep track of, allocate and deallocate server names
Design a system to detect and implement API rate-limiting for a server.
Design and build a merchant dashboard from scratch
Store Foursquare-style location check-ins and figure out where a user is at a given time
Write the code to replay a list of HTTP requests from a file represented as JSON
Design an API for tracking events in different clients
Write a map implementation with a get function that lets you retrieve the value of a key at a particular time. t:0 A =1 t:2 A = 2 get(A, t:1) -> 1 get(A, t:3) -> 2
Are there any parts of the development process don't you like doing? Why?
Fix a bug in a large codebase you have never seen.
Write a stateful HTTP client for Stripe API using your favorite framework in your favorite language.

• How would you choose between the subscription and the market-place based options i.e. evaluate which would be better for the business in the long run?
• Can you share a project experience that shows how you collaborate with others?
• Standard SQL and communication questions.

-

• Video-conference on product execution - classic execution, how do you measure the success of a given product, define a north star metric for a given product, how do you move the metric, how do you set goals, metric x is going up/down, why?
• Interview with engineering manager - focused on figuring out how you work with engineers, technical understanding of products you built, why you made some of the technical choices, how do you remove roadblocks, how do you push back against engineers etc.
• Interview with design manager - focused on how you think about products from a design perspective, product you like/dislike and why, how to improve a stripe product from a design perspective, how would you design a product for x (could be anything, try to be as specific and clear as possible)
• Interview with PMs - focused on Product Sense, a little bit about previous work but mostly focused on why you like/dislike a product, how to improve x, how to improve adoption of a Stripe product, if you built app y from scratch what/how would you build?
Interview with hiring manager - questions about your weaknesses and strengths as they relate to product management, how you improve/leverage them with examples, questions about managerial style and how you set people up for success, some generic estimation/root cause question about a tech product (uptick [pick an action] for product x in a given locale for a given week, why?)
GTM plan and market sizing for a Stripe product.

Mission

Our mission is to increase the GDP of the internet