---
id: M-019
type: mechanism
title: "Take-Home Evaluation Fatigue & Asymmetry"
lang: en
registry: 2026.08.2
canonical: https://hoba.work/mechanisms/M-019
json: https://hoba.work/api/v1/mechanisms/M-019.json
---

# Take-Home Evaluation Fatigue & Asymmetry

Reviewers perform hurried 5-minute scans of complex 15-hour take-home projects, missing subtle architectural patterns and tests.

> **On the canonical path** — [Assessed on the work, against a rubric that is shared](https://hoba.work/process#WF-003-work-sample)
>
> One timeboxed exercise that resembles the job. The candidate is given the criteria before starting, the timebox is enforced against the evaluator as well, and the same rubric scores everyone.
>
> This entry is one of the ways that commitment stops being kept.

## At a glance

- Actor: hiring manager
- Nature: noise
- Visibility: opaque
- 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.

**Review record for a 15-hour submission** — *reconstruction*

```
  Submission: 41 files, 78 tests, migrations, README with design rationale.
> Reviewer time logged: 6 minutes. Files opened: 3.
  Note: no tests visible, structure unclear.
```

*What to notice* The note is false about the submission and true about the review. The asymmetry between the two efforts is the mechanism.

## 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:** A submission and a review slot wedged between the team's own delivery work. The rubric is a form with fields for structure, correctness and tests.
- **What it means from there:** What the opened files show is what the submission shows. Anything held elsewhere in the repository is not part of the assessment being written.
- **What happens next:** Fills the rubric from what was opened and carries that note into the debrief, where it stands as the account of the whole submission.

### Recruiter

- **What reaches them:** A completed rubric and a one-line verdict. The time logged against the review is not in the fields the recruiter reads.
- **What it means from there:** The panel read the work and the verdict stands for the reading. Nothing in the record separates a thin submission from a thin reading of one.
- **What happens next:** Sends the rejection in the template wording and closes the record. The review note stays inside the debrief; nothing obliges it to travel further.

### Candidate

- **What reaches them:** The hours the assignment took, the date it was submitted, and a rejection in standard wording some days later.
- **What it means from there:** The work was read and found insufficient — the only reading the message supports, since nothing in it separates a person's verdict from a rule's.
- **What happens next:** There is no named defect to correct. The next assignment is approached the same way, or declined once the unpaid hours are weighed against a process whose state is unknown.

## What this observation does NOT establish

- Take-home rejection under evaluation fatigue does not measure true software engineering craftsmanship.

## Related entries

- operates at — [B-006](https://hoba.work/barriers/B-006) — Take-Home / Work Sample Evaluation
- emits — [A-006](https://hoba.work/artifacts/A-006) — Take-home assignment exceeding reasonable stated scope
- emits — [A-002](https://hoba.work/artifacts/A-002) — Generic "closer alignment" rejection template
- amplifies — [M-012](https://hoba.work/mechanisms/M-012) — Interview Resource & Scheduling Saturation
- 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.