The Numbers That Should Be on Every Developer's Radar
Something quiet has been happening to the economy, and it matters a lot more to developers than most tech coverage suggests. The labor share of income in the United States, meaning the slice of total economic output that flows to workers as wages and salaries rather than to capital as profits and returns, has fallen to its lowest point since World War II. That's not a minor statistical blip. It's a structural shift, and it has direct consequences for anyone whose income depends on writing code for a living.
To be concrete: when labor share falls, corporate profits absorb a larger portion of GDP while worker compensation grows more slowly than productivity. You can work harder, ship more features, and generate more value than ever, and still find that your paycheck doesn't keep pace with what you're actually producing. Sound familiar?
What "Labor Share" Actually Means (and Why It's Not Just an Econ Class Problem)
Labor share is straightforward as a concept. Take everything the economy produces in a year. Now figure out what fraction went to workers (wages, salaries, benefits) versus what went to the owners of capital (profit, rent, dividends, interest). That ratio is labor share. When it's high, workers capture most of the gains from growth. When it's low, capital does.
Post-COVID data tracked by researchers at the New York Federal Reserve shows that the decline accelerated sharply after 2020. You can read their full analysis as further reading at Liberty Street Economics. The short version: corporate margins expanded dramatically while wage growth, despite some headline gains, didn't fully offset the productivity and profit gains flowing to shareholders.
For a software developer at a mid-size company, this might look like: your team ships a product that generates $10M in new ARR, the company buys back stock, and you get a 3% raise.
Tech Workers Aren't Insulated Anymore
The 2010s created a widespread belief that software developers were immune to broader economic pressures. High salaries, signing bonuses, and fierce recruiting competition made it feel like the rules were different in tech. But the post-2022 environment has been a correction. Mass layoffs at companies that were extremely profitable, hiring freezes at profitable companies, and the aggressive expansion of AI tooling have all signaled that developer labor is no longer treated as scarce in the same way.
The falling labor share is part of the backdrop for all of this. When companies face pressure from investors to expand margins, developer headcount is now a visible target. Tools like GitHub Copilot, Cursor, and Claude give engineering managers a concrete argument: one senior engineer with AI tooling can do what three did before. Whether or not that's fully true in practice, it's the argument being made in budget meetings.
And the data doesn't care about your feelings on the matter. If labor share is at a 75-year low, something structural is happening to the negotiating power of workers across the economy, including tech workers. The question is what you do about it.
The AI Tooling Angle Is More Complicated Than It Looks
There's a tempting narrative here: AI is killing developer jobs, and the falling labor share proves it. That's too simple. AI coding tools are genuinely increasing what individual developers can produce. That's real. But the question of who captures the value of that productivity is entirely separate, and that's where labor share comes in.
If you use Cursor or Copilot to ship twice as fast, but your employer uses that as justification to hire half as many developers, the productivity gain went to shareholders, not to you. On the other hand, if you're a freelancer or an indie developer, you capture that productivity gain directly. You can see how developers are actually using AI at work to understand what the real day-to-day looks like, separate from the hype.
This isn't an argument against using AI tools. It's an argument for thinking clearly about who benefits from the leverage those tools create.
What This Means for Your Career Strategy
A low labor share environment rewards people who have some claim on capital or on the output of their work beyond a salary. That sounds abstract, but the practical implications are pretty concrete for developers.
Building something you own matters more. A side project, a SaaS product, a niche tool, anything where you capture the upside directly rather than earning a fixed wage for your contribution, positions you differently in an economy where wages are losing ground to profits. This isn't a pitch for hustle culture. It's a structural observation: the economy is increasingly rewarding ownership over labor.
Your skills need to command a premium, not just a salary. Generic software development skills are becoming commoditized faster than specialized ones. The developers who remain highly compensated as employees tend to be those who own a critical domain, whether that's a specific technical area (compilers, hardware, security), a business domain (fintech compliance, medical imaging pipelines), or an organizational one (being the person who can actually ship things in a chaotic environment).
Freelancing and consulting have structural advantages right now. When you bill by the project or by the outcome, you're closer to capturing the productivity gains from AI tools than when you bill by the hour or collect a fixed salary. A consultant who uses AI to do three weeks of work in five days and charges for the outcome, not the time, is positioned very differently than an employee whose productivity gains flow to their employer's margins.
And if you're documenting your tech journey, building a public portfolio, or writing about what you're learning, that's also a form of capital accumulation. Audience, reputation, and network are assets that compound, unlike a salary.
The Honesty Part: This Doesn't Have Easy Answers
It would be dishonest to end this with a tidy "5 steps to beat the labor share decline." That's not how structural economic shifts work. Most developers will still be employees, and being an employee isn't inherently a losing position. What matters is understanding the environment you're operating in so you can make better choices.
Some of those choices are about negotiation. Understanding that corporate profits are at record highs while wage growth has lagged productivity is useful information when you're sitting across from an HR person who says "the budget is tight this year." It's not tight everywhere. The money exists. The question is where it's flowing.
Some of those choices are about being honest about what AI actually changes in your work and your value, rather than believing either the catastrophist or the utopian version of events.
And some of those choices are simply about paying attention. The developers who navigated the 2022-2023 layoff waves best weren't necessarily the best coders. They were the ones who saw the structural shift coming, had diversified their income or their skills, and weren't caught flat-footed when a company that had been hiring aggressively suddenly wasn't.
One Thing to Actually Do This Week
If the labor share trend continues, and there's no obvious reason to expect a sharp reversal, the divide between developers who own some slice of what they build and those who purely sell their time will keep widening. So the most useful question you can ask yourself is: what do I own? Not in a legal sense, necessarily. But what do you have that compounds independently of whether your current employer keeps paying you?
That could be a project, a library with real users, a newsletter, a specialization that makes you the obvious person for a specific problem, or even just a well-documented body of work. None of those things protect you completely from structural economic forces. But they put you in a very different position than someone whose only asset is a job title at a company whose margins are being watched by investors who've never written a line of code.
Start there. Pick one thing you can begin building ownership in, and put one hour toward it before the week is out.
