// review and decisions
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.
// the problem
Why run history matters in a coding interview
Final code tells you where the candidate ended up, not how they got there. How someone tests, reads an error and fixes it is often the most useful signal in a coding interview.
// how it works
How does run history work?
Open Run history
On the review page, every run is listed newest first.
Scan the summary
Each row shows who ran it, the language and question, the outcome, the duration and the time.
Expand a run
See the exact code that ran, the program input, the output and any errors.
Load more
Long interviews page in 25 runs at a time.
// 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 run history fits with the rest
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.
Explore →Session review
The review page shows each question with its prompt and the candidate’s final code in every language they used, alongside the session timeline and facts.
Explore →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 →// faq
Run history: questions
Does run history show the code at the time of each run?
Yes. Each run keeps the exact code that ran, which is often different from the final code.
Are the interviewer’s runs included?
Yes, labeled with the interviewer’s name.
Is there a limit to how many runs are kept?
Every run is kept; the page loads them 25 at a time.
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