Managing interviews

Interviews in the top navigation has four tabs: Interviews (the list), Templates, ScoreCards and Questions. This page covers the list — scheduling, running the pipeline, and the actions available at each stage.

Scheduling

Create an interview with the candidate's name and email, a title, and a date, time and duration. You can also record a job role and a link to the posting, a description, and additional interviewers.

Each interview gets a room code as well as a link. The code is the practical way for a colleague to join from a phone or a machine that is not signed in.

Statuses

Ten statuses, in two groups — and the distinction matters more than it looks.

Set automatically by the platform:

Set by a person, never automatically:

Plus Cancelled and No Show.

Nothing in the platform ever sets Rejected or Hired. No score, no proctoring signal and no elapsed timer moves a candidate into an outcome — a person does, and the platform records who and when. That is what keeps the hiring decision, and the accountability for it, with you. See Reviewing results.

Hired, Rejected, Declined Offer and Cancelled are terminal. An interview in one of those states is closed and its actions are gone.

What you can do at each stage

The row menu changes with the status, so an action you used yesterday may be absent today. That is deliberate rather than a bug.

Start only works from Scheduled. An interview cannot be restarted after it has ended, and ending it records the real elapsed duration rather than the duration you scheduled — which is the number your interview minutes are billed on.

Setting a status

A status change requires a note. The dialog will not submit without one, and the note is written to the interview's status history along with who changed it and when.

That history is visible on the report. It is the record that answers "why was this candidate rejected?" months later, when nobody remembers — and it is the record you want to exist if a candidate ever asks.

The report

View Report collects everything the interview produced:

• Questions & Submissions — each question used, with the candidate's Final Submission and, where they ran their code more than once, a Run History tab showing the earlier attempts
• Interview Notes — what interviewers wrote
• Evaluation Scores — either the eight built-in categories or your scorecard, depending on what the interview used. See Scorecards
• Status History — every status change, with its note and author

Notes

Notes are private by default. They belong to the interviewer who wrote them and are for your side of the conversation, never the candidate's.

View Notes is available at every stage, including on cancelled and terminal interviews, because the note usually outlives the reason it was written.

Finding an interview

Search by candidate or position, filter by any of the ten statuses, and filter by date range.

Cancelling versus deleting

Cancel sets the status to Cancelled and keeps everything — notes, scores, code, history. This is what you want in almost every case.

Permanently Delete removes the interview and its contents. It is restricted to Organization Admins and Managers, and it is irreversible. Cancel unless you have a reason the record itself should not exist.

Audit log

Interviews → Audit logs records interview created, updated, cancelled, completed and deleted actions, with who performed each. Filter by action type and date range.

This is separate from status history: status history explains a candidate's progression, the audit log explains what your team did to the record.