---
id: P-003
type: pattern
title: "Experience-Age Impossibility"
lang: en
registry: 2026.08.2
canonical: https://hoba.work/patterns/P-003
json: https://hoba.work/api/v1/patterns/P-003.json
---

# Experience-Age Impossibility

Requisition requires more years of hands-on experience in a specific framework or tool than that technology has existed in the open-source ecosystem.

> **What made this ordinary** — [A fixed number of seats](https://hoba.work/eras#E-004) (2024–2026)

## At a glance

- Evidence: supported

## Trigger rule

Job description or automated screen requires X years of experience where X > technology_age.

## What it looks like

Composite excerpts, written to be typical rather than copied. No particular message, company or person is quoted here.

**The requirement, as published** — *reconstruction*

```
Subject: Senior Platform Engineer — requirements

  7+ years of production experience with Kubernetes.
> 5+ years with a framework first released three years ago.
  Screening is automated: applications below the stated year counts are filtered before human review.
```

*What to notice* This is checkable against a release date, which makes it one of the few claims in hiring that can simply be false rather than debatable.

**What the filter did with it** — *reconstruction*

```
  00:00:04  Application submitted
> 00:00:05  Rule: years_with_framework >= 5 — candidate value 3 — FAIL
  00:00:05  Status: Rejected — does not meet minimum criteria
```

*What to notice* No one decided anything about this candidate. An impossible threshold was copied into a rule and the rule ran.

## From each side

The same entry from inside each position that meets it: what reaches them, what it means from there, and what happens next given what they control.

### Candidate

- **What reaches them:** A posting requiring more years with a framework than the framework has existed, and a rejection minutes after submitting, outside working hours.
- **What it means from there:** The threshold is checkable against a release date, which makes this one of the few claims in a posting that can be false rather than arguable.
- **What happens next:** Keeps the posting text and the time of the rejection, which can be set against the release date; the requirement itself reaches nobody who could rewrite it.

### Hiring manager

- **What reaches them:** A draft posting assembled from the template of a previous requisition, reviewed for the part that describes the team's work.
- **What it means from there:** Years of experience is a shorthand for depth, and in the draft that figure carries less weight than the description of the role.
- **What happens next:** Approves the draft and returns to the delivery the requisition exists to cover; the number reaches a screening rule without passing a technical review.

### ATS vendor

- **What reaches them:** A configured knockout rule comparing a parsed year count against a threshold the customer entered.
- **What it means from there:** A value below the threshold is a fail; whether the threshold is reachable at all is not a property the rule can evaluate.
- **What happens next:** Rejects at submission and emits the standard does-not-meet-minimum-criteria notice, in seconds, at whatever hour it arrives.

## What this pattern establishes

- Job description was authored without technical review, using copy-paste templates with automated gating rules.

## What this observation does NOT establish

- Does not imply technical team is incompetent, only that HR screening pipeline lacks technical validation.

## Related entries

- [A-002](https://hoba.work/artifacts/A-002) — Generic "closer alignment" rejection template
- [A-009](https://hoba.work/artifacts/A-009) — Rejection within minutes of application submission
- [M-008](https://hoba.work/mechanisms/M-008) — Automated Keyword / Qualification Filter
- [M-024](https://hoba.work/mechanisms/M-024) — Inflated Requisition Requirements vs Actual Team Needs

---

hoba — a public, versioned atlas of hiring obstacles. Content CC BY-SA 4.0. This document is generated from the registry; the canonical page is linked above.