- What reaches them
- A gap in the team's coverage of a specific set of rules or protocols, and a candidate whose depth is in an adjacent shape of the same problem.
- What it means from there
- Transferable depth plus a ramp-up the team pays for while it is already short-handed. A miss on the vertical is visible after the hire and has a name on it.
- What happens next
- Holds the vertical as a requirement rather than a preference, and the round turns on it whatever the rest of the panel recorded.
Domain Specificity Over-Weighting
The interviewer holds experience in one exact vertical — adtech, crypto, a named payment processor — as a requirement, ahead of transferable systems depth.
Mechanism mech.domain_specificity_over_weighting Intermediary dependent Actor: hiring managerNature: biasVisibility: inferableAgency zone: intermediaryEvidence: supported
📐 On the canonical path
One panel, one question each, one decision rule — 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
A fixed number of seats (2024–2026) — The conditions that made hiring expensive were reversed; the number of positions was not. The contraction now runs through the hiring channel rather than the separation channel, which is why it is competition for a fixed and shrinking number of seats rather than a shortage of qualified people.
What it looks like
Composite excerpts, written to be typical rather than copied. No particular message, company or person is quoted here.
- 12:03 Interviewer You have built settlement systems, but not in cards specifically?
- 12:09 Candidate Not cards. Same problem shape though — idempotency, reconciliation, chargeback-equivalent reversals.
- 12:19 Interviewer We really need someone who has lived in card rails. The scheme rules are their own world.
What to notice: Transferable depth was heard and set aside for vertical familiarity. That is a legitimate preference and a narrow one; the rejection is about the filter, not the engineering.
Barriers where this mechanism operates
Observations this mechanism emits
- obs.rejection_naming_a_specific_industry_sector_as_required Rejection naming a specific industry sector as required Fidelity: direct Read by the candidate at: Recruiter
- obs.generic_closer_alignment_rejection_template Generic "closer alignment" rejection template Fidelity: euphemism Read by the candidate at: Recruiter
- obs.explicit_feedback_citing_skill_depth_shortfall Explicit feedback citing skill-depth shortfall Fidelity: direct Read by the candidate at: Team
What this does NOT establish
- Transferable general engineering skills are not disproven by lack of specific proprietary protocol knowledge.
Causal relations
Reached without being linked
The relations above are one step. This is what the entry reaches only by walking through them — the shape of it, since the list runs long in a registry this cross-referenced.
- 11
- entity.artifact2Barrier7Mechanism2
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.
- What reaches them
- A technical conversation that goes well until a question about a specific vertical, then a rejection worded as closer alignment.
- What it means from there
- The engineering was heard and the vertical decided it, or the engineering was the reason and the vertical is the wording. The email carries both.
- What happens next
- Records where in the round the turn happened, and reads the next posting's domain nouns as requirements rather than as context.
- What reaches them
- A brief with a vertical named in it, and panels returning notes that cite the vertical rather than the technical rubric.
- What it means from there
- A requirement that narrows the pool while time-to-fill keeps counting, and one the hiring manager holds rather than the recruiter.
- What happens next
- Screens on the vertical, because a shortlist without it comes back from the hiring manager, and sends the standard wording to the rest.
- What reaches them
- A requirement entered as a domain term, and a ranking model for which that term is a feature like any other.
- What it means from there
- A configured preference, scored as specified. The platform has nothing that represents an adjacent domain solving the same problem.
- What happens next
- Ranks and filters on the term as entered, and profiles whose depth is described in other nouns fall below the review threshold.
ClientNot visible from here
From this position the entry is not visible. That is not a gap in the atlas — it is the finding: the decision is made where nobody in this position can see it.
Employer policyNot visible from here
From this position the entry is not visible. That is not a gap in the atlas — it is the finding: the decision is made where nobody in this position can see it.
Public policy and industry standardsNot visible from here
From this position the entry is not visible. That is not a gap in the atlas — it is the finding: the decision is made where nobody in this position can see it.
