---
id: M-008
type: mechanism
title: "Automated Keyword / Qualification Filter"
lang: en
registry: 2026.08.2
canonical: https://hoba.work/mechanisms/M-008
json: https://hoba.work/api/v1/mechanisms/M-008.json
---

# Automated Keyword / Qualification Filter

Deterministic filter rejecting applications missing exact acronyms, certifications, or specific years-of-experience thresholds.

> **On the canonical path** — [Machine work stays mechanical](https://hoba.work/process#WF-003-machine-check)
>
> Automation deduplicates, extracts and orders. It does not decide. Where a rule does end an application, the rule is stated and it is one a person would defend out loud.
>
> This entry is one of the ways that commitment stops being kept.

## At a glance

- Actor: system
- Nature: rule
- Visibility: inferable
- Agency zone: candidate
- Evidence: established

## What it looks like

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

**Screening rules, as they ran** — *reconstruction*

```
  +0.4s  Rule 1: must_contain("Kubernetes") — PASS
> +0.4s  Rule 2: must_contain("CKA") — candidate holds CKAD — FAIL
  +0.4s  Rule 3: not evaluated (short-circuit)
  +0.5s  Status: Rejected — does not meet minimum criteria
```

*What to notice* An adjacent certification is not a near miss to a string match; it is a miss. The filter compares tokens, not competence.

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

### ATS vendor

- **What reaches them:** The rule as the customer configured it and the string it tests for, evaluated against the parsed fields of one application. Whether an adjacent qualification sits in those fields is not something a string comparison can represent.
- **What it means from there:** The rule ran to specification: the token is present or it is absent. A failed knockout is a determinate result, not a low score.
- **What happens next:** Writes the rejection status in the same session and emits the notification the customer configured. The rule stays on until a customer turns it off.

### Hiring manager

- **What reaches them:** The shortlist that reaches the review, and the requirements as they were written into the posting. What that wording removed before the shortlist is not in the view.
- **What it means from there:** A thin pipeline reads as scarcity of the skill in the market rather than as the reach of the requirement as it was written.
- **What happens next:** Holds the bar and asks for more sourcing, or rewrites the requirements once the search runs long.

### Candidate

- **What reaches them:** A rejection that arrives minutes after submission, in template wording that names no field.
- **What it means from there:** The interval is the only evidence about how the application was read, and the message does not distinguish a rule from a person.
- **What happens next:** Records the interval between submission and reply, and carries the exact strings the posting names into the next application.

## What this observation does NOT establish

- Passing keyword filters does not guarantee interview invitation.

## Related entries

- operates at — [B-002](https://hoba.work/barriers/B-002) — Automated Filter & Parser Threshold
- emits — [A-009](https://hoba.work/artifacts/A-009) — Rejection within minutes of application submission
- emits — [A-002](https://hoba.work/artifacts/A-002) — Generic "closer alignment" rejection template
- amplifies — [M-011](https://hoba.work/mechanisms/M-011) — Employment Gap Downranking Bias
- amplifies — [M-013](https://hoba.work/mechanisms/M-013) — Mid-Process Role Requirement Redefinition

---

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.