There is a comfortable myth about engineering management: that it is mostly a people job. Run good one-on-ones, advocate for your team, smooth out conflict, keep everyone happy, and the engineering takes care of itself. Companies hire engineering managers on that theory all the time. Then they are surprised when those managers fail.
I have watched this play out for thirty years. The pattern is consistent. The engineering managers who succeed are good at the people part, but that is not what earns them the right to lead. What earns it is being a trustworthy technical leader. Engineers follow people they trust with technology.
Why the people-manager model fails with engineers
Engineers are a particular kind of team to lead. They are paid to be skeptical, they can smell hand-waving, and they give their best work to leaders they respect. A manager who cannot engage with the actual work struggles to earn that respect. When the hard technical call arrives, a disagreement about architecture, a painful tradeoff, a decision about what to cut, a manager who cannot reason about the substance has nothing to offer. The team notices, and quietly stops bringing them the real problems.
Perks do not fix this. Neither do good intentions. You cannot lead engineers on warmth alone.
What good engineering managers actually do
This is not an argument that people skills do not matter. They matter enormously. The best engineering managers are genuinely good at the human work: growing careers, giving honest feedback, building an environment where people can do their best work and tell the truth. My own version of that, written down, lives in my user’s manual.
But they pair it with technical leadership. They can dive into the work when it matters. They make sound calls on tradeoffs. They remove technical blockers instead of just escalating them. They have their team’s back in a technical argument because they actually understand it. That combination, real care plus real technical judgment, is what builds trust. And trust is the currency everything else runs on. Trust is why a team gives you discretionary effort, follows you into a hard quarter, and tells you about the problem while it is still small.
The two hiring mistakes
Companies tend to fail in one of two directions. They hire a pure people manager with no technical depth and hope the team will respect them. Or they promote their strongest engineer, who has no interest in or aptitude for the human side, and hope leadership will come naturally. Both bets usually lose. You need both halves, and of the two, technical trust is the foundation. You can coach a trusted technical leader into a stronger people manager far more easily than you can give technical credibility to someone the team does not believe in.
What to look for
When I help a company build its engineering organization, I look for leaders who can hold both at once: people who clearly care about the humans on the team, and whom engineers visibly respect on the merits. I would rather develop a respected senior engineer into a manager than hire a polished manager the team will never quite trust. The first path is hard but reliable. The second tends to end with a quiet exodus.
Building engineering leadership that teams actually trust is central to what I do as a fractional CTO with Artificer Innovations, whether that means hiring, coaching your managers, or shaping the org. If you are working through this, let’s talk.