Two rounds at Stripe, and one part short

Interviews   · 1 min read

CompanyStripe
RoleSoftware Engineer, New Grad
LocationVirtual
DateNovember 2025
How it startedCold application
Rounds2, an online assessment and one interview
OutcomeRejected after the interview

The language I chose has now cost me two loops. This was the first, two months before Bloomberg.

The format

A Stripe round is not one problem. It is one problem in four parts, each built on the one before, and a part has to pass before the next one opens. So the score is not whether you can solve something. It is how far you get before the hour runs out.

RoundWhat it wasProblemHow far I got
1Online assessmentObject-oriented design in four parts. HardPassed
2InterviewString manipulation in four parts, the same formatThree parts of four

The mistake was the language

I wrote the interview in C++. In a format that rewards how much working code you produce in an hour, that was the wrong call, and the problem made it worse. String manipulation is where Python is shortest: splitting, slicing, dictionaries and formatting are a line each, and in C++ each of them takes several. Less code would have meant faster code, and I think it would have been enough to finish the fourth part.

Then again at Bloomberg

Two months later C++ cost me again, for a different reason: at Bloomberg the interviewers could not read it. Stripe was a speed problem and Bloomberg a communication one, but they come from the same habit, reaching for the language I think fastest in without asking whether it suits the round.

← All writing