Stripe Interview Experience

Stripe Interview Experience


6 min read


I interviewed for the position of Staff Software Engineer at Stripe in December 2023. They were hiring engineers in the Verification & Identity Platform team. I applied through a referral as that increases your chances of getting shortlisted. For those who haven't heard much about Stripe:

  1. It is one of the big players in global payment products.

  2. In the past, Stripe has been known to be the largest Ruby codebase in the world. They used Sinatra (not Rails) for web apps, so they're not the largest Rails codebase (which Shopify is).

  3. They have a wide tech stack now but their founder explains why they used Ruby to start with. Stripe also has a very popular technical blog.

Note: Stripe asks the candidates to sign a NDA because of which I cannot share the exact interview questions but I'll still share the format of interview and difficulty of questions to some extent.

Interview rounds

  1. Telephonic round with Recruiting team - This was scheduled to understand my role, projects, career goals and set up alignment with the role. The recruiter was based out of Singapore and was taking care of APAC hiring. Although they were not technical, they were expert in explaining the job description and were clearly able to point out things that I was not doing right now in my job role (that they needed for the role). For example, I work as a Staff Engineer at LocoNav which is a small team. So here, my role doesn't involve regularly setting up technical direction for the team but considering Stripe's scale, Staff Engineers are very senior in role and they take care of the same on regular basis. So, they told me before hand that based on my performance, I might be down-levelled if they see a need to do this. This could sound discouraging as the position below Staff Engineer was of Software Engineer but they explained that engineers with the experience range of 0-15 years of experience do fall under this role. This is so because Staff Engineers are very senior in Stripe and they do not have a middle role (i.e. Senior Software Engineer).
    On a side note, I wrote about titles and down-levelling incase you want to understand when it is good or bad for you. Additionally, although the JD mentioned the location as Remote, the recruiter clarified that they're planning to start WFO soon (early 2024) so the location would be Hyderabad/Bangalore.

  2. System Design Round - Staff Engineers at Stripe typically go through two System Design rounds. In each round, there is a Staff Engineer who evaluates your design. In this round, the interviewer was from a different timezone and a very senior person (~10 years senior to me). They explained the problem statement and waited for me to probe for details. While many companies ask for the design of well-known large systems (eg. Youtube, Whatsapp, Google Drive, etc), Stripe is known to ask questions around their own systems only. So the question was related to payments product. This was first ever System Design Interview that I was giving in my career, so I was skeptical on my approach. The problem statement seemed very simple and I queried 2-3 times (like "is this is what I have to build?"). At that time, I was not familiar with the fact that simple problems can also be asked for senior roles, but the expectation of solution is with respect to candidate's expertise/seniority. Just to explain this more - You might have heard that some companies (like Atlassian) have High level design (or System Design) round even for hiring college freshers. At their level, the expectation is that they should understand basic building blocks of the overall system and have some idea on non-functional requirements. The same problem statement can be given to a Senior Engineer where the expectations will be very different. The interviewer can probe into specifics of protocols, choice of databases and so on. For Staff/Principal/Distinguished levels, the discussion can go towards privacy, compliance, regional failovers, disaster recovery etc. I started attempting the question and explained the components of the system and some APIs. I missed one thing around scale of data that the interviewer pointed out. At this point, I realised that exposing an API endpoint is not a good idea and we should have a queueing mechanism like Kafka in between for improved reliability at scale (eg. if consumer system crashes, it can retry from where it left on the Topic).
    Because this was my first ever System Design interview, I was a bit confused during my attempt and the interviewer sensed that. They shared the feedback with the recruiting team that I'm a good candidate but probably I should be considered for a lower level (i.e. Software Engineer). The same was conveyed to me and I agreed to be evaluated again for SE role. The interview process restarted.

  3. Coding round - As per the documents shared with me, Stripe's interview format claims to be very different than big tech companies as they have rounds where you engage more with the interviewer to solve problems and debug issues. For example, their interview process mentions some rounds where you have a codebase ready in which you implement a specific functionality or solve a bug that they've intentionally added. Surprisingly, this round was nothing like that and I was presented with a typical data structures problem 😢. It was a simple problem, again related to their products (i.e. payments). I asked my doubts and implemented the solution that worked. The interviewer modified the problem statement and asked me to accommodate the same in my solution. This one took some time but I was still able to solve it. With this, the interview came to an end and he asked me if I have questions. I asked how many more variations exist in the problem, to which he said "total of five". After the interview, I searched for the problem and found that this question was a typical Google's telephonic interview round question (not one "related to their products") 😲.

After a few days, I was informed through email that I did not clear the round. I thought - maybe I was expected to solve more variations of the problem within the given time because my solution was working for the given cases. As usual, I thought I'd reach out to the recruiter to seek the exact feedback but couldn't do so because they were on new year vacation. They asked me to schedule a slot on their calendar that never loaded on my browser. Even today if I open the link, it keeps loading like this:

LOL. Not blaming it on them. They might have responded if I had mailed them back with the loading issue, but I lost touch due to their vacations and never contacted them again.


It was a good experience with Stripe team. The recruiter was responsive on call/chat/email throughout and ensured timely response. I like their culture of writing that starts from their CTO - something that everyone should do (if they can). I would have performed better in System Design Interview if this was not my first ever HLD interview but no regrets. Failures are integral to the journey of success πŸ“ˆ.

If you liked reading this, I'd suggest a few more:

  1. If you're switching from your role, you might want to understand how levels work across companies.

  2. My recently wrote about my Atlassian Interview Experience for the position of Senior Software Engineer.

  3. If you work remotely, then make sure you're doing it efficiently. I've compiled the best of what I learnt by working remotely in the past 4+ years.