Passa al contenutoPassa al piè di pagina
  • Lavori
  • Aziende
  • Stipendi
  • Per le aziende

      Migliora la tua carriera

      Scopri le tue potenzialità di guadagno, trova lavori da sogno e condividi approfondimenti su lavoro e vita privata in forma anonima.

      employer cover photo
      employer logo
      employer logo

      Stripe

      Questa è la tua azienda?

      Chi siamo
      Recensioni
      Stipendi e benefit
      Lavori
      Colloqui
      Colloqui
      Ricerche correlate: Recensioni su Stripe | Offerte di lavoro di Stripe | Stipendi di Stripe | Benefit di Stripe
      Colloqui di StripeColloqui per Software Engineer presso StripeColloquio di Stripe


      Glassdoor

      • Chi siamo
      • Contattaci

      Aziende

      • Account Business gratuito
      • Spazio per le aziende
      • Blog per le aziende

      Informazioni

      • Aiuto
      • Linee guida
      • Condizioni d'uso
      • Privacy e scelte pubblicitarie
      • Non vendere né condividere le mie informazioni
      • Strumento per l'accettazione dei cookie

      Lavora con noi

      • Inserzionisti
      • Carriere
      Scarica l'app

      • Cerca:
      • Aziende
      • Lavori
      • Località

      Copyright © 2008-2026. Indeed, Inc. "Glassdoor," "Worklife Pro," "Bowls" e il relativo logo sono marchi registrati di Indeed, Inc.

      Aziende seguite

      Non lasciarti sfuggire opportunità e informazioni privilegiate seguendo le aziende dove vorresti lavorare.

      Ricerche di lavoro

      Ricevi suggerimenti e aggiornamenti personalizzati avviando le tue ricerche.

      Colloquio per Software Engineer

      31 mag 2018
      Candidato anonimo a colloquio
      San Francisco, CA
      Nessuna offerta
      Esperienza positiva
      Colloquio facile

      Candidatura

      Ho presentato la mia candidatura tramite segnalazione di un dipendente. La procedura ha richiesto 2 settimane. Ho sostenuto un colloquio presso Stripe (San Francisco, CA) nel mese di mag 2018

      Colloquio

      I was exploring some other remote opportunities, and I knew someone who worked at Stripe so I decided to check things out to see if it might be a good change of scenery. First I had a phone call with a recruiter who told me about the company and the engineering teams. Then set up a technical screen that was conducted over Zoom (the format was "pair programming"). I did virtually no preparation as the other responses on Glassdoor signaled that the technical interview question would be more of a real world problem (server provisioning) and I figured there wasn't much I could do to ready myself for that. I was expecting to be evaluated on things like SOLID design principles, etc. In the end my technical interview focused on comparators, and most of the content of those questions felt like they might have come straight off a site like hackerrank or the like. Each question built off the last. None of it was particularly difficult, but I must say the format of the interview had me pretty nervous and it was really tough to focus. Because the interview is only ~45min long, you also don't have time to read through the specifics of any of the problems. The interviewer summarizes things, and you jump into implementing code that makes some tests pass, bouncing ideas and questions off the interviewer as you go. I ultimately got hung up on one of the last questions we worked on, not because the question itself was particularly difficult, but the explanation was a bit fuzzy in the moment. Overall the experience was good. The interviewer was also very engaged and professional. I mostly kick myself for not taking the whole thing a bit more seriously. The technical problems ultimately didn't feel terribly relevant and likely wouldn't resonate with a lot of the day to day work of most developers (I've done full stack dev for the last decade, building lots of complex systems, and I can't recall the last time I did work resembling this).

      Domande di colloquio [1]

      Domanda 1

      Comparators
      Rispondi alla domanda
      3

      Altre recensioni di colloqui per Software Engineer presso Stripe

      Colloquio per Software Engineer

      6 lug 2026
      Candidato anonimo a colloquio
      Nessuna offerta
      Esperienza negativa
      Colloquio nella media

      Candidatura

      Ho sostenuto un colloquio presso Stripe

      Colloquio

      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.

      Domande di colloquio [1]

      Domanda 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.
      Rispondi alla domanda

      Colloquio per Software Engineer

      1 lug 2026
      Dipendente anonimo
      Bucarest,
      Offerta accettata
      Esperienza positiva
      Colloquio difficile

      Candidatura

      Ho sostenuto un colloquio presso Stripe (Bucarest, )

      Colloquio

      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

      Domande di colloquio [1]

      Domanda 1

      About my previous experience in a large project
      Rispondi alla domanda

      Colloquio per Software Engineer

      2 lug 2026
      Dipendente anonimo
      Offerta accettata
      Esperienza positiva
      Colloquio nella media

      Candidatura

      Ho presentato la mia candidatura tramite un selezionatore. Ho sostenuto un colloquio presso Stripe nel mese di lug 2026

      Colloquio

      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.

      Domande di colloquio [1]

      Domanda 1

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