- 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.
Hidden Evaluation Rubric or Undisclosed Priority
The panel grades the candidate against architectural preferences, internal frameworks and house conventions that were not stated in the posting or in the round.
Assessed on the work, against a rubric that is shared — 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.
What it looks like
Composite excerpts, written to be typical rather than copied. No particular message, company or person is quoted here.
- 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 given.
Barriers where this mechanism operates
Observations this mechanism emits
- obs.explicit_feedback_citing_skill_depth_shortfall Explicit feedback citing skill-depth shortfall Fidelity: distortion Read by the candidate at: Technical
- obs.conflicting_feedback_across_different_interviewers Conflicting feedback across different interviewers Fidelity: direct Read by the candidate at: Team
What this does NOT establish
- Not guessing an unstated preference is not a shortfall in core competence.
Causal relations
Interventions targeting this mechanism
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.
- 8
- entity.artifact2Barrier5Mechanism1
- 2
- Intervention2
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
- 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.
ATS vendorNot 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.
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.
RecruiterNot 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.