Why Your Strongest Senior Engineer Might Be Your Weakest Manager

The promotion made sense at the time. The engineer had consistently delivered the most technically sophisticated work on the team. Their code reviews were the most insightful. Their architecture decisions were the ones the team trusted. When the engineering manager role opened, the path of least resistance, and it seemed the path of most logic, was to promote the person who was obviously best at the work.

Six months later, something is wrong. The team is not performing at the level it was. Decisions are being made too slowly. Junior engineers are not growing. The manager is spending more time in their own code than in one-on-ones. Escalations that should be resolved at the team level are arriving at the CTO’s desk.

The person who was your best engineer is now visibly uncomfortable in a role they accepted partly out of obligation, partly out of ambition, and partly because nobody had explained to them what the role actually requires.

That last part is the diagnosis. Not the person. The explanation that was never given.

The Peter Principle, Nigerian Edition

The Peter Principle, the observation that people are promoted to their level of incompetence, applies universally. In Nigerian tech, it has a specific expression: the technical excellence that produced the promotion is precisely the capability that becomes a liability in the management role.

The best engineer is best because they have developed exceptional individual judgment. They know exactly how to approach a technical problem. They have strong opinions about the right architecture, the correct abstraction level, the appropriate trade-off between speed and quality. These opinions are valuable when the engineer is producing technical output. They become a bottleneck when the engineer’s role is to develop other engineers who need to develop their own judgment, rather than receiving the senior engineer’s judgment as a correction.

The coach and the expert are different roles.

The expert demonstrates. The coach develops. The expert’s primary output is the quality of their own work. The coach’s primary output is the quality of other people’s work. These are not complementary capabilities that naturally coexist. They require genuinely different orientations. And the orientation toward coaching is not developed by being excellent at the technical work. It is developed by deliberate practice in a different set of skills. Skills that the standard engineering promotion path does not develop, and that most Nigerian tech companies do not teach.

What the Role Actually Requires

The engineering manager role requires four capabilities that have no direct relationship to technical depth.

1. Developing people rather than solving their problems.
The instinct of the senior engineer, when a junior presents a problem, is to see the solution and share it. The instinct of the effective manager is to ask questions that help the junior find the solution, even when this takes longer and produces a less elegant outcome than the manager would have produced themselves. The first instinct scales to one person. The second instinct scales to a team. The manager who cannot make this shift is the manager whose team never develops beyond their current level, because every solution is provided rather than earned.

2. Communicating with non-technical stakeholders.
The engineering manager’s relationship upward, with product, with the CTO, with the business leadership, requires translating technical reality into business terms without losing accuracy in either direction. This is a communication skill that is distinct from technical skill and that many strong engineers have not needed to develop deeply. The engineer who cannot make this translation forces every technical-business interface through the CTO’s desk, which is where the escalations are coming from.

3. Managing performance explicitly.
The senior engineer who has always been a high performer often has no experiential model for having a structured performance conversation with someone who is not performing. These conversations are uncomfortable for people who have not been trained in them and who may have an instinct that directness about performance is harshness rather than clarity. The team that is not being managed explicitly is the team that tolerates its own spread, quietly, until the spread becomes a crisis.

4. Operating in ambiguity.
The engineer’s world is relatively precise: a function either works or it does not, a test either passes or it fails. The manager’s world is genuinely ambiguous: a person is sometimes performing well and sometimes not, a team is often partially effective, a decision is usually a trade-off without a clearly correct answer. The engineer who has built their confidence on the precision of technical problem-solving often finds the ambiguity of management genuinely disorienting. They retreat to the code because the code gives them the clarity the management role does not. This is where the “spending more time in their own code” observation comes from. It is not laziness. It is a competence gap seeking the domain where competence still feels available.

The Three Options That Are Better Than the Standard Promotion

When a senior engineer is clearly the best technical candidate and a management role needs to be filled, three options deserve genuine consideration before the standard promotion is executed.

1. The dual-track career path.
The most technically excellent engineers do not need to become managers to have growing careers and compensation. A principal engineer track, with its own progression, compensation, and scope, gives the best engineers an internal career path that does not require them to abandon the work they are excellent at. This track exists in most mature engineering organisations globally and is rare in Nigerian tech companies. Its absence is why the management path feels like the only path to seniority, which is why engineers accept promotions they are not equipped for.

2.The structured management trial.
Before committing to a permanent promotion, offer the engineer an explicit management trial: a defined period of three to six months in which they take on management responsibilities while the organisation assesses their development in the role. This protects both the company and the individual. If the management role does not suit them, they return to an individual contributor role without the cost of a failed promotion to either party. The trial surfaces incompatibility before it becomes embedded.

3. A hire for the management role.
When the management capability required is genuinely different from what the best internal technical candidate offers, hiring an experienced engineering manager from outside, while retaining the strong engineer in an expanded technical role, is often the best decision for both people and for the team. The strong engineer does the work they are excellent at. The experienced manager develops the team. Both are in the role that matches their capability.

The Bottom Line

The promotion of your best engineer into a management role they are not equipped for does not fail immediately. It fails slowly, over six months, in the specific ways described at the start of this article. By the time the failure is visible enough to act on, the team has absorbed months of suboptimal management, the engineer has absorbed months of professional discomfort, and the company has spent six months discovering something it could have known before the promotion was made.

Promoting your best engineer into a management role they are not equipped for is the most expensive gift you can give your competitors.

Revent Technologies places engineering leaders who are both technically credible and demonstrably capable of developing teams: people who have managed before, at your scale, and produced outcomes. If the engineering management seat in your company is occupied by the wrong person, the team is already paying for it.

Start here: www.reventtechnologies.com/site/hire-a-developer

Research Sources
– Gallup State of the Global Workplace 2026: manager quality and team engagement variance
– Enboarder: 83% of managers have no formal training in people management
– DexNova Consulting: 2026 Nigerian recruitment: management capability gaps in growing tech companies