We’ve all seen the post-mortem for a failed software project: bad architecture, shifting business requirements, unrealistic deadlines, technical debt, or simply “execution problems.” But when you dig deeper into why a previously capable team stopped performing, the root cause is sometimes much higher up the organizational chart. It is the hidden, compounding cost of putting the wrong person in a management role.
There is still an expensive misconception in tech that exceptional individual performance naturally translates into exceptional leadership. A brilliant senior engineer becomes the obvious choice for Engineering Manager. A high-performing specialist gets promoted because management seems like the logical next step. Then the job changes almost overnight.
Instead of solving technical problems, they are expected to resolve conflict, give difficult feedback, coach different personalities, communicate upwards, protect the team from unnecessary noise, prioritize competing demands, hire well, and make decisions with incomplete information. Technical credibility certainly helps. But management is not simply senior engineering with more meetings. It is a different profession.
The Multiplier Effect — For Better or Worse
An individual contributor primarily influences their own output and the work immediately around them. A manager can multiply — or drastically reduce — the effectiveness of an entire team. That is what makes a management hiring mistake particularly expensive. A poorly matched engineer can create technical problems that need to be fixed. A poorly matched manager can create an environment in which several good engineers gradually stop performing at their best. And the damage isn’t always obvious at first.
• The Micro-Manager
Every decision needs approval. Every implementation is questioned. People are given responsibility on paper but very little autonomy in practice. Eventually, experienced engineers learn that independent thinking creates more friction than simply waiting for instructions. The manager may interpret this as increased control. In reality, the team is becoming dependent on them — and slower because of it.
• The Absentee Manager
The opposite extreme can be equally damaging. The manager provides autonomy but very little direction. Priorities remain unclear, difficult conversations are postponed, stakeholders communicate conflicting expectations directly to engineers, and nobody is quite sure who owns the final decision. The team may be technically capable and extremely busy while still moving in the wrong direction. Autonomy without context isn’t empowerment. Sometimes, it is simply ambiguity.
• The Political Manager
Perhaps the most damaging pattern is the manager who manages upwards far better than they manage their team. Success travels upwards as personal achievement. Failure travels downwards as someone else’s responsibility. Over time, people notice. Trust disappears, problems are hidden instead of discussed, and strong employees start considering whether their energy would be better invested somewhere else.
The Cost Doesn’t Appear on One Invoice
This is where companies often underestimate the financial impact of a management hiring mistake. The obvious costs are relatively easy to calculate: recruitment, onboarding, salary, and potentially the cost of replacing the manager. The indirect costs are much larger. A struggling manager can affect the performance of five, ten, or twenty people. Projects slow down. Decisions are revisited. Senior engineers spend more time navigating internal friction. Employees disengage. Strong performers leave. The remaining team absorbs additional workload while replacements are recruited and onboarded. Then there is the loss that is particularly difficult to quantify: institutional knowledge. When an experienced engineer leaves, the company isn’t only losing one employee. It may be losing years of product context, undocumented architectural knowledge, stakeholder relationships, historical understanding of previous decisions, and the informal knowledge that helps everyone around them work faster. Replacing the headcount does not immediately replace that value. This is
why the cost of a bad management hire can extend far beyond the manager’s own compensation.
The Retention Problem Often Appears Downstream
From a recruitment perspective, one of the most interesting signals is what candidates say when they explain why they want to leave. Compensation matters. Technology matters. Career progression
matters. But experienced professionals also talk extensively about management. They describe constantly changing priorities. Lack of recognition. Decisions made without context. No room for ownership. A manager who doesn’t defend the team. Feedback that arrives only when something goes wrong. Promises about progression that never turn into concrete conversations.
People rarely leave because of one unpleasant Tuesday. Usually, the decision builds gradually. And while the phrase “people don’t leave companies, they leave managers” oversimplifies reality, leadership quality unquestionably plays a significant role in whether strong employees can imagine themselves staying. That makes management hiring a retention decision as much as a recruitment decision.
The Best Engineer Isn’t Automatically the Best Engineering Manager
One of the biggest mistakes organizations make is treating management as a promotion rather than a career path. A senior engineer may be exceptional precisely because they love deep technical work.
Moving them into people management can remove them from the work where they create the most value and place them in a role they never genuinely wanted. The result can be two losses at once:
the company loses an excellent individual contributor and gains an unhappy manager. Before promoting internally, it is worth asking whether the person actually wants to manage people — not whether they want the title, salary increase, or recognition associated with the role.
• Do they enjoy developing others?
• Can they give difficult feedback without avoiding the conversation or making it personal?
• Can they delegate work they could probably complete faster themselves?
• Can they make decisions without needing to be the smartest technical person in every discussion?
• Can they handle the fact that their success will increasingly be measured through other people’s performance rather than their own visible output?
Those questions tell us much more about management potential than technical excellence alone.
Hiring Managers Requires a Different Interview
The same principle applies when hiring externally. Management candidates can be particularly difficult to evaluate because leadership vocabulary is easy to learn. Almost everyone knows they
should talk about empowerment, psychological safety, servant leadership, coaching, and autonomy.
The important question is what those concepts look like in practice. Instead of asking only, “What is your management style?”, companies can explore specific situations:
• Tell us about a strong employee who was underperforming. What did you do?
• Describe a situation where you disagreed with senior leadership and had to protect your team.
• When have you changed your mind because someone more junior challenged your decision?
• How do you identify whether someone needs more autonomy or more support?
• Tell us about someone you helped progress professionally.
• What happened the last time your team missed an important deadline?
• How do you handle a technically brilliant employee who damages collaboration within the team?
Strong management interviews should reveal patterns of behaviour, not simply familiarity with the correct leadership terminology.
Looking for the Right Traits
The modern technology landscape moves too quickly for old-school command-and-control leadership. The strongest managers today aren’t taskmasters tracking every Jira ticket or measuring
productivity through visible activity. Their value lies increasingly in creating the conditions in which other people can perform.
• They provide clarity without controlling every decision.
• They provide accountability without creating fear.
• They understand enough of the technical context to make informed decisions without needing to prove that they are still the strongest engineer in the room.
• They translate changing business priorities into something a technical team can actually execute.
• They notice when organizational noise is consuming engineering time and remove it.
• They give credit publicly and difficult feedback privately.
• And perhaps most importantly, they understand that leadership isn’t about becoming the centre of the team’s work. It is about building a team that can operate effectively without everything passing through them.
Management Hiring Deserves More Attention
Companies often invest enormous effort into assessing technical hires. Engineers complete coding exercises, system design interviews, technical discussions, and several rounds of evaluation.
Yet someone who may soon influence the performance and retention of an entire engineering team can sometimes be assessed primarily through a few conversational interviews and an impressive
management title on their CV. That imbalance is worth reconsidering.
Hiring the right manager can improve much more than delivery metrics. It can strengthen retention, develop future leaders, improve communication between technology and the business, and create
an environment where talented people actually want to stay. Hiring the wrong one can quietly undo years of work spent building exactly those things. In technology recruitment, we often focus on
whether someone has the skills to do the job.
For management positions, there is an additional question that matters just as much: What happens to the people around this person when they do it?