---
id: M-001
type: mechanism
title: "Genuine Technical Skill Shortfall"
lang: en
registry: 2026.08.2
canonical: https://hoba.work/mechanisms/M-001
json: https://hoba.work/api/v1/mechanisms/M-001.json
---

# Genuine Technical Skill Shortfall

The candidate’s verified technical execution or domain depth does not meet the established baseline for the role level.

> **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: candidate
- Nature: rule
- Visibility: inferable
- Agency zone: candidate
- Honest baseline
- Evidence: established

## What it looks like

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

**Feedback naming the gap** — *reconstruction*

```
Subject: Feedback — technical round

  The panel was positive on communication and on how you structured the problem.
> The gap was concrete: the concurrency exercise needed a bounded worker pool and the submitted solution spawned unbounded goroutines, which the panel would expect to be caught at this level.
  We would genuinely welcome a re-application once that area has had some time.
```

*What to notice* A named exercise and a named property. This is the shape of feedback that is about the work rather than about fit — rare, and worth keeping.

## 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 panel's written notes against the bar set for this level, and the exercise the notes refer to.
- **What it means from there:** A gap at this level is something the team carries while it closes. A bad hire is visible for a year and has a name on it; a missed one has neither.
- **What happens next:** Declines at the level assessed. The panel's specifics stay inside the loop unless they are passed on in a form the recruiter can quote.

### Recruiter

- **What reaches them:** The panel's recommendation and whatever note comes with it, not the scores behind it.
- **What it means from there:** A decline that has to be worded before the next screen. Whether the reason can be repeated to the candidate depends on the form in which it arrives.
- **What happens next:** Writes the rejection. Time-to-fill is measured and time-to-clarity is not, so a specific reason reaches the message where a quotable note already exists.

### Candidate

- **What reaches them:** Either a message naming the exercise and the property that was missed, or a template that names neither.
- **What it means from there:** A named gap can be checked against the work. A template leaves the bar, the level and the rest of the cohort all unstated.
- **What happens next:** Records the wording and the date, and can work on the named area. That is the one branch of this the candidate controls.

## What this observation does NOT establish

- Rejection does not mean the candidate has no engineering ability, only that the requirement bar was unmet for this specific benchmark.

## Related entries

- operates at — [B-005](https://hoba.work/barriers/B-005) — Technical Screen / Live Assessment
- operates at — [B-006](https://hoba.work/barriers/B-006) — Take-Home / Work Sample Evaluation
- operates at — [B-007](https://hoba.work/barriers/B-007) — Hiring Manager In-Depth Review
- emits — [A-008](https://hoba.work/artifacts/A-008) — Explicit feedback citing skill-depth shortfall
- emits — [A-002](https://hoba.work/artifacts/A-002) — Generic "closer alignment" rejection template

---

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.