---
id: L-003
type: loop
title: "Inflated-Requirements Search Saturation Loop"
lang: en
registry: 2026.08.2
canonical: https://hoba.work/loops/L-003
json: https://hoba.work/api/v1/loops/L-003.json
---

# Inflated-Requirements Search Saturation Loop

Teams write inflated requirements, filtering out strong generalists, prolonging open search, causing recruiter fatigue and mid-process role redefinitions.

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

## At a glance

- Evidence: hypothesis

## What it looks like

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

**The same requisition, rewritten twice** — *reconstruction*

```
  Month 0 — 8 required technologies, 7+ years, staff-level scope. Applications: 340. Advanced to onsite: 2. Hired: 0.
> Month 3 — search still open. Requirements rewritten upward: 10 technologies, 9+ years, plus formal lead experience.
  Month 6 — search still open. Recruiter reassigned; team now covering the work with overtime.
```

*What to notice* The response to a failed search was a narrower filter. The filter was the reason the search failed, which is the turn that makes this a loop.

**Where the requirement came from** — *reconstruction*

```
  month 3 Recruiter  Do we really need nine years and Rust for this? The backlog is mostly billing endpoints.
> month 3 Hiring manager  Nobody good has applied in three months. If we lower the bar we will get more of the same.
```

*What to notice* The inference runs backwards: an empty pipeline is read as evidence that the bar is too low. That reading is what tightens the next iteration.

## 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.

### Hiring manager

- **What reaches them:** Three months of applications, two candidates reaching onsite, no hire, and the team covering the work with overtime.
- **What it means from there:** The pipeline holds nobody the panel wanted, and a lower bar would add to the pool it has already turned down.
- **What happens next:** Rewrites the requirements upward, adds the missing signal as a formal requirement, and reposts: a bad hire is recorded against them and an open search is not.

### Recruiter

- **What reaches them:** A requisition ageing past the time-to-fill it is measured on, and a requirements list that got longer at the rewrite.
- **What it means from there:** The requirements belong to the hiring manager, who is the internal client for this search.
- **What happens next:** Raises the question once, posts the revised text, and moves screening capacity to requisitions that can close.

### Candidate

- **What reaches them:** A posting with ten required technologies, a nine-year threshold and a lead requirement, republished with a longer list than the version before it.
- **What it means from there:** The list is either the bar or a wish, and the posting does not say which; the year thresholds are the part a filter can act on.
- **What happens next:** Skips the posting or applies against a list they do not match, and never learns which of the requirements the screen enforced.

## Related entries

- [M-024](https://hoba.work/mechanisms/M-024) — Inflated Requisition Requirements vs Actual Team Needs
- [M-008](https://hoba.work/mechanisms/M-008) — Automated Keyword / Qualification Filter
- [M-013](https://hoba.work/mechanisms/M-013) — Mid-Process Role Requirement Redefinition

## Edges of this causal loop

- M-024 amplifies M-008
- M-008 amplifies M-013
- M-013 amplifies M-024

---

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.