Performance evaluation
Developer turnover: the role of a career path
In this article
A career ladder for developers is the set of levels, criteria and conversations that shows each person in tech what is expected of them today and what has to change for them to grow. Without one, departures tend to arrive without warning and, according to Gallup, cost from half to twice the person’s annual salary. This article explains the concept, shows where that cost hides and how HR can sustain a ladder with clear criteria, without needing to read code.
In short
- A career ladder for developers is the written, shared answer to three questions: where the person stands today, what is expected at the next level and what has to change to get there.
- According to Gallup, replacing a person costs from half to twice their annual salary, and 52% of people who leave voluntarily say the company could have prevented it.
- In many tech teams, what is missing is not the ladder on paper but the criteria behind it: without a standard that is known and the same for everyone, promotion depends on each manager’s reading.
- HR does not need to read code or monitor anyone: it writes the criteria with engineering, defines what the ladder looks at and what it does not, uses data to start the conversation and puts career talks on the calendar.
- Devint supports those criteria with the DevScore, built from six dimensions with open composition, and the number never decides a promotion or a dismissal on its own.
What is a career ladder for developers, and why does it matter?
In essence, it is the written, shared answer to three questions: where the person stands today, what is expected of them at the next level and what has to change to get there. It is not a promise of promotion or a table of job titles and salaries. It is what gives that table its meaning.
In practice, a complete ladder has four elements:
| Element | Question it answers | Sign that it is missing |
|---|---|---|
| Levels | What are the steps (for example, junior, mid, senior and above)? | The titles exist, but nobody explains what separates one from the next |
| Criteria per level | What is expected of someone at each step? | Promotion depends on the opinion of whoever is evaluating |
| Tracks | Can people grow without becoming managers (the so-called dual career ladder)? | Those who prefer the technical path see management as the only way up |
| Regular conversation | Where am I and what is my next goal? | Career only comes up when someone asks for a raise or gets an outside offer |
It helps to separate three terms that tend to get mixed up. The career ladder is the general map, the same for all developers in the company. The skills matrix is the tool that describes the criteria for each level. The IDP (individual development plan) is each person’s route between one point and another on that map.
How much does losing a developer without a career ladder cost?
According to Gallup, replacing a person costs from half to twice their annual salary, and Gallup itself treats that range as a conservative estimate. It is US data and applies to any role, not only technology. So the best use is as an order of magnitude, not as a forecast for your company.
That cost shows up in three layers:
- Direct: recruiting, interview time, hiring and onboarding.
- Indirect: the gap until the new person is productive, the extra load on those who stay and the code and product knowledge that leaves with the person.
- Strategic: delayed deliveries, lower morale and the loss of someone who could have become a technical reference in the coming years.
The most uncomfortable part is that much of this bill is avoidable. The same Gallup research shows that 52% of people who leave voluntarily say their manager or the company could have done something to prevent it. In addition, 51% say that in the three months before leaving, nobody talked with them about job satisfaction or their future at the company.
In Brazil, two recent surveys point in the same direction:
- A Robert Half survey, reported by CartaCapital (in Portuguese), interviewed 1,000 professionals from several fields, including technology. Looking at the second half of 2026, 47% planned to change jobs, and 31% wanted a higher position but saw few chances to grow where they were. Among those who preferred to stay, 47% cited a defined career plan with growth opportunities.
- The HR Trends 2026 survey (in Portuguese), by Koru with Chiefs.Group, interviewed 330 HR leaders. For 43% of them, the lack of career perspective is among the causes of departures, on par with leadership failures.
None of these studies is exclusive to technology. They show the direction of the problem, not its exact size in your team.
Why is a missing career ladder usually a missing set of criteria?
In many tech teams, what is missing is not the ladder on paper but the criteria that hold it up. The company may have titles, salary bands and even a design for tracks. But without written criteria for what changes from one level to the next, the decision to promote depends on each manager’s reading.
This creates four effects that HR knows well:
- Developers do not know what to do to grow. The ladder becomes a vague promise, and the career conversation only happens when it is already too late.
- Each squad uses its own yardstick. People who work under a more demanding manager tend to find the process unfair, even with the same ladder on paper.
- HR is left without a basis. Without a reading of technical signals, it depends on the manager’s word and has little material to question or calibrate a decision.
- Invisible work disappears. Architecture, mentoring and code review rarely show up in any number. Whoever dedicates time to them risks being read as less productive.
When the criteria are unclear, those with the most options in the market tend to be the first to accept an outside offer. That is why a missing ladder tends to take from the company exactly the people it would most like to keep.
The practical conclusion is that a career ladder only retains people when they believe the yardstick is the same for everyone and know what it is.
How can HR build a career ladder without reading code and without it becoming surveillance?
HR does not need to understand code to build a ladder. It needs to make sure the criteria exist, are clear and apply to everyone, and leave the technical reading to those with the context for it. It also does not need to become surveillance, because measuring delivered work is different from monitoring people.
A path in five steps:
- Write the criteria with engineering, in management language. For each level, describe observable behaviors, such as “reviews colleagues’ code and explains why the changes were made”, instead of adjectives like “proactive”.
- Define what the ladder looks at and what it does not. Make it clear that the evaluation considers work delivered over a cycle, not real-time tracking of each person’s routine.
- Make the criteria known to the people being evaluated. If developers do not know what the yardstick is, the ladder does not reduce uncertainty, it only moves it somewhere else.
- Use data to open the conversation, not to decide on its own. A number or a drop is a reason to ask what is going on, never a verdict on promotion or dismissal.
- Put the career conversation on the calendar. Gallup’s finding about three months of silence shows the risk of waiting for the developer to bring it up.
How does Devint support the career ladder with clear criteria?
Devint is a platform for evaluating the performance of technology teams with clear criteria. It delivers a score, the DevScore, for each person and each squad, combining signals from Git, hours, AI use and a structured leadership assessment, with open composition. The logic behind the score comes from more than eight years of Espresso Labs managing thousands of developers. For HR, this fills the gap described above: the criteria stop being opinion and become a reading that engineering and HR share.
The DevScore is made up of six dimensions, with these default weights:
| Dimension | Default weight | What it measures |
|---|---|---|
| Delivery pace | 20% | Commits per working day and PRs per week, within a healthy range and with a cap |
| Code contribution | 20% | Code that stays and change entropy, with an open calculation |
| Hard skills | 20% | Structured leadership assessment |
| Hours logging | 15% | Consistency of time entries, not the amount of hours worked |
| Soft skills | 15% | Assessment by the manager and the Tech Lead; self-assessment does not count |
| AI and agent adoption | 15% | AI use tied to each person’s results, with a cap |
In practice, this answers the points the article raised:
- Same criteria for everyone. People are read against reference ranges by level, and the score composition is open.
- Invisible work. Written code is read alongside the leadership assessment, which helps tell apart someone who writes little because they are doing architecture from someone who is blocked.
- Resistance to gaming. Each dimension has a cap, so inflating a number does not raise the score.
- No surveillance. Consolidation happens in closings every two weeks, not through real-time monitoring.
- Career conversation. DevCoach, the developer’s growth plan, gives each person a trajectory goal to bring to the conversation with their lead.
One principle matters above all: the number opens the right conversation, but it never decides a promotion or a dismissal on its own. The decision stays with people, now with a basis that everyone can see. Implementation is assisted.
Frequently asked questions
What is the difference between a career ladder, a skills matrix and an IDP?
The career ladder is the general map, the same for all developers in the company. The skills matrix describes the criteria for each level, and the IDP (individual development plan) is each person’s route between one point and another on that map.
How much does it cost to replace a developer who leaves?
According to Gallup, replacing a person costs from half to twice their annual salary. It is US data that applies to any role, so it works as an order of magnitude and not as a forecast for your company.
Does HR need to understand code to build a career ladder?
No. HR makes sure the criteria exist, are clear and apply to everyone, and leaves the technical reading to those with the context for it. The criteria can be written with engineering, in management language, describing observable behaviors instead of adjectives.
Can developers grow in a technical career without becoming managers?
Yes, with tracks that separate the technical path from the management path, the so-called dual career ladder. Without them, people who prefer to stay technical see management as the only way up.
Is evaluating performance to support the ladder a form of surveillance?
It does not have to be. Measuring work delivered over a cycle is different from monitoring people in real time. At Devint, consolidation happens in closings every two weeks and the DevScore composition is open.
Does the DevScore decide promotions and dismissals?
No. The number opens the right conversation, but it never decides a promotion or a dismissal on its own. The decision stays with people, now with a basis that everyone can see.
How often should HR talk about careers with developers?
On a fixed schedule, not only when someone asks for a raise or gets an outside offer. Gallup shows that 51% of people who leave voluntarily say nobody talked with them about their future at the company in the previous three months.
Next step
A career structure does not retain people because it is written down, but because it is clear, the same for everyone and discussed regularly. If your HR team wants to get there without relying on separate spreadsheets for management and technology, the next step is to see the criteria working in the context of your team.
Talk to the Devint team or request a demo and see how the DevScore and DevCoach support the career conversation with data that engineering and HR can read together.
Sources
- Gallup, “This Fixable Problem Costs U.S. Businesses $1 Trillion”, by Shane McFeely and Ben Wigert, published 03/13/2019 and updated 05/13/2025.
- CartaCapital, “Quase metade dos trabalhadores deseja trocar de emprego em 2026”, 08/18/2026, on a Robert Half survey (in Portuguese).
- Exame, “Tendências de RH para 2026: pesquisa revela ‘reengenharia silenciosa’ no setor”, 12/11/2025, on a Koru survey in partnership with Chiefs.Group (in Portuguese).
- Devint, DevScore dimensions and default weights.