We covered the salary story in SA developers feel underpaid, which unpacks why 49% of developers and 62% of juniors feel undercompensated. This piece is about what sits underneath that frustration: the near-total absence of career infrastructure in South African tech, and how AI has quietly collapsed whatever informal ladders were left.
SA developer career framework: The broken rung
The most counterintuitive finding is that the clarity problem gets worse as developers become more senior. Among graduates, 29% say they lack a career framework. Among juniors, 37%. By mid-level, 38%. By senior, 45%. At the tech lead level, 44%. At the executive level, 56% have no defined framework for their own growth. The very top of the technical ladder is where the rung simply isn't there.
The same pattern holds for knowing what it takes to level up. Only 35% of developers say they understand the criteria, and the number barely improves with seniority. They're expected to intuit the rules of a game nobody wrote down.
This isn't benign neglect: When the path forward is undefined, companies lose senior engineers to competitors who offer at least the illusion of clarity, or to international markets that offer both. The talent retention problem that SA founders and CTOs cite constantly has one of its roots right here.
The feedback desert
Career frameworks only work when reinforced by consistent feedback. That's the second place SA tech teams are failing.
45% of developers receive feedback only a few times a year, or never. Only 8% get it weekly. The neglect is sharpest at the senior level: despite 62% of senior developers saying they find feedback genuinely useful, 40% rarely or never receive it. The implicit logic seems to be that juniors need guidance while seniors should already know. But knowing how to do the work and knowing whether you're doing the right work for the right outcomes are different things.
Between 61% and 65% of developers across all levels identify actionable feedback as what they value most from a manager. Between 69% and 79% want managers who understand what they actually do day to day. They're not asking for hand-holding. They're asking for a system that sees them.
AI broke the old metrics
Whatever informal signals developers used to navigate career growth (output volume, ticket velocity, lines shipped) are no longer reliable. AI has changed what "good work" looks like, and most companies haven't caught up.
97% of SA tech teams use AI in their workflows. 50% say it's shifting their work toward higher-value, strategic tasks. 54% report significantly increased productivity. These aren't marginal changes.
The problem is that 42% of leaders are rethinking how to measure performance in this new environment, and 27% haven't even started. Only 31% feel their current metrics still hold up. The old markers made sense when "senior developer" meant someone who could write a lot of good code quickly. They make less sense when an entry-level engineer with strong AI fluency can produce comparable output. What's now scarce isn't raw production; it's judgment: The ability to ask the right questions, direct AI with intent, and make architectural decisions that compound over time.
36% of developers say they're unsure whether how they're evaluated still reflects how work actually gets done. 11% feel their work is less visible or valued than before AI became central to their workflows.
The control problem
Even where managers understand what good performance looks like and want to reward it, the system breaks at the next level up.
Only 8% of managers (one in 12) have full control over pay decisions. 34% have no real control at all. Another 34% say that when they push for a raise or promotion, leadership overrides the decision. Only 32% of developers work in environments where clear goals, regular feedback, and a link between performance and pay all exist at once. For most, at least one of those three is missing.
What this means if you're hiring right now
71% of SA tech companies are hiring for specific high-impact roles. 60% expect higher productivity per engineer as a baseline. 55% treat AI fluency and product thinking as entry-level requirements.
If you're hiring for impact and expecting AI fluency, you are implicitly demanding a more sophisticated kind of seniority: the ability to direct AI thoughtfully, think at a systems level, and make strategic decisions. That kind of seniority needs to be developed, not just hired for. And developing it requires the things 81% of SA tech teams currently lack: a framework that defines what excellence looks like, feedback that helps developers know whether they're reaching it, metrics that reflect how work actually happens in 2026, and managers with enough authority to connect performance to real outcomes.
Asking developers to hit a target they can't see, measured by standards that haven't been defined, rewarded by managers who don't have the power to reward them — that's the system most of the SA developer workforce currently operates in. The pay frustration is real, but it's a symptom. This is the underlying condition.
Data from the OfferZen Salary and Benefits Report 2026, based on 2,270 valid responses collected in February 2026.
This news first appeared in our 29 April ‘26 edition, featuring the Locstat bank fraud detection.
You might also like:
Read the companion piece on why SA developers feel underpaid. See the full data on SA AI adoption in 2026. And explore the Stellenbosch founders building the companies these developers work for.
Get more SA tech and business news and subscribe to The Open Letter.



