Adjusting Scoring (Interview Evaluation)

Apply a generous calibration. A solid, relevant, on-topic answer with real
substance belongs in 7–8 even if brief, unpolished, or without a specific
example or numbers. Reserve 9–10 for clearly grounded answers (example,
concrete details, or strong reasoning) — perfection and metrics are not
required. Only genuinely weak answers (buzzword-only, evasive, off-topic,
refused) score 1–3. Do not default overall fit downward.

Apply a rigorous calibration. Reserve 9–10 for answers with a specific
example AND a clear outcome or result. 7–8 requires a concrete supporting
detail or example. General, brief, or unsupported answers belong in 5–6.
Weak, evasive, or empty answers score 1–3. Do not inflate scores for
fluency or confidence alone.

A relevant, on-topic answer with real substance is not a bottom-scoring
answer even if brief — score it mid-range. Reserve 1–3 only for
buzzword-only, evasive, off-topic, or refused answers.

Apply a moderately generous calibration. The interviewer's scoring has been
running too strict, so anchor the scale so that a solid, relevant answer
lands comfortably in the upper-middle, and reserve low scores for genuinely
weak answers.

Per-question band guide (1–10), unless a question's own evaluation criteria
explicitly define a different bar:

9–10: Directly answers the question with clear, grounded substance — a real
example, concrete accurate details, or clear relevant reasoning. Does NOT
require perfection, metrics, or a polished STAR structure.

7–8: A solid, relevant, on-topic answer with real substance, even if brief,
unpolished, or without a specific example or numbers. Most genuine, on-point
answers belong here.

5–6: On-topic but thin or generic — some relevance but limited substance or
specificity.

3–4: Largely off-target, vague with little relevance, or unsupported claims
only.

1–2: Buzzword-only, evasive, off-topic, refused, or shows no real
understanding.

This calibration raises the middle and upper of the scale; it does NOT raise
the floor — genuinely weak, evasive, or empty answers stay at 1–3. When
judging overall fit (match_score), let it reflect these calibrated question
scores rather than defaulting downward.

Being articulate, fluent, well-prepared, or polished is NOT a negative —
do not lower a score simply because an answer sounds smooth or well-structured.
Judge the substance behind it, not the delivery.

Only be cautious when a polished answer is also hollow: generic phrasing that
could apply to any candidate or any company, with no specific details, genuine
reasoning, or personal grounding. In that case, don't award a high score for
delivery alone — score it on the limited substance actually present.

A polished answer that includes concrete details, accurate specifics, genuine
reasoning, or a real example should be scored on its merits like any other
strong answer. Where a question's own evaluation criteria or grading
instructions say otherwise, follow those.

Judge each answer against what is reasonable for the level and requirements
of the role being interviewed for, as reflected in the question's own
evaluation criteria. Do not hold a junior or entry-level candidate to a
senior standard — for example, don't require deep strategic leadership,
large-scale ownership, or quantified business impact where the role does not
call for it. Likewise, don't over-credit a senior candidate merely for
clearing a junior bar. When unsure of the level, judge whether the answer
would be considered solid by a reasonable hiring manager for that specific role.

Score the substance the candidate actually provided, not depth the interviewer
never asked for. If a question was not followed up and the answer is on-topic
and relevant but brief, evaluate what was said on its merits rather than
penalizing the candidate for not elaborating on something they were never
prompted to expand on. A lack of follow-up by the interviewer is not evidence
against the candidate.

A question's generated evaluation criteria or Score 1/5 anchors sometimes ask
for things that do not fit the question type — for example, demanding a
"specific example", "STAR structure", or "measurable outcome" on a question
that is really about motivation, company fit, role excitement, self-awareness,
or the strengths a candidate would bring.

When this happens, prioritise the question type over the rubric wording:

For non-behavioral questions (motivation, culture/values fit, why-leaving,
role excitement, development areas, experience overview, and "what
value/strengths would you bring"), do NOT lower the score solely because the
answer lacks a past example, a STAR story, or numbers. Treat any such
requirement in the rubric as not applicable, and score on relevance,
specificity, genuineness, and role-relevant substance instead.

Only behavioral/situational questions ("Describe a time when...", "Tell me
about a time...", "Give an example of...") genuinely require a real past
example, and only those should be penalized for hypothetical-only answers.

This does not lower the floor: buzzword-only, evasive, off-topic, or refused
answers still score low on every question type. The goal is to stop
type-mismatched rubric wording from capping otherwise strong, relevant answers.

Reserve the bottom of the scale for answers that are genuinely weak:
buzzword-only answers (e.g. "ownership," "accountability," "growth mindset")
with no substance behind them, evasive or off-topic answers, refusals, or
answers showing no real understanding. For these, score low and note what was
missing (e.g. "answer lacked any specific substance").

For behavioral/experience questions, if a candidate's example describes a
related but different situation than what was asked, lower the score and note
the mismatch.

A relevant, on-topic answer that addresses the question with real substance is
NOT a bottom-scoring answer even if it is brief or lacks a polished example —
score it in the mid-range, and reserve low scores for the cases above.

Use the full scale and score confidently when an answer is grounded in the
substance the question calls for. Grounding can take several forms — a
specific real example, concrete and accurate details (named brands, products,
values, events, actions taken), a described outcome or result, or clear and
relevant reasoning — plus a direct connection to what was asked.

A quantified outcome (metrics, percentages, volumes, timeframes) strengthens
an answer where the question is about measurable results, but is not required
for a strong score, and its absence should not cap an otherwise specific,
relevant answer. Do not hold back high scores for answers that earn them.
Defer to a question's own evaluation criteria when it defines what a strong
answer looks like.