A widely shared data point suggests software engineering job postings have rebounded to their highest level since November 2023, complicating the narrative that AI is systematically eliminating coding roles.
A Reddit post on r/singularity flagged something this week that the tech industry's doom-and-gloom contingent was not expecting: software engineering job postings, by at least one measure, have climbed to their highest point in roughly eighteen months. The post drew 57 upvotes and 34 comments within its first hour, which is the kind of immediate traction that suggests it hit a nerve. The "AI killed the coding job" narrative has been repeated often enough that it has started to feel like settled fact. This data point, if it holds up to scrutiny, suggests the reality is considerably more nuanced.
Before treating this as confirmation of a full hiring recovery, the sourcing deserves careful attention. The Reddit post did not specify which job board the figures came from, what geographies were included, or how the count handled duplicate postings across platforms like LinkedIn, Indeed, and Greenhouse. Job posting data is notoriously noisy. A single company posting the same role across five platforms inflates raw counts without reflecting genuine demand. That caveat matters here because the gap between postings and actual hires has widened significantly since 2022, as companies have used postings to build candidate pipelines without committing to headcount. The signal is real enough to take seriously, but it warrants treating as a directional indicator rather than a precise employment forecast.
Assuming the underlying trend is directionally accurate, the more important question is what is driving it. The simplest explanation is cyclical: tech hiring collapsed through 2023 and into early 2024 following the mass layoffs at Meta, Amazon, Google, and Microsoft, and a rebound from those lows was always probable regardless of what AI was doing to productivity. Hiring freezes do not last forever. The companies that cut aggressively in 2023 are now sitting on leaner teams while their revenue lines have recovered, and some degree of backfilling was inevitable.
But cycle alone does not explain the full picture. There is strong anecdotal and job-category evidence that the roles coming back are not the same ones that disappeared. Infrastructure engineering, security, and ML-adjacent full-stack roles appear to be absorbing a disproportionate share of new postings. This tracks with what is happening at the product level: companies that integrated AI tools into their workflows in 2023 and 2024 are now discovering that running those tools at scale requires more engineering capacity than anticipated, not less. AI systems need monitoring, evaluation pipelines, fine-tuning infrastructure, and integration work that does not disappear when the model itself is mature.
The entry-level picture is harder to read and probably less encouraging. The roles that have historically served as on-ramps for junior engineers, basic CRUD applications, internal tooling, and straightforward API integrations, are precisely the categories where coding agents and vibe coding tools have made the most measurable impact on individual productivity. A senior engineer with Cursor or GitHub Copilot can now absorb work that previously justified a junior hire. That compression is real and it is not reversing. What is recovering is the senior end of the market, and that distinction matters enormously for anyone thinking about pipeline and career development.
What Founders Should Actually Do With This
For startup founders making hiring decisions in mid-2026, the practical read is this: if you have been waiting for a sustained signal that engineering talent is available and not yet repriced upward, that window may be closing. Compensation benchmarks for senior engineers, particularly those with ML infrastructure or security experience, have already started moving. A hiring rebound concentrated at the senior level in a market where the total supply of experienced engineers has not grown proportionally is a straightforward recipe for wage pressure.
The team structure question is equally worth examining. The most common mistake founders make when interpreting a job market recovery is assuming they should rebuild headcount along the same lines as before. The productivity tools available in 2026 genuinely do change the calculus. A three-person engineering team with the right tooling and a senior architect making good decisions about what to automate versus what to build by hand can outperform a ten-person team operating the way engineering teams operated in 2020. The job posting rebound does not mean the old staffing models are back. It means demand for the people who know how to operate in the new model is finally showing up in the data.
The broader implication for the industry is that AI and software engineering employment were never headed toward a zero-sum outcome. The more likely long-term pattern is what economists call task displacement with occupational expansion: some entry-level work disappears, demand grows for people who can supervise, evaluate, and extend AI-generated output, and the total number of roles stabilizes at a different distribution than before. The November 2023 peak being matched again in early 2026 is consistent with that story. It is not a vindication of the status quo. It is evidence that the transition is messier, slower, and more uneven than either the optimists or the pessimists predicted.
Also read: Apple Was Not Ready for How Many People Wanted an AI MacBook and That Tells You Something Important • Building a transformer from scratch in C++ with no external dependencies is not a stunt it is a signal about what founders need to understand • The Economist's AI wealth loop argument is not science fiction and founders need to understand the mechanism before it reshapes the ground under them
