Agentic Engineers: Role, Market, and Career Outlook
TL;DR — The agentic engineer role is a convergence of existing disciplines (software engineering, LLM integration, retrieval/data engineering, DevOps, security, workflow design) rather than a brand-new one. Demand and pay signals are strong but noisy; the deciding variable is engineering and governance discipline.
The Emergence of Agentic Software Engineering
TL;DR — Coding-agent adoption is now broad — a verified study estimates ~22–29% adoption across its 128,018-repository sample — yet a much narrower frontier cohort has moved from prompting models to constructing autonomous infrastructure. Covers the collapse of vibecoding, the CRAFT framework, the Core Four architecture, the OpenClaw access-risk case study, and the convergence of software and industrial automation.
Andrej Karpathy on Vibe Coding: Notes for Agentic Engineers
TL;DR — In a February 2026 one-year retrospective, Karpathy distinguished the casual “vibe coding” he coined in 2025 from “agentic engineering” — his proposed name for the professional default, where you orchestrate AI agents under oversight rather than accept generated code unchecked. The scarce engineering skill shifts from writing code to directing and verifying it.
The Transformation of Software Engineering: From Syntax to Intent
TL;DR — The primary developer-machine interface has shifted from writing syntax to expressing intent. Covers the persistent “80% problem,” context and harness engineering as the real performance bottleneck, multi-agent swarms, the “slopsquatting” supply-chain threat, and CapEx-vs-OpEx token economics.