Delete the Years-of-Experience Line From Your Job Posting

Take the years-of-experience requirement off the job description. If someone showed up with four years and was obviously excellent, you'd hire them anyway… which means that number was never measuring the thing you claimed it measured.

That line is a symptom of something bigger. The way we write job descriptions, run interviews, and evaluate candidates is aimed squarely at the problems we have today, with the tools we have today. Those problems change. Market realities shift, business problems move, and next year's work looks different from this year's. So testing purely for current knowledge and current experience selects for a moment that's already passing. Skills have a much shorter shelf life than most of us assume. The thinking underneath them doesn't, because new tools get built on top of what came before. A designer who genuinely understands user research adapts to whatever methodology emerges next. A product manager who understands business and market dynamics picks up the new framework without much trouble. An engineer with real systems thinking absorbs a new technology stack. Hire for the thinking, not the tool.

What that looks like changes with level. Early career, you still have to validate core skills, since there's no track record to lean on. Ask how quickly they ramped up somewhere before, and how they went about learning something unfamiliar. Mid-career, stop asking how well they know your specific stack. Ask how they've navigated change, and how they adapted when the priorities shifted underneath them. Senior, the domain and technical knowledge is table stakes. The conversation should be about how they help other people adapt, how they decide with incomplete information, how they drive outcomes, and whether they see around corners. So look at your own interview loop and ask whether it's built for what you need this quarter or for what you'll need next year. The best hires aren't the ones who know everything now. They're the ones who can figure anything out later.

0:00 Why we hire for today's problems instead of tomorrow's needs

0:37 Testing for adaptability vs. knowledge and experience

0:52 How skills transfer across new tools and technologies

1:47 Interview strategies by seniority level

2:45 Moving beyond meaningless experience requirements

SUBSCRIBE for more insights on leadership, product, and technology

Newsletter: https://www.nathanbroslawsky.com

LinkedIn: https://www.linkedin.com/in/broslawsky

#hiring #leadership #recruiting #engineering #productmanagement #management