How to Evaluate Evidence for Years of Experience in a Specific Skill: A Resume Interval Method

Direct answer

Career length is not skill experience. A dated role that mentions Ansible establishes that the skill was used at some point in that role; it does NOT establish continuous use from the role’s start to end. Count a supported duration only when the source explicitly documents the skill’s start, end, or sustained period of use. Otherwise record duration as unknown, with the employment dates separately labeled as a possible outer envelope.

If a documented skill-use span meets the requirement, flag the evidence for recruiter verification, not automatic qualification. When the resume only associates a skill with a dated role, ask the candidate when and how long the skill was actually used. A general skills-list entry establishes no duration. Never infer a duration from the full tenure of the job.

Why "years of X" is usually measured wrong

Requisitions often say "3+ years of Kubernetes" when the hiring manager means "has run Kubernetes in production long enough to have seen upgrades and incidents". Recruiters under time pressure then measure the nearest available number, total years in the industry or years since the first mention of the skill. Both overstate. Someone with ten years in infrastructure may have used Kubernetes for one, and a skill first mentioned in 2019 may have been used for six months.

Formal hiring systems that credit experience do it with explicit rules rather than impressions. In U.S. federal hiring, OPM qualification standards require that specialized experience be equivalent to at least the next lower grade [S1], and OPM’s examiner practice material treats ten months as not meeting a one-year requirement [S2]. Your requisition is not a federal position, but the lesson carries over: decide the counting rule before you read the resume, and apply it the same way to everyone.

The interval method in seven steps

1. List every dated role and project as an interval with a start and end month, ending "present" at the resume date.
2. For each interval, quote the exact text that mentions the skill and identify whether the statement dates the SKILL ACTIVITY itself or merely the job. A role-associated skill mention alone establishes no minimum duration.
3. Grade each quote: A = explicitly dated, sustained skill activity with a stated start and end ("maintained Ansible automation every month from March 2022 through September 2024"); B = evidence of a specific task or project inside a role with no proven continuous span ("migrated two services to Kubernetes in 2025"); C = the skill is named for that job without a dated activity; D = general skills list only.
4. Convert explicitly stated SKILL-use intervals to inclusive months, merging overlaps. For a year-only skill-use statement such as "used Ansible throughout 2021," require clarification before claiming a minimum; the most it could support as an outer date envelope is twelve months. Do not automatically convert a role date into a skill date.
5. Documented duration: merge only grade A skill-use intervals with explicit start/end, removing overlaps. If no sustained skill-use interval is documented, show "unknown" (not 0 years of actual experience). Grade B/C mentions do not create a continuous-month minimum.
6. Date envelope: optionally show the union of dated job/project periods in which the skill is mentioned, clearly marked "upper bound if continuous use is later confirmed, not skill tenure." Grade D contributes no dates. Do not combine an undated statement into a measured total.
7. Decide. Only confirmed skill-use intervals can establish documented months; otherwise ask the candidate for actual dates, continuity, depth and use. The resume not documenting a duration is never proof that the candidate lacks the skill or a reason for automatic rejection.

Worked example: one fictional resume, two requirements

The resume is fictional and dated September 2026. The requisition asks for 5+ years of Ansible and 3+ years of Kubernetes.

Ansible: the resume explicitly shows relevant tasks across two roles and a freelance project, but does not state when skill use started or whether it was continuous. Documented continuous skill duration: UNKNOWN, not 86 months. The 2018–2020 and 2022–2026 role dates are possible outer envelopes only, not proof of 86 months. The year-only 2021 project establishes a task occurred, not that Ansible was used for twelve months. Ask for skill-specific start/end periods before resolving the 5-year requirement; do not automatically screen in or out.

Kubernetes: the 2025 migration proves a task occurred during that year, not continuous work for twelve months, and it does not establish an absence of earlier experience. Documented duration: UNKNOWN. Ask "Tell me about the Kubernetes work at Example Retail: when did it start, how long were you using it, and what did you own in production?" The resume has insufficient date evidence to conclude either that the 3-year requirement is met or that the candidate lacks that experience.

Edge cases and how to count them

Write the result so the next person can check it

Requirement: 5+ years Ansible (must-have)
Documented sustained skill-use span: UNKNOWN (role dates only, no continuous skill-use dates)
Evidence: Ansible tasks appear in 2018–2020, a 2021 project, and 2022–2026 role
Decision: ask for explicit skill use dates, continuity and ownership; do not infer qualification from job tenure

Requirement: 3+ years Kubernetes (must-have)
Documented sustained skill-use span: UNKNOWN (single migration mentioned in 2025)
Decision: ask when and how long used, and what was owned in production
Employment dates and skill spans not independently verified.

This note fits into a requirement-by-requirement evidence record like the Candidate 360 profile template, and it follows the same rule as the candidate evidence review checklist: unknown stays unknown until someone establishes it.

Keep the requirement itself honest

Years-of-experience thresholds are blunt. Before applying the method, confirm with the hiring manager that the number reflects a job-related need, and ask what evidence of capability would substitute for it. The EEOC advises that pre-employment questions be limited to what is needed to judge whether someone is qualified for the job [S3]. The method applies the requirement consistently; it does not make an arbitrary requirement fair.

Related guides

• Cleared technical sourcing guide
• A worked sourcing investigation
• Candidate 360 profile template
• Candidate evidence review checklist

Source ledger

This is mainly a method guide; the external sources support only the context claims. The sandbox could not open opm.gov or eeoc.gov, so the OPM sources were reached through search-result summaries (one of them a mirror) and the EEOC link is carried from an existing SourcingOS guide. A person must re-check them before publication.