A veteran engineering leader who has run software teams at Microsoft, Snap, and Google is pushing back on the "AI kills coding jobs" narrative, and his argument is worth taking seriously. His framing: engineers were hired to solve problems, and code was just the tool they used to do it. That changes how you should be thinking about your own position right now.
The piece is honest about not knowing what happens after the next 12 to 18 months. But within that window, the author is clear that the shift is already underway and moving faster than anything the industry has seen before. AI agents can scaffold, generate tests, wire up APIs, and churn out boilerplate faster than any human team. That part of the job is effectively being automated, and the open question is what fills the space that creates.
The implication for you is concrete. If the execution layer gets cheaper and faster, the constraint moves up the stack. Deciding what to build, understanding why it matters, and navigating the messy human context around a product become the scarce resource. The engineers who thrive in this shift are the ones who were already doing that work, or who start doing it now before the window closes.