Skip to main content
Blocked from publishing until the auth and gating checklist in Authentication & Scopes lands. The configure and override operations additionally require decisions:write and must never sit in the default read tier.

​
Purpose

Stack Ranking sits on top of every interview round and produces the ranked view of candidates for a job, with the justifications behind each score.

​
Read back

​
Configure and override (decisions:write scope only)

Decision overrides mutate the hiring audit trail. They require an explicit decisions:write scope and must never be granted by default.

​
FAQs

All candidates for a job, across their completed rounds, into one ordered leaderboard.
Yes. scoreJustifications returns the reasoning behind a candidate’s score for a given interview type.
The mechanism is public; the actual weights live in scoringConfig and your signed configuration, not in these docs.
The override is written to the hiring audit trail and requires the decisions:write scope. Nothing is silently changed.

Calibration

How scores trace to rubric versions and recalibrate.

Auditability

How overrides and decisions are traced.