How Do We Actually Judge Engineers We're Hiring?
You say you don't know how to evaluate engineers. That isn't quite true. You know how to be impressed, and you know how to be unsure. Those are feelings. They are not a standard, and you have been hiring on feelings. The interview feels like guesswork because no one on your team has agreed, out loud, what good engineering looks like here — not in general, but on your systems, with your constraints, under your deadlines. Without that agreement, every interviewer is grading a different test. Fix that first, together, before you look at another resume. The hiring bar is not a clever question you spring on candidates. It is a decision your team makes about itself.
The guesswork isn't in the candidate — it's in you. You cannot judge what you haven't defined. Before your next interview, sit with your team and write down three things 'good work' looks like in your shop. Test only for those. Everything else is noise you're mistaking for signal.
What changes unlock by starting
- A written hiring standard every person on your team can state without looking it up.
- Interviews that test for your actual work instead of general cleverness.
- Less argument after interviews, because the argument happened beforehand, over the standard.
- Fewer hires you quietly regret six months in.