---
id: M-010
type: mechanism
title: "Hidden Evaluation Rubric or Undisclosed Priority"
lang: en
registry: 2026.08.2
canonical: https://hoba.work/mechanisms/M-010
json: https://hoba.work/api/v1/mechanisms/M-010.json
---

# Hidden Evaluation Rubric or Undisclosed Priority

The interview team grades candidate against specific undisclosed architectural dogmas, internal frameworks, or unwritten biases.

> **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: hiring manager
- Nature: bias
- Visibility: opaque
- 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.

**The rubric that was not in the brief** · minute 29, design round — *reconstruction*

```
  29:04 Candidate  I would put a queue between them so the write path stays available if the consumer is down.
> 29:12 Interviewer  Mm. We do not use queues here.
  29:18 Candidate  Is that a constraint I should design within?
  29:21 Interviewer  Just carry on.
```

*What to notice* A house preference was applied as a grading criterion without being stated as one. The candidate could not have designed to a rule they were not told.

## 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 write-ups, in the vocabulary the team uses for its own systems. What the candidate was sent before the round is not in front of the panel.
- **What it means from there:** A design that departs from the pattern the team runs on reads as a shortfall in depth, not as a mismatch with a preference. A criterion the team shares is not experienced as a criterion; it is the standard.
- **What happens next:** Records the objection in the panel's own terms and sets the level from it. The brief for the next candidate is unchanged.

### Candidate

- **What reaches them:** The questions as they were asked and the reaction in the room, and afterwards a reason stated in general terms.
- **What it means from there:** The feedback names a shortfall that cannot be checked against the criterion applied, because that criterion was not stated in the round.
- **What happens next:** Records the exchange and asks in the round whether a stated preference is a constraint to design within. There is no revision available against a rule that was not given.

## What this observation does NOT establish

- Failure to guess unstated preferences is not equivalent to lack of core competence.

## Related entries

- operates at — [B-005](https://hoba.work/barriers/B-005) — Technical Screen / Live Assessment
- operates at — [B-007](https://hoba.work/barriers/B-007) — Hiring Manager In-Depth Review
- operates at — [B-008](https://hoba.work/barriers/B-008) — Team & Cross-Functional Panel
- emits — [A-008](https://hoba.work/artifacts/A-008) — Explicit feedback citing skill-depth shortfall
- emits — [A-014](https://hoba.work/artifacts/A-014) — Conflicting feedback across different interviewers
- amplifies — [M-022](https://hoba.work/mechanisms/M-022) — Hiring Manager Consensus Impasse
- masks — [M-001](https://hoba.work/mechanisms/M-001) — 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.