- 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.
Experience-Age Impossibility
A requisition requires more years of hands-on experience with a specific framework or tool than that technology has existed in the open-source ecosystem.
Pattern pat.experience_age_impossibility Evidence: supported
⏳ What made this ordinary
A fixed number of seats (2024–2026) — The conditions that made hiring expensive were reversed; the number of positions was not. The contraction now runs through the hiring channel rather than the separation channel, which is why it is competition for a fixed and shrinking number of seats rather than a shortage of qualified people.
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.
Title: 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.
- 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.
What this pattern establishes
- The job description was written without technical review, from a copied template whose thresholds run as automated gating rules.
What this does NOT establish
- Does not establish that the technical team is incompetent, only that the HR screening pipeline has no technical review.
Observations this pattern requires
- obs.generic_closer_alignment_rejection_template Generic "closer alignment" rejection template A standard automated email saying that the team has decided to proceed with candidates whose profiles match the requirements of the role more closely.
- obs.rejection_within_minutes_of_application_submission Rejection within minutes of application submission Automated rejection email arrives within 2 to 30 minutes of form submission, outside business hours.
Compatible mechanisms in this pattern
- mech.automated_keyword_qualification_filter Automated Keyword / Qualification Filter candidate Deterministic filter rejecting applications missing exact acronyms, certifications, or specific years-of-experience thresholds.
- mech.inflated_requisition_requirements_vs_actual_team_needs Inflated Requisition Requirements vs Actual Team Needs intermediary The posting lists 10+ named technologies and a Staff-level bar for a role whose actual work is feature delivery.
Interventions that mitigate this pattern
Reached without being linked
The relations above are one step. This is what the entry reaches only by walking through them — the shape of it, since the list runs long in a registry this cross-referenced.
- 24
- entity.artifact6Barrier14Mechanism4
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.
- 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.
- 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.
ClientNot visible from here
From this position the entry is not visible. That is not a gap in the atlas — it is the finding: the decision is made where nobody in this position can see it.
Employer policyNot visible from here
From this position the entry is not visible. That is not a gap in the atlas — it is the finding: the decision is made where nobody in this position can see it.
Public policy and industry standardsNot visible from here
From this position the entry is not visible. That is not a gap in the atlas — it is the finding: the decision is made where nobody in this position can see it.
RecruiterNot visible from here
From this position the entry is not visible. That is not a gap in the atlas — it is the finding: the decision is made where nobody in this position can see it.
