Every week, another breathless headline declares software engineering dead. Another AI demo shows a chatbot building a full-stack app in 90 seconds. Another LinkedIn thought leader posts a funeral wreath emoji next to the words "traditional coding."
And every week, I watch senior engineers at real companies quietly doing something that looks nothing like those demos. They're not typing code line by line. But they're not being replaced, either. They're doing something I've started calling plan-and-review software engineering. And honestly, it's the biggest change in how software gets built since the move from waterfall to agile.
What Is Plan-and-Review Software Engineering?
Plan-and-review software engineering is a workflow where engineers spend most of their time designing systems, writing specifications, orchestrating AI coding tools, and reviewing the output — rather than writing code by hand. The engineer becomes a director. The AI becomes the production crew.
This isn't theoretical. It's already happening. Sundar Pichai disclosed on an earnings call that more than 25% of new code at Google is now generated by AI, then reviewed and accepted by engineers. GitHub's own research shows Copilot users accept roughly 30% of code suggestions, and that number keeps climbing as models improve. Tools like Cursor, Claude Code, and Aider are pushing the boundary further every month.
I've been building software for over 14 years. The shift happening right now is real. Two years ago, I used AI assistants as glorified autocomplete. Today, I routinely describe an entire feature's architecture in natural language, let an AI agent scaffold the implementation, then spend my time reviewing, adjusting, and stress-testing the result. My job didn't disappear. It changed shape.
How Is the Software Engineering Role Changing Because of AI?
Here's the thing nobody's saying about this shift: it doesn't make the job easier. It makes it different. In some ways, harder.
When I was writing every line myself, I had intimate knowledge of what the system was doing because I'd typed it into existence. Now, when an AI generates 200 lines of a service layer in seconds, I need to understand that code just as deeply without having written it. That's a genuinely different kind of expertise.
The engineers I see thriving in plan-and-review workflows share a specific set of skills:
- System design thinking. If you can't articulate what needs to be built at an architectural level, you can't direct an AI to build it well. Vague prompts produce vague code. Every time.
- Specification writing. The prompt is the spec now. Engineers who write precise, unambiguous descriptions of behavior get dramatically better results than those who wing it.
- AI orchestration. Knowing which tool to use for which task, how to chain agents together, when to break a problem into sub-problems the AI can handle independently. I've written about how AI coding agents are reshaping the way we think about code, and this orchestration layer is where the real leverage lives.
- Critical code review. Not just "does this compile" review. Deep review that catches subtle logic errors, security holes, and architectural drift. AI-generated code looks confident even when it's dead wrong.
- Domain expertise. The AI doesn't know your business rules, your compliance requirements, or why that edge case from three years ago almost took down production at 2 AM. You do.
Addy Osmani, Engineering Lead at Google, has written extensively about this. He's argued the developer's role is moving toward being a "reviewer-in-chief" — someone whose primary value comes from judgment, not keystrokes. That framing tracks with what I'm seeing on the ground.
The engineers who will be most valuable in 2026 aren't the ones who type the fastest. They're the ones who think the clearest.
What's the Difference Between Vibe Coding and Plan-and-Review Engineering?
Most people are conflating these two things. That's a mistake.
Vibe coding is what happens when someone opens an AI tool, types "build me a task management app," and ships whatever comes out. It's fast. It's fun. And it produces code that, in my experience auditing AI-generated projects, creates serious technical debt within weeks. I've personally seen vibe-coded applications with hardcoded secrets, SQL injection vulnerabilities, and architectural patterns that make future changes nearly impossible.
Plan-and-review engineering is the professional version of the same technology stack. The difference isn't the tools. It's the process.
A plan-and-review engineer starts with architecture. They define the data model, the API contracts, the error handling strategy, and the testing approach before the AI writes a single line. Then they use AI to accelerate implementation of a well-defined plan. Then they review the output with the same rigor they'd apply to a junior developer's pull request. Probably more rigor, honestly, because AI makes confident mistakes that a junior would at least flag with a comment saying "not sure about this."
Same equipment. Wildly different outcomes.
This is why I push back hard when people say AI will eliminate the need for engineering skill. It's the opposite. AI amplifies the gap between engineers who understand systems deeply and those who don't. A strong engineer with AI tools is 10x more productive. A weak engineer with AI tools produces 10x more bugs.
Will AI Replace Software Engineers?
Short answer: no. Longer answer: it will replace software engineers who refuse to adapt.
The data tells a clear story. Stack Overflow's 2024 Developer Survey found that 76% of developers are using or planning to use AI tools, but only 43% trust the accuracy of AI-generated code. That trust gap is exactly where human engineers live. Someone has to close it.
I've shipped enough features to know that the hard part of software engineering was never typing. It was figuring out what to type. It was debugging the interaction between three microservices at 11 PM when the monitoring dashboard lit up red. It was sitting in a room with a product manager and translating "we need it to be faster" into a concrete set of database indexes and caching strategies.
AI can't do that yet. And even when it gets closer, someone will still need to validate that it did it correctly. That's the plan-and-review loop.
What is disappearing is the junior developer task of implementing well-specified, straightforward features from scratch. If the task is "add a CRUD endpoint for this data model," an AI can do that in seconds. This means the entry path into software engineering is shifting. New engineers need to develop system-level thinking faster than previous generations did. I've written about how the state of software engineering is evolving in 2026, and the through-line is clear: the floor for what counts as "engineering work" is rising. Fast.
What Skills Do Software Engineers Need in the Age of AI?
If I were starting my career today, here's where I'd put my time:
- Architecture and system design. This is the highest-leverage skill in a plan-and-review world. If you can design the system correctly, AI can build it. If you can't, no amount of tooling saves you.
- Reading code faster than writing it. Most engineering education optimizes for writing. The future optimizes for reading, understanding, and evaluating code you didn't write. Get comfortable reviewing large diffs quickly.
- Prompt engineering as specification. Not the gimmicky "10 magic prompts" stuff. Real specification writing. The kind where you define constraints, edge cases, and acceptance criteria in natural language so precisely that an AI produces correct code on the first try.
- Testing and validation. If AI writes the code, humans validate the behavior. Property-based testing, integration testing, adversarial testing. These become even more critical when the code wasn't written by someone who understands the business context.
- Domain knowledge. The deepest moat any engineer can build. AI is generic. Your understanding of healthcare compliance, financial reconciliation, or real-time bidding systems is specific and irreplaceable.
Having worked on teams that adopted AI-assisted development early, I can tell you: the engineers who struggled weren't the ones with fewer years of experience. They were the ones who had spent their careers optimizing for code output rather than system understanding. The fast typists suddenly had less of an edge. The careful thinkers had more of one.
The Director's Cut
Here's my prediction: by the end of 2027, the majority of professional software will be built using some version of plan-and-review. Not because it's trendy, but because the economics are brutal. A team of three senior engineers using AI-assisted plan-and-review workflows can match the output of a team of ten working the old way. Companies that don't adopt this will lose on speed and cost. Period.
But that prediction comes with a warning. The quality of software built this way depends entirely on the quality of the humans doing the planning and reviewing. We've already seen what happens when organizations treat AI coding as a shortcut to eliminate engineering judgment — they get code quality crises and maintenance nightmares.
Software engineering isn't dying. The craft of writing code by hand is becoming a smaller part of a much larger discipline. The engineers who recognize this and invest in the skills that actually matter — architecture, orchestration, validation, domain expertise — won't just survive the AI era. They'll define it.
Stop mourning the old job. Start mastering the new one.
Originally published on kunalganglani.com