3 ms·
You were always qualified and they shouldn’t have rejected you the first time. This is an example of what not to do on the hiring managers part.
by flappyeagle 4y ago
You were always qualified and they shouldn’t have rejected you the first time. This is an example of what not to do on the hiring managers part.
- faraaz98 4y agoNo I was very unprepared, even I could tell
- flappyeagle 4y agoAs an interviewer, my job isn't to judge whether a candidate is prepared. My job is to judge whether they can do the job. If the interviewer says "I think you're a good engineer", the next sentence should be "we would like to make you an offer". If I could hire people by reading their mind and understanding their ability, without requiring an ounce of preparation, I would do that.
- munchbunny 4y agoI disagree that the second sentence follows from the first. Interviewing is a game of incomplete information, and you won’t find consensus among programmers for how they would rather be interviewed. It’s entirely possible that the candidate was just off their game that day, or they weren’t “warmed up”. I get noticeably better at interviewing after the first few. It happens, but the interviewer has the information they got, and it’s not possible to totally control for that kind of variance. What hiring managers should be actively minimizing, that most hiring managers I’ve seen do not, is variance that their interview process introduces by, for example, not standardizing and training their interviewers.