But here is the precise cruelty of the moment: the people hiring did not stop needing software built. Upwork data from their latest investor filing shows AI-related job postings grew 53 percent year-over-year. Companies are not retreating from software. They are restructuring who they hire to build it.
What has collapsed is not software work. What has collapsed is the economic viability of being a competent, reliable, non-specialist developer. The person who can build a form, integrate an API, deploy a Rails app, or write maintainable SQL—the bread-and-butter work that used to be a sustainable, portable income stream—now competes with tools that can execute all of that on demand. And the market has noticed.
The Problem
Commodity contract development—the bulk of freelance work on Upwork, Fiverr, and PeoplePerHour, handled by developers without a specific domain authority—now pays $15 to $30 per hour as a market floor. That is according to Upwork’s official resource documentation on highest-paying skills. Ten years ago that was already thin. Now it is nonviable for anyone in a developed economy paying actual rent.
Meanwhile, developers who positioned themselves around AI—LLM fine-tuning, RAG systems, prompt engineering frameworks, computer vision pipelines—command $50 to $100 per hour on the same platforms. Upwork’s official data shows the hourly premium for AI-related work sits at 22 percent above baseline, and some reports cite higher figures for specialized subdomains. On salary basis, the gap is starker: Levels.fyi’s population of actual offer data shows ML/AI engineers at $244,785 median total compensation in Q3 2025, representing a 70 to 100 percent premium over junior developer offers in the $127,000 to $178,000 range.
But here is what makes this a structural problem rather than a cyclical opportunity: the number of commodity jobs is also contracting. Programmer employment is falling at a 14.3 percent annual rate as of 2025, according to Kelly Services—more than five times the prior pace of decline. The Bureau of Labor Statistics projects a 6 percent employment decline through 2034. The market is not just paying less for commodity work. It is hiring less of it, period.
The phenomenon has a name in labor economics: skill-biased technical change paired with labor substitution. When a new capability emerges—in this case, code generation that is broadly competent though not infallible—the workers closest to the bottom of the income distribution face simultaneous pressure on volume and on rates. Not because anyone is conspiring against junior developers. Because the economic incentive to pay for commodity execution dissolved.
The thing that has held is specialization. Developers with domain authority—the ability to judge when an LLM solution is sound and when it is dangerous, to architect systems that leverage AI primitives without outsourcing critical judgment, to operate in regulated domains where “the model did it” is not an acceptable explanation—have become more valuable, not less. They command not just a premium. They command a durable premium that has actually widened as the commodity floor has dropped.
This leaves a peculiar gap in the middle: developers with five to ten years of solid, generalist experience, who built their credibility on being able to execute well across a stack, are now stranded. They are too expensive to bid on commodity work and too undifferentiated to capture the AI specialist premium. They have become invisible to both tiers of the market.
Why This Is Happening
The mechanism is straightforward, though it takes a moment to absorb. Code generation—whether through GitHub Copilot, Claude, or GPT-4—has made the marginal value of undifferentiated developer labor approach zero in a specific way. It is not that the tools write production code flawlessly. They do not. It is that the transaction cost of reviewing, validating, and integrating LLM output is now lower than the cost of hiring someone to write commodity code from scratch, especially at scale.
This creates a price floor. If I can pay $25 an hour for a developer to write a form validator, but I can pay $0.50 in compute cost to have an LLM attempt it and then pay a $60-per-hour senior developer 15 minutes to validate it, I will never pay $25 again. The cost structure has changed. The floor has moved.
Lightcast’s analysis of 1.3 billion job postings shows that while AI skills command a 28 percent salary premium overall—approximately $18,000 annually—51 percent of AI job postings are now outside IT, indicating new role creation rather than substitution. But that role creation is happening at a level of abstraction higher than “person who can code well.” It is happening for “person who understands this domain AND can architect AI into it” or “person who can judge when automation is sound in this regulated context.” The 28 percent premium is real. The new roles are real. But they are not commodity positions. They are judgment positions.
Meanwhile, the developers most affected are the ones with the least negotiating power. Stanford’s finding that employment for developers aged 22-25 fell 16 percent in AI-exposed occupations is not a fluke. It is what happens when you add a labor substitute to the market at the exact moment when new entrants are trying to establish a beachhead. An experienced developer with a network and a reputation can pivot or command respect through past work. A recent grad competing on price against LLM output has no margin to compete on.
The platforms—Upwork, Fiverr, PeoplePerHour—have tried to stratify the market by introducing separate job categories for AI-related work. Upwork now surfaces “AI/ML” as a distinct category, pulling those jobs out of the commodity pool and making them visible to developers with relevant credentials. But this has simply made the stratification more explicit rather than resolving it. A developer who does not have demonstrated AI expertise cannot see those jobs. A developer who has only commodity experience cannot credibly claim it.
The partial solutions that do exist—online certifications on Coursera, DataCamp, and Udacity offering 8 to 16 week credentials; free materials from Hugging Face and Weights & Biases—create a pathway, but a narrow one. The person who wants to pivot from generic backend work to “someone who can deploy and fine-tune LLMs” now has to retrain, usually while earning less or taking time away from paid work. That is a real cost. And it is not guaranteed to land the specialist premium. Credentials are not credibility.
The deeper failure is that there is no visible, trustworthy layer between “I learned Python on Codecademy” and “I have shipped production ML systems.” No signal that says: “I understand this specific domain well enough to judge whether AI automation is appropriate here, and I can explain why.” That layer used to be built through years of on-the-job experience at a company. Now companies are less willing to incur that cost, and developers are less able to build it as an individual.
What Developers Are Actually Doing
Ask a developer with seven years of experience in mid-market contract work what they are doing in 2025, and the answer varies between three uncomfortable options: pivoting toward AI, taking a full-time role with lower pay to stabilize income, or rebranding as a “consultant” while doing the same work at lower rates.
The reddit discussions on r/ExperiencedDevs make this visible. Developers with solid portfolios—people who could reliably build a backend API, ship a feature, deploy to production—are reporting that traditional contract and staff roles have either dried up or now require dual expertise they do not have time to acquire. The market has moved, and the runway to move with it feels short.
Some developers are trying to add AI adjacent skills without fully rebranding. A backend developer might add “LLM integration” to their profile. A data engineer might lean into “prompt optimization.” But these are not specialist roles. They are flavors of commodity work, now with an AI label. The hourly rates for these hybrid positions have not collapsed quite as thoroughly as pure backend work—Upwork data suggests $35 to $50 per hour for developers calling themselves “AI engineers”—but they are not commanding the $50 to $100 range that genuine specialists pull.
Others are going full-time. A developer who spent five years building a livelihood on Upwork at $40 to $60 per hour is now taking staff roles at $90,000 to $120,000 per year because the contract flow has become too thin. They get health insurance and stability. They lose the leverage and the upside. And crucially, they start a clock on their specialist development. A full-time role at a non-AI company builds domain expertise in that company’s problem space, not in AI systems. The opportunity cost is real.
The third cohort is attempting to reposit themselves as “architects” or “technical advisors” while actually still executing. This is the rebrand-without-moving move. They justify $80 per hour on the theory that they bring judgment, not just execution. Sometimes it works, especially if they already have a network. More often it does not, because title inflation without a visible, externally credible reason for the new title does not move the market. An hour of review work is not worth double an hour of execution work unless someone outside the arrangement already knows and believes that.
What none of these moves address is the underlying problem: the market structure has changed. Individual developers attempting to optimize within the old structure are making rational moves in an irrational context.
Why This Is Happening: The Infrastructure Gap
The deepest layer of the problem is not economic or technical. It is institutional. Specialization requires credibility, and credibility requires a visible, trustworthy mechanism to establish it. A developer cannot simply claim expertise in “LLM systems design” and expect to command the specialist premium. Someone outside the arrangement—a hiring manager, a contract buyer, another developer—has to believe it is true.
In traditional employment, this credibility was built through institutional trust. You worked at Scale AI or Anthropic, and your employer’s reputation transferred to you. You shipped a paper, and the research community knew your name. You maintained a popular open-source library, and GitHub users implicitly trusted your judgment.
But the market for AI development has moved faster than these institutional mechanisms can operate. A developer who wants to build credibility through open-source contribution or published work on LLM systems is competing against a flood of noise. GitHub is full of toy projects. ArXiv is full of papers that describe experiments on toy data. The signal-to-noise ratio is so high that individual effort almost never breaks through.
Meanwhile, the platforms—Upwork, Fiverr, Indeed—have minimal infrastructure to help a developer build credibility in the first place. They can display credentials. They can show past work. They cannot assess whether the past work demonstrates real judgment about AI systems or whether the developer just happened to work on a project that had LLM tools in it.
This is a coordination gap. There are developers who want to build credibility in AI specialization. There are buyers who want to hire people with that credibility. There are no visible, scalable mechanisms to connect them. So the market segments by observable signals: people with existing institutional credibility (companies, papers, large follower counts on Twitter) can command the specialist premium. Everyone else has to either pivot fully into being an AI engineer, wait for institutional employment, or accept commodity rates.
What Developers Are Actually Doing
The small subset of developers who have successfully navigated this transition share a pattern: they built visibility before positioning. They shipped something small but clearly competent in an AI domain—a fine-tuning framework, a prompt optimization tool, a retrieval system—and made it public. Other developers used it, filed issues, contributed. Within 6 to 18 months, this work became the foundation of a positioning narrative. When they pitched themselves as specialists, the work spoke for them.
These developers did not rebrand from “backend engineer” to “AI engineer.” They credibly demonstrated that they could build AI infrastructure by building it visibly. The premium they now command—$60 to $100+ per hour on contract basis, or $250,000+ in total compensation at a company—is directly traceable to that work.
But this path requires something most developers do not have: a 6 to 18 month runway where they can work on something unpaid or low-paid, purely to build a public credibility signal. A developer with rent to pay, student loans, or family obligations cannot afford that runway. They have to choose between immediate income and future positioning.
The developers taking full-time roles are making a different calculation. They are trading leverage for stability and the hope that working inside an AI-adjacent company will build domain knowledge they can later position as specialty expertise. This works sometimes, especially if the role involves working alongside ML engineers or building infrastructure that touches production AI systems. But it is gambling. Many full-time roles build no such knowledge and consume the time that could be spent building public credibility.
The developers attempting to hold the middle ground—claiming $50-80 per hour as a hybrid “AI-adjacent” developer without either full specialist credentials or public work to back it up—are, in most cases, not succeeding at maintaining pre-2022 income levels. They are either holding steady at lower rates or slowly migrating toward one of the other two paths.
The precise trap is this: the developers who have both the runway and the skills to build public credibility work are, almost by definition, the ones who already had enough income or support to sustain themselves. The developers who most need a path forward—those whose commodity income has already compressed—are the ones least able to afford the investment in positioning.
The Build Opportunity
Three distinct infrastructure opportunities exist in this gap. They are not ideas for startups in the typical sense. They are coordination mechanisms or tools that would address specific parts of the problem.
The first is a credibility registry or portfolio layer specific to AI systems work. Not a job board. Not a certificate mill. A system where a developer who has built a specific piece of AI infrastructure—a retrieval system, a fine-tuning pipeline, a prompt evaluation framework—can register that work in a way that other developers and buyers can independently verify. GitHub repositories are close to this, but GitHub does not weight or surface AI-specific work. A registry purpose-built for AI development work could make signal much sharper. It could surface “this developer has built and maintained a production RAG system handling 10M+ queries” in a way that “has 12 open-source repositories” cannot. The hard problem is preventing false positives without becoming a gatekeeper. The opportunity is real if that problem is solved.
The second is a structured transition pathway for mid-market developers attempting to specialize. Not a course. Not a bootcamp. A genuinely practical map: “If you are a backend engineer wanting to move into LLM systems, here is the minimum technical knowledge you actually need, here are the real projects that build it, here is where to build public work, here is how to position it.” Most developers attempting this pivot are doing it alone, learning through trial and error, often failing. A well-researched, honest, publicly available transition guide would lower that friction substantially. An adjacent opportunity: someone building a small, real AI system project that junior developers can contribute to rather than just learn from. Not a tutorial. A working system where a developer with three years of backend experience could actually write and ship code that matters.
The third is a credibility acceleration mechanism for developers with limited runway. This is the hardest problem and possibly the most important. The issue is not that developers cannot build public credibility. It is that building it requires time or money most cannot spare. A model that explicitly paid developers a stipend—$1,500 to $3,000 monthly, enough to reduce financial pressure—to work on specified open-source AI infrastructure work could dramatically change the economics. The developer gets runway. The infrastructure work gets built. The open-source contribution becomes the credibility signal. It is essentially a grant program masquerading as a job. It would require institutional backing (a large AI company, a foundation, a VC firm willing to operate at the edge of employment law) but the mechanism is clear. Several open-source communities have versions of this working. None currently exist specifically for developers transitioning into AI specialization.
None of these is a project a solo developer should tackle alone. They require either infrastructure-level thinking (the registry), deep research and curation (the transition guide), or institutional capital (the credibility acceleration fund). But they are specific enough that a small team—a developer, a researcher, someone with hiring experience—could scope and prototype each one within 8 to 12 weeks.