If you were cut in October's wave at Netflix, HubSpot, Airtable or Amazon, the headlines don't line up. Tech layoffs in 2026 have already passed all of 2025. Software postings are also up more than 20% from a year ago. Both are true. The catch is that the job coming back is a different job from the one that left, and your resume and target list should be rebuilt around that.
Is the software engineer job market recovering in 2026?
Yes, but only partly, and the recovery is lopsided. The US software development postings index (February 2020 = 100) was 78.3 on October 2, 2026. A year earlier it was 64.3, which works out to a gain of about 21.8%. The low point was 61.1 in May 2025.
CNBC's October 11 report, citing Indeed, frames it a bit differently. Software development postings are up almost 15% since late February 2025, while overall US job postings fell 7% over the same stretch. Software is growing while the wider market shrinks.
Keep three things in mind:
- Postings are still about 27.5% below their pre-pandemic level. A recovery from a deep hole still leaves you in a hole.
- Layoffs are running alongside the hiring. Layoffs.fyi counted 128,536 tech layoffs across 299 companies as of September 10, already more than the 122,606 for all of 2025. Trackers count differently (TrueUp is near 194,800), so check the live number before you quote it in an interview.
- The growth is concentrated. Most of it is senior work, and much of it carries AI in the title. That's the part that should change what you do.
Why are layoffs and postings rising at the same time?
Because fewer companies are making bigger cuts, while a different set of teams is hiring for different work. In 2023, 1,194 companies laid off an average of 220 people each. In 2026 so far, 299 companies have averaged 430 each. About a quarter as many employers are each cutting roughly twice as deep.
| Year | Tech layoffs (layoffs.fyi) |
|---|---|
| 2022 | 165,269 |
| 2023 | 265,660 |
| 2024 | 152,922 |
| 2025 | 122,606 |
| 2026 (to Sep 10) | 128,536 |
The October wave fits that pattern:
- Netflix is cutting about 6% of its workforce, roughly 1,000 of about 16,000 full-time staff. It's the company's biggest layoff since 2022.
- HubSpot cut about 660 people (7%). CEO Yamini Rangan wrote that the cut "is not driven by AI-related efficiencies" and reorganized product teams around customer outcomes with fewer management layers.
- Amazon cut "fewer than 1,000 white-collar workers" in its stores division.
- Airtable, after Bending Spoons' $1.28B acquisition, cut staff on what Federico Simionato called a "deep belief that small teams ship more and better."
Rangan's line matters because it complicates the easy story. Not every cut means AI took the job. Some are reorganizations toward smaller teams and fewer layers. Smaller teams need each person to own more, and that's exactly what senior postings ask for.
The batch size has a practical effect too. When about a thousand Netflix product and tech staff hit the market in the same week, the generic application stops working. Near-identical resumes land on the same openings, and the tailored one is the one that gets read.
Who is the software hiring rebound actually for?
Mostly senior engineers, and especially those working on AI. In Indeed economist Guillermo Gallacher's July 8 Hiring Lab analysis, 71% of the increase in software postings from May 2025 to May 2026 came from senior roles, and 37% came from AI-titled jobs.
Two caveats before you use those numbers:
- The time windows differ. The 71% covers May 2025 to May 2026, not the October year-over-year figure. Don't put "21% growth, 71% senior" in the same sentence as if they describe one period.
- The groups overlap. A senior AI engineer counts in both, so the 71% and 37% can't be added together.
The seniority mix of the postings themselves is starker. In Q1 2026, senior-level postings made up 69.3% of US software development listings. Entry-level made up 4.5%, the smallest share of any sector Indeed measured. That leaves roughly 26% for mid-level roles.
| Level | Share of US SWE postings (Q1 2026) |
|---|---|
| Senior | 69.3% |
| Mid-level | ~26% |
| Entry-level | 4.5% |
Are entry-level software engineer jobs coming back in 2026?
No, not in any meaningful volume. Entry-level roles are 4.5% of software postings, and Stanford reports that software developer employment for ages 22 to 25 fell nearly 20% from 2024.
Indeed, Q1 2026. The smallest entry-level share of any sector it measured.
The supply side makes it worse. In Refolk's index of professional profiles, there are 421,865 US Software Engineer or Developer profiles classified as entry-level and 214,698 US engineers currently titled Senior or Staff Software Engineer. That's about 1.96 entry-level profiles for every senior or staff one, competing for postings that tilt about 15 to 1 the other way.
| Measure | Entry-level | Senior / Staff |
|---|---|---|
| US profiles (Refolk's index) | 421,865 | 214,698 |
| Share of postings (Indeed Q1 2026) | 4.5% | 69.3% |
| Profiles per point of posting share | ~93,700 | ~3,100 |
Read that last row as directional, not exact, because the two profile counts use different filters (seniority for entry-level, title for senior). The direction is still unmistakable: on a per-posting basis, entry level is roughly 30 times more crowded than senior and staff.
Indeed economist Sneha Puri has warned that employers who don't build entry-level pipelines now will run short of senior talent in a decade. That's a real problem for the industry. It doesn't help a laid-off engineer this quarter.
Should a mid-level engineer apply to senior software engineer roles?
Yes, if you can show ownership. Senior postings outnumber mid-level ones about 2.7 to 1 (69.3% vs. roughly 26%) and entry-level ones about 15 to 1. Stepping down to a junior posting puts you in the most crowded pool in the market. It's the worse bet.
The usual instinct after a layoff is to lower the bar and take anything. In this market that's backwards. The junior roles are scarce and swamped, and a mid-level engineer applying to them can be read as overqualified or as a flight risk.
Aim at the senior posting if your history includes at least two of these:
- You owned a system end to end. Design, launch, on-call and the decision to deprecate it.
- You reviewed and merged other people's code regularly, including code an AI agent wrote.
- You integrated something across team boundaries, such as a model, a vendor API or a data pipeline feeding another team's product.
- You made a call that changed scope, such as cutting a feature, picking a vendor or killing a migration.
- You mentored or unblocked someone, even without the title.
If you have none of these, apply to mid-level postings and frame your bullets toward the senior shape. Don't drop to entry level.
What job is actually coming back?
The integrator: the engineer who connects AI models to a company's data, security and existing systems, then ships the result. The clearest signal is the forward deployed engineer (FDE), someone embedded with customers to get AI into production.
Lightcast counted more than 7,300 US FDE postings in the first nine months of 2026, against about 1,200 in all of 2025 and fewer than 200 in 2023. Median advertised pay reached $195,456.
Up from about 1,200 in all of 2025 and fewer than 200 in 2023 (Lightcast).
The big buyers are spending on this role:
- AWS committed $1B to its FDE organization. Asa Kalavade, VP of Forward-Deployed Engineering, says the team starts with hundreds of engineers, with thousands planned.
- Anthropic is putting $100M into its Claude Frontier Academy to train 10,000 deployed engineers by the end of 2027. The first cohorts come from Accenture, Deloitte and Morgan Stanley.
The bottleneck has moved from writing code to making a model work inside a real company, with its data, security and existing systems. That's integration work, and it rewards engineers who've shipped across system boundaries before, whether or not "AI" was ever in their title.
How to rewrite a senior software engineer resume for AI-assisted work
Rewrite your bullets around what you oversaw, integrated and shipped, not just what you wrote. GitHub says one in three pull requests now involve an AI agent, up from fewer than one in ten a year earlier. Writing code is no longer the scarce skill. Judging it, connecting it and shipping it safely is.
Lead with three verbs
- Oversaw: review volume, merge standards, incidents caught before production.
- Integrated: which systems you connected, across which team or security boundary.
- Shipped: what reached users, and what changed because it did.
Before and after
Fill the brackets with your own real figures. Never estimate in a way you can't defend in an interview.
| Before | After |
|---|---|
| Wrote backend services in Go | Owned [service], reviewing [N] PRs a week (about [X]% agent-generated) and blocking [N] regressions before release |
| Worked on ML features | Integrated [model] with [internal data source] behind existing auth, shipping to [N] customers in [timeframe] |
| Improved test coverage | Raised coverage on [module] from [X]% to [Y]% so agent-written changes merged without manual QA |
| Helped with migration | Led cutover of [system] across [N] teams and made the call to drop [scope] to hit the date |
Mirror the posting's AI wording
Part of the 37% AI-titled growth may be existing roles renamed rather than new ones, and the data can't separate the two. That doesn't make the label meaningless to you. The title change is what the screen filters on. If a posting says "AI platform engineer" or "LLM integration," your matching experience should use those words, not your old team's internal name for the same thing.
That means a different resume for nearly every posting, and that's the work Refolk takes off your plate. It writes your resume from your own history, then rewrites it for each posting you paste in, mirroring the posting's language without inventing experience you don't have.
How should you build your target list?
Target mid-size infrastructure, data and security companies alongside the AI labs, and send fewer, tailored applications. In a 25-profile sample of the 214,698 senior and staff engineers in Refolk's index, current employers skewed toward companies like Datadog, Vanta, Airbyte, Starburst and Dragos.
That skew tells you where senior engineers are employed right now, and infrastructure, data and security products are where integration work lives. By contrast, the most common employers in a 25-profile sample of entry-level engineers were Google (4) and Figma (2). The samples are small, but the pattern is consistent with the posting data: big names attract the junior crowd, and mid-size infrastructure firms quietly employ the seniors.
A practical way to build the list:
- Start with 20 companies, split between infrastructure, data and security firms and the AI or consulting firms building FDE teams.
- Filter by posting language. Keep roles that mention integration, deployment, review or platform ownership.
- Score your fit honestly before applying. A senior posting you match on four of five requirements beats an entry-level posting you match on all five.
- Tailor every application. With layoffs arriving an average of 430 people at a time, mass-applying puts you in the same pile as everyone else from your old company.
Step 3 is where most people go wrong, because they either over-apply or talk themselves out of a role they'd get. Refolk scores how well you actually fit each posting and drafts the cover letter, so you can spend your hours on the applications worth sending.
FAQ
Are software developer jobs coming back?
Some are. The US software development postings index was 78.3 on October 2, 2026, up from 64.3 a year earlier, about 21.8% higher. Postings are still about 27.5% below their pre-pandemic level, and the growth is concentrated in senior and AI-titled roles rather than generalist or junior positions.
Should I take an entry-level role after a layoff?
Usually not. Entry-level roles are 4.5% of US software postings, and on a per-posting basis that pool is roughly 30 times more crowded than senior and staff. If you have evidence of ownership, reviewing, or cross-team integration, apply to senior or mid-level postings and frame your bullets around that evidence.
What is a forward deployed engineer?
A forward deployed engineer works embedded with customers to get AI systems into production, connecting models to company data, security and existing infrastructure. US postings for the role passed 7,300 in the first nine months of 2026, up from about 1,200 in 2025, with a median advertised salary of $195,456.