---
id: mech.inflated_requisition_requirements_vs_actual_team_needs
type: mechanism
title: "Inflated Requisition Requirements vs Actual Team Needs"
lang: en
registry: 1.0.0
canonical: https://hoba.work/mechanisms/mech.inflated_requisition_requirements_vs_actual_team_needs
json: https://hoba.work/api/v1/mechanisms/mech.inflated_requisition_requirements_vs_actual_team_needs.json
---

# Inflated Requisition Requirements vs Actual Team Needs

The posting lists 10+ named technologies and a Staff-level bar for a role whose actual work is feature delivery.

> **On the canonical path** — [A real opening, described honestly](https://hoba.work/process#proc.the_path_as_it_is_supposed_to_run-real-need)
>
> The requisition describes work that exists now, at a level the team actually needs, inside a band the budget already covers. Nothing here is aspirational: the list of requirements is what the job uses, not what the last four candidates happened to have.
>
> This entry is one of the ways that commitment stops being kept.

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

## At a glance

- Actor: hiring manager
- Nature: incentive
- Visibility: inferable
- Agency zone: intermediary
- Evidence: supported

## What it looks like

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

**The posting against the first month of work** — *reconstruction*

```
> Posting: 10+ years distributed systems, Kubernetes, Kafka, Rust, Go, Terraform, GraphQL, ML serving, on-call leadership, mentoring.
  Same team, standup notes from the quarter: CRUD endpoints for the billing dashboard, a report export, two library upgrades.
  Both descriptions are of the same role.
```

*What to notice* The requirement list is a wish, an anchor and a filter at once. It describes the ceiling somebody imagined, not the work in the sprint.

## 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:** An approval form with one requirement list to cover the whole of what the role might have to absorb, and a level that has to be justified against the grid.
- **What it means from there:** The list is the only written statement of the ceiling. A requirement left off cannot be screened for later without going back through approval.
- **What happens next:** Writes the superset — the whole stack, the seniority the level needs — and calibrates afterwards against real candidates, in the screen and on the panel.

### Recruiter

- **What reaches them:** The requirement list as written, and a pipeline that thins under it. What the manager requires but has not written down is not visible from here.
- **What it means from there:** Until the manager says otherwise, the list is the screening standard, and the pool that clears it is small.
- **What happens next:** Screens against the written list, then goes back to the manager to find which items are movable — while time-to-fill runs from the day the requisition opened.

### ATS vendor

- **What reaches them:** The requirement list as configurable criteria: years, titles, named technologies, each one a feature the ranking model can read or a knockout rule the customer can switch on.
- **What it means from there:** Every listed item is a requirement. Nothing in the record separates what the role needs from what someone hoped for.
- **What happens next:** Applies the criteria as configured and ranks accordingly. A longer list yields a smaller qualified pool, and the pool size is what the customer sees.

### Candidate

- **What reaches them:** A posting listing a stack of named technologies and a seniority level, and later the same role posted again.
- **What it means from there:** The list is the bar. Which items are load-bearing is stated nowhere the candidate can reach, and neither is the level they would be assessed at.
- **What happens next:** Either does not apply to a role whose actual work is within reach, or applies and spends the hours; when the role reappears, there is nothing available to tell an unmet bar from a list nobody clears.

## What this observation does NOT establish

- Failing to meet an inflated "wishlist" does not establish anything about how the candidate would do the team's actual work.

## Related entries

- operates at — [bar.requisition_approval_public_posting](https://hoba.work/barriers/bar.requisition_approval_public_posting) — Requisition Approval & Public Posting
- operates at — [bar.automated_filter_parser_threshold](https://hoba.work/barriers/bar.automated_filter_parser_threshold) — Automated Filter & Parser Threshold
- operates at — [bar.recruiter_screening_call](https://hoba.work/barriers/bar.recruiter_screening_call) — Recruiter Screening Call
- emits — [obs.generic_closer_alignment_rejection_template](https://hoba.work/observations/obs.generic_closer_alignment_rejection_template) — Generic "closer alignment" rejection template
- emits — [obs.materially_similar_role_reposted_shortly_after_rejection](https://hoba.work/observations/obs.materially_similar_role_reposted_shortly_after_rejection) — Materially similar role reposted shortly after rejection
- amplifies — [mech.automated_keyword_qualification_filter](https://hoba.work/mechanisms/mech.automated_keyword_qualification_filter) — Automated Keyword / Qualification Filter
- amplifies — [mech.unstated_compensation_band_discrepancy](https://hoba.work/mechanisms/mech.unstated_compensation_band_discrepancy) — Unstated Compensation Band Discrepancy

---

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.