The Recruiter's Real Experience

The Busy Excuse

Whenever I criticize how hiring works, someone defends the other side with one word: busy.

The recruiter is busy. The hiring team is drowning. Two hundred applications came in for one role, and a human being cannot read two hundred resumes with care. So they scan, they filter, they move on. Fair enough. That part is real.

But let me push on that word, because I think it hides more than it explains. Busy. Everyone is busy. The marketing team is busy. Sales is busy. The person who applied and never heard back is busy too. "Busy" isn't a reason, it's a state everyone is in. So the real question isn't whether the hiring side is busy. It's why the one function whose entire job is to evaluate people gets to be too busy to actually see them, and then treats that as the candidate's problem.

Because that's the part you notice once you're close to it. From the hiring side, the story is almost always about what the job seeker did wrong. They didn't respond fast enough. They interviewed badly. They wrote the resume wrong. They didn't pick up the phone. It's a long list, and the one name never on it is the hiring team's own.

"Not a Good Fit"

Take the rejection line you'll get if you get one at all, some version of "we've decided to move forward with a candidate whose experience more closely matches what we're looking for right now." Matches what, exactly, and decided by whom? A salesperson who wants to move into customer success. A product manager who wants to move into marketing. Are they not a fit, or is that sentence just the easiest thing to send? In 2026 people want to change lanes. They have transferable skills and transferable experience, and a lot of them would be great. But the resume says what you've already done, and if what you've done doesn't match the box, you're out. If you're trying to reinvent yourself, it's nearly impossible.

What I think is going on is simpler than either side admits. The hiring side is not equipped to see people. It is barely equipped to see the resume — the title, the KPIs, the numbers, the dry text on the page. If your story lines up with the boxes, you move forward. If it doesn't, it "won't work," and no one looks any closer.

The Fear Nobody Admits To

There's a harder truth underneath the busy excuse and the rigid-box problem, and almost nobody says it out loud. Sometimes the strongest candidate in the room doesn't get picked, not because the fit is wrong, but because picking them feels risky to the person doing the picking.

Take "overqualified." It sounds like a judgment about the candidate. Real, peer-reviewed research on how hiring practitioners actually think about overqualified applicants says otherwise: the rejection is mostly built on assumption, not evidence, that this person will get bored, leave the moment something better shows up, or expect a salary the role was never going to pay. Nobody tested any of that against the actual person in front of them. It's a risk being managed, not a fact being weighed. Ask the plain version of the question: if you could hire someone twice as strong for the same money, why wouldn't you? Sometimes the honest answer has nothing to do with the candidate. It's "something about this feels like it could go wrong for me."

The brand-name effect works the same way, and I heard this straight from people who do the hiring. A few independent headhunters, people with enough of their own business built up to speak freely without a client relationship to protect, told me close to the same thing, more than once: see "Google" or "Meta" on a resume, and that candidate is already halfway in, whether or not their actual work was the reason those companies looked good. A stronger candidate who never worked somewhere recognizable loses to a weaker one who did. Real research on elite hiring backs this up directly, a landmark study built on real interviews with the people doing the hiring at top firms found that cultural and pedigree fit routinely outweighed the actual evidence of who could do the job better. A recognizable name isn't a shortcut to finding the best candidate. It's a shortcut to not having to defend a riskier pick to your own boss later.

I saw the plain, structural version of the same gap too. A friend who's worked as a headhunter for years told me she had no real way to rank incoming candidates against each other, best fit to worst, nothing that scored them side by side. In 2026. I built her something that did. When nobody's actually equipped to compare candidates on the merits, a brand name or a gut feeling rushes in to fill the space where a real comparison should be.

And there's a third version I want to name plainly, even without a study to point to. Some hiring managers and recruiters quietly avoid the strongest person in the room because that person is a threat, not to the company, to them personally. A genuinely excellent hire can make the person who hired them look outshined, replaceable, or like they took a reckless chance on a "wild card" if anything goes even slightly sideways. A safe, forgettable hire is nobody's fault if it doesn't work out. A brilliant one who doesn't quite land is. I can't hand you a peer-reviewed paper for this part, and I think that absence is itself the point. This is the kind of thing an entire industry has watched happen for years and talks about privately, never in print, because naming it means implicating themselves or the people they work with. Not everything true comes with a citation attached. Just be aware: sometimes the best person in the room doesn't get picked, and it was never really about them.

It May Not Be Their Fault, Either

I don't want to throw recruiters under the bus. And here's the honest part that job seekers never hear: it may not be the individual recruiter's fault at all. In a 2026 survey of 1,681 HR professionals (McLean & Company), only 19% rated their own department highly effective at project execution. If hiring teams are that stretched — too many projects, no time, weak job descriptions, no clear direction from the company about who they actually need — then the person on the other end of your silence isn't a villain. They're underwater. And in a lot of companies, the silence isn't even overwhelm, it's policy: legal teams often tell HR to give no specific reason for a rejection at all, because a specific reason is exactly what a discrimination claim needs to work with. Nobody explains that to the job seeker either. They just get the silence, however it was produced.

You can see the exact same overwhelm in the one channel that's supposed to be the easy case. Referrals are, by a wide margin, the best source of hires anyone has: referred employees perform better, stay longer, and convert from application to hire at roughly ten times the rate of a job-board applicant. Companies know this, most pay a real cash bonus for a successful referral. And still, only 2% of companies say their referral program meets its own goals. Not the goal of hiring the best possible person. The goal of using the program at all. I had a friend go out of his way to push me internally at a company he was excited to have me join. Weeks went by with nothing. He followed up. The answer was that they'd missed it, and the role had already closed. Nobody involved was lazy or careless in some cartoonish way. The referral just entered the same overwhelmed pipeline as everything else, and the pipeline didn't have room for it, even though it had just been handed the easiest, most pre-vetted candidate it could possibly get.

Stuck in the Dark, Both Sides

But the job seeker doesn't get told any of that. They send the application into the void and hear nothing. And when nothing comes back, they don't think "that team is under-resourced and overwhelmed, or under legal advice to say nothing." They think it's about them.

I've heard the same sentence more times than I can count, including from my own 1:1 career-consulting clients, impressive people, three degrees, real experience, ambition, a plan. One of them put it to me exactly this way: "I checked every box on the job description, and no one wrote back. Not even a no." He wasn't just puzzled by it. He was frustrated, and underneath the frustration, genuinely upset, the kind of upset that comes from being that capable and still left wondering what you did wrong. Is that a job description problem? A process problem? A resume problem? He had no idea, because nobody on the other side had the time, or maybe the standing, to tell him.

So both sides end up stuck in the dark. The candidate can't see why they were passed over. The recruiter can't see the person behind the page. And the resume, the one object sitting between them, was never built to fix that for either of them.