StackScholar

Mock Interview

Three ways to practise: an AI interviewer that grades your written answers and pushes back, a full design session with a six-phase 45-minute timer, and a rapid drill over all 71 questions. All of them work best out loud.

New

AI interviewer

Nobody can practise articulating answers alone. Type what you would say - the interviewer grades it against the model answer, tells you what you missed, and follows up until you run out of depth.

Track

Difficulty

71 in pool

An interviewer who talks back

You get a real question from the bank. Type the answer you would say out loud - the AI grades it against the model answer, tells you exactly what you missed, and follows up the way an interviewer would.

Your typed answers go to the AI grader and are not stored anywhere. The verdict feeds your on-device review queue only if you choose.

Practise solo

Your prompt

Design a URL shortener like bit.ly

Scale: 100M new URLs/day, 100:1 read:write, global

Before you start

  • Get paper or a whiteboard. Do not type - you will not be typing in the real thing.
  • Speak out loud, the whole time. Record yourself if you can.
  • The timer moves through six phases. Let it push you; do not pause it when you fall behind.

Getting real value out of a mock

  • Record yourself. Play it back at 1.5×. You will hear the filler, the circling, and the decisions you never actually justified.
  • Do not pause the timer when you fall behind. Falling behind is the finding. Note where it happened and study that.
  • Draw on paper, not a screen. You will be drawing on a whiteboard or a shared canvas, and the physical constraint changes how you lay a design out.
  • Start mocks in week 3, not week 10. Mocks surface communication gaps that solo study cannot. Early feedback tells you what to prioritise.