Our latest report asked engineering leaders how they've reorganized their teams for AI. When our CTO, Ameya Kanitkar, dug into the answers, he found almost no common pattern, and that turned out to be the most interesting finding of all.
He explained his thinking on LinkedIn:
Ameya Kanitkar, co-founder and CTO of Larridin, on LinkedIn:
Engineering leaders are reorganizing teams for AI and making completely opposite changes.
In our latest report, 40.8% said they had reorganized teams around products or outcomes over the past year.
But there was no common pattern.
Some made teams smaller. Others made them bigger.
23.5% widened manager spans. Exactly 23.5% narrowed them.
Some companies created more tech lead roles. Others added engineering managers. Some removed engineering manager roles entirely.
19.4% changed the mix of senior and junior engineers. Another 15.3% introduced roles focused on verification, agent platforms, or AI enablement.
And 29.6% had not changed their organization at all.
The answers are different because companies are running into different problems.
If agents allow a small team to own more, smaller teams may work.
If agents increase code output but create more work in review, architecture, and coordination, companies may need more technical leadership.
If AI adoption is uneven, the immediate need may be enablement rather than a new team structure.
There is no standard engineering organization for the AI era yet.
Companies are changing one part of the organization, watching what happens, and adjusting again.
If you're under pressure to redesign your org for AI, you'd hope someone has already written the playbook. Nobody has. Engineering leaders are making opposite bets, and that's useful to know before you copy anyone's org chart.
Here's what engineering leaders told us in a live poll at LDX3 New York in September 2026. It had approximately 98 respondents and allowed multiple selections; the results describe that room, not all engineering organizations.
The split shows up in roles too: Some companies created more tech lead roles, others added engineering managers, and a few removed engineering manager roles entirely.
Ameya's read is that the answers differ because the problems differ:
The same theme came up again and again at LeadDev's engineering leadership conference in New York. Ameya's biggest takeaway: agreement on the technical foundations is arriving faster than agreement on the organization that should run them.
The foundations people are converging on include spec-driven development, development environments built for agents, telemetry across the SDLC, and structures for managing AI costs.
A few other things stood out from those conversations:
There's no standard engineering organization for the AI era yet. Companies are changing one piece, watching what happens and adjusting again.
That's a reasonable way to work, as long as you're deliberate about it. Name the problem first: is it ownership, review load, or uneven adoption? Pick the change that fits that problem, then measure whether it worked before making the next one.
Ameya shares this kind of practical, data-first stuff on LinkedIn pretty regularly. If you want more of it in your feed, follow Ameya Kanitkar on LinkedIn. He's co-founder and CTO of Larridin.
On larridin.com: