Ask HN: SWEs how do you future-proof your career in light of LLMs?

Perceived impact on SWE roles

• Many expect junior and “code monkey” roles to shrink first; LLMs already handle boilerplate, tests, CRUD, and simple scripts.
• Some argue mid‑level devs also at risk where work is mostly gluing APIs and frameworks.
• Others think all levels (including seniors) are exposed in the long run if “agents” become truly capable; some predict AI‑justified layoffs starting 2025.
• Counter‑view: capable senior devs are unlikely to be replaced by current or near‑term tech; the real scarcity will be people who can own complex systems and make good decisions.

LLMs as tools vs. replacements

• Strong camp seeing LLMs as a major productivity tool: faster scaffolding, tests, refactors, docs, SQL, and learning unfamiliar stacks.
• Opposing camp finds LLMs a net negative: hallucinations, wrong APIs, bad edge‑case handling, and extra review outweigh speed gains.
• Several report that LLM‑generated PRs “work” but are sloppy, inconsistent, hard to explain, and break non‑happy paths—often requiring rewrites.
• Widespread view: current LLMs excel at small, well‑scoped tasks; they struggle with large, messy, multi‑service systems and long‑horizon design.

Business incentives, outsourcing, and layoffs

• Executives and consultants may over‑believe AI hype and cut staff prematurely, using LLMs as a layoff justification.
• Some companies already claim they are freezing or reducing hiring because of AI, though they still recruit engineers in practice.
• Several predict a Darwinian phase: organizations that over‑automate will ship fragile systems, then later pay heavily for consultants and cleanup.

Future‑proofing strategies

• Learn to use LLMs effectively; being the engineer who can steer tools well is seen as protective.
• Move “up the stack”: domain expertise, architecture, requirements, trade‑offs, product sense, and communication with stakeholders.
• Specialize where data is scarce and reasoning is hard: systems, embedded, obscure hardware, scientific computing, security, etc.
• Develop “talent stacks”: combine SWE with SRE, product, a vertical domain (finance, bio, automotive), or people/management skills.

Limits, risks, and long‑term scenarios

• Fundamental limitations cited: lack of real understanding, brittle reasoning, time/context constraints, and unverifiable hallucinations.
• Fear that over‑reliance will erode junior training pipelines, leaving too few future seniors.
• Some see this as another hype cycle like CASE tools, no‑code, or self‑driving; others think we are at the start of a real paradigm shift whose endpoint (up to AGI and broad job loss) is highly uncertain.