// features · by area
Every feature of Autessa Technical Interviews
Autessa Technical Interviews is technical interview software with a live coding room, a question bank, interview sessions with private candidate links, a candidate coding room and a full review. Here is every feature, grouped by area.
// 01
Live coding room
The live coding room is one shared editor where the interviewer and the candidate write, run and discuss the same Python or Java code in real time.
Collaborative code editor
Autessa Technical Interviews includes a collaborative code editor: interviewer and candidate edit one shared file in real time, and each person’s cursor stays put when the other types.
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 →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 →Autocomplete and editor tools
The interview editor has Python and Java autocomplete (including members after a dot), syntax highlighting, bracket matching, folding and search, so candidates code the way they do at work.
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 →Presence and reliable sync
The room shows whether the other person is connected and whether your code is saved; if the connection drops, typing keeps working and syncs as soon as it is back.
Explore →// 02
Question bank
The question bank holds every coding question your team asks, with the prompt the candidate reads, starter code and notes only interviewers see.
Coding question bank
Autessa Technical Interviews includes a technical interview question bank where your team stores every coding question with its difficulty, tags and notes, searchable by title or tag.
Explore →Question editor with Markdown
Questions are written in Markdown with headings, bold, inline code, code blocks and lists, with a side-by-side preview of exactly what the candidate will read.
Explore →Starter code per language
Each question can carry separate Python and Java starter code, and the candidate’s editor opens with it in whichever language they pick.
Explore →Interviewer notes on questions
Every bank question can hold private interviewer notes, such as hints, the expected solution and follow-ups, shown beside the live room and never sent to the candidate.
Explore →Question snapshots
When a question is added to a session, its title and prompt are copied in, so editing the bank later never rewrites what a past candidate was asked.
Explore →// 03
Interview sessions
A session is one live coding interview with one candidate: the questions in order, the languages allowed and a private link you control.
Session setup
Setting up a session takes the candidate’s name, an optional email, a title, the languages allowed and an ordered list of questions from your bank.
Explore →Private candidate links
Each session has a private candidate link that the interviewer copies in one click, can close to end the candidate’s access instantly, and can reopen later.
Explore →Multi-question interviews
One session can hold several questions: the interviewer switches the question on screen for both people with one click and can add a bank or blank question mid-interview.
Explore →Sessions list and live status
The sessions list shows every coding interview with a Live, Open, Submitted or Closed status and when the candidate was last active, sortable on every column.
Explore →// 04
Candidate experience
Candidates join from a private link into a calm coding room that saves as they type, shows what is installed, and lets them submit when they are done.
Candidate coding room
Candidates join the coding interview from a private link with no account or download, and their code saves automatically as they type.
Explore →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.
Explore →What’s available and clear limits
A “What’s available” panel lists the installed libraries and the run time limit, and every limit or link problem is explained to the candidate in plain language.
Explore →// 05
Review and decisions
Review shows exactly what happened in the interview: final code per question and language, every run, the timeline and the interviewer’s private notes.
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 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 →Private interviewer notes
Interviewers keep private notes on each session that save as they type, follow them from the live room to the review page, and are never shown to the candidate.
Explore →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