AppsTechnical Interviews

// question bank

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.

Questions · your question bank+ New questionSAMPLE
⌕ Search by title or tag☐ Show archived (2)
Title ↕Difficulty ↕TagsUpdated ↕
Two sumEasyarrayshash maps2 days ago
Balanced bracketsEasystacksstrings2 days ago
Merge intervalsMediumsortingarrayslast week
LRU cacheMediumdesignhash mapslast week
Rate limiterHarddesignqueues3 weeks ago

// the problem

Why coding question bank matters in a coding interview

Interview questions scattered across docs and personal notes lead to uneven interviews: one interviewer asks a warm-up, another asks a system design puzzle. A shared bank gives every interviewer the same well-written questions.

// how it works

How does coding question bank work?

  1. Start with samples or your own

    An empty bank offers the sample questions Two sum and Balanced brackets, or a blank new question.

  2. Organize

    Give each question a difficulty (easy, medium or hard) and comma-separated tags.

  3. Find questions fast

    Sort by title, difficulty or last updated, and search by title or tag when picking questions for a session.

  4. Retire without deleting

    Archive a question to keep it out of the picker; restore it any time. Past interviews keep their copy either way.

// options and settings

Every option, in one place

Option
What it does
Columns
Title, Difficulty, Tags, Updated; sortable.
Show archived
Toggle to include archived questions, with a count.
Search in pickers
Matches title, tag or difficulty.
Sample questions
Two ready-made questions with prompts, Python and Java starter code and notes.
Archive and restore
Archived questions disappear from the session picker only.

// permissions

Who can do what?

Who
Can
Interviewers (anyone your company admin gives access to the console)
Create, edit, archive and restore questions in the shared bank.
Candidate (anyone holding the session link while it is open)
Never sees the bank; only the questions put on screen in their session.

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 coding question bank fits with the rest

Question bank

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 →
Question bank

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 →
Question bank

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 bank

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 →

// faq

Coding question bank: questions

Can I build my own technical interview question bank?

Yes. The bank is yours: write questions with a Markdown prompt, starter code, difficulty, tags and private notes.

Does it come with questions?

It offers sample questions to start from. Most teams then write their own.

What happens when I archive a question?

It no longer appears when you pick questions for a session. Restore it any time; past sessions are unaffected.

$ start --interview

Try coding question bank 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