I got a rejection after my Stripe interview, they mentioned they synched with the team and decided not to move forward. It might have been the best coding rounds I have ever given. The original question was about a page or two long and I completed 3 additional questions building on top of that before we ran out of time (~45 minutes). I used python, used pycharm and shared my screen. Went with TDD, 100% test coverage and accurate solution. had about 120 lines of code at the end of the interview. Stripe folks, What are the criteria for the technical round?
Same experience. I don't know why the fuc* are they conducting interviews at first place.
I went through the phone screen, I thought it went alright. Didn't really write any tests. Got through 4 stages of the question. I got very positive feedback and I'm doing the full loop next week. These things are super random 🤷♂️
hi, how was your further interview? can you share details on integration and system design round? I am just done with my coding round. Thanks in advance!
I did 3 or 4 interviews I think. The hardest one was the bug bash, overall I think I did pretty well but did not get the offer. Requested more feedback but the recruiter ghosted me. A meh experience.
Was this tech screen or on-site ? Maybe the non-coding interviews didn’t go as good ?
This was the tech screen
Didnt have any non-coding interview
Being personable is important
Did you try asking the recruiter for feedback?
I did. She said she couldn’t give feedback at this point in the process.
Maybe because you did TDD, idk anyone who does that
I just made it through on-site. I don't even remember the specific problem on the phone screen, but I did write tests. I was also very chatty with the interviewer while we worked through the problem. I also don't remember writing anything close to 100 lines, even with tests. They stated that the care mostly about the quality of your code and abstractions.
TDD is very good for Stripe interviews. So long as you can manage the question in the time allotted (speed matters, even if it's not explicitly measured).
Based on your description alone, I would have expected you to pass. Could the interviewer have seen some non-technical red flags and arrived at a “no hire” response? Otherwise, I’d chalk it up to bad luck and move on (sucks but it happens).
Agree that the current description looks like a pass. Could have been communication-related? Usually candidates writing tests + covering edge cases on their own is a yes. I have seen candidates fail because they didn't communicate, but usually you'd need to get marked down by 4+ interviewers before it's considered too much.
Be glad you didn’t make it! You would be spending all your time fire-fighting and cleaning up other people’s shit! There’s gabillion firms you can goto from MS that are better than Strip
Sarcasm?
Nope! Sad reality!!
Testing is important. Getting through the required number of parts is important. Debugging efficiently is important. The rest is about getting a decent interviewer I suppose. Most interviewers I've seen try to stay objective and unbiased, but that's not always the case
You gotta be an endangered species to pass
Now I feel special.