You can’t hire someone who already holds your team’s judgment. Nobody has it.

The incidents that built it happened in your production, against your data, with your customers finding the failure modes only your product has. The best engineer on the market shows up with deep judgment about systems that aren’t yours. Worth a lot, and not the same thing.

So the trait that matters isn’t how much someone already knows. It’s how fast they go from not having your context to having it. Absorption rate, not inventory.

Most interview loops measure the opposite. They score what a candidate already knows, for a job that pays out on how fast they learn what only your system can teach. Same résumé, different slope, and that gap decides who compounds the moat and who quietly draws it down.

As models close the gap on syntax, this is the line that’s left. You’re not hiring for the code. You’re hiring for the slope.

Wrote about how to measure it: https://joaofogoncalves.com/articles/2026/06/14-the-moat-that-walks-out-the-door/