Trent Got Rejected in One Slack Message
A lot of hiring decisions aren't decisions. They're flinches.
No explanation. No real discussion. Just a quick “pass” buried in a hiring panel thread.
Something about it didn’t sit right with me.
We’re in the middle of a brutal C-level search right now. Real feedback is hard to get. The interview panel keeps shifting. Some candidates sail through the first screens and others — equally strong, sometimes stronger — don’t. It’s the kind of search that makes you question yourself. But giving up was never on the table.
We were close to closing this role a few months ago. Then we lost our top candidate to one of the hottest AI companies out there right now. You can guess which one. Back to baseline we went — researching, sourcing, screening, calling in favors. And every time we surface a strong candidate, their LinkedIn profile gets dissected like a doctoral dissertation defense.
That’s how Trent (not his real name) almost slipped through the cracks.
He got the cold-Slack rejection. No real reasoning attached. When I started asking around, I realized nobody on the panel could actually articulate why he wasn’t a fit. They just hadn’t loved him enough to say yes — which isn’t the same as a real no.
So I kept him warm for a couple weeks while I picked my moment. Then I went to the decision-maker and pushed back — not on them, on their reasoning. They heard me out. Trent’s back in the process, and his first interview is on the calendar.
I could’ve let it go. Accepted the non-answer and moved on to the next resume. But I’d done my homework — I knew the role, I knew the criteria, and I knew Trent fit. Whether he ends up being “the one” is still TBD. But I’m glad I pushed for the truth instead of the path of least resistance.
Here’s what I keep coming back to: a lot of hiring decisions aren’t decisions. They’re flinches.
A panel reads ten profiles in a row, gets tired, and the eleventh one gets a “pass” that’s really just decision fatigue wearing a business suit. Nobody’s being malicious. They’re just not being asked to explain themselves — so they don’t.
If you’re a hiring manager: next time you reject a candidate, make yourself say the actual reason out loud. Not “not feeling it” — the specific, defensible reason. If you can’t articulate one, that’s information too.
If you’re a candidate: a rejection — especially a fast, silent one — usually says less about you than you think. Plenty of “no’s” are really just nobody pushing back on a maybe.
If you’re navigating a search where the right person keeps almost getting passed over for reasons nobody can quite explain, that’s exactly the kind of mess we like untangling. Hit reply — I’d love to hear what’s going on.
PS — sending this a day early since half of you are already mentally on a boat for the 4th. Happy Fourth.


Good insight, "decision fatigue" is an apt way to put it.....