Workflow
Recruiters run the process. Engineers spend their time on the candidate.
Each step has an owner. Interviewers only see the positions and candidates they are on.
| Step | Recruiter (HR) | Engineers on the Panel |
|---|---|---|
| Position | Creates it, or uploads the job description for AI to fill in, and adds the hiring panel. | Are added to the panel, each with their weekly hours for interviews. |
| Screening | Adds résumés, sees each match score and sends the online test to the shortlist. | Can build their own tests, send them and mark the written answers. |
| Technical Round | Schedules it. Calendar invites and emails go to the panel and the candidate. | Run the interview with the shared code editor and keep private notes. |
| Feedback | Sees whose feedback is still owed on the dashboard. | Give a recommendation, a rating from 1 to 5, strengths and concerns. |
| Report | Reviews the AI draft, edits it and finalises it. | Read the final report of the interviews they were on. |
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 claimedRan in 42 msPassed
Skills evidence
See the candidate work, not just talk about it.
The test and the interview each leave something a reviewer can go back to.
- Online tests with single choice, multiple choice, short answer and long answer questions. Choice questions are marked all or nothing; written answers by a person.
- A shared code editor in the interview that runs JavaScript (Node.js), TypeScript, Python 3, Java, C++, C#, Go and SQL (SQLite).
- A live transcript of the call, kept with the recording, so a quote can be checked against what was actually said.
- Integrity signals with their times, for review only. How signals work
Interview handoff
From the recruiter to the panel, without forwarding notes.
Invites, the room, notes, feedback and the record afterwards all live on the interview itself.
- Invites everyone can open
- The panel and the candidate get an email with a calendar invite. The candidate joins by link and waits in a lobby; no account needed.
- Tests engineers can write
- Interviewers can build an online test of their own, send it and mark it. They see their own tests' results, not everyone's.
- Notes that stay private
- Each interviewer's notes during the call are their own. Feedback is given separately, on the same form for everyone.
- One record afterwards
- The recording, the transcript, the code and the report sit on the interview, so whoever reviews it can go back to what was actually said and written.
Implementation
What you need to get started.
KASAUTI IQ runs in the browser. Most of the setup is deciding who is on each hiring panel.
- A company account. Register and your free trial starts straight away.
- Your team, invited by email with a role each. Panel members you add to a position get an email to set their password.
- Your company's email domains (up to five), so a hiring panel only takes people from your own organisation.
- Questions for each position, from your own bank, the Question Library or the AI question generator.
- Candidates added in the app with their résumés. There is no ATS connection, so nothing has to be set up for one.
- A browser with a camera and microphone for everyone in an interview. Nothing to install.