> ## Content Index > Fetch the complete content index at: https://www.trentcotton.com/llms.txt > Use this file to discover other available public pages before exploring further. # Years of Experience Lied to Us: Why Job Descriptions Need to Score Skills, Not Tenure - URL: https://www.trentcotton.com/years-of-experience-lied-to-us-why-job-descriptions-need-to-score-skills-not-tenure/ - Published: 2026-09-17T00:00:42.000Z - Updated: 2026-09-17T00:00:41.000Z - Author: Trent Cotton - Tags: Sprint Recruiting, High Performance Recruiting ## **TL;DR: Does years of experience actually predict who can do the job?** No. Tenure tells you how long someone sat in a seat, not what they can do in it, and job descriptions built around years-required keep filtering out the candidates most likely to succeed. **Key stats you need to know:** - 70% of employers used skills-based hiring in 2026, up from 65% the year before (NACE, Job Outlook 2026). - 90% of companies using skills-based hiring report fewer mis-hires (SHRM, citing a 2025 TestGorilla study). - A bad hire costs 30-50% of that person's first-year salary (U.S. Department of Labor, via SHRM). **The leadership takeaway:** If your job description still leads with "5+ years required," you're screening for the wrong variable, and you're going to pay for it in a termination within the year. ## Sign up for The Human Capitalist Twenty years building HR from the inside. I write for CHROs who want the operating model for AI, not the hype around it. Subscribe Email sent! Check your inbox to complete your signup. No spam. Unsubscribe anytime. ## Does years of experience actually predict who can do the job? No. Tenure is a proxy, and it's a bad one. It tells you how long someone occupied a title, not whether they can perform the actual work the role requires. The adoption numbers show the industry already knows this. NACE's Job Outlook 2026 survey found 70% of employers now use some form of skills-based hiring, up from 65% the year before, and 71% of those employers use it at least half the time. SHRM, citing 2025 assessment data, reports that 90% of companies using skills-based hiring saw a reduction in mis-hires. Companies aren't experimenting with this anymore. They're correcting a mistake. I watched that mistake happen in real time. I ran a role through an AI-powered technical interview and it graded two finalists on the same test. One candidate had 8 years of on-paper experience. The other had 2 years, self-taught, no traditional pedigree. The 2-year candidate outperformed the 8-year candidate on the assessment, clearly and measurably. The hiring managers still wanted the 8-year candidate, because 8 years still reads as safer than 2\. We hired him. Six months later, we terminated him because he couldn't do the job. The assessment had already told us that. We just didn't listen to it. That's not a one-off story, it's the predictable result of screening on the wrong signal. Korn Ferry estimates the gap between the demand for skilled workers and the supply of them will cost the U.S. economy $1.7 trillion by 2030\. Every job description that gatekeeps on years instead of demonstrated skill is making that gap wider, one rejected qualified candidate at a time. ## What is the Scorecard Job Description, and why does it matter? A Scorecard Job Description defines the specific, demonstrable skills a candidate must show to succeed in the role, weighted by how much each one matters, with no arbitrary years-required minimum standing in the way. Compare that to what most companies still publish, which is a Commercial Job Description. A commercial JD is written to sell the company. It leads with culture, perks, and a laundry list of "requirements" that are really just tenure gates dressed up as qualifications: "5+ years in a similar role," "Bachelor's degree required." It filters for a resume that looks safe on paper, not for a person who can do the work. The two documents do different jobs, and most companies are asking one document to do both, badly. A Commercial JD sells the role. A Scorecard JD tests for it. If your only job description tries to be both, it will underperform at each. Read [my earlier take on why job descriptions aren't dead, they just need to evolve](https://www.trentcotton.com/blog/job-descriptions-arent-dead-they-just-need-to-evolve) for where this idea started. In a boardroom, I'd say it this way: your job description is either a scorecard for skill or a commercial for the company. Pick one on purpose. If you're trying to do both in the same document, you're optimizing for neither, and that's exactly how an 8-year resume beats a 2-year skill set on paper every single time. ## How should C-suite leaders respond? C-suite leaders and CHROs should respond by auditing the tenure gates baked into every open requisition before they touch anything else. 1. **Audit every JD for a hard years-of-experience minimum.** Ask whether that number is protecting against a real regulatory or safety requirement, or whether it's a lazy stand-in for "we trust this less." Most of the time, it's the second one. Replace it with a skill threshold you can actually test for. This connects directly to the shift covered in [The Great Reskilling and how AI is changing talent strategy](https://www.trentcotton.com/blog/the-great-reskilling-how-ais-changing-the-talent-strategy). 2. **Give hiring managers a decision rule, not a veto.** My managers had the assessment data in front of them and overrode it anyway, because gut instinct about tenure still outranked evidence about skill. If your process lets a manager's comfort level beat a validated assessment score, the assessment is decoration. Build the rule that says the higher score wins unless there's a documented, specific reason. 3. **Track mis-hire cost as a leadership KPI, not an HR footnote.** A bad hire runs 30-50% of that person's first-year salary. Put that number in front of the same executives who keep asking recruiting to move faster. Speed without skill validation is how you generate that cost. 4. **Model the language.** When you talk about a hiring decision in a leadership meeting, talk about the skill evidence, not the resume pedigree. What leaders say out loud about why someone got hired is what the org actually optimizes for, regardless of what the JD says on paper. 5. **Build the assessment before you post the JD.** A scorecard job description is only credible if there's a real way to test the skills it claims to require. This is where AI-assisted skills assessment is doing real work, covered in [Generative AI and soft skills](https://www.trentcotton.com/blog/generative-ai-and-soft-skills) and [recruiting for the AI talent gap](https://www.trentcotton.com/blog/recruiting-for-the-ai-talent-gap). ## Summary: What this means for you as a leader Your job descriptions are rewarding tenure and quietly filtering out the people most likely to actually perform, and the data on mis-hires, adoption, and cost all point the same direction. Winning looks like auditing your own reqs before your competitors do, because the leaders who keep the years-required line in place aren't protecting quality. They're protecting a habit, at a cost of 30-50% of a salary every time it fails. **Find out what FutHRist mindsets you have with this free assessment:** --- ## FAQ **Is skills-based hiring trying to eliminate experience from hiring entirely?** No. It demotes experience from a hard gate to one input among several. A candidate's history can still support a hiring decision, it just can't be the only qualifying filter before a skill is ever tested. **Is skills-based hiring creating or destroying jobs?** Neither, directly, it's redistributing who gets access to jobs. NACE data shows 70% of employers already use some form of it, which opens roles to capable candidates who don't have a traditional pedigree, while raising the bar on what "qualified" actually means. **Why is there a premium for demonstrated skill over years of experience?** Because tenure is cheap to fake on paper and expensive to get wrong in practice. Korn Ferry's $1.7 trillion talent-shortage projection reflects exactly this: companies competing for a shrinking pool of the right skills while still screening for the wrong signal. **How does a Scorecard Job Description actually improve job quality?** It forces clarity before the req ever posts. If you can't define a testable skill, you can't put it on the scorecard, which strips out vague requirements that exist only to gatekeep. **What is the Scorecard Job Description in simple terms?** It's a job description that lists what a candidate has to prove they can do, weighted by importance, instead of a description that lists where they've worked and for how long. **What should CHROs and CEOs do first?** Pull every open requisition and find the years-of-experience minimum. For each one, ask whether it's protecting a real requirement or standing in for an assessment you haven't built yet.