Mock Interviews
AI mock interviews for software engineers: pick from 39 roles and 16 rounds, answer in writing or by voice, and get a 0–10 report on every round.
How do CodeKairo's mock interviews work?
Three choices make an interview — the role and round you are preparing for (six one-click presets, or any of 39 roles and 16 rounds, or your own), whether you type or speak, and the level and format: seniority from intern to lead, difficulty, and up to eight focus areas — with style and stack optional. A spoken round also picks its interviewer, one of eight voices you can hear before choosing. It runs as a timed interview: a written round of seven questions answered one at a time, with a starter stub for coding rounds, or a spoken round of 10, 20 or 30 minutes over your microphone in English, Hindi or Hinglish. Every round ends in a report scoring each answer 0–10 with a readiness band, strengths, weaknesses and next steps. Every setup you start is kept for one-click reruns. From 1 January 2027, the free plan allows two rounds a week, roadmap chests add bonus rounds, and paid plans raise the limit. Building needs no account; running a round needs a free one.
How it works
- Pick the round. Choose what you are preparing for, type or talk, then seniority, difficulty and any focus areas; for a spoken round, the length and the interviewer's voice. Style and stack are under More options. Start saves the setup — up to thirty per account — so it is one click to rerun.
- Run the round. Written: seven questions, one at a time, code in the editor or prose in the answer box, dictation if you prefer to speak. Voice: a live conversation with follow-ups, in the language you answer in.
- Read the report. An overall score out of 10, a readiness band, per-topic averages, strengths, weaknesses, next steps, and every question with your answer, its score and what was missed.
- Rerun before the day. The history page keeps every round with its score and trend; the same setup run again shows whether the weak topics moved.
Who it is for
Anyone with an interview in the diary — a fresher rehearsing a campus round, an engineer switching stacks, a product manager or analyst whose loop is not a coding loop. The roles and rounds cover all of them, and the report says what to fix before the real one.