Quotes, not vibes
Every score cites the transcript. Anything the model cannot back with a verified quote is dropped rather than guessed at.
Voice interviews, scored with their evidence
Candidates hold a real conversation with an AI interviewer. Recruiters get a report where each number is attached to a verified quote and the moment in the recording it came from — not a black-box rating.
Candidate
liveRecruiter
Rubric coverage 83%
Our vision
Most screening tools speed up a decision without ever showing their working. A candidate gets rejected by a number nobody can explain, and a recruiter has to trust it anyway. We think the number is worthless unless you can see what produced it.
Every score cites the transcript. Anything the model cannot back with a verified quote is dropped rather than guessed at.
They get written feedback on how the conversation went. No band, no verdict — enforced in the schema, not by a checkbox.
Pauses, pitch and filler words track nerves, not ability. We report them and refuse to multiply them into the result.
How it works
Add a job and its description. Versions are kept, so you can see what a candidate was actually interviewed against.
Questions and a weighted rubric are generated from the role and the candidate's CV. Edit or approve before anyone joins.
The candidate joins a voice call from a link. No scheduling, no panel, no calendar tetris.
A scored report lands with quotes, timestamps and rubric coverage — plus separate written feedback for the candidate.
Features
Speech recognition, the language model and speech synthesis run on a live turn budget, so the conversation flows instead of stuttering.
Questions are written from the job description and the candidate's own CV, then checked for grounding before anyone is asked them.
The recording is re-transcribed after the call, so every quote a score depends on is checked against what was really said.
Tab switches, pasting and webcam frames, with thresholds per role. Off by default where a false positive would be unfair.
A recruiter PDF with the full evidence trail, and a separate candidate PDF with feedback and no score anywhere in it.
Every tenant is separated by row-level security in Postgres, so a forgotten filter in application code still cannot leak a row.
The part most tools skip
An unsupported number still reads as authoritative, and that is what makes a rejection unappealable. So the scorer verifies each quote against the transcript, drops paraphrases, and discards any score left with no surviving evidence.
System design
4.2 / 5
Described a concrete migration they led, including the failure mode that forced it and what they would do differently.
Illustrative example — not a real candidate.
Create an organisation, add a role, and send a candidate a link. Nothing to install on their side.