Job Postings for Software Engineers Are Rapidly Rising

Job postings for software engineers appear to be ticking up again after a sharp post‑2022 slump, but many question whether narrow metrics and selective time windows are being used to oversell a rebound. Commenters debate how rapidly improving AI coding tools are reshaping the labor market: some see them as amplifying experienced engineers’ output while hollowing out junior and “perpetual intermediate” roles, others argue they generate technical debt and have yet to show clear productivity gains for firms. Underneath is a broader uncertainty over whether AI will ultimately expand demand for software and specialized engineering skills, or concentrate power and jobs in fewer hands even as coding itself becomes easier.

Job posting data and chart skepticism

  • Several commenters say the article cherry-picks a short time window and uses exaggerated axes to make a modest uptick (~9% over a few months) look dramatic.
  • Others link the full FRED series and note: big COVID-era hiring spike, sharp post-2022 drop, then a gradual rise since ~2023.
  • Debate over whether this recent increase is meaningful trend or noise; consensus that more years of data are needed.

LLMs and the nature of software work

  • Many see LLMs as strong code generators for boilerplate, CRUD, and “vibe coding” prototypes, but weak at complex, high-invariant or low-level systems.
  • Common pattern: experienced engineers use LLMs as “interns” or assistants, especially for tests, documentation, small tools, and repetitive tasks.
  • Several argue you still need humans to translate product requirements into architecture, manage complexity, and maintain quality.

Limits of agentic coding

  • Recurring theme: context window and comprehension limits cause agents to degrade large codebases, create “god objects,” and accumulate technical debt.
  • Some find agents good at skeletons; others only trust them for extensions within well-designed modules. Success depends heavily on prior design and task decomposition.
  • Concern that massive AI-generated PRs are effectively unreviewable and hide bugs/security issues.

Workplace AI mandates and hype

  • Reports of companies tying performance to token usage, requiring 100% AI-written code, and prioritizing “AI-native” behavior over actual productivity.
  • Criticism that this is investor- and management-driven hype rather than proven efficiency.
  • Disagreement on measured productivity impact: some cite studies showing losses or failures of gen-AI pilots; others reference newer results with modest gains.

Software labor market and cycles

  • Several see current conditions as a post-bubble hangover (COVID overhiring, rate hikes, tax changes), not primarily AI-driven.
  • Views diverge:
    • Pessimists predict fewer developers per project and consolidation of power/wealth.
    • Optimists expect more total projects, more startups, and rising demand for experienced engineers who can wield AI.
  • Some predict higher senior salaries and weaker prospects for “perpetual intermediates” and juniors.

SaaS and broader business impact

  • Mixed views on a coming “SaaS apocalypse”:
    • Some think AI will enable teams to replace expensive SaaS with tailored internal tools.
    • Others argue big SaaS (e.g., enterprise CRM) is protected by compliance, sales footprint, and organizational inertia, not just code.