If you have spent long enough in the technology industry, you have probably seen downturns before. The dot-com collapse. The 2008 financial crisis. The 2020 pandemic shock. In most of those cycles, the pattern for workers was painful but familiar. Layoffs arrived, hiring paused and then, within a year or two, most engineers and product people found their way back into similar roles.

The 2026 slump feels different, not because the headline layoff numbers are larger, but because the absorption mechanisms that used to bring people back into the market are themselves being dismantled.

ETtech's Morning Dispatch this week described laid-off tech workers returning to the U.S. job market and facing an "unprecedented job slump back home." That phrase is not hyperbole. The structure of demand for tech labour is changing at the same time as layoffs are rising.

AI tools are great at answering questions. But what if they could actually do the work?

Agent A by Ahrefs is an AI marketing agent with access to Ahrefs data and reports. It can analyze competitors, find content gaps, identify technical issues, track brand visibility in AI search, create content strategies, build reports, and much more.

Unlike generic AI assistants, Agent A comes with pre-built marketing skills and can connect to tools like Slack, Notion, HubSpot, WordPress, and Linear to fit directly into your workflow.

See what an AI agent built specifically for marketers can do at ahrefs.com/agent-a.

Explore Agent A

Let us start with the scale. According to Layoffs.fyi data reported by ETtech, over 100,000 people have been laid off from U.S. tech companies so far in 2026, across firms including Meta, Amazon and Oracle. Crunchbase's tracking shows at least 2,704 U.S. tech workers cut or scheduled for layoffs in the week ending June 24 alone, on top of approximately 127,000 tech layoffs in 2025.

Challenger, Gray & Christmas reported that April 2026 saw 83,387 announced job cuts, up 38 percent from March, with AI explicitly cited as the primary reason for 21,490 of those cuts. In May, tech firms announced plans to eliminate 38,242 positions, the highest number since August 2024, bringing total tech cuts this year to 123,653, up more than 65 percent year-on-year.

That is the quantitative backdrop. The qualitative picture from ETtech's reporting is where the difference becomes clear. Laid-off workers, particularly those returning from H-1B stints in the U.S. back to India or other home markets, are not just facing fewer openings. They are facing hiring freezes in large companies, mid-tier roles that are being removed rather than paused, and a growing reliance on AI coding tools that directly reduces headcount demand in the very categories those workers occupy.

In prior downturns, the job market recovered in layers.

Senior leaders took time to find the right landing spots. Junior talent often struggled. But mid-tier engineers and product managers were usually absorbed by companies that had scaled down hiring during the shock and then scaled it back up once conditions stabilised.

This time, there is a clear "missing middle" problem.

Large firms are doing something they rarely did before. They are eliminating entire strata of roles in the middle rather than simply slowing intake. TechCrunch's running list of major tech layoffs in 2026 where employers cited AI shows this pattern across multiple companies. GitLab cut roughly 350 workers, about 14 percent of staff, to fund AI investments. Oracle disclosed a reduction of 21,000 employees over 12 months, explicitly linking cuts to AI deployment in its annual filing. Amazon removed 16,000 corporate roles following 14,000 cuts in late 2025.

In each case, the roles removed belonged disproportionately to mid-level engineering, operations and support functions, where routine work can now be partially automated or centralised.

This is where laid-off workers used to land. When those bands are thinned out, the recovery curve changes shape. Instead of a dip followed by a re-absorption wave, you get a step change to a lower baseline.

The other structural change comes from the tools inside engineering teams.

Opsera's AI Coding Impact 2026 Benchmark Report analysed 250,000 developers across more than 60 enterprises. It found that AI coding tools reduce time-to-pull-request by up to 58 percent, but AI-generated PRs then wait 4.6 times longer in review and introduce 15 to 18 percent more security vulnerabilities.

That is a nuanced result. It does not say "AI replaces developers." It says "AI lets some developers move much faster, but creates new review and risk costs."

Crucially, the report found that senior engineers capture nearly five times the productivity gains of junior engineers, widening the execution gap inside teams. Twenty-one percent of AI coding licenses go underutilised, indicating that organisations are still figuring out adoption.

From a hiring perspective, this matters. If senior engineers using AI tools can produce more output per person, and if junior engineers are slower to capture those gains, the incentive to hire large numbers of mid-level and junior engineers diminishes. Companies can point to efficiency metrics and argue that fewer engineers can deliver the same or more output.

The World Economic Forum's January 2026 work on developers found that 65 percent of developers expect their role to be redefined this year, moving away from routine coding toward architecture, integration and decision-making. Thirty-seven percent said AI had already expanded their career opportunities. That optimism is real. It just sits alongside a short-term hiring pattern where many roles that previously focused on routine coding are being cut.

ETtech's newsletter highlighted a specific group: H-1B holders who have had to return from the U.S. after layoffs or visa limitations. These workers often have mid-level experience and strong technical skills, but their timing is unfortunate.

They are re-entering home markets at precisely the moment when:

The result is an unprecedented mismatch. Highly capable workers face a home job market that does not resemble the one they left and that is not yet ready to absorb them into adjacent roles.

Historically, someone with five to ten years of U.S. engineering experience could come home and slot into a senior role at an Indian IT services firm or a fast-growing product company. Today, those firms already have strong senior pipelines, are automating parts of their delivery and are themselves facing margin pressure. They are being far more selective.

If you are a laid-off tech worker looking at this landscape, the point of spelling it out is not to discourage you. It is to help you focus on moves that have a chance of working.

Three practical shifts are worth serious consideration:

Move from output to ownership. The roles that will survive and grow are ones where you own outcomes rather than tasks. That means architecture, technical leadership, integration work and product thinking. If your CV is heavy on feature implementation, invest time in building evidence of system-level thinking.

Lean into domains, not just tools. AI coding skills are becoming table stakes. What differentiates a candidate is domain knowledge: payments, logistics, healthcare, cybersecurity. The WEF data shows developers expect their roles to move towards decision-making supported by tools, not pure implementation. Pick a domain and go deep.

Be realistic about geography. If your closest market is saturated, look at remote roles in firms that still struggle to hire locally, or at companies in adjacent industries undergoing digital transformation. The jobs may not sit inside the classic tech sector, but the skills map can match.

None of these are easy moves. All are more promising than waiting passively for "the market" to come back to where it was.

The most useful way to frame the current tech job market is to say that it combines a cyclical downturn with a structural shift.

The cyclical part is familiar: rates, valuations, overhiring and correction. The structural part is new: mid-tier role elimination, AI-assisted productivity changes and a different shape to the demand curve for developer labour.

When you put those together, you do not get a gentle return to the previous baseline. You get a new baseline. The workers caught in that transition deserve more than general reassurance. They need clear sight of what has changed and where their skills can fit in a market that will not look like 2018 again.