
I’ve been on both sides of the hiring table, and let me tell you, “did a good job” is one of the most ambiguous phrases in recruitment. If you’re a candidate hearing that after an interview, it’s natural to feel unsure. But here’s the thing: it’s rarely a strong signal of an offer. When I’m evaluating candidates, I use a structured scoring system based on key competencies like problem-solving, cultural fit, and communication. “Did a good job” usually means the candidate met expectations but didn’t stand out. In fact, a 2024 LinkedIn survey found that 68% of recruiters use neutral phrases like “did a good job” when they are not ready to move forward, but also don’t want to discourage the candidate. To get a clearer picture, I always ask for specific behavioral examples during the interview. For instance, if a candidate says “I did a good job leading a team,” I’d probe deeper: “What was the team size, what challenge did you overcome, and how did you measure success?” That’s where the real signal lies. If you’re a recruiter, replace vague praise with actionable feedback—it helps candidates improve and builds trust. If you’re a candidate, don’t rest on that phrase. Follow up with a thank-you email that reiterates your key contributions and asks about next steps. That shows initiative.

I’ve been job-hunting for six months, and hearing “you did a good job” from a recruiter always makes me nervous. It’s too generic—like a polite way to say “thanks but no thanks.” I’d rather get specific feedback, even if it’s critical. Last time I heard that, I didn’t get the job. Now I treat it as a neutral signal and keep applying until I have a written offer.

As someone who coaches early-career professionals, I tell them “did a good job” is often a placeholder for “I’m not sure yet.” Recruiters use it when they’re comparing candidates. If you hear it, ask two things: “What specifically stood out?” and “What would make me a stronger candidate?” Their answers reveal if there’s real interest. Table below shows common recruiter phrases and their likely meanings:
| Phrase | Likely Meaning |
|---|---|
| “Did a good job” | Neutral, not a top contender |
| “We’ll be in touch” | Low priority, possible rejection |
| “You’re a strong candidate” | High interest, likely to advance |
| “Let me check with the team” | Result pending, but positive |

I’m a recruiter, and I cringe when I hear colleagues say “did a good job.” It’s lazy feedback. We should use a competency-based framework instead. For example, rate candidates on a 1–5 scale for skills like adaptability, teamwork, and technical knowledge. Then share specific ratings. If a candidate scores a 3 on problem-solving, I’ll say “You gave a solid approach, but I’d like to see how you handle ambiguity.” That’s useful. Vague praise hurts everyone—it misleads candidates and weakens our employer brand.

From a hiring manager’s perspective, “did a good job” often means the candidate passed the initial screen but didn’t wow me. I’m looking for “wow” moments—specific examples of impact, like saving the previous company $100K or launching a product early. In my last round, I interviewed five people. Three got “did a good job” feedback, and none were hired. The one who got an offer had a measurable story: “I reduced customer churn by 15% in six months.” That’s the difference. So if you’re a candidate, quantify your results—even if you’re just starting out, use metrics like “improved team efficiency by 20%” or “handled 50+ client calls weekly.” It makes the phrase irrelevant.


