---
id: A-018
type: artifact
title: "Rejection naming a specific industry sector as required"
lang: en
registry: 2026.08.2
canonical: https://hoba.work/artifacts/A-018
json: https://hoba.work/api/v1/artifacts/A-018.json
---

# Rejection naming a specific industry sector as required

The stated reason is the absence of experience in one named sector, rather than the depth or correctness of the work assessed.

## At a glance

- Stage: Recruiter, Technical
- Evidence: hypothesis

## What it looks like

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

**Feedback after the technical round** — *reconstruction*

```
Subject: Following your technical session

  The exercise was solid and the reasoning about failure modes was strong.
> The team decided to go with someone who has already worked in the payments domain.
  We would be happy to talk again for a role where that is less central.
```

*What to notice* The work is assessed positively and the ground for the decision is elsewhere. That combination is what makes the sector legible as the operative line — and leaves open how heavily it was weighed.

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

### Candidate

- **What reaches them:** A reason that names an industry rather than a capability: payments, health, advertising, trading — a sector the candidate has not worked in, stated as the thing that was missing.
- **What it means from there:** The sector is a real difference. Whether it is a difference in what the work requires, or a proxy standing in for that, the message does not distinguish — and the two look identical from outside.
- **What happens next:** Compares the sector named against the requirements the posting listed, because a requirement that appears only in the closing message appeared somewhere between the two.

### Hiring manager

- **What reaches them:** Two candidates who can both build the system, one of whom has already met the constraints this sector imposes and will not spend the first quarter discovering them.
- **What it means from there:** Sector context is a real cost, paid in ramp-up time that the team carries. Weighing it is judgement, not a rule, and nothing in the process asks how much of it was weighed.
- **What happens next:** States the difference plainly, because it is the most concrete thing that separated two people who both passed.

### Recruiter

- **What reaches them:** A requirement that was written into the search brief as a preference and is now being applied as a threshold.
- **What it means from there:** Preferences and thresholds are recorded in the same field. Which one a line was is decided when it is used, not when it is written.
- **What happens next:** Passes the reason on in the manager's words, because it is specific enough to send and not attributable to anything the recruiter assessed.

## What this observation does NOT establish

- Does not establish that the sector was irrelevant to the work.
- Does not establish that the assessed work fell short in any respect.

## Diagnostic probes

- **PROBE-A-018-1** (low) — Compare the sector named in the message against the requirements section of the posting as it stood on the day of application. → Establishes whether the sector was listed as required, listed as preferred, or absent.

---

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.