Honestly, figuring out if a candidate really did a good job goes way beyond just a gut feeling. From my experience running dozens of hiring panels, the most reliable approach is to use structured evaluation criteria before the interview even starts. You need to define what “good” looks like for each role—not just skills, but also how they handle pressure, communicate, and align with your team’s culture. I always create a scoring rubric with 3–5 core competencies, each rated on a 1–5 scale. For example, if the role demands client-facing problem-solving, I’d watch for specific examples where they explained a complex issue simply and then followed up with a clear resolution.
One thing I’ve learned is that behavioral questions are gold. Instead of asking “Did you do a good job on that project?” I ask “Tell me about a time you had to recover from a major mistake.” Their answer reveals far more about their actual performance than any self-assessment. I also rely on reference checks that dig into measurable outcomes—like “What percentage of their projects came in under budget?” or “How did their team’s retention rate change after they joined?”
If I’m still unsure, I run a quick work sample test related to the actual job. A candidate who did a good job will produce something that meets or exceeds the benchmark. Here’s a simple table I use to weigh evidence:
| Evaluation Method | Weight | Example Indicator |
|---|
| Structured interview score | 40% | Average rating ≥ 4.0 across competencies |
| Work sample / task | 30% | Completed with no errors, delivered ahead of time |
| Reference verification | 20% | Quantified achievements (e.g., “reduced costs by 15%”) |
| Cultural fit assessment | 10% | Team interview feedback aligned with values |
The key is to avoid confirmation bias—don’t let one strong answer overshadow weaker areas. I always compare notes with other interviewers before making a call. In the end, a candidate who did a good job leaves a trail of concrete evidence, not just a good impression.
