[ThrowawayR2]

> "...interviewers know after 20 seconds whether they'll hire someone..."

Without even seeing a single like of code from the candidate? That definitely doesn't translate to tech interviewing. It takes at least 30 minutes to get enough code out of the candidate to form even a first impression.

[bradlys]

> It takes at least 30 minutes to get enough code out of the candidate to form even a first impression.

Yeah, gonna stop you there. It takes less than 30 seconds to get a first impression. That's the whole point of first impressions. As soon as you see a person, you have a first impression.

I've talked to many interviewers - they all agree that they basically have an impression formed within the first few minutes and then use the interview to solidify that impression. It is wildly uncommon for them to come in, have a very negative first impression, and then have it completely turned around by the end.

[ivalm]

Grandop said

> research suggests that interviewers know after 20 seconds whether they'll hire someone.

That’s not first impression, that’s a meaningful ability to see if I hire someone. I can tell you that without seeing code/discussing some previous experience there is zero chance I can form hiring decision for most reasonable candidate (the only 30 second hiring impression I can form is perhaps a negative one).

[brailsafe]

I meant to be less specific than "hire someone", but I'd wager that once a subconscious impression is formed, you'd be more likely to bias your interpretation of whatever else they say.

[ivalm]

Right, I am sure I have a first impression, which could be good or bad, and that impression does inform my later views. However, just objectively I know for a fact that I declined some candidates I initially liked and I hired a few people who initially was super shy/not communicative.