Why the Best Engineers Aren't the Ones Writing the Best Code

Walk into any engineering team that's been together a while and ask: who's the engineer everyone wants on their project? It's almost never the one writing the cleverest code.

It's the one who notices when a teammate has been quiet for three standups in a row. The one who asks the question in a design review that turns out to be the right question. The one who says "I think I missed something — walk me through that part again?" instead of nodding through.

For years, I treated emotional intelligence as a separate bucket from technical skills. Then I saw how Daniel Goleman reframed it: in a room full of smart engineers, IQ is just the entry ticket — EQ is what actually predicts who thrives.

That doesn't sound like it should be true. Engineers? The job that seems like it should be most about raw cognitive ability? But once you see the explanation, it changes how you think about performance in almost any technical field.

The floor effect that makes IQ irrelevant

To become an engineer, you need an IQ of about 115 or more — roughly a standard deviation above average. That's the entry ticket. Once you're in the room, everyone has cleared that bar.

A separate paper showed that above an IQ of 120, there's no measurable relationship between IQ and career success. The range of IQ variation among engineers is just too narrow to explain who thrives and who doesn't.

Emotional intelligence, on the other hand, varies enormously — even among people with identical cognitive profiles.

Goleman puts it this way: the person who went around asking teammates "What are you doing? How can I help?" got further than the person who stayed in their office writing perfect code all day. You don't write code in isolation anymore. Everyone works on projects together. You have to coordinate, influence, persuade, and be a good team member.

All of those are emotional intelligence competencies.

The AI angle: the technical floor keeps rising

Here's why this matters more now than it did ten years ago. AI can write code. It can draft reports, analyze data, generate test cases, refactor functions, even review pull requests. The technical floor in software engineering — the baseline competence that separates a working engineer from a non-engineer — is rising fast.

What AI can't do is read the room. It can't tell when a teammate stops contributing because they're overwhelmed. It can't notice that a stakeholder said "yes" but meant "I'm not bought in." It can't build the trust that makes someone willing to admit they're stuck on a problem they should have shipped two weeks ago. It can't sense the moment in a design review where pushing harder would shut a junior engineer down for the rest of the meeting.

That's the differentiator now. As the technical floor rises, the human ceiling — the part that determines who actually leads, persuades, and ships — is increasingly emotional.

The emotional recession

Here's something concerning. Six Seconds' global data shows that since 2020, emotional intelligence has been declining worldwide:

• EQ scores down 3.5%
• Wellbeing down 3.92%
• Optimism down 4.87%

Only 21% of employees worldwide are engaged. Another 19% are actively disengaged. The remaining 60% are what Gallup calls "quiet quitting" — showing up but not invested. Managers account for roughly 70% of the variance in employee engagement.

In other words: the skill that's becoming most important is the skill that's getting scarcer. That's a gap.

What the research shows (the short version)

I won't rehash the full evidence base here — I cover the studies, the mechanisms, and the seven leadership practices in the deep-dive companion post: Why Emotional Intelligence Wins at Work Even When IQ Doesn't. But the headline pattern from decades of research is consistent:

• EQ is roughly twice as predictive of job performance as IQ, and a better predictor than skill, knowledge, or expertise
• Higher EQ is linked to higher salaries — people who read emotions better navigate organizational politics and interpersonal dynamics more effectively
• Collective intelligence in teams depends on social sensitivity and equal turn-taking, not individual brilliance — both are EQ competencies
• At the C-suite level, executives are far more often fired for EQ deficits than for technical or strategic failure
• Most importantly: EQ is learnable at any age. Unlike IQ, it responds to deliberate practice.

That last point is what makes everything practical. If EQ were fixed, this would be an academic curiosity. Because it's learnable, every interaction is a training rep.

Every team wants someone who can listen and understand — not just someone who writes great code. Emotional intelligence used to be a nice-to-have. Now? It's what defines a great engineer.

The technical floor keeps moving up under all of us. AI takes another inch every quarter. What it doesn't take — what it can't take — is the human work of figuring out who needs what, knowing when to push and when to back off, and making someone feel heard enough to admit they're stuck.

Emotional intelligence isn't a soft skill. It's the skill that makes all the other skills work.

If you want the full picture — the salary research, the c-factor on team performance, the cognitive biases EQ guards against, and the seven practices for actually building it — that's all in the deep dive on emotional intelligence at work.

Sources

• Daniel Goleman, Emotional Intelligence (1995) and subsequent research — Used for: engineer IQ study, floor effect, the "how can I help?" anecdote
• Six Seconds, "The Business Case for Emotional Intelligence" (2023, 2026 editions) — Used for: emotional recession data and engagement statistics
• Companion post: Why Emotional Intelligence Wins at Work Even When IQ Doesn't — for the full research base and seven leadership practices