Interviewing & Decision-Making

01Why interviews stay mandatory

A resume, however carefully evidenced, is a self-reported document. It can't verify communication skill, team fit, how someone actually thinks through a problem in real time, or a dozen other things a structured conversation reveals that no CV-scoring system — deterministic or otherwise — can substitute for. Every credible academic framework on hiring assessment treats structured interviews as a load-bearing part of the process, not an optional formality after an automated score has already decided the outcome, and we designed around that rather than against it.

02Scheduling and feedback capture

Interviews are scheduled directly from a candidate's record — phone, video, technical, onsite, or panel — with duration, location or link, and the assigned interviewer(s) all attached to that specific application. When the interview concludes, the interviewer logs a numeric score and written feedback immediately, attached permanently to that interview record rather than living in a separate email thread or someone's private notes that evaporate a few weeks later when the hiring decision is actually made.

03Team input alongside the score

Team members can leave threaded notes and a simple up/down/neutral vote on any candidate, visible alongside — not blended into — that candidate's CMS score. This is a deliberate separation: the deterministic score and human team judgement are two distinct inputs to a decision, shown side by side rather than combined into one number that would obscure which part came from evidence-based measurement and which came from a colleague's gut read.

04The complete decision record

By the time a hiring decision is made, a candidate's record contains the CMS score with its full dimension-level breakdown, every piece of interview feedback from every interviewer, team notes and votes, and a timestamped stage history showing exactly when and by whom the candidate moved through the pipeline. This composite record is what makes a hiring decision defensible after the fact — not because the score alone justifies it, but because the full trail of evidence and human judgement that led to it is preserved and retrievable.

05Common ways interview processes lose their value silently

A structured interview stage set up correctly can still degrade in practice through a few well-documented patterns. Feedback delay is the most common: an interviewer who fills in their scorecard three days later, after several other candidates have blurred together in memory, produces measurably less reliable feedback than one captured within the hour — which is why feedback capture is tied directly to the interview record rather than left to a separate, easily-deferred step.

A second pattern is halo effect from the CMS score itself — an interviewer who sees a 96% match score walking into the room may unconsciously interview to confirm that impression rather than genuinely test it, and the reverse happens with a low score. There's no purely technical fix for this; the discipline is procedural; some hiring teams deliberately withhold the CMS score from interviewers until after feedback is submitted, specifically to prevent this anchoring effect, which the platform supports as a workflow choice rather than enforcing one way or the other.