12 ms·
Yea there's a huge element of randomness to these kinds of interviews. I wasn't a big fan of them at Stripe. You can get some signal like: - do they methodical
by trevor-e 2y ago
Yea there's a huge element of randomness to these kinds of interviews. I wasn't a big fan of them at Stripe. You can get some signal like:
- do they methodically approach the problem?
- do they understand the bug?
- do they know how to use debugging tools?
- do they know advanced debugging tools?
- do they work well in an unfamiliar codebase?
But in practice I'd say most candidates check those boxes, at which point it becomes an arbitrary evaluation unless you pass/fail them based on whether they solved the bug.
- zug_zug 2y agoAs it happens the place I had a really bad experience with it was stripe. I had pretty much aced every other question, but basically was setup with a problem where I didn't have a way to reliably get it running (and I wasn't even clear what the app was supposed to do, it was just some random project off of github). Fortunately I already had an offer onhand from facebook.
- leoqa 2y agoI gave this interview 100+ times and my criteria boiled down to: did they propose a hypothesis and then follow it to a conclusion? Doesn’t matter if it was wrong, just mattered that they were able to falsify it or find the solution. At the end, I would have them walk me through the bug, its cause, and the fix in very high level terms to make sure they could articulate the path we took.