The Single-Seat Architect
A lot of professionals aren't making it back into the market.
That's not a prediction. That's what's happening right now. And if you're in this industry, you already know someone it's happened to. You probably just haven't said it out loud yet.
So let me say it.
How We Got Here
A non-trivial percentage of CEOs discovered ChatGPT sometime in the last two years. They typed a prompt. They got something back that looked like a product spec, or a business plan, or a chunk of code. And something broke in their brain.
They didn't learn what AI can do. They learned what AI looks like it can do. And that's a dangerous distinction — because now they think building software is easy. They think the reason it was hard before was the developers, not the problem. They think the $200/hr architect was overhead, not the only person in the room who understood why the last three projects failed.
This isn't new. Developers have been treated like they were a dime-a-dozen for fifteen years. Every outsourcing wave, every bootcamp boom, every "we'll just hire three juniors instead of one senior" decision — it all came from the same place: the belief that software is a labor problem, not a thinking problem.
AI didn't create that delusion. It compounded it.
What Actually Changed
Now the thinking goes: if AI can generate code, why do I need a team? If ChatGPT can write a PRD, why do I need a product person? If I can get a working prototype in a weekend, why was that project estimated at six months?
And here's the thing — they're not entirely wrong that the landscape changed. They're just catastrophically wrong about what changed.
What changed isn't that software got easier to build. What changed is that the floor collapsed. The baseline tasks that used to require a human — writing boilerplate, translating specs into code, wiring up CRUD endpoints — those aren't jobs anymore. They're prompts.
The hard problems are exactly as hard as they were before AI. System design. Ambiguity resolution. Figuring out why the requirements contradict each other before you've built the wrong thing for six months. Understanding regulatory constraints. Knowing when the architecture will collapse under scale and why. Making trade-offs between consistency and availability when a product person is staring at you waiting for a yes.
AI can't do any of that. Not because the models aren't good enough yet. Because those problems require judgment, context, and the kind of earned intuition that only comes from having been wrong enough times to recognize the shape of the next mistake before you make it.
The Other Side
I know this because I lived the other side of it.
I spent three quarters unemployed last year. Twenty-plus years of building software, and I couldn't get back in. Companies everywhere were claiming they were hiring, but I honestly don't think 90% of them were. Many were preparing for headcount budgets that never materialized. Others were taking advantage of a flooded market, low-balling experienced engineers 50 to 70 percent below their market rate — and finding takers, because people were desperate.
The market was nasty. From what I'm hearing, it still is.
And while I was in that gap, I watched the AI narrative accelerate in real time. Every week, another LinkedIn post about shipping a product in a weekend. Another CEO tweeting about replacing their engineering team. Another think piece about how developers need to "adapt or die" — written by someone who's never had to adapt to anything harder than a new iPhone.
Who's Actually Coming Back
But here's what I noticed from the other side.
The professionals starting to make it back aren't the ones with the deepest specialization. They're the ones with the widest experience. The developer who also understood product. The backend engineer who also did infrastructure. The architect who'd sat in sales calls and heard what the customer actually needed versus what the ticket said.
They didn't just learn to code. They learned to think across boundaries. And now, paired with AI, those people are devastating.
A new role is settling under that collapsing floor. I'd call it the single-seat architect — someone who spent years accumulating lateral experience across product, engineering, data, infrastructure, and operations, and who now discovers that AI gives them the leverage to build entire products on their own.
Not prototypes. Not MVPs held together with API calls and prayer. Actual products with real architecture, real domain modeling, real compliance, real coherence across every layer of the stack.
That's not hype. I'm building this way right now — solo, with AI as my architecture partner. The rigor isn't lesser because there's no team. It's different. AI doesn't replace the people I've worked with over the years. It replaces the limitations of working alone.
The Uncomfortable Part
The market isn't going to correct for this kindly. There will not be a gentle transition period where displaced specialists reskill into architects over a few months of online courses. Architecture isn't a certification. Lateral thinking isn't a bootcamp. The judgment that makes someone valuable in the AI era was built over years of cross-disciplinary work — product decisions, infrastructure trade-offs, customer conversations, failed projects, recovered projects.
You can't speedrun that.
So when I hear people say "AI won't replace developers, it'll just change what developers do" — I think that's a comforting lie dressed up as optimism. AI is already replacing developers. What it won't replace is the person who knows which problem to solve, how the pieces fit together, and what's going to break at 3 AM when the architecture can't support what sales just promised.
If that's you — if you spent your career going wide instead of just deep — this is your moment. The market has never valued lateral thinkers more than it does right now, even if it doesn't know how to say that in a job posting yet.
And if that's not you yet — stop learning another framework. Start learning an adjacent discipline. Product. Data. Infrastructure. Compliance. Sales. Anything that forces you to think about software as a system rather than a stack.
The floor is gone. Nobody's going to rebuild it for you. Not your employer. Not a bootcamp. Not the next framework.
But if you've spent your career learning how things break — not just how they're built — you don't need a floor. You never did. The floor was for people who needed something to stand on. You're the person other people called when the floor gave out.
That hasn't changed. The market just forgot for a minute.
Remind them.
Get new posts in your inbox. No spam, unsubscribe anytime.