// live coding room
Shared output console
Every run in the room lands in one shared output console that both the interviewer and the candidate see, labeled with who ran it, its exit status and how long it took.
// the problem
Why shared output console matters in a coding interview
When only one person sees the output, the other is left asking “what did it print?”. Interviewers also lose track of which attempt failed and why, which matters later when the team discusses the candidate.
// how it works
How does shared output console work?
Anyone runs code
A run from either side lands in the same output console on both screens.
Each run is labeled
Every entry shows who ran it (Candidate or the interviewer’s name), the language, the exit status and how long it took.
Output and errors are separate
Standard output and errors show in their own blocks, so a stack trace never hides the printed result.
New output is never missed
If the interviewer has put the output panel away, a dot on the Output button signals a new run.
// options and settings
Every option, in one place
// permissions
Who can do what?
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 shared output console fits with the rest
Run Python and Java code
Autessa Technical Interviews runs Python 3.12 and Java 21 code in the browser during the interview, with numpy, pandas, Guava, Gson and other common libraries preinstalled.
Explore →Run history
Run history keeps every run from the interview with who ran it, the exact code, the input, the output, any errors, the exit status and how long it took.
Explore →Focus mode and room layout
Focus mode leaves just the code and the output on screen, and the question pane and output panel collapse or resize, remembered per browser.
Explore →// faq
Shared output console: questions
Does the candidate see the interviewer’s runs?
Yes. Both people see every run in the room, labeled with who ran it.
Are runs kept after the interview?
Yes. Every run, with its code, input, output and errors, is kept in the session’s run history on the review page.
What does “Not run” mean?
The code runner could not take the run at that moment. Nothing about the candidate’s code is implied; try again.
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