Leadership Philosophy

Why "Years of Experience" Is a Bad Proxy for Engineering Leadership Ability

Two managers with the same five years on paper can have completely different judgment. Here's why tenure alone is such an unreliable signal of leadership ability.

Engineering Management Academy4 min read

"Five years of engineering management experience" reads like a credential. It sits in a job posting as a filter, in a resume as a headline, in a promotion case as evidence. But it isn't a credential at all — it's a duration. It tells you how long someone occupied a seat, not what they did with the time or how good they got at the job.

Compare two managers. One has spent five years leading a stable team at a company with predictable roadmaps, few incidents, and low attrition — a comfortable environment where most decisions are low-stakes and mistakes are easy to hide. The other has spent eighteen months leading a team through a reorg, two production crises, and a round of layoffs, and has had to make dozens of real, consequential calls under pressure. On paper, the first candidate has three times the experience. In practice, the second has almost certainly developed sharper judgment. Tenure doesn't distinguish between these two people. It treats them as equivalent because it only counts time, not what the time was spent doing.

Exposure is not the same as judgment

The core problem is that "years of experience" measures exposure to a role, not the quality of decisions made within it. Someone can spend years running the same routine 1:1s, approving the same routine PRs, and attending the same routine planning meetings without ever being tested — without a genuine ambiguous tradeoff, a difficult performance conversation, or a moment where the "safe" answer and the "right" answer diverge. That person accumulates tenure but not necessarily capability. Meanwhile someone earlier in their career, dropped into a genuinely hard situation, can develop more real judgment in a fraction of the time simply because they were forced to exercise it.

This isn't an argument that experience doesn't matter — it clearly does, on average, correlate with skill. It's an argument that experience is a noisy, indirect proxy for the thing organisations actually want to know: can this person make good calls when it counts? Years served answers a different question entirely.

How this plays out in hiring

The practical cost shows up constantly in how companies screen candidates. A job posting requiring "5+ years of engineering management experience" is a blunt instrument. It reliably filters out people who developed strong judgment quickly — often the exact people worth hiring — while letting through candidates whose five years were spent coasting in a low-stakes environment, never really stretched, never really tested.

Recruiters and hiring managers reach for years-of-experience thresholds because tenure is easy to verify and judgment is hard to observe from a resume. It's a proxy chosen for convenience, not accuracy. The result is a hiring funnel that systematically over-selects for longevity and under-selects for capability — and then organisations are surprised when a manager with an impressive-looking tenure turns out to struggle with the actual demands of the role.

What "real judgment" actually looks like

If tenure isn't the signal, what is? Leadership judgment shows up in a specific, observable set of capabilities: how someone handles ambiguous tradeoffs, gives and receives feedback, sets technical direction under uncertainty, manages people through difficult moments, and communicates decisions to stakeholders who don't share their context. These are the kinds of situations covered across the five domains in the EMA Body of Knowledge — and they're testable independent of how many years someone has been doing the job. You can put a candidate in front of a realistic scenario and observe how they reason through it, regardless of whether they've been a manager for eighteen months or eighteen years.

That's a fundamentally different kind of evidence than a tenure line on a resume. It doesn't ask "how long has this person been exposed to management situations?" It asks "how well does this person actually navigate them?"

Experience as a proxy, assessment as the real signal

None of this means experience should be discarded. Scope of responsibility genuinely does tend to grow with time, which is why EMA's own three-tier structure still uses years as a rough guide — EMA-I has no experience requirement at all, EMP-II expects 3+ years, and EME-III expects 7+. But at every tier, the credential itself isn't earned by having survived that many years — it's earned by scenario-based examination of judgment. Tenure gets you to the right room. It doesn't certify what you do once you're in it.

The fix isn't to ignore experience — it's to stop treating it as sufficient proof on its own and start pairing it with a real test of judgment. That's the gap an assessment-first credential is built to close.

Want to know where your leadership judgment actually stands, regardless of how many years are on your resume? Take EMA-I — a scenario-based exam that tests how you'd actually handle situations like these, not how long you've been in the room where they happen.

Test your judgment, not your recall.

EMA-I is a scenario-based exam — free during the founding cohort.

Start EMA-I — Free →