AppsTechnical Interviews

// 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.

Edit question · Merge intervalsMediumSAMPLE

Prompt · Markdown

# Merge intervals
Given a list of `[start, end]` pairs,
merge every overlap.

## Example
```
[[1,3],[2,6],[8,10]]
→ [[1,6],[8,10]]
```

- **Sort first** if you like

Preview · what the candidate reads

Merge intervals

Given a list of [start, end] pairs, merge every overlap.

Example

[[1,3],[2,6],[8,10]]
→ [[1,6],[8,10]]

• Sort first if you like

// the problem

Why question editor with markdown matters in a coding interview

A good prompt reads like a well-formatted ticket: a clear statement, inputs, an example in a code block. Plain text boxes make every question look like a wall of words.

// how it works

How does question editor with markdown work?

  1. Title it

    Give the question a short title, such as “Merge intervals”.

  2. Write the prompt in Markdown

    Use # headings, **bold**, `inline code`, fenced code blocks and lists.

  3. Preview it

    Show the preview side by side to see exactly what the candidate will read.

  4. Save

    The question is saved to the bank and is ready for the next session.

// options and settings

Every option, in one place

Option
What it does
Title
Required, up to 200 characters.
Difficulty
Easy, Medium or Hard.
Tags
Comma-separated; tidied and de-duplicated on save.
Prompt
Markdown, shown to the candidate.
Preview
Show or hide a rendered preview beside the editor.
Starter code and notes
See Starter code and Interviewer notes on questions.

// permissions

Who can do what?

Who
Can
Interviewers (anyone your company admin gives access to the console)
Write and edit questions.
Candidate (anyone holding the session link while it is open)
Reads the rendered prompt in the room.

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 question editor with markdown fits with the rest

// faq

Question editor with Markdown: questions

Can prompts include code examples?

Yes. Fenced code blocks and inline code render in the candidate’s question pane.

Can I preview a question before using it?

Yes. The editor shows a side-by-side preview of the rendered prompt.

Does editing a question change past interviews?

No. Sessions keep the copy that was added, so past interviews always show what the candidate saw.

$ start --interview

Try question editor with markdown 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