The Interviewer Who Called a Candidate "Too Stupid to Work Here" — And Why He's the One Who Failed
Here's a story that should make every hiring manager squirm.
A software engineer shared on Reddit (r/recruitinghell) what happened to him in a *third-round interview*. He'd already passed a coding test — completing it in half the allotted time, no less. Two rounds down. Then he sat in front of a hiring manager who handed him a piece of intentionally bad code and asked how he'd fix it.
The candidate analyzed it, explained what it did, and gave his answer: "Hash table."
A textbook correct answer.
The interviewer's response? That's not the answer. And when the candidate, now second-guessing everything he learned in college, pushed back — the manager snapped:
> *"Everyone I interview says hash tables. That's not the f-ing answer."*
Then, after one more stumble on the next question, he delivered the knockout line:
> *"If you can't answer this, then you're too stupid to work here. We're done here."*
Let's be crystal clear about who failed this interview. **It wasn't the candidate.**
Failure #1: He Was Grading Answers, Not Ability
This manager didn't want to find the best engineer. He wanted someone to recite *his* answer. That's not interviewing — that's a trivia game with one lucky winner.
The right move when a candidate gives a technically sound answer that isn't yours? Say: *"Walk me through your reasoning."* That's how you evaluate someone's actual thinking. Instead, this manager treated every answer as a personal insult and swore at a person who'd already cleared two rounds of vetting.
When your question has multiple valid solutions, demanding one specific answer doesn't filter mind-readers.
Failure #2: The Process Set Him Up to Explode
If a question is truly a dealbreaker, it belongs in **round one** — not round three, after a candidate has invested weeks of interviews and passed a timed technical test. Routing people this deep into the pipeline only to ambush them with a gotcha question wastes everyone's time and signals a broken, disorganized process.
And let's be honest about what this smells like: a manager who saves his gotcha question for round three to show off how smart * Candidates who get rejected by interviewers like this aren't being evaluated. They're being used as an audience.
Failure #3: He Torched the Company's Reputation on His Way Out
The candidate named the company. Solidigm's communications team responded that the behavior described isn't consistent with their values — a smart, professional statement. But the damage is done, and it's ongoing.
Here's what companies forget: *every interview is a PR event.*
The candidate this manager humiliated will tell this story forever — to friends, to colleagues, to thousands of strangers online. Everyone he knows now associates that company with a swearing, abusive interviewer. And here's the kicker: by the company's own process, this was someone good enough to reach round a person who was already *won over* — until one ego-driven manager flipped him into a permanent brand enemy.
Rejected candidates become your future customers, vendors, and — or your loudest critics. You choose which, every single time you sit across the table.
If you're a hiring manager, take this as your mirror check:
- **Ask follow-up questions, not gotchas.** "Why did you choose that approach?" reveals more than any trick question ever will.
- **Front knockout criteria.** Never ambush a candidate in round three with something you could've tested in round one.
- **Never, ever insult a candidate.** Not even the ones you reject. Especially you reject.
The candidate wasn't too stupid to work there. But that interviewer proved something worse: he was too unprofessional to ** — and too careless to realize the person he was really interviewing in that room was himself.
And the candidate passed that interview. The manager didn't.