// security · data handling · permissions
Security for coding interviews: candidates see the question, nothing else
Autessa Technical Interviews keeps your question bank and notes inside the interviewer console. Candidates reach the coding room only through a private link that you can close at any moment, and every action they take is checked against that link.
// two halves, two levels of trust
How is candidate access separated from your data?
The product is two apps. Your team works in the interviewer console; candidates work in a public coding room that cannot read your data directly.
interviewer console
Signed in, your team only
Interviewers sign in with Autessa. They see the question bank, every session, the live room, the review and all notes. Company admins decide who can open the console.
candidate coding room
Public, link-checked, minimal
The coding room can only open, sync, run and submit. Every action checks the link and returns only the question on screen, the code and the runs. It has no direct access to your data, your question bank or your notes.
// controls
Data handling, permissions and audit, in detail
// good practice
Running secure coding interviews
Send the link only to the candidate
Anyone with the link can join while it is open.
Close the link when you finish
It takes one click and the candidate’s work stays saved.
Keep answers in notes, not prompts
Prompts are shown to candidates; interviewer notes never are.
Use the email field for your records
Autessa does not email candidates, so you choose how the link is sent.
For Autessa’s security program, policies and reports, visit the Autessa Trust Center.
// faq
Security questions
Can a candidate see our question bank or interviewer notes?
No. The candidate room is a separate public app that can only open the session, sync code, run it and submit. Every action checks the session link and returns only what a candidate needs: the question on screen, the code and the runs. The bank and all notes stay in the interviewer console.
How do I stop a candidate from getting back into a session?
Click Close link in the live room. Access ends immediately, and every later request from that link is refused. The candidate’s work stays saved, and you can reopen the same link if you need to.
Where does candidate code run?
On Autessa’s code runner, not on the candidate’s or interviewer’s machine. Each run gets up to two minutes, 100,000 characters of code and 20,000 characters of input, and rapid repeated runs are slowed down.
Where can I find Autessa’s compliance reports?
In the Autessa Trust Center at trust.autessa.com, which lists Autessa’s security program and documents.
100% customizable, code and all
Make Autessa Technical Interviews fully your own.
Use it out of the box, then change anything. Ask Autobot, Autessa’s AI builder, for a new field, screen, report, workflow or agent and it builds it into your copy of the app. Or open the code and edit it yourself. Nothing is locked: the app, its data and its code are yours.
Start free and make it yours