Which Half Have You Hired?

If you are a SaaS leader, start paying attention: 50% of software engineers have not written a single line of code by hand this year.

Which half have you hired?

Why this question matters more than your AI roadmap

The split isn't junior vs. senior, and it isn't about effort. It's a split between engineers who have rebuilt their workflow around AI — specifying, reviewing, orchestrating, and verifying — and engineers still producing software the way they did in 2022. Both halves show up to the same standups. Their output is no longer comparable.

For an engineering leader, this changes three things:

1. Hiring. Interviews that test hand-writing algorithms select for the wrong half. You want to watch a candidate direct AI through an ambiguous task: what they specify, what they question, what they refuse to ship.
2. Productivity math. If part of your team operates at AI-assisted throughput and part doesn't, your capacity planning is fiction. The variance inside one team is now larger than the variance between teams.
3. Engineering discipline. When code is generated faster than it can be read, review, testing, and evaluation become the actual engineering. Quality gates move from "did a human write this carefully" to "can the system prove it behaves correctly."

I've led this transition firsthand — introducing AI into the SDLC for requirements, test definition, and execution, and watching automated QA coverage climb from 5% to 30% in three months once the tooling and discipline were in place. The leverage is real. But it only compounds for the half of the team that has actually changed how they work.

So before the next AI strategy meeting, ask the simpler question: which half have you hired — and what are you doing for the half you already have?

---

Originally shared on LinkedIn.