Something is happening in tech hiring that most people haven’t named yet.
Job titles are lying to us. Or more accurately, they haven’t caught up with what companies actually need.
Go look at what’s being posted right now. Vercel is hiring a “Design Engineer” who needs to write production React, operate in Figma, understand SEO, and run growth experiments. Coursera just listed a “Senior Full Stack AI Engineer” who needs React, Node, Python, LLM orchestration, and RAG pipelines. Indeed currently shows over 66,000 open listings for “Full Stack AI Engineer,” a job title that barely existed two years ago. Tesla is hiring for the same profile in their electronic systems division.
These aren’t junior generalist roles. These are senior, high paying positions that sit at the intersection of disciplines that used to have entirely separate career paths, separate teams, separate hiring pipelines.
I’ve been calling this Role Convergence.
The idea is simple. Technology is compressing the distance between disciplines faster than our hiring frameworks can process. A frontend engineer who can prompt an LLM, query a vector database, and ship a working product end to end is no longer a unicorn. That person is a job listing on Vercel’s careers page with a $196K to $294K salary band.
When we started mapping this at Neoveda, we identified multiple convergent roles that are already showing up in the wild. Roles like AI Agent Developer, Conversational AI Engineer, Growth Engineer, Platform Reliability Engineer, Edge AI Engineer, Vibe Coder. None of these existed in any standard skills taxonomy couple of years ago. Most of them still don’t. And yet companies are hiring for them right now, today, with real budgets and real urgency.
The problem? There’s no shared language for these roles. No consistent way to assess whether someone can actually perform across the converged skill surfaces these jobs demand. Every company is writing its own version of the job description, inventing its own interview loop, hoping for the best.
This is exactly what we’re building Knovia to solve. We’re constructing a predictive skills taxonomy that doesn’t just catalog what exists today but anticipates what’s converging next. We’re tracking signals from research papers, patent filings, GitHub activity, public repos, NPM and PyPI package adoption patterns, all of it feeding into a living map of how skills cluster, migrate and converge into new role shapes before the job titles catch up.
I think we’re at the very beginning of the biggest restructuring of how technical roles are defined since the cloud era began. And the companies that figure out how to identify, validate, and hire for converged roles will have a structural advantage over everyone still posting job descriptions from 2019.
Would love to hear if you’re seeing this play out in your own hiring or career. What roles are you encountering that didn’t exist three years ago?
#FutureOfWork #HiringTrends #RoleConvergence
AI engineer is basically both right?it combines the fullstack + llm implementation skills. But its more then just create an application with intergrated llm. its about thinking of token costs, how to deal with high traffic, load balancers, api gateway, serve the application in the cloud.