## The Layoffs Are Just the Beginning
Every week, another headline: thousands of engineers laid off at a major tech company. The narrative in most newsrooms is that AI is "coming for" software engineering jobs. That framing is wrong — but not in the way most engineers hope.
The truth is simpler and more uncomfortable: AI will not replace software engineers. It will make most of them unnecessary.
That distinction matters. And if you understand it, there is an enormous opportunity sitting right in front of you.
## From Teams of Ten to Teams of Two
Here is what I am seeing on the ground, not in think pieces, but in actual production work. Tasks that used to require a frontend developer, a backend developer, a DevOps engineer, a QA tester, and a project manager can now be handled by one or two people who know how to work with AI-powered development tools.
I am not talking about toy demos or weekend projects. I am talking about full production applications — deployed, maintained, and serving real users. The productivity multiplier is not 2x or 3x. It is closer to 5x or 10x for the right person with the right tools.
What does that mean for companies? It means the team of ten becomes a team of two or three. Not because the work disappeared, but because the work got dramatically faster to execute. The remaining engineers will be more senior, more productive, and significantly more valuable. They will command higher salaries because they are doing the work of five people.
But the other seven? They need a new plan.
## The Engineers Who Survive Will Thrive
Let me be clear: software engineering as a discipline is not going anywhere. Someone still needs to architect systems, make design decisions, debug the hard problems, and understand what the AI-generated code is actually doing. The engineers who can do that — who can think at the systems level and use AI as a force multiplier rather than a crutch — will be in the strongest position of their careers.
The problem is that most software engineering work was never about those high-level decisions. It was about implementation. Writing the CRUD endpoints. Building the forms. Setting up the CI pipeline. Configuring the database. That work is exactly what AI handles best, and it is exactly what employed the majority of engineers.
The floor is rising. What used to be senior-level productivity is becoming the baseline for anyone who can effectively prompt an AI coding assistant.
## The Real Opportunity Is Not in Engineering
Here is where most analysis of this shift stops. "Engineers will be reduced, the good ones will be fine, tough luck for everyone else." That is incomplete.
The real story is on the business side.
Every small business, every mid-size company, every enterprise department is now trying to figure out how to implement AI. They do not need a team of software engineers. They need someone who can build the tools. Someone who understands what AI can do, what it cannot do, and how to bridge that gap for a specific business problem.
Think about what businesses actually need right now: a custom internal dashboard that pulls data from three different systems. An automated workflow that handles client onboarding. A tool that lets the sales team query their CRM with natural language. A content pipeline that drafts, reviews, and publishes with human oversight at key checkpoints.
None of these require a computer science degree. All of them require someone who understands the business problem and knows how to use AI-powered development tools to solve it.
## Tool Creators: The New Essential Role
I call these people "tool creators" — and they are the most in-demand role that most companies do not even know they need yet.
A tool creator is not a traditional developer. They are someone who can sit with a business owner, understand the workflow, and build a working solution using tools like Claude Code, Cursor, or similar AI-powered development environments. They ship fast. They iterate based on feedback. They do not write code from scratch — they direct AI to write it, then validate, test, and deploy.
This role does not require four years of computer science education. It requires a different set of skills: clear thinking about business processes, the ability to break problems into components, enough technical literacy to evaluate what AI produces, and the judgment to know when something is good enough to ship versus when it needs more work.
These people are going to be everywhere in the next three years. Every accounting firm will need one. Every logistics company. Every real estate office. Every marketing agency. The businesses that hire them first will have a massive competitive advantage over those still doing everything manually or waiting for off-the-shelf SaaS products to add AI features.
## This Is What We Teach
This is exactly why I built [uCreateWithAI](https://www.ucreatewithai.com). Not to produce more software engineers — the market is already correcting on that front. But to turn sharp, motivated people into capable AI tool builders who can walk into any business and create real value.
Our students learn to use the same tools I use in production every day. They build real applications. They deploy to real infrastructure. They learn to think about problems the way a senior engineer does, without spending years climbing the traditional engineering ladder, because AI has collapsed that ladder.
The curriculum is practical and direct. No theory for theory's sake. No outdated frameworks. Just the skills that companies are willing to pay for right now.
## The Window Is Now
If there is one thing I want you to take from this, it is urgency. The gap between "most businesses have no idea how to implement AI" and "every business has someone who handles this" is going to close fast. The people who position themselves in that gap right now will build careers, businesses, and financial security that lasts decades.
In five years, this will be obvious. Everyone will be teaching it. The market will be crowded. The premium for being early will be gone.
Right now, the opportunity is wide open. The businesses need help. The tools are mature enough to build real solutions. And there are not nearly enough people who know how to do this work.
Do not wait for permission. Do not wait for the market to tell you it is safe. [Start building](https://www.ucreatewithai.com).
Get posts like this in your inbox
No spam. New articles on AI strategy, governance, and building with AI for small business.
Keep Reading
The Highest-Paid Skill in an AI World Isn't Prompting
Everyone's chasing prompt engineering. But the skill that actually commands a premium is the one AI can't replicate: knowing what good looks like. Domain expertise just became more valuable, not less.
The Wheel Spins Faster: AI Ambition and the Health Tax Nobody Talks About
Last week I ran Claude Code agents on three codebases, researched protocols, tested new models, shipped a client feature, wrote about all of it, and tried to be a CTO. I didn't have this many parallel tracks before AI. Not even close. Here's what I'm learning about staying healthy while the wheel keeps accelerating.
Companies Are Hemorrhaging Millions Through Unmonitored Corporate Credit Cards
Most companies hand employees credit cards with no real-time monitoring, no automated controls, and no AI-driven oversight. The result? Millions in unauthorized spend, duplicate charges, and policy violations that go undetected for months. Here's why this is still happening — and what AI can do about it.