The News
Andela has published research analyzing 47,101 technical job postings from Fortune 500 companies, finding that enterprise hiring language is failing to keep pace with the actual skill combinations employers need. The analysis identified 22 recurring skill bundles that do not map cleanly to standardized job titles, eight of which appear to represent genuinely new roles. Among the most prominent examples: the LLM Application Engineer, a role focused on building with foundation models rather than training them, and the MLOps Pipeline Engineer, which spans five existing disciplines. The central finding is that familiar titles increasingly mask hybrid requirements, with 53% of roughly 1,832 postings for roles like AI Engineer and ML Engineer requiring skills associated with at least two established roles.
Analyst Take
The job title is a lagging indicator
Andela’s research puts a number on a tension that engineering leaders have felt for the better part of three years: the skills market is moving faster than the classification systems used to hire into it. When skills associated with LLM Application Engineering began appearing in job postings as early as 2016, Fortune 500 HR systems were still years away from having a consistent vocabulary for them. That gap has widened considerably with the generative AI wave. The practical consequence for ITDMs is straightforward. Organizations that define technical headcount through job titles and traditional role taxonomies are measuring the wrong thing. They’re hiring for yesterday’s abstractions while the work has already moved on.
This is not a recruiting process problem in isolation. It’s a workforce architecture problem. When 53% of AI Engineer and ML Engineer postings actually require skills spanning multiple established disciplines, it means that compensation bands, career ladders, team structures, and skills assessments are all calibrated to a map that no longer matches the territory.
What government tech shops can learn from this
The implications extend well beyond Fortune 500 commercial hiring. In the public sector, where workforce planning cycles run longer and classification systems are even more rigid, the lag is likely more severe. According to ECI Research’s Google GovTech Survey, 47.2% of respondents selected “Developer velocity and ease of integration” as the factor carrying the greatest weight in their final technical selection process, once baseline compliance requirements are met. That preference for velocity is entirely consistent with what Andela’s data shows: organizations want to ship faster, but their workforce planning apparatus is structured around roles that don’t reflect how modern software is actually built.
The Andela findings also put pressure on a specific structural problem in government acquisition. ECI Research’s Google GovTech Survey found that 43.0% of respondents rely on a hybrid model where external Systems Integrators develop code while internal teams own architecture. If internal teams are responsible for architectural decisions but are hired and classified under role definitions that don’t account for LLM orchestration, vector databases, or agentic workflows, the architectural oversight function is compromised. You can’t govern what you can’t evaluate, and you can’t evaluate capabilities your classification system hasn’t named yet.
The developer experience angle
For developers, the Andela research validates something many already know from lived experience: the job title on their offer letter often has little to do with the actual work. The MLOps Pipeline Engineer spanning five disciplines isn’t an edge case. It’s the norm. Developers navigating this reality face a skills development problem with no clear roadmap, because the destination roles don’t yet have stable names or canonical curricula attached to them.
This connects directly to retention risk. ECI Research’s Google GovTech Survey found that 56.8% of respondents reported that developer frustration or burnout is having a moderate impact, with complaints being common even where retention remains steady. Ambiguous role definitions, mismatched expectations, and the cognitive overhead of operating across multiple disciplines without formal recognition all feed that frustration. Andela’s data suggests the problem isn’t that developers are being asked to do too much generically. It’s that they’re being asked to operate as hybrid roles while being evaluated, compensated, and managed as single-discipline specialists.
Looking Ahead
The near-term implication for enterprise workforce planning is clear: skills-based hiring frameworks will displace title-based ones faster than most HR organizations expect. Vendors offering skills taxonomy infrastructure, AI-assisted candidate assessment, and role-agnostic proficiency measurement are positioned to benefit directly. Andela’s positioning as an OpenAI Select Partner, combined with its investment in measuring the impact of agentic AI training on actual engineer proficiency, suggests the company is building toward exactly this kind of continuous skills intelligence rather than point-in-time role matching.
Over the next 18–24 months, the organizations that move to skills-based workforce models will have a structural advantage in both hiring and internal talent development. The ones that don’t will continue posting familiar titles for unfamiliar work, wondering why candidates look good on paper and underperform in practice. For public sector organizations, the urgency is higher, not lower, given the longer lead times on workforce change. The window to get ahead of this shift is narrowing.
Stay Ahead of Application Development Trends
Get weekly analyst insights, research notes, event coverage, and AppDevANGLE updates delivered directly to your inbox.
Subscribe for Weekly Insights
Join technology leaders, practitioners, and GTM teams following the trends shaping modern software delivery.
Looking for deeper research access?
Explore ECI Research reports, survey insights, and market analysis through the ECI Research Portal.
