Interviews stop being a personality contest.
Async video, live rooms and coding tasks with question banks tied to the scorecard. The AI notes competencies with timestamps, flags where interviewers disagreed, and produces a comparison the hiring committee can actually read.
Last updated
Illustrative example of one interview round, not a measured result. What a round produces depends on your scorecard, your panel and the role.
Every interview structured, scored and comparable.
Question banks mapped to competencies per role.
Async video at volume, ranked with reasons.
Live rooms and coding tasks with live scorecards.
Scoring drift and bias flags surfaced.
Scores do not live in a separate tool. They update the candidate's stage inside your ATS pipeline, so a sourced candidate from the sourcing engine and an inbound applicant are compared on identical evidence. Once an offer is accepted, the same record carries into HRMS onboarding.
What interview intelligence does for you.
Screen at volume without booking a single slot.
Competency evidence linked to the moment it happened.
Interviewer scoring compared and corrected over time.
Practical work samples inside the same record.
Across calendars, time zones and interviewer load.
Structured criteria, redaction options, auditable reasons.
Related reading: interviews and assessments, interview scheduling software, interview management software and interview questions by role.
How does interview software actually work?
Underneath the interface, interview software is a scorecard attached to a schedule and a recording, and almost all of the work happens before a conversation is booked. Someone decides which competencies the role genuinely requires, writes a question for each, and gives each competency to exactly one round and one interviewer. That mapping is the interview loop, and it is what the software stores. Delivery is the straightforward half; the design decides whether two candidates can be compared at the end.
Each round then does one job. A one-way round sends every candidate the same questions with the same preparation time, which is how a large pool is screened without booking a slot per person. Live rounds carry the questions that need a follow-up, since a recorded answer cannot be probed, and practical work such as a coding task tests what the job involves rather than a description of it.
Scoring is where the value is created or lost. Interviewers rate the competency they own against written anchors and submit before the debrief, because a rating entered afterwards mostly records the discussion. The software then does bookkeeping a spreadsheet does badly: holding evidence beside the rating, showing where two people who watched the same answer disagreed, and keeping the record intact long enough to compare finalists. Because interview scheduling and the stage in your ATS pipeline read from that record, nothing is reconciled afterwards.
Structured interviews vs unstructured — what actually differs
The difference is not formality. It is whether two candidates were asked the same questions and rated against the same anchors. A structured interview fixes the question set and the scoring guide in advance, so variation in the outcome is more likely to be about the candidates. An unstructured interview is improvised: different things asked of different people, one impression formed at the end. It feels more human, and that is the problem — two people are never assessed on the same basis, so the results cannot honestly be compared.
Research in industrial psychology has consistently placed structured formats among the stronger predictors of job performance, and the reason is unglamorous: standardisation removes noise. When the questions and the scale both move, the gap between two candidates carries the interviewer's mood and rapport alongside anything about capability. Most teams land on semi-structured — a fixed core of scored competency-based or situational questions, with room for a few follow-ups. Watch for a rigorous-sounding question set that maps to nothing the role requires: structure applied to the wrong questions only makes a weak signal consistent.
Who needs structured interviewing, and who genuinely does not
If one person runs every interview, hires a handful of people a year, and has never had to explain a rejection to anybody, structure will not improve those decisions much. There is one standard being applied because there is one head applying it. A scorecard in that situation is administration, and not yet is a legitimate answer.
What moves the decision is rarely volume on its own — it is the number of people whose judgement has to add up. The signals are specific: two interviewers land a full rating point apart and nobody can see which evidence they disagreed about; a hiring manager overturns a shortlist and no one can reconstruct what was scored; the same role reopens and the questions are rewritten from scratch; a rejected candidate asks for a reason and the honest answer is a feeling. Regulated and client-facing hiring reaches that point sooner, because someone eventually asks for the basis of a decision in writing.
More than one person interviews for the same role · you hire for that role repeatedly · a rejection may have to be explained to a candidate, a client or an auditor · interviewers disagree and nobody can see which evidence they disagreed about.
One person runs the whole loop and makes the call · you hire a handful of people a year · every role is different enough that no question set is reused · nobody outside the room needs to see the reasoning. Revisit when one of those stops being true.
What changes in the first 90 days of structured interviewing
The first fortnight is writing things down, and the common mistake is redesigning the loop while configuring it. Mirror the rounds you already run, awkward ones included. The one piece of genuinely new work is the interview scorecard: a small set of criteria per role, each with a written description of what a weak, adequate and strong answer looks like.
Between days sixty and ninety comes the thing you actually bought: comparison. One full cycle of independent scores shows which interviewers sit above or below the rest of the panel, which questions everybody passes and therefore separate nobody, and where in the loop candidates leave. That is the raw material for interview calibration, and the first point at which the bar can be moved deliberately instead of argued about. One caveat, and it is the whole caveat: the report is only as good as whether people scored before the debrief.
What interview software does not solve
It does not tell you what a good hire looks like. If the team has never agreed what the role must actually produce, a scorecard records that disagreement in a tidier format — several people confidently rating several different jobs. The criteria come out of a job analysis somebody has to sit down and do. The software supplies the form, not the answer, and a vague brief upstream stays vague downstream.
It does not make an untrained interviewer good. Someone who follows whichever thread sounds interesting and writes three lines afterwards will do exactly that inside a structured template, and the ratings are no more meaningful for having a scale attached. Teaching the mechanics is interviewer training; getting already-trained interviewers to put the bar in the same place is calibration. Both are people programmes, and neither ships with a product.
And a scorecard does not remove bias. It makes bias visible. Fixing criteria in advance narrows the room to move the goalposts after the fact, and independent scoring stops the loudest voice in the debrief becoming the group's opinion — both of those are real. But the criteria themselves can encode a preference nobody examined, and a consistent process applies a biased standard consistently, to everyone, faster than a messy one did. Automated scoring has the same property: it reflects whichever signals it was pointed at. What structure buys you is a record you can audit and argue with, which is a precondition for addressing bias rather than a substitute for doing it.
Two boundaries worth being blunt about. Interviewing does not create candidates: if a role attracts a handful of applicants, assessing those few more rigorously will not fill it, and that belongs to the sourcing side. And no tool settles whether a decision was fair or lawful. It preserves the evidence somebody would need to examine that, which is worth having and is not the same thing.
How to evaluate interview tools without a six-month process
Feature grids are how this turns into a quarter-long project, because nearly every vendor ticks nearly every box and the grid ends up measuring who writes better marketing copy. Run one real loop instead: take a role you are genuinely hiring for, build its scorecard in the tool, send one asynchronous round, run one live panel, have every interviewer score independently, and produce the comparison you would take to a debrief.
While you do it, test the four things that break after purchase. Does the scorecard bend to your competencies, or impose the vendor's? Can an interviewer submit a rating before seeing anybody else's — that ordering is the entire point, and some tools show the panel by default. What does the candidate experience: preparation time, retakes, and a visible alternative for anyone who cannot complete a recorded round. And can you get recordings, ratings and evidence back out in a readable form. Then ask the vendor to explain one rating in front of you, because a score with no evidence behind it cannot be defended to a hiring manager, let alone to the candidate.
What to check before you record or auto-score an interview
Treat this as a legal question in your jurisdiction rather than a product question, and assume the answer changes. Rules on recording, consent, candidate notice, data retention and automated employment decision tools differ by country and often by state or province, and several have been rewritten in recent years. Nothing on this page states what any jurisdiction requires, and none of it is legal advice. The list below names the categories worth putting in front of your own counsel before a round goes live.
Five recur. Recording and consent — who has to be told, who has to agree, and whether that is captured before the first frame. Notice for automated tools — where a system scores, ranks or filters candidates, some places require that candidates are told and some require independent bias auditing. Data protection — what is stored, for how long, who can open it, whether it crosses a border, and how a deletion request is honoured. Accessibility — a candidate who cannot complete a recorded round needs a visible alternative rather than one they have to discover. Adverse impact — any assessment that filters candidates can affect groups differently, and that has to be measured rather than assumed away.
The habits underneath are the same everywhere: ask every candidate for a role the same job-related questions, keep the reasoning attached to the decision, stay off subjects unrelated to the ability to do the job, and be able to say who watched what. Our interviewer training entry goes deeper, and the hiring guides place the interview stage in the wider process.
What buyers ask before they switch.
How is an AI interview scored?
Every question maps to a competency on the role's scorecard. The AI notes where a competency was evidenced, timestamps it against the recording, and rates only what it can point to. The evidence sits beside the score, so a hiring manager can disagree with a rating and see exactly what produced it.
Does AI make the hiring decision?
No. It ranks and evidences; people decide. Scores are advisory, every rating is traceable to a moment in the interview, and a human can override any of them. The audit trail records who changed what.
What is the difference between async and live interviews?
Async (one-way) interviews let a candidate record answers on their own time, which is how you screen a large applicant pool without booking slots. Live rooms are for the later stages, where a panel scores against the same scorecard in real time. Both land in the same candidate record.
Can we use our own interview questions?
Yes. Question banks are yours to write and reuse, and each question is tied to the competency it tests. You can start from the generated set for a role and edit it, or import the bank your team already uses.
How does this connect to the rest of hiring?
Interview intelligence is part of the same platform as the ATS, so a scored interview updates the candidate's pipeline stage directly. There is no export step and no second system to reconcile.
What is an interview scorecard, and who writes it?
An interview scorecard is the form interviewers use to rate a candidate against criteria agreed before the first conversation: a small set of competencies, a rating scale, space for evidence, and a recommendation. It is written by whoever owns the role, not by interviewers on the day. The evidence field is what does the work — making an interviewer note what the candidate actually said turns a verdict into something a colleague can review.
How many interview rounds should a loop have?
Cap the loop by the total hours you ask of a candidate rather than by a count of rounds, and give each round one competency and one owner. Extra sessions cost you most among exactly the people you want: those already employed, those with caring responsibilities, and those holding faster offers. If another round feels necessary, ask instead which existing round produces evidence nobody uses at the debrief.
Do candidates dislike one-way video interviews?
Many do, and it is worth designing around rather than denying. Recording answers to a lens gives a candidate no reaction to read and no way to ask a clarifying question. Generous preparation time, at least one retake, an explicit statement that background and setup are not scored, and a named person to contact all reduce abandonment. The coldness of the format does not go away, so it belongs in high-volume screening rather than senior hiring.
Is AI interview scoring legal where we hire?
That depends on your jurisdiction and it changes, so it is a question for local counsel rather than for a vendor page. Rules on recording consent, candidate notice for automated employment decision tools, bias auditing and data retention differ by country and often by state or province, and nothing on this page states what any jurisdiction requires. The preparation is the same everywhere: be able to show what was asked, what was scored, and who watched the recording.
Can we keep the interview process we already run?
Yes, and starting that way is usually the better rollout. Mirror the stages and questions you already use, awkward ones included, so the only new work in the first fortnight is writing down what a weak, adequate and strong answer looks like. Changing the process and the tooling at once makes it impossible to tell which caused a problem. Redesign the loop later, once a full cycle of scores has shown where it is weak.
Running a contingent bench as well? Vendor management scores agency submissions against these same interview stages. For a vertical view, see ATS by industry, or talk to us on the contact page.
The applicant tracking system for recruiters and hiring teams
Pitch N Hire is an applicant tracking system. Post roles, screen applicants, run structured interviews, and make offers from a single pipeline — free for 1 user.
Free for 1 user · No credit card · Talk to a real hiring expert
See a real interview scored on your own roles
Get a walkthrough of structured interviewing and scorecards on the roles you are actually hiring for. No slides, no obligation.
Prefer to talk? Book a demo Talk to sales View pricing
Free 1-user plan · No credit card · Talk to a real hiring expert
See a real interview scored, end to end.
Free managed migration, live in five working days, and no annual lock-in. The free plan is free forever for one user.