
I’ve seen the phrase “great job” thrown around a lot in recruitment, and honestly, it’s one of the most overused—and underdefined—pieces of feedback out there. When someone says you did a great job, what exactly do they mean? After years of working with hiring teams and candidates, I’ve learned that “great job” isn’t just a pat on the back; it’s a signal that specific, measurable outcomes were achieved.
For a recruiter, doing a great job often means hitting key performance indicators like time-to-fill, quality of hire, and candidate satisfaction scores. But it’s deeper than that. A great job might involve sourcing a passive candidate who wasn’t even looking, negotiating a salary range that satisfies both the company and the hire, or building a talent pipeline that reduces future hiring costs. Let’s break it down with a simple framework I use:
| Criterion | What “Great Job” Looks Like |
|---|---|
| Speed | Filled a critical role in under 30 days, beating the industry average of 42 days |
| Quality | The candidate stays beyond the 90-day probation period and exceeds performance benchmarks |
| Candidate Experience | Net Promoter Score (NPS) from candidates is 70 or above |
| Cost Efficiency | Reduced agency spend by 20% by using internal sourcing and employee referrals |
| Diversity | Increased the share of underrepresented groups in the shortlist by 15% |
For a candidate, “great job” might mean demonstrating structured interview skills—like using the STAR method effectively—or showing a deep understanding of the company’s culture. It’s not about being perfect; it’s about showing growth, adaptability, and alignment with the role.
The key is to move from vague praise to specific, data-backed recognition. When you say “you did a great job,” follow it up with the why. That’s what turns a compliment into a tool for professional development.

For me, “great job” in recruitment means the interviewer actually listened. I’ve been on both sides—as a candidate and as a team lead. When a recruiter takes the time to tailor questions to my actual experience instead of reading off a script, that’s a great job. It shows they prepared, they value my time, and they care about fit. I don’t need a trophy. Just honest, specific feedback like “You nailed the technical part—your explanation of the algorithm was clear.” That’s worth more than a generic “great job” any day.

When I say a candidate did a great job, I’m looking at three things: did they answer the core question directly, did they back it up with a real example, and did they ask me a thoughtful question at the end? If they skip the fluff and get straight to the point, that’s a win. I’ve interviewed hundreds of people, and the ones who do a great job are the ones who make my decision easy. They don’t leave me guessing. They connect their past work to what we need now. That’s the gold standard.

From a recruiter’s standpoint, doing a great job means closing the loop without drama. I’ve recruited for high-volume roles and executive searches alike. A great job isn’t just filling a position—it’s keeping the hiring manager informed, managing candidate expectations, and handling rejections with empathy. If I can get a “yes” from both sides without any last-minute salary surprises or ghosting, that’s a win. I track this with a simple metric: percentage of offers accepted without negotiation. When that’s above 85%, I know I did a great job.

I help people understand what “great job” really means in performance reviews. The problem is that recruiters and managers often use the phrase as a placeholder. They don’t attach it to behaviors. So I tell my clients to ask for examples: “What specifically did I do that made it a great job?” If they can’t answer, the feedback is hollow. A genuine “great job” should be backed by observable actions—like meeting a tight deadline, solving a conflict, or landing a tough client. That’s how you turn praise into a growth point.


