--- id: mech.domain_specificity_over_weighting type: mechanism title: "Domain Specificity Over-Weighting" lang: en registry: 1.0.0 canonical: https://hoba.work/mechanisms/mech.domain_specificity_over_weighting json: https://hoba.work/api/v1/mechanisms/mech.domain_specificity_over_weighting.json --- # 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. > **On the canonical path** — [One panel, one question each, one decision rule](https://hoba.work/process#proc.the_path_as_it_is_supposed_to_run-panel) > > 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](https://hoba.work/eras#era.a_fixed_number_of_seats) (2024–2026) ## At a glance - Actor: hiring manager - Nature: bias - Visibility: inferable - Agency zone: intermediary - Evidence: supported ## What it looks like Composite excerpts, written to be typical rather than copied. No particular message, company or person is quoted here. **Where the round turned** · minute 12 — *reconstruction* ``` 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. ## 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 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. ### Candidate - **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. ### Recruiter - **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. ### ATS vendor - **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. ## What this observation does NOT establish - Transferable general engineering skills are not disproven by lack of specific proprietary protocol knowledge. ## Related entries - operates at — [bar.recruiter_screening_call](https://hoba.work/barriers/bar.recruiter_screening_call) — Recruiter Screening Call - operates at — [bar.hiring_manager_in_depth_review](https://hoba.work/barriers/bar.hiring_manager_in_depth_review) — Hiring Manager In-Depth Review - emits — [obs.rejection_naming_a_specific_industry_sector_as_required](https://hoba.work/observations/obs.rejection_naming_a_specific_industry_sector_as_required) — Rejection naming a specific industry sector as required - emits — [obs.generic_closer_alignment_rejection_template](https://hoba.work/observations/obs.generic_closer_alignment_rejection_template) — Generic "closer alignment" rejection template - emits — [obs.explicit_feedback_citing_skill_depth_shortfall](https://hoba.work/observations/obs.explicit_feedback_citing_skill_depth_shortfall) — Explicit feedback citing skill-depth shortfall - amplifies — [mech.hidden_evaluation_rubric_or_undisclosed_priority](https://hoba.work/mechanisms/mech.hidden_evaluation_rubric_or_undisclosed_priority) — Hidden Evaluation Rubric or Undisclosed Priority - masks — [mech.genuine_technical_skill_shortfall](https://hoba.work/mechanisms/mech.genuine_technical_skill_shortfall) — 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.