Re:How to Interview Engineers
by jjav on Tuesday October 13, 2020 @04:25AM
(#24763456)
> but no one wants to go out on a limb and make suggestions about how to improve it.
That's not really true, plenty of suggestions on how to improve it. Many of those based on experience doing it for the long haul.
Personally I always advocate for a technical discussion of their experience. Read the resume in detail. Talk about it. Pick some past project to go deep. Also let them pick a favorite past project to go deep in detail. It means the interviewer needs enough technical depth to follow along. This works. I've never said "yes" to a hire and later thought that was a mistake, in ~25 years of doing interviews.
Just the other day here someone was saying they received over 50 resumes for a role so they had to interview over 50 people. No. Don't do that. You can't go deep, so it just leads to meaningless puzzles. Read the resumes, pick the top 5 or so, interview them personally. Hire the best of those. Done, move on with getting work done.
That's not really true, plenty of suggestions on how to improve it. Many of those based on experience doing it for the long haul.
Personally I always advocate for a technical discussion of their experience. Read the resume in detail. Talk about it. Pick some past project to go deep. Also let them pick a favorite past project to go deep in detail. It means the interviewer needs enough technical depth to follow along. This works. I've never said "yes" to a hire and later thought that was a mistake, in ~25 years of doing interviews.
Just the other day here someone was saying they received over 50 resumes for a role so they had to interview over 50 people. No. Don't do that. You can't go deep, so it just leads to meaningless puzzles. Read the resumes, pick the top 5 or so, interview them personally. Hire the best of those. Done, move on with getting work done.