Ten years as a software engineer, and I’ve never met a technical shift that aimed straight at the profession itself the way agent coding does — and it all happened in the last three months. I recently read Augment’s “How we hire AI-native engineers now,” which redefines the human role as moving “from author to architect and editor.” The line that stung: pure coding ability is no longer the primary thing that differentiates engineering talent. This is my own reflection after reading it — not a retelling. The original is worth reading yourself.
A question that stung a little
Augment’s piece (by Alex Ding, Alyah Sablan, Chris Marty, and Vinay Perneti) opens with a blunt question: how do you hire engineers when agents write 99% of the code? Link at the bottom — I really recommend the original.
What stung was personal: the core capital I’ve built over ten years is exactly the thing getting commoditized — “writing code fast and correctly.” So my reflexive anxiety isn’t “I can’t write code anymore.” It’s the harder one — what’s left of my differentiation?
Underneath sit two things that were bundled together for a decade and are now splitting apart: being good at writing code, and being good at deciding what to write and steering a human-plus-agent system to the right outcome. Inside the phrase “he’s a good engineer,” those two always felt like one thing; only when code gets cheap do you see that one is depreciating and the other appreciating.
When the cost of producing code drops toward zero, the most expensive mistake becomes building the wrong thing — and your moat moves with it, from “how fast you write” to “how right you choose.”
The map Augment draws
The article has a “traditional vs AI-native engineering” table that I think is its sharpest part (paraphrasing their framework):
| Traditional | AI-native |
|---|---|
| Writing code | Specifying intent, evaluating tradeoffs |
| Implementing solutions | Orchestrating agents |
| Solving problems | Choosing the right problems |
| Individual output | System-level outcomes |
From there they derive six dimensions of AI-native engineering, each with a core question:
- Product & Outcome Taste — Are we building the right thing?
- System & Architectural Judgment — Will this survive production?
- Agent Leverage — Can you turn AI into real engineering throughput?
- Communication & Collaboration — Can you communicate intent clearly and collaborate across perspectives?
- Ownership & Leadership — Do you drive outcomes, not just tasks?
- Learning Velocity & Experimental Mindset — Can you evolve as fast as the tools?
Notice what’s missing from the list: “pure coding ability” doesn’t appear as a standalone dimension. Not because it’s unimportant, but because it’s no longer the thing that separates one engineer from another. They also name four talent profiles (AI-native systems / product / applied-AI / early-professional engineers), each weighting the six dimensions differently — details in the original.
Three takeaways for me
For a working engineer, the useful thing about reading someone’s hiring rubric is translating it into “where do I invest next.” Mine:
1. Move skill investment from “coding speed” to things that compound. Capital invested narrowly in “fast and correct” is now a depreciating asset; capital in judgment, product taste, agent orchestration, and learning velocity compounds. This isn’t a one-time tradeoff — it’s a revaluation of career capital, charged with interest, by the year.
2. “Agent leverage” is a delegation skill. The article has an analogy I like: using agents is like managing a report who’s astonishingly fast and occasionally, very confidently, wrong. Shaping a problem so it can execute well, pulling it back when it drifts, and verifying its output — that’s a different muscle from writing code.
3. Don’t declare “coding doesn’t matter” across the board. Where the hard part is the code — novel algorithms, performance-critical kernels, areas agents are still weak — raw coding ability remains a differentiator. Commoditization advances unevenly; this split hasn’t reached every corner.
Closing
I’m not pessimistic. This isn’t an “engineers are out of a job” story — it’s a “the craft is moving up the abstraction stack” story. Just as high-level languages once commoditized assembly skill and the value moved up a rung, agent coding is the next rung. What gets commoditized was never “the engineer” — it’s the most automatable layer of the engineer’s work.
Augment says it themselves: nobody has this fully figured out yet, but hiring is already changing whether the interview process has caught up or not. As a ten-year engineer still actively learning and adapting to the new tools, I’m sharing this in that spirit.
Original (read it): How we hire AI-native engineers now — Augment Code
