3 ms·
It's been a long time (late '90s) since I've seen a formalized (documented) interview process. It helped immensely. We basically treated recruiting like a sales
by specialist 14y ago
It's been a long time (late '90s) since I've seen a formalized (documented) interview process. It helped immensely. We basically treated recruiting like a sales funnel, had a ranking/scoring system, had self-selecting teams, etc.
Since then, seems like everyone's just making it up as they go. Hiring, evals, reqs, QA/test, whatever. The pinnacle of methodology may have sucked, but at least we all pretended to try.
When I interview candidates now, when it's a "no", I chop it off asap. I give precise reasons why, as nicely as possible. It's fair, honest, constructive, and is how I would want to be treat. I also believe in the Roman Evaluation Method, where anything less than a yes by everyone is a no.
Alas, I'm a solo act in a large organization. eg, Another interviewer, even after it's a clear "No" (we compare notes via IM), let's things drag on, always doing the "do you have any questions for us?" bit, and then wraps up with a "our people will contact you..."
- andrewcooke 14y agoif i were the candidate, i think i'd prefer this. it saves my time and it sounds like you are reasonably courteous and give some kind of feedback, which is more than i would get otherwise. in the past, when i've been the interviewer, i've "kept going to the end". i've not interviewed people recently, but if that changes in the future i will try this approach. (vaguely related - thinking back, at least twice, as the candidate, i've volunteered myself as not suitable for the job. one resulted in an early exit; the other limped awkwardly on.)