Aller au contenuAller au pied de page
  • Emplois
  • Entreprises
  • Salaires
  • Pour les employeurs

      Boostez votre carrière

      Découvrez votre salaire potentiel, décrochez des emplois de rêve et partagez vos témoignages de manière anonyme.

      employer cover photo
      employer logo
      employer logo

      Stripe

      Est-ce votre entreprise ?

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur Stripe | Offres d’emploi chez Stripe | Salaires chez Stripe | Avantages sociaux chez Stripe
      Entretiens chez StripeEntretiens d’embauche pour Software Engineer chez StripeEntretien chez Stripe


      Glassdoor

      • À propos
      • Récompenses
      • Blog
      • Nous contacter
      • Guides

      Employeurs

      • Compte employeur gratuit
      • Centre employeur
      • Blog pour les employeurs

      Informations

      • Aide
      • Règles de la communauté
      • Conditions d'utilisation
      • Confidentialité et choix publicitaires
      • Ne pas vendre ni partager mes informations
      • Outil de consentement aux cookies

      Travailler avec nous

      • Annonceurs
      • Carrières
      Télécharger l'application

      • Parcourir par :
      • Entreprises
      • Emplois
      • Lieux

      Copyright © 2008-2026. Indeed, Inc. « Glassdoor », son logo, « Worklife Pro » et « Bowls » sont des marques déposées de Indeed, Inc.

      Entreprises suivies

      Tenez-vous au courant des dernières opportunités et profitez de conseils d’initiés en suivant les entreprises de vos rêves.

      Recherche d’emplois

      Obtenez des recommandations et des mises à jour personnalisées en démarrant vos recherches.

      Entretien pour Software Engineer

      9 nov. 2017
      Candidat à l'entretien anonyme
      Orlando, FL
      Aucune offre
      Expérience négative
      Entretien facile

      Candidature

      J'ai postulé via une autre source. Le processus a pris 4 semaines. J'ai passé un entretien chez Stripe (Orlando, FL) en oct. 2017

      Entretien

      I have a mixed feeling about the whole process. They contacted me at GHC in early-Oct, first round interview was a pair-coding one, the interviewer was your "partner", I enjoyed the experience so much and it's so special compared to all the companies I interviewed at. Soon Stripe became a company on my dream list. A week later, they emailed me to say something about the next step. I had an offer deadline, I told them it might be better to speed up the process, but the recruiter was too busy to "read" my email. Later, the recruiter said my onsite interview would be on mid-Nov. What? I already finished my first round in early-Oct, then my onsite would be on mid-Nov? I said I would visit SF before mid-Nov so I didn't need them to book anything if the interview could be scheduled earlier, then a long silence. Now I've already accepted another offer, but hey, Stripe, you are a unicorn, why do you move so slow? I know recruiters are always busy during the recruiting season, but Stripe's recruiters seem to be much busier. Overall, I like my experience talking to their engineers, but I am disappointed with their slow and unorganized interview process.

      Questions d'entretien [1]

      Question 1

      Algorithm, not necessary to be bug-free, but you need to detect the bug quickly.
      Répondre à cette question
      1

      Autres retours d’entretien d’embauche pour un poste comme Software Engineer chez Stripe

      Entretien pour Software Engineer

      6 juill. 2026
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience négative
      Entretien moyen

      Candidature

      J'ai passé un entretien chez Stripe

      Entretien

      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.

      Questions d'entretien [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.
      Répondre à cette question

      Entretien pour Software Engineer

      1 juill. 2026
      Employé (anonyme)
      Bucarest,
      Offre acceptée
      Expérience positive
      Entretien difficile

      Candidature

      J'ai passé un entretien chez Stripe (Bucarest, )

      Entretien

      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

      Questions d'entretien [1]

      Question 1

      About my previous experience in a large project
      Répondre à cette question

      Entretien pour Software Engineer

      2 juill. 2026
      Employé (anonyme)
      Offre acceptée
      Expérience positive
      Entretien moyen

      Candidature

      J'ai postulé via un recruteur. J'ai passé un entretien chez Stripe en juill. 2026

      Entretien

      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.

      Questions d'entretien [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
      Répondre à cette question