AppsTechnical Interviews

// candidate experience

Submit and lock

When the candidate submits, their editor turns read-only and the interviewer is told the time; the interviewer can turn editing back on with one click.

Candidate · submitSAMPLE

Submit your work?

Your code is saved and shared with your interviewer. After you submit, you can’t edit or run it anymore.

Keep workingSubmit
Interviewer · live roomSubmittedSAMPLE

The candidate submitted at 11:24. Their editor is read-only; yours still works.

↶ Let the candidate edit again

// the problem

Why submit and lock matters in a coding interview

Without a clear finish line, interviews end awkwardly and code keeps changing after the call. A deliberate Submit gives the candidate closure and gives you a fixed final version.

// how it works

How does submit and lock work?

  1. The candidate presses Submit

    A dialog explains that the code is saved and shared, and that after submitting they cannot edit or run it.

  2. Their editor locks

    The candidate sees “Submitted. Your interviewer has your work.” and a read-only editor.

  3. You are told

    The interviewer’s room shows when the candidate submitted; their own editor still works.

  4. Undo if it was early

    “Let the candidate edit again” turns their editor back on with one click.

// options and settings

Every option, in one place

Option
What it does
Submit
Candidate-only; with a Keep working option.
Submitted time
Shown in the room, the review page and the sessions list status.
Let the candidate edit again
Interviewer-only.

// permissions

Who can do what?

Who
Can
Candidate (anyone holding the session link while it is open)
Submit once they are done.
Interviewers (anyone your company admin gives access to the console)
See the time, keep editing, turn candidate editing back on.

Company admins decide who on your team can open the interviewer console. Candidates never sign in; they only ever use their session link.

// connects to

How submit and lock fits with the rest

// faq

Submit and lock: questions

Can a candidate change code after submitting?

No, unless the interviewer turns editing back on.

What if the candidate submits by mistake?

The interviewer clicks “Let the candidate edit again” in the live room.

Is submitting the same as closing the link?

No. Submit locks the candidate’s editor; Close link ends their access entirely. You can do both.

$ start --interview

Try submit and lock in your next interview.

Create a session, send the link and see it working with a real candidate.

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