Interviews that leave a record you can go back to.

Schedule the round, send the candidate a link, and talk in a recorded room with a live transcript and a shared code editor. Each interviewer then gives their own feedback.

Book a Demo See Interview Reports

Backend Engineer · Round 2Sample data

Interviewer

Candidate

Recording00:24:18

Live Transcript

24:02Interviewer: How would you stop two workers taking the same job?

24:09Candidate: I'd claim it with an update that only succeeds while the row is still unclaimed…

claim_job.sqlSQL (SQLite)

update jobs
set worker = :me,
    claimed_at = now()
where id = :job
  and worker is null;

-- 1 row claimed

Ran in 42 msPassed

Before the call

From invitation to the room in four steps.

The candidate gets one email with everything they need. Your panel gets the same event in their calendar.

Interview Invitation · EmailSample data

Thu14

Backend Engineer · Round 2

11:00 – 12:00 · 60 minutes

Technical · L2 · 2 interviewers

invite.icsJoin the Interview

Join Interview · CandidateSample data

Your Camera Preview

Microphone On

I agree that this interview is recorded
I agree to the integrity checks during the interview
I agree that AI helps the interviewers write their notes

Waiting for the interviewer to let you in.

The interview starts as soon as you are let in.

01
Schedule the round
Pick the candidate on a position, the level (L1 to L4, or an HR round), general or technical, and up to 5 interviewers. The panel's weekly hours show as hints, and you're warned if an interviewer is already busy.
02
Send the invitation
The candidate and the panel get an email with a calendar invite. A change updates the same calendar event, a cancellation removes it, and reminders go out before the start.
03
The candidate joins by link
No account and nothing to install. The private link works only for that interview, and a newer email replaces the link in an older one. The candidate checks their camera and microphone before joining.
04
Consent, then the lobby
The candidate agrees to what this interview uses (recording, integrity checks, AI help with notes) and waits until an interviewer lets them in.

In the room

Talk, code and take notes in one place.

Everything happens in the browser, for the candidate and the panel.

Recorded, with a live transcript

The call is recorded once the candidate has agreed. What is said is transcribed while you talk, and the interviewers see it line by line, with who said it.

The candidate is told the interview is recorded before they join, and asked to agree.
The live transcript goes to the interviewers only.
Pick one of the position's prepared questions and put it straight into the code editor. Each pick is marked on the recording.

Live Transcript · Interviewers OnlySample data

Recording00:13:05

12:41Interviewer 1: What happens if two ranges only touch at the end?
12:47Candidate: They should merge, so I compare with less-than-or-equal, not less-than.
13:02Interviewer 2: And if the list is empty?
13:05Candidate: Then ranges[0] fails. I'd return an empty list first.

Code Editor · Technical RoundSample data

Python 3InputRun

# Merge overlapping ranges
def merge(ranges):
    ranges.sort()
    out = [ranges[0]]
    for a, b in ranges[1:]:
        last = out[-1]
        if a <= last[1]:
            last[1] = max(b, last[1])
        else:
            out.append([a, b])
    return out

JavaScript (Node.js)
TypeScript
Python 3
Java
C++
C#
Go
SQL (SQLite)

[[1, 6], [8, 10]]Passed

A shared code editor that runs the code

In technical rounds, the candidate and the interviewers work in the same file. Run it, give it input, and see the output or the error together.

JavaScript (Node.js)
TypeScript
Python 3
Java
C++
C#
Go
SQL (SQLite)

Three kinds of notes

Private Notes: Only the interviewer who writes them can read them. Saved as you type.
Shared Notes: One document the interviewers edit together during the call. The candidate never sees it.
Candidate Notepad: The candidate can write out their thinking. Interviewers see it live, and it is kept for the report.

Integrity signals

Moments to check, not verdicts.

When integrity checks are on and the candidate has agreed, the interviewers see an alert for each signal, and every one is placed on the recording with its time.

How each signal works

Camera: No face, more than one face, looking away, camera off. Checked in the candidate's browser; the video isn't sent anywhere for this.
Attention: Switching to another tab and another window taking focus, with how long it lasted.
Editor and Screen: A large paste into the code editor. In technical rounds, a whole-screen share, and a note if only a window was shared.
Photos: A camera photo every few minutes, kept for the period your company sets.

After the call

Every interviewer gives their own view.

Scorecards are written separately, so one strong opinion doesn't become the panel's.

Your Feedback · Interviewer 1Sample data

Technical Knowledge
Problem Solving
Reasoning and Decisions
Communication
Ownership and Role Fit

Overall Rating4 · Above the Bar

RecommendationYes

ConcernsDidn't test the empty-list case until asked.

A scorecard per interviewer

A rating from 1 to 5 for technical knowledge, problem solving, reasoning, communication and fit for the role.
An overall rating and a recommendation: Strong Yes, Yes, No or Strong No.
Strengths and concerns, in their own words.
Feedback still owed a day after the interview shows on the dashboards.

Recording · Key MomentsSample data

00:02Candidate let in
08:15Question shown: merge overlapping ranges
19:40Code run: passed
27:05Switched to another tab

The recording, with its key moments

Jump to when the candidate joined, a question was shown or the code was run.
Reviewers also see the integrity signals on the same timeline.
The transcript, notes and final code sit beside the video.
Recordings are in private storage and play through links that expire after 30 minutes.

Questions about interviews

No. They open the private link from their invitation email. It works for that interview only, on one device at a time, and stops working shortly after the scheduled end.

Yes. Recording and integrity checks are chosen per interview. Without a recording there is no transcript, so no AI report is drafted for that round.

The interviewers in the call. The candidate doesn't see it. Afterwards, reviewers and the people on the panel can read it beside the recording.

Yes, in a sandbox. The editor runs JavaScript (Node.js), TypeScript, Python 3, Java, C++, C#, Go and SQL (SQLite). The candidate and the interviewers edit the same code, can give the program input, and see the output or the error.

Your company sets it: recordings for 30 to 365 days, camera photos for 7 to 180 days, transcripts and reports for 90 to 1,095 days. A nightly job removes what is past its date. A candidate's interview data can also be deleted on request.

See it with your own hiring process.

Tell us the roles you hire for. We'll walk through an assessment, an interview and its report, built around one of them.

Book a Demo See Pricing

1
We reply within one working day to agree a time and the roles to cover.
2
A 30-minute walkthrough of the product with your own positions.
3
A pilot if it fits with a defined group of candidates.

Interviews that leave a record you can go back to.

From invitation to the room in four steps.

Schedule the round

Send the invitation

The candidate joins by link

Consent, then the lobby

Talk, code and take notes in one place.

Recorded, with a live transcript

A shared code editor that runs the code

Three kinds of notes

Moments to check, not verdicts.

Every interviewer gives their own view.

A scorecard per interviewer

The recording, with its key moments

Questions about interviews

Does the Candidate Need an Account?

Can We Run an Interview Without Recording?

Who Sees the Live Transcript?

Does the Code Editor Run the Code?

How Long Are Recordings Kept?

See it with your own hiring process.