How do I prepare for Stripe Backend SWE interview ?

Nike / IT
tofu’s

Go to company page Nike IT

BIO
Software Engineer
tofu’s
Apr 6 7 Comments

Hey all you amazing developers,
I am about to schedule a technical round with Stripe and have a lot of questions.

What time line is good to prepare for the technical round ?

What exactly do I expect ? - I get a lot of answers saying it’s real world problems but that is a bit vague. How do I prepare for it ? They say no LC but in some blogs I do see some LC String problems.

Also what is a good timeline to prepare for all rounds ?

Where can I get mock interviews for this company specifically ? Is anyone willing to take a mock interview ?

YOE: 5
Current TC: 🥜🥜

Really need to switch jobs current pay and team is the worse. Any help would be greatly appreciated.

Thanks. 🙏

#tech

comments

Want to comment? LOG IN or SIGN UP
TOP 7 Comments
  • Google
    brocoIiman

    Go to company page Google

    brocoIiman
    Phone screen is like LC easy/medium with multiple parts that build on one another. They focus on readability, completeness, and testing.

    Coding round is the same.

    Debugging round is when you are presented with an unfamiliar repo and a GitHub issue. Find the bug and fix it if you can.

    Integration round is stitching together some REST APIs to produce the expected results.

    Behavioral round with manager for fit/leadership/etc.

    If you are applying for Frontend, you have an interactive UI component round.

    If you are applying for full stack, you could choose the UI round or opt for a system design round.

    If you are applying for back end or infra, you go through a system design round.

    TBH, you can only realistically prepare for coding and system design… other rounds would be easy if you already do them at your job… but they will be incredibly difficult if you are not exposed to them day-to-day.
    Apr 6 4
    • Google
      brocoIiman

      Go to company page Google

      brocoIiman
      Aside from googling the exact issue description verbatim, you can pretty much look anything up during the interview. They want to see you dive into an unfamiliar codebase and quickly reason out where the potential bug is. You can step through the code and think about what the expected behavior should be. Then you can use debugger or print to console and narrow down the problematic areas. It is important to talk about which part of the code IS working to help you uncover which part ISN’T working. Keeping track of states in your head also helps with debugging. I don’t think it is required to find/fix the bug to pass… but try your best?

      I didn’t get APIs for coding rounds. But integration rounds kinda need APIs to be meaningful.

      Lastly I was told to prioritize progress over optimal solution. So if you have been LC med/hard then you will be okay :)
      Apr 6
    • Nike / IT
      tofu’s

      Go to company page Nike IT

      BIO
      Software Engineer
      tofu’s
      OP
      Thanks a lot. That is very helpful!
      Apr 6
  • Stripe
    BigMouth🐟

    Go to company page Stripe

    BigMouth🐟
    Your recruiter should share a google doc with what to expect in each interview session.
    Apr 6 1