Structured interview scorecards

Give every interviewer a shared standard.

Prepare role-specific questions, review the scoring guidance, and bring ratings and evidence notes into the same debrief.

Request a scorecard demo View a completed scorecard

Explore a prepared example. Sharing your own workflow is optional.

Completed demo question about tenant workload isolation, rated Strong, with reviewer notes describing the candidate’s implementation and operational contribution. — Product view from the completed Software Engineer demo scorecard. Ratings reflect reviewer judgment; the notes show what informed it.

Scroll the image horizontally when needed to read the detail.
View full product screenshot: A rating with the explanation beside it →

Useful before you book a meeting

A completed specialist scorecard you can adapt.

Five Software Engineer questions, evidence guidance, worked notes, and a blank interview record in an editable HTML file.

Illustrative sample · question 1 of 5

“Walk through a service you changed to keep one customer’s workload from slowing down others.”

Listen for: the candidate’s contribution, isolation mechanism, failure behavior, and how they checked the result.

Fictional evidence note: described implementing per-customer worker limits and a mixed-load test; explained why a single shared queue caused delays. Did not yet explain behavior when a customer exceeds its allocation.

Reviewer assessment: evidence of a concrete design and test; the overload path remains unassessed.

Next question: “What happens at the limit, and what test covers that?”

Take the whole interview plan.

Questions on system design, measurement, testing, rollout, and collaboration.
Question-specific evidence cues and follow-up prompts.
Completed fictional notes showing both supporting evidence and uncertainty.
An editable blank record with a “Download my edited copy” action that saves your notes in the file.

Read the full sample → Download editable scorecard

No email required. Open the completed example now; edit and download your own record locally. This teaching example is separate from the product screenshots and is not a customer record or a product export.

Make the interview purposeful

What makes a question useful?

Connect it to a requirement, define what you are listening for, and prepare a follow-up before the conversation starts.

01 · Role requirement

Name the work being assessed.

For a Software Engineer: design and operate a service that isolates different customers’ workloads.

02 · Listening cues

Look for an explanation you can examine.

Ask about personal contribution, design trade-offs, test conditions, and operational limits.

03 · Follow-up

Close the specific evidence gap.

“What happens when one customer exceeds its allocation, and how did you test that behavior?”

The example above is interview preparation guidance. Review it with someone qualified to assess the role; it does not establish a candidate’s ability.

From preparation to debrief

Use the same plan through the conversation.

Your team reviews the draft, records the evidence, and owns the interpretation.

Draft around the role

Use the role brief and success goals to prepare questions about the work that matters.

Review the interview plan

Check the questions, rating guidance, follow-ups, and accommodation needs before interviewing.

Record the conversation

Capture the candidate’s explanation and your evidence notes. Leave unanswered questions marked as not asked.

Debrief from the record

Read the evidence behind each rating and agree what needs further specialist review.

Demo scorecard editor with editable questions, a five-level rating guide, listening cues, follow-up prompts, and linked roles. — Product view · demo data. Review and tailor the questions and scoring guidance before your team starts interviewing. Open image to inspect.

Examine disagreement

Bring the reasons behind the ratings.

Different impressions become easier to discuss when reviewers can point to the answer, the criterion, and what was left unanswered.

Connect the debrief to your shortlist →

Illustrative debrief

Same discussion. Different evidence needs.

Reviewer A: saw a clear design explanation and a concrete test.

Reviewer B: still needs evidence about overload and recovery.

Team follow-up: ask the candidate to walk through the failure case before resolving that criterion. Keep both reviewers’ reasons in the discussion.

A score summarizes reviewer-entered ratings. It is not an objective measure of quality, a prediction of performance, or an automatic hiring recommendation.

Start with one role

Before your team uses a shared scorecard.

Can we edit the questions and scoring guidance?

Yes. Tailor the questions, guidance, follow-ups, and order before the interview. Review generated content for accuracy, relevance, fairness, and accommodation needs.

Can this help with specialist roles?

It can clarify outcomes, metrics, trade-offs, and useful follow-ups. It does not replace qualified specialist review when that expertise is needed.

Do interviewers need to follow a script?

No. They can keep their conversation style while using a shared plan. Agree on the evidence you need, test the scorecard on one role, and adjust it together.

Which plans include scorecards?

Core, Enterprise, and recruiting plans include structured scorecards. Companion focuses on interview protection. Compare plan capabilities and usage.

See the plan and the completed record

Walk through a scorecard your team could use.

See how questions, guidance, evidence notes, and ratings fit the interview and debrief. We can use a prepared example; your own role is optional.

Request a scorecard demo View the sample first