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 Full Stack Developer 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. Glassdoor LLC. "Glassdoor," "Worklife Pro," "Bowls" e il relativo logo sono marchi registrati di Glassdoor LLC.

      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 Full Stack Developer

      25 giu 2026
      Candidato anonimo a colloquio
      Toronto, ON
      Nessuna offerta
      Esperienza negativa
      Colloquio difficile

      Candidatura

      Ho sostenuto un colloquio presso Stripe (Toronto, ON) nel mese di mag 2026

      Colloquio

      The process is long tedious and even if you are near perfect its not enough. I did seven rounds in total. This industry is crazy and this interview process is simply not worth your time. There was definitely a real job because on the final loop last two rounds the team members looked excited to meet me. They both said I could be working with them. Maybe it was because I was nervous throughout every interview lol? Honestly though, wouldn't you be nervous af not knowing what the question is going to be and that any misstep in any interview spells doom? Round 1: I did 1 take home Hackerrank Challenge which I passed. Not easy. From what I remember each part expands upon the last so make it modular based code. Round 2: I did an virtual call with two interviewers and completed the hackerrank coding challenge in which I got perfect in all three parts after running the tests. I was surprised because this is such a rarity for me. Usually a few tests fail. Looks like all that leetcode grinding has helped. This led to the final loop where there are five rounds: Final Loop Round 1: Talk with the manager. Standard questions. Maybe I was too nervous? Final Loop Round 2: Api integration round. You use your own IDE. I choose VSC. Do not have autocomplete on. For all I know maybe that's what screwed me. This had four parts in total. It is extremely difficult to do within the allocated time. I completed part 1, and part 2. I didn't get to part 3. Part 2 had a lot to take in. Maybe this is what led to my downfall? If I had more time I would have started part 3. Final Loop Round 3: Bug bash. Also I got to use my own IDE. You need to have your IDE ready to step through code. The fixes are just one liners. Two parts. The first part was relatively easy. The second I actually managed to guess and get right. Maybe its because I guessed it was not enough? I legit didn't understand the context of the question. It was a repo I had to download. I legit didn't understand the MIME types and stuff like that. Part 4 - System design. Three parts. Data model part, pseudo code part and then you draw the frontend part (i.e. success, fail and error states). I thought I did pretty well here too. Part 5 -AI round. Do not trust the AI and obviously don't get it to do everything. I got good feedback here for my approach. I got to part 3 here.

      Altre recensioni di colloqui per Full Stack Developer presso Stripe

      Colloquio per Full Stack Developer

      1 ott 2025
      Candidato anonimo a colloquio
      Toronto, ON
      Nessuna offerta
      Esperienza positiva
      Colloquio nella media

      Candidatura

      Ho presentato la mia candidatura online. La procedura ha richiesto 3 settimane. Ho sostenuto un colloquio presso Stripe (Toronto, ON) nel mese di giu 2025

      Colloquio

      1. HR Screen 2. Engineering Team Screen (not LeetCode-style) 2. Virtual Onsite (4 technical rounds + 1 behavioural) Overall, both the recruiters and interviewers were extremely kind and supportive throughout the process. None of the technical interviews were LeetCode-style problems, which made the experience feel more practical and conversational. The virtual onsite consisted of five rounds in one day, which was a bit exhausting. However, there is an option to split the interviews across two days, and I would definitely recommend taking that option if possible. Another positive point was that the recruiter clearly explained the reasoning behind the final decision, which I really appreciated.

      Domande di colloquio [1]

      Domanda 1

      One of the coding questions involved implementing logic using objects rather than solving an algorithmic-style problem.
      Rispondi alla domanda

      Colloquio per Full Stack Developer

      27 apr 2025
      Candidato anonimo a colloquio
      Nessuna offerta
      Esperienza negativa
      Colloquio difficile

      Candidatura

      Ho presentato la mia candidatura online. La procedura ha richiesto una settimana. Ho sostenuto un colloquio presso Stripe nel mese di apr 2025

      Colloquio

      I had a recruiter screen. Then had a programming interview. Programming interview was on an online IDE. It was multiple parts to the programming question. There was more interviews after but I did not get to those.

      Domande di colloquio [1]

      Domanda 1

      It was a programming question about calculating shipping costs. I did the first 2 parts. My advice, use a dynamic language, get to understand how to use the data. Then dive into solving the problem.
      Rispondi alla domanda
      1