Practice the interview. Then read the interviewer's notes.
A live AI mock interview that follows up like a real interviewer — then shows you what they write down and never say: which answer had no result, which phrase sounded unsure, which claim you backed with proof.
Free 10-minute interview with a full report. No card needed.
Tell me about a time you made a slow part of a system faster.
I think we kind of1 moved the report generation into a background queue, and p95 load time went from 9 seconds to 1.42. Everyone was pretty happy with it.3
- 1Hedge + "we". Your own part is unclear. Say what you did.Ownership
- 2Concrete result. Numbers you can defend count as evidence.Impact
- 3Vague ending. What changed for users or the business?STAR: Result
What did you build yourself, and why a queue rather than caching the reports?
Pick what you're interviewing for
Each track sets the competencies, question style and difficulty. Or start blank and type any role and stack.
By role
A full interview for the job title.
- Software Engineer (SDE) Mid
- Frontend Developer Mid
- Backend Developer Mid
- Full Stack Developer Mid
- Data Scientist Mid
- Data Analyst Junior
- DevOps Engineer Mid
- Product Manager Mid
- Machine Learning Engineer Mid
- AI / LLM Engineer Mid
- Data Engineer Mid
- Engineering Manager Senior
- All 25 roles AI, cloud, design, business
By skill
Go deep on one language or topic.
By round
Rehearse the conversation, not the code.
How a session works
About 20–30 minutes from setup to report. End any time and you still get feedback on what was covered.
-
Set your target
Pick a role, level and stack. Add a job description or your resume if you want questions about your real projects.
-
Answer live
Speak or type. The interviewer follows up on thin answers, raises the difficulty when you're doing well and switches to code when it fits.
-
Read the notes
A report scores every competency, quotes the answers that cost you, and gives you a prep plan for the next session.
A report that quotes you, not a pat on the back
Every score links back to something you actually said.
-
Competency scores
Weighted to the role you picked, so a system design gap counts more for a senior backend role than for a frontend junior.
-
STAR check on every story
See which part of each behavioral answer was missing — usually the Result.
-
How you sounded
Filler words, hedging, "I" versus "we", and whether you cited real numbers — measured from your words, and compared between the first and second half of the interview.
-
A prep plan
The two or three things to practice next, and a skill graph that tracks them across sessions.
Competencies — sample report
STAR — "Tell me about a missed deadline"
How you sounded
It decides what to ask next, like a real interviewer
After every answer the interviewer picks one move. You'll feel the difference from a list of questions in the first five minutes.
- Follows upWhen an answer is vague or skips your own role.
- Raises the barWhen you're clearly comfortable, so you don't coast.
- Eases offWhen you're stuck, to find where your knowledge actually stops.
- Switches to codeOpens the editor for a coding question when the role calls for it.
- Sets a scenario"Your cache just went down" — to test judgment, not recall.
- Ends when coveredStops once every important competency has enough evidence, not at an arbitrary count.
Scores you can argue with
Most of each score comes from measurable things in your answer: structure, specifics, hedging, ownership language. The AI's opinion can move a score only a little, and never on its own. Run the same answer twice and you get the same result.
Confidence score weighting: measured language signals carry the majority; AI adjustment is limited to ±10 points.
Fix what they'll read before they meet you
The same evidence-first review for your profile. Run them and your interview starts asking about your real projects.
Resume review
ATS checks, bullet-by-bullet impact scoring and job-description match.
GitHub review
Profile and repository quality: READMEs, tests, activity and pinned work.
LinkedIn review
Headline, About and experience checked for specifics and consistency.
Portfolio review
First impression, project depth and technical health of your site.
Questions
What is an AI mock interview?
A practice interview run by an AI interviewer. It asks a question, listens to your answer, then decides what a real interviewer would do next — a follow-up, a harder or easier question, a coding task, or a new topic. At the end you get a scored report.
How is my answer scored?
Each answer is scored against the competencies your target role needs. Deterministic language analysis (hedging, filler words, ownership language, concrete numbers, STAR structure) carries most of the weight; the AI's judgment can only nudge a score within a bounded range, so results are consistent and explainable.
Can I practice for a specific role or language?
Yes. There are tracks for roles like Software Engineer, Frontend and Data Scientist, skills like Python, Java and System Design, and rounds like Behavioral and HR. You can also type any role and tech stack yourself.
Do I speak or type my answers?
Either. Voice works in browsers with speech recognition (Chrome and Edge work best). You can type at any point, and coding questions use an in-browser editor.
Will it use my resume?
If you add your resume, the interviewer asks about your actual projects and the report flags claims your answers didn't back up. It's optional.
Is it free?
Your first interview each month is free for up to 10 minutes, and you get its full report. Paid plans add full-length interviews, more of them, and the 360 report.