Rehearsing a Job Interview Out Loud
Paste the job description and your CV in as a topic, and you can be questioned on them out loud — behavioural questions, technical ones, the awkward gap in your history — as many times as you like. The conversation is written down afterwards, so you can read back what you actually said rather than what you meant to say.
Setting It Up
Interview practice is just a topic, so build one out of the material the interview will actually be about:
- The job description — paste it in as the topic description, or upload it as a PDF. The responsibilities are the syllabus.
- Your CV — include it too. Questions then come from your history as well as the role, which is where the uncomfortable ones live.
- Name the topic for the interview, not the job — for example "Interview: senior analyst, retail banking" — so the roadmap is built around being asked rather than around learning the subject.
- Use subtopics as rounds — the roadmap breaks the material into subtopics, and each one is a sensible unit for a single rehearsal call.
Running a Rehearsal
Start a spoken conversation on one subtopic and answer out loud, without notes. Let the follow-up questions come — being pushed on a vague answer is the whole point, and it is the part reading your notes cannot do. A call runs up to nine minutes, which is close to a real interview round, so treat each call as one round rather than trying to cover everything in one sitting. Then start a fresh call on the next subtopic, so every rehearsal begins cold the way the real thing will.
What It Does Not Do
It does not score you. There is no rating of your delivery, no analysis of your tone or pace, no filler-word count and no percentage at the end. Tools built specifically for interview coaching sell exactly that, and we would rather tell you plainly than imply we do it. What you get instead is the rehearsal itself — being asked, having to answer aloud, being pushed when you were vague — and a written transcript afterwards.
Interviewing in a Second Language
If the interview will be in a language that is not your first, set the topic's content language to that language and rehearse in it. The tutor answers only in that language and will not switch back when you hesitate, which is uncomfortable and is exactly the discomfort you are training for. You can read the explanations in your own language first by creating a second topic — understand the material in the language you think in, rehearse it in the language you will be judged in.
Technical Interviews
For a technical round, make the technical material the topic — the stack, the domain, the system you will be asked to reason about — and use the conversation to explain concepts out loud under questioning. It will not run a live coding environment or watch you write code. What it is good for is the part of a technical interview that is actually spoken: explaining a trade-off, defending a design choice, admitting what you do not know without falling apart.