Why some of the worst hires in tech are the ones who sound like great collaborators
Somewhere along the way, collaboration stopped being a means to an end and became the end itself. Today, many tech orgs are littered with the byproducts of this shift: people who look like team players, sound like culture fits, and somehow leave every sprint worse than they found it. Those who “communicate well” but don’t deliver. Those who participate in every retro but never learn. Who nod, smile, and “circle back” right into the graveyard of missed deadlines and burned-out devs.
This isn’t just a hiring problem. It’s a cultural cancer.
The collaboration con
Let’s call it what it is: a professional cosplay of value-add.
These folks are polished, personable, and highly fluent in the new dialect of workplace diplomacy. They name-drop psychological safety, take notes in Notion, and will absolutely create a mural board if left unsupervised. They have no edge — and that’s the edge.
They’re excellent at performative alignment. They thrive in:
- Meetings-heavy orgs, where output is measured in airtime, not impact.
- Consensus cultures, where disagreement is taboo and indecision is strategy.
- Hybrid limbo zones, where everyone’s accountable for everything and no one’s responsible for anything.
The real problem? These “collaborators” aren’t lazy — they’re incentivized to operate this way. They’ve figured out that in many orgs, being nice and visible beats being decisive and useful. They create motion, not movement. They don’t block — they fog.
Why we keep hiring them
Let’s be fair: this is partly self-inflicted.
Tech’s had its fill of brilliant jerks. That archetype — the 10x engineer with the emotional intelligence of a doorstop — left enough wreckage that companies overcorrected. Now, instead of hiring for courage and clarity, we hire for vibes.
You see it in job descriptions: “strong communicator,” “team-first mindset,” “comfortable with ambiguity.” These aren’t red flags on their own. But in aggregate, they signal a hiring strategy that favors the least offensive candidate, not the most capable one.
And these hires? They interview like pros. They’ve read the Medium posts. They know how to talk about failure without owning it. They’re fluent in phrases like “I was proud of the way we navigated that challenge as a team,” which sounds great — until you realize they navigated it by quietly waiting for someone else to make a decision.
The damage done
Let’s be crystal clear: these hires slow you down.
They may not break things, but they break momentum. Here’s how:
- They absorb accountability without action. Tasks hover in Jira limbo, “awaiting alignment.”
- They overprocess. What should be a two-sentence Slack exchange becomes a week-long workshop.
- They sanitize feedback loops, hijacking retros to talk about “communication norms” instead of missed estimates and busted APIs.
Eventually, the builders on the team — the ones who debug late, ship ugly, and fight for better — start asking themselves why they’re killing themselves to carry dead weight. That’s when attrition spikes. That’s when trust erodes.
And here’s the kicker: these collaborator-types survive. Because they’re pleasant. Because they play the game. Because no one remembers what they actually delivered, only that they always showed up.
How to spot (and stop) it
It’s not hard to detect this pattern — if you’re willing to interrogate your own hiring and management reflexes. Start here:
1. Look beyond likability.
Affable ≠ effective. Ask candidates when they pushed back, not just when they “aligned.”
2. Prioritize receipts.
Who did the work? What shipped? Don’t accept vague portfolio fluff — ask what broke, who fixed it, and how fast.
3. Probe for discomfort.
Real collaborators take heat. They’ve stepped on toes. They’ve been wrong. Ask what they learned — not what they “facilitated.”
4. Protect friction.
Disagreement isn’t dysfunction. The healthiest teams fight well. If you’re filtering out all the sharp edges, you’re sanding down your own effectiveness.
Until we fix this…
“Collaboration” will keep rewarding the wrong behaviors.
The people who stay quiet will get promoted. The ones who push will get pushed out.
The goal of teamwork isn’t to feel good. It’s to build better things faster. That means having hard conversations. Making bets. Shipping despite the risk of blame. And valuing the ones who do that over the ones who just show up polished and inoffensive.
So the next time you’re dazzled by a candidate’s Zoom charm or a teammate’s diplomatic finesse, ask one simple question:
What have they actually delivered?
Because real collaborators leave a trail of working software, fixed systems, and stronger team.
Will Kelly is a writer, content strategist, and keen observer of the IT industry. Medium is home to his personal writing projects. His professional interests include generative AI, cloud computing, DevOps, and collaboration tools. He has written for startups, Fortune 1000 firms, and leading industry publications, including CIO and TechTarget. Follow him on X: @willkelly. You can also follow him on BlueSky: willkelly.bsky.social.
