---
id: M-013
type: mechanism
title: "Mid-Process Role Requirement Redefinition"
lang: en
registry: 2026.08.2
canonical: https://hoba.work/mechanisms/M-013
json: https://hoba.work/api/v1/mechanisms/M-013.json
---

# Mid-Process Role Requirement Redefinition

Team changes tech stack, seniority requirements, or project scope mid-funnel, invalidating previous interview assessments.

> **On the canonical path** — [One panel, one question each, one decision rule](https://hoba.work/process#WF-003-panel)
>
> Every interviewer knows what they are measuring and that nobody else is measuring it. The rule that turns their scores into a decision is agreed before the first conversation, and no round is added after the process has started.
>
> This entry is one of the ways that commitment stops being kept.

> **What made this ordinary** — [Rates up, payroll repriced](https://hoba.work/eras#E-003) (2022–2023)

## At a glance

- Actor: hiring manager
- Nature: noise
- Visibility: inferable
- Agency zone: none
- 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 role that changed underneath** — *reconstruction*

```
  Thank you for the four rounds — the panel notes were strong throughout.
> Since we opened this req the team has moved the service to Rust and folded the on-call leadership into the role. Weighted against the new profile we are looking for someone with production Rust and formal lead experience.
  I recognise you interviewed against the previous description. I am sorry about that.
```

*What to notice* The assessments were not re-run, they were re-scored against a target that moved after they were taken.

## 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:** The scope the role has to absorb has moved since the requisition was written, and the panel notes in front of them were taken against the earlier description.
- **What it means from there:** Strong notes against a target that no longer exists. Re-running four rounds costs the team weeks it is already short of.
- **What happens next:** Rewrites the requirements, re-scores the existing notes against them, and decides at which level, if any, the candidate is still a candidate.

### Recruiter

- **What reaches them:** A requisition whose description changes while candidates are mid-loop, and a hiring manager asking for a profile that was not in the original brief.
- **What it means from there:** The pipeline built for the old brief no longer converts, and time-to-fill keeps counting from the date the requisition first opened.
- **What happens next:** Restates the role to everyone still in process, or closes them out with the standard wording and sources again against the new description.

### Candidate

- **What reaches them:** Four rounds of positive signal, then a rejection describing a role different from the one applied to, and a materially similar posting on the board afterwards.
- **What it means from there:** The rounds were passed and the target moved, or the rounds were not passed and the changed description is the courteous version. Both readings fit the same email.
- **What happens next:** Records the original description, the dates, and the wording of the change, and decides whether to ask which requirement is the new one.

### Employer policy

- **What reaches them:** An amended requisition arriving for re-approval at a different level or band, with the original still counted as open.
- **What it means from there:** A level and band change on a requisition already approved, which is what the levelling grid exists to settle. Nothing in the amendment records the interview hours already spent against the old scope.
- **What happens next:** Approves or refuses the new level and band, and the process resumes or stops at the reconciliation step.

## What this observation does NOT establish

- Candidate rejection was driven by shifting team mandate, not prior interview answers.

## Related entries

- operates at — [B-007](https://hoba.work/barriers/B-007) — Hiring Manager In-Depth Review
- operates at — [B-008](https://hoba.work/barriers/B-008) — Team & Cross-Functional Panel
- operates at — [B-009](https://hoba.work/barriers/B-009) — Compensation & Leveling Reconciliation
- emits — [A-003](https://hoba.work/artifacts/A-003) — Position closed after final interview without hire
- emits — [A-004](https://hoba.work/artifacts/A-004) — Materially similar role reposted shortly after rejection
- amplifies — [M-004](https://hoba.work/mechanisms/M-004) — Unstated Compensation Band Discrepancy
- amplifies — [M-024](https://hoba.work/mechanisms/M-024) — Inflated Requisition Requirements vs Actual Team Needs
- masks — [M-001](https://hoba.work/mechanisms/M-001) — Genuine Technical Skill Shortfall

---

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.