01
Empathy first
I sat in that chair for two decades. I like the headphones, the latte, the green bar at the end of a quiet hour. The craft is real. So is the satisfaction. None of that is the question.
Slide 01
A new job family is forming and it deserves its own name. Call it the AI Engineer. It is not a marketing phrase. It is what this profession is becoming and what your competitors are already hiring for. The engineer two desks over is quietly turning into one while your senior writes their fifth comment thread about why the model "doesn't really understand the system."
Slide 02
The engineer who is happy in 2026 is the engineer who ships. The engineer who is unhappy is often the one being asked to leave behind a definition of "happy" that quietly stopped applying. Those are not the same person.
If that frame annoys you, I am doing my job. Keep reading.
I sat in that chair for two decades. I like the headphones, the latte, the green bar at the end of a quiet hour. The craft is real. So is the satisfaction. None of that is the question.
The work the comfort was built around stopped being the work. The friction the platform team was paid to remove is the friction the model removed instead. Removing friction from work that no longer needs to be done by a human is not a benefit. It is denial.
It tells you the old shape no longer fits. The right move is not to make the old shape comfortable again. It is to step into the new one before someone else does it on your roadmap with your customers.
Slide 03
Squads. Tribes. Autonomy. The first widely circulated articulation of what a happy engineering org might look like at scale. Half the industry copied the org chart. Most missed the point.
The book landed. Conferences mushroomed. "Craft" became the moral frame for the daily work. A generation of senior engineers anchored their identity to it.
DORA gave the industry its first defensible link between developer experience and business outcomes. The CFO had a number. Happiness had a P&L line.
Removing the small daily indignities — the 2009 laptop, the 47-minute CI, the missing paved road — paid for itself in retention. That was the right intervention for that era.
Slide 04
Slide 05
The AI Engineer is what comes next. Same craft floor — CI/CD, automated testing, roll-forward deploys, the catalogue of things we know is good. None of that goes away. It compounds. The leverage on top of it is now orders of magnitude higher.
The published working standard for the role lives at We Went Through the Training and We're Not Seeing the Value. That piece is the job description. This deck is why your engineers should want to be one — and why you should want to fund the ones who already are.
Slide 06
If you are Bob's manager and Bob is unhappy, congratulations. You are doing your job.
Last quarter you asked him to start using AI Agent Dev Tooling and to stop hand-rolling the same five test scaffolds he has been hand-rolling since 2019.
Real instincts about state management. About idempotency. About the weird race condition in the payment retry loop nobody else can find. You do not want to lose those. They are not what is in question.
To ship working tested product to customers. Not to feel soothed. Those two things are not the same, and the gap between them is now the gap between Bob and the engineer two desks over.
The Bob I see most is fifteen years in. The next most common Bob is twelve months out of bootcamp at a Vim setup he spent two weekends configuring, treating AI as "training wheels for people who never learned the craft." Same headphones. Same one article about hallucinations that decided the issue.
Slide 07
CRUD endpoints. Report screens. A scheduled job that emails someone if it breaks. Pick any company that is not a chip designer or a flight controls vendor — that is the work their engineers are doing. There is no longer a defensible reason to write it the way Bob wrote it in 2019.
One engineer with AI Agent Dev Tooling who knows what they are doing and reviews what comes back. Same quality bar. Same test coverage. Shipped at the end of the day instead of the end of the quarter. The numbers are not subtle.
Two engineers replacing a ten-person hiring plan in twelve months. Real production code, real roadmap, real monolith decomposed. Most companies measuring this on private dashboards stay quiet because they do not want their competitors to copy them. Read the case.
If Bob is producing one feature per sprint and the engineer next to him is producing seven, you do not have a tooling problem. You have a Bob problem.
Slide 08
Slide 09
There is a market for hand-crafted. It is small. It is luxury. The marketing claim is "we built this by hand." That is the entire pitch and the entire price.
Nobody pays extra because the door panels were hand-fitted. The buyer wants the car to start when they turn the key. That is the deal. That is the entire deal.
Nobody asks the cook whether the tortillas were pressed by hand. Try selling a $5 "hand-pressed artisan" version out of the same window and you lose to the truck across the street that does the $2 version twice as fast.
Bob's craft is real. It is also invisible. The customer cannot see it. The buyer is not paying for it. The competitor across town who ships at three times the cadence is taking the deal anyway.
Slide 10
Slide 11
When you ask Bob why he does not trust AI, he points to a mistake an AI agent made for him in February of 2024. He has not touched it since. That was two years ago. Skepticism is staying current with what a tool can and cannot do. What Bob is doing is using a single bad experience from a previous era as permanent permission to stop looking.
That is the behavior of an engineer who needed an excuse, and February 2024 happened to provide one.
Has the years. Has the title. Goes to the craftsmanship conference every spring and comes back with notes on hexagonal architecture and value objects. By the standards of 2024, exactly what "senior software engineer" was supposed to mean.
Fewer years on his resume. Has never spoken at a conference. Ships seven times what Bob ships on the same quality bar. By the standard of the job that exists now, Marcus is the senior engineer in the room.
A standard that was retired while he was at the meetup. The instincts about state management still matter. The years of careful refactoring still matter. The unwillingness to update the toolchain does not. Pay for the parts that compound. Stop subsidizing the part that does not.
Slide 12
If your standups, sprint length, code review, and release process look identical to what you ran in 2024, that is the signal you missed. Bob complaining about the new tools is not the dangerous Bob. The dangerous Bob is the one who is content with the old ones, because the content Bob is not generating the friction that would tell you the work has already changed.
If a competitor down the street is shipping seven features a sprint with the same headcount, on the same quality bar, what is your plan when their pricing drops twenty percent and your customers notice? What do you tell your board? What do you tell Bob two years from now, when the soothing has nowhere left to go?
Slide 13
Pair with him. Teach him. Sit next to him for an afternoon and use the new tools together on a piece of work from your backlog, not a tutorial. Show him what shipping at the new cadence looks like in your codebase, on your stack, on the ticket he was about to spend a sprint on. That is the intervention.
If you cannot do that — if you have not used the tools yourself, if you cannot demonstrate the new cadence on a problem you own — that is a different post, and Bob is not your problem.