Engineering is going to eat the org chart
A line from Jared Palmer stuck with me. The shift isn't hiring more engineers — it's more people operating with an engineering mindset. Welcome the full-stack operator.
I read a line from Jared Palmer that stuck with me: engineering is going to eat the org chart. One sentence, but it named something I'd already been watching happen inside my own companies.
What it looks like on the ground
At Riqra and Ciro, the engineering team isn't fenced into a ticket queue. The same people are in product, design, support, and operations. The engineer who ships a feature is usually the one who specified it, designed it, and answers the customer when something breaks.
This isn't a slogan. It's what building software with AI actually rewards. When one person can hold the whole loop — definition, design, implementation, support — the handoffs between four specialists start to look like overhead, not process.
The role is spreading past engineering
At Clay there's a role called GTM Engineer — engineers working inside sales and distribution. Not building the product; building the go-to-market. Automations, data plumbing, and workflows that used to need a team now sit with one person who thinks like an engineer.
That's the tell. The engineering mindset is leaking out of the engineering department and into every function that touches a system.
More engineers, or more people who operate like one?
Here's the reframe. The future probably isn't just hiring more engineers. It's more people across the company operating with an engineering mindset — decomposing problems, automating the repeatable parts, and leaning on agents to cover the rest.
Maybe the future isn't more engineers. It's more people who operate like one.
Call it the full-stack operator: someone who moves fluidly from product to design to operations to support, because the tools finally let one person hold ground that used to take four.
If you're a founder or CTO
Look at your org chart. How much of it is a real division of labor, and how much is inherited from a time when one person couldn't hold the whole loop? AI didn't just make engineers faster. It changed what a single motivated person can own end to end.
I share the public pieces of this here. When the workflow problem is already real, I also help a few founder-led teams install the system behind it.
Are we entering the era of the full-stack operator?