3 ms·
I don't know why you would want to make time pressure a feature in your interview process. Normally it only happens because there's a fixed number of questions
by avianlyric 5y ago
I don't know why you would want to make time pressure a feature in your interview process. Normally it only happens because there's a fixed number of questions that people want to ask, but they're unprepared to allocate more an a hour to do so.
I fail to see how creating artificial time pressure makes your interview process better at finding good candidates. It results in an environment that isn't even vaguely like actual work conditions.
- Jabbles 5y agoIf I allocate more time to each interview question, then how am I supposed to judge between a candidate that completes it in half the allotted time vs one that completes it using all the time? Whether the time pressure is explicitly mentioned, it is clear (to me) that there is an implicit expectation that the faster you answer the question, the better, all other things being equal. I don't want to give the impression that I think the current standard of software engineering interviews are perfect, so if you think it can be improved, please tell me how.
- xboxnolifes 5y agoIf you want to use speed as a measure, then you can't avoid time pressure. But you don't need to use speed as a measure.
- avianlyric 5y ago> If I allocate more time to each interview question, then how am I supposed to judge between a candidate that completes it in half the allotted time vs one that completes it using all the time? How about you judge them on the quality of their answers? Is giving a long more detailed and nuanced answer a bad thing?