Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

What is really crazy about this though is that sometimes it really is the interview setting, as people unused to interviews can, at times, emotionally collapse. I have seen people who are actually good programmers get wrecked by simple questions because of their inability to handle stress, and how the lack of interview practice turns a simple exercise into a hellscape.

It's not as if testing for performance under stress is useless: Tough on call rotations happen, and you might need someone that does well under pressure at 3 am in the morning. But the picture you get on a screening isn't as clear as it appears.



Not to imply that you're wrong, but I've always been bad at LC interviews, but surprisingly (for myself) passable when called upon to troubleshoot and code up a hot fix in the middle of the night. Maybe those are not entirely similar types of pressures.


There is a big difference between solving a critical bug, which is your job, vs. passing an arbitrary leetcode test from a disinterested 22 year old where you might lose your house if you get it wrong. You have 15 minutes.


The cure for such fears is to:

1. study the leetcode books in advance

2. do lots of interviews

In the military, there's a saying: train hard => fight easy


It’s also not the same kind of stress. I’ve interviewed many a candidate who were sweating and/or shaking at some point of the interview (with heavy reassurance and me trying to to steer the conversation towards and area where they feel stronger), but they can often end up being calm and reliable alert responders nonetheless. So far I’ve seen very little if any correlation between being able to handle interview stress and on-call stress.


Leetcode performance isn’t going to be representative of 3am incident response though. If that matters, you’re probably better off asking a classic “tell me about a time you responded to a page in the middle of the night” type question.


> Tough on call rotations happen, and you might need someone that does well under pressure at 3 am in the morning.

On a stop-the-world production incident at 3am I know that codebase like the back of my hand, and my job very likely doesn’t depend on whether I solve it in the next 30m. There’s barely anything stressful about it.

On an interview, with my future on the line, and presented with an unfamiliar problem?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: