A stronger title can hide a weaker fit. An engineer who excels at understanding complex systems may enjoy management, or may find that the new role removes the work they most want to do. Neither outcome says that the person lacks ambition.
The chess knight wearing a rook costume illustrates a career transition that has not been examined carefully. Leadership needs to ask about the work someone wants to grow into, not assume that people management is the only meaningful next step.
Describe the new job honestly
Management involves different responsibilities: clarifying expectations, providing feedback, handling conflict, making staffing decisions, and creating conditions in which others can succeed. Technical judgment remains valuable, but personal implementation is no longer the whole job.
Before offering a promotion, discuss a representative week. Which responsibilities will the person stop doing? Which difficult conversations will they now own? Who will help them learn? A role description built only around status and compensation leaves the transition underexplained.
Ask what the person wants more of, and what they would miss. Do not mistake reluctance to manage people for reluctance to take responsibility.
Make technical growth visible
GitLab's engineering career guidance provides an example of separate individual-contributor and management paths. It illustrates a possible structure, rather than proving that every company should adopt identical titles or levels.
For a smaller organization, the useful principle is clarity about technical influence. An experienced individual contributor might own an architectural area, improve engineering standards, mentor colleagues, or lead a difficult cross-team technical effort. Define that scope and explain how the contribution is recognized.
A nominal technical path with no authority, growth, or recognition will not solve the problem. People notice whether the organization rewards the work it claims to value.
Test the transition with support
Where practical, offer a bounded opportunity to try management responsibilities with clear expectations and coaching. Explain how the arrangement will be reviewed and what happens if the role is not a good fit. Avoid presenting a return to technical work as a failure.
Protect the person from carrying two full jobs indefinitely. If they remain the default engineer for every hard implementation while taking on a full team, the experiment measures overload as much as management interest.
Use feedback from the new manager, their team, and relevant partners. Focus on the responsibilities actually assigned rather than comparing them to an experienced manager without equivalent support.
Plan the technical gap before moving the person
Promoting a key engineer creates a capacity decision. Which technical responsibilities need a new owner? What knowledge should be shared? Which parts require another senior contributor or technical lead?
EnzRossi can support US teams with senior LATAM engineers and technical leadership while roles evolve. Talk through the responsibility that needs a new owner. A career move works better when it advances the person and leaves the team with a realistic plan for the work.
