Skip to contentSkip to footer
  • Community
  • Jobs
  • Companies
  • Salaries
  • For Employers
      Notifications

      Loading...

      Elevate your career

      Discover your earning potential, land dream jobs, and share work-life insights anonymously.

      employer cover photo
      employer logo
      employer logo

      Stripe

      Is this your company?

      About
      Reviews
      Pay & benefits
      Jobs
      Interviews
      Interviews
      Related searches: Stripe reviews | Stripe jobs | Stripe salaries | Stripe benefits | Stripe conversations
      Stripe interviewsStripe Software Engineer interviewsStripe interview


      Glassdoor

      • About / Press
      • Awards
      • Blog
      • Research
      • Contact Us
      • Guides

      Employers

      • Free Employer Account
      • Employer Center
      • Employers Blog

      Information

      • Help
      • Guidelines
      • Terms of Use
      • Privacy & Ad Choices
      • Do Not Sell Or Share My Information
      • Cookie Consent Tool
      • Security

      Work With Us

      • Advertisers
      • Careers
      Download the App

      • Browse by:
      • Companies
      • Jobs
      • Locations
      • Communities
      • Recent Posts

      Copyright © 2008-2026. Indeed, Inc. "Glassdoor," "Worklife Pro," "Bowls," and logo are proprietary trademarks of Indeed, Inc.

      Company Bowl sample

      Want the inside scoop on your own company?

      Check out your Company Bowl for anonymous work chats.

      Bowls

      Get actionable career advice tailored to you by joining more bowls.

      Followed companies

      Stay ahead in opportunities and insider tips by following your dream companies.

      Job searches

      Get personalized job recommendations and updates by starting your searches.

      Software Engineer Interview

      Feb 17, 2024
      Anonymous Interview Candidate
      Bucharest, Bucuresti
      No offer
      Neutral experience
      Average interview

      Application

      I applied online. The process took 1 week. I interviewed at Stripe (Bucharest, Bucuresti) in Feb 2024

      Interview

      Phone screen: It contains a code shared session with an interviewer (you can use your own IDE). String manipulation mostly and validation of some edge cases. It is formed as an HTTP problem, but in reality is just a method parsing 2 input params.

      Interview questions [1]

      Question 1

      # Your previous Plain Text content is preserved below: # Part 1 # In an HTTP request, the Accept-Language header describes the list of # languages that the requester would like content to be returned in. The header # takes the form of a comma-separated list of language tags. For example: # Accept-Language: en-US, fr-CA, fr-FR # means that the reader would accept: # 1. English as spoken in the United States (most preferred) # 2. French as spoken in Canada # 3. French as spoken in France (least preferred) # We're writing a server that needs to return content in an acceptable language # for the requester, and we want to make use of this header. Our server doesn't # support every possible language that might be requested (yet!), but there is a # set of languages that we do support. Write a function that receives two arguments: # an Accept-Language header value as a string and a set of supported languages, # and returns the list of language tags that will work for the request. The # language tags should be returned in descending order of preference (the # same order as they appeared in the header). # In addition to writing this function, you should use tests to demonstrate that it's # correct, either via an existing testing system or one you create. # Examples: # parse_accept_language( # "en-US, fr-CA, fr-FR", # the client's Accept-Language header, a string # ["fr-FR", "en-US"] # the server's supported languages, a set of strings # ) # returns: ["en-US", "fr-FR"] # parse_accept_language("fr-CA, fr-FR", ["en-US", "fr-FR"]) # returns: ["fr-FR"] # parse_accept_language("en-US", ["en-US", "fr-CA"]) # returns: ["en-US"]
      Answer question
      93

      Other Software Engineer Interview Reviews for Stripe

      Software Engineer Interview

      Jul 6, 2026
      Anonymous Interview Candidate
      No offer
      Negative experience
      Average interview

      Application

      I interviewed at Stripe

      Interview

      First an OA which is very hard, you have to be really fast. Then HR call and then phone round. Unfortunately I got unlucky and my interviewer was doing something else while doing the interview, he was muted and I had to ask for his attention twice. Of course in the end he said I did very well and one day later I was rejected. The phone round is not particularly difficult but you have to be fast and talking too much will cost you.

      Interview questions [1]

      Question 1

      They have a bunch of questions about string parsing, more often than not you will need to read a CSV so know how to do that, and know how to use the split function.
      Answer question

      Software Engineer Interview

      Jul 1, 2026
      Anonymous employee
      Bucharest, Bucuresti
      Accepted offer
      Positive experience
      Difficult interview

      Application

      I interviewed at Stripe (Bucharest, Bucuresti)

      Interview

      1 round of team screen - go/no go with a multi step problem Design - classic interview Integration - work on integrating some new systems Bug bash - find and solve a bug Programming exercise - same as team screen maybe a bit harder

      Interview questions [1]

      Question 1

      About my previous experience in a large project
      Answer question

      Software Engineer Interview

      Jul 2, 2026
      Anonymous employee
      Accepted offer
      Positive experience
      Average interview

      Application

      I applied through a recruiter. I interviewed at Stripe in Jul 2026

      Interview

      started with a quick recruiter chat (checking developer infrastructure know-how), followed by a 45-min live coding screen where they look for production ready code. onsite was 5 rounds: coding, bug bash, integration, system design, and behavioral. bug bash was the most interesting part. they just drop you into a random repo with failing tests and watch how you track down the root cause. integration is pure API work - reading docs and wiring things up, but they lean heavy on error handling. sys design felt very grounded. instead of drawing huge scalable architecture, we basically just talked through failure modes and backward compatibility.behavioral was standard. across the board, stripe cares way more about readable code and communication than tricky algorithms.for prep, practice reading other people's code and fixing bugs. i had a mock on prepfully with a stripe SWE to test my bug bash process, and it really highlighted some messy debugging habits i had. tough loop, but it actually feels like real engineering.

      Interview questions [1]

      Question 1

      Given a stream of Stripe checkout session events, identify sessions abandoned at each step of the checkout flow and calculate conversion rates
      Answer question