Everyone on the panel thought they bombed the algorithm question.
But then we heard them speak: they’d onboarded two interns, led a recovery after a production outage, and wrote internal docs so good the team printed them out.
We hired them.
Sometimes, it's not about solving puzzles. It's about showing impact.
(Ask HN: How do you balance storytelling vs coding performance in your interviews?)
But then we heard them speak: they’d onboarded two interns, led a recovery after a production outage, and wrote internal docs so good the team printed them out.
We hired them.
Sometimes, it's not about solving puzzles. It's about showing impact.
(Ask HN: How do you balance storytelling vs coding performance in your interviews?)