AI mock interviews for tech roles

Practice your next tech interview out loud.

An AI interviewer reads the job and your resume, asks you questions out loud, and follows up on what you say. Then you get a score and a stronger version of every answer.

Start your free interview

Your first two interviews are free. No card needed. Then from $1.27 per interview.

  1. Interviews
RL

Interviews

Senior Backend Engineer

73out of 100
Good performance

Strong on trade-offs, light on numbers

You explained your design choices clearly and handled follow-ups on queues with confidence. Your answers would land harder with measured results.

How you scored

Each area is the average of how your answers scored on it, from 1 to 5. That average becomes points from 0 to 100 (1 is 0, 3 is 50, 5 is 100), and your overall score is the average of those points.

  • Communication

    Clear and calm, even under follow-ups. You sometimes restarted sentences when the topic got technical.

  • Answer structure

    Good context and actions, but several answers stopped before the result.

  • Domain depth

    Solid command of queues, caching, and idempotency, with sensible trade-offs.

  • Evidence and impact

    Concrete examples, but impact was rarely measured. Bring the numbers.

  • Role fit

    Your backend work maps well to the role, with a gap in Kubernetes.

  • Overall score

    (80 + 65 + 85.0 + 60 + 75) ÷ 5 = 73

Your strengths

  • Clear reasoning about trade-offs
  • Calm under follow-up questions
  • Concrete examples from real systems

What to improve

Most important first.

  1. 1. Bring the numbers

    Metrics make your impact credible.

    How to practice

    Prepare one metric for each project on your resume.

  2. 2. Close every story

    Several answers ended before the result.

    How to practice

    Finish each answer with the outcome and what you learned.

Question by question

Open a question to see what worked and what a stronger answer covers.

1. Scaling the reporting API to ten times the traffic

Scores by area
Communication4/5
Answer structure4/5
Domain depth5/5
Evidence and impact3/5
Role fit4/5
What worked
You split reads from heavy work and moved reports to a queue.
What was missing
How you would measure success, like p95 latency before and after.
A stronger answer
Cache the read endpoints, move report generation to a queue, and track p95 latency so you know it worked.

2. Duplicate charges from webhook retries

Scores by area
Communication4/5
Answer structure3/5
Domain depth4/5
Evidence and impact3/5
Role fit4/5
What worked
You found the root cause quickly.
What was missing
The mechanism you used and the result.
A stronger answer
I added an idempotency key to each payment request, so a retried webhook could never charge twice. Duplicate charges went from about 40 a week to zero.

3. A disagreement in code review

Scores by area
Communication5/5
Answer structure4/5
Domain depthNot assessed
Evidence and impact4/5
Role fit4/5
What worked
You listened first, then proposed a test to settle it.
What was missing
What changed in how the team works afterwards.
A stronger answer
Close with the outcome: the team now adds a benchmark to every performance change.

How you spoke

You lean on ‘like’ when you start an answer, and you restart sentences when the topic gets technical.

  • I built a APII built an API
  • we had less incidentswe had fewer incidents
  • me and the tech lead decidedthe tech lead and I decided

Competencies for this role

  • Distributed systems

    Reasoned well about retries, queues, and failure modes.

    "We made every payment request carry an idempotency key."

  • API design

    Thought about versioning and how clients migrate.

  • Kubernetes

    Not assessed

    Not covered during the interview.

Job requirements

  • Distributed systems and message queues

    Demonstrated

    Explained retries, dead letters, and idempotent consumers.

  • 5+ years with Go or Java in production

    Partial

    Strong backend experience, mostly in PHP and Node.

  • Kubernetes in production

    Not shown

    It came up, but you gave no example.

How you used your CV

Highlighted well

  • Payment service migration at a fintech

Worth bringing up

  • Cutting infrastructure costs by 30%

Your practice plan

Exercises for your next practice session.

  1. Write down one metric for each of your three main projects.
  2. Practice the payments story ending with the result.
  3. Prepare a Kubernetes example, even a small one.

Generated by AI from your interview answers, the job description and your CV. Use it as practice guidance, not as a hiring decision.

Live preview. Click around.

From job post to feedback in three steps.

  1. 01

    Bring the job

    Paste any job description or pick one from the practice library. Your resume goes in once.

  2. 02

    Answer out loud

    Camera and mic on, up to twenty minutes, or thirty-five for system design. One question at a time, with follow-ups on what you say.

  3. 03

    Get your score

    A score out of 100, what each answer missed, and a stronger version to say next time.

It asks about what you actually said.

A rehearsed answer won’t carry you. Every follow-up comes from your last answer, the way a real interviewer digs into your story.

Practice the stage you are about to face.

Pick a stage and see the kind of questions you will get. What gets scored changes with it.

Interview stage

Questions you might hear

  • How do you find the cause of a slow endpoint in production?

  • Why did you pick Postgres over MongoDB there?

  • Tell me about the hardest bug you have fixed.

Practice in the language of your interview.

Interviews run in English, Portuguese, Spanish, French, or German. Whatever the language, your report shows how you spoke: the filler words you lean on, and each slip next to the corrected version. It stays apart from your technical score.

  • English
  • Portuguese (Brazil)
  • Spanish
  • French
  • German

Questions, before you start.

Are the first two interviews really free?

Yes. Your first two interviews are free, with no card needed, and a system design interview counts as two. You only pay if you want to keep practicing.

Can I practice technical interviews?

Yes. The technical stage covers the stack in the job description and the trade-offs behind the projects on your resume. System design has its own stage, where you draw the architecture on a whiteboard while you talk. There’s no live coding.

Which languages can I practice in?

English, Portuguese, Spanish, French, or German. In every language, your report shows how you spoke: filler words, hesitations, and grammar slips with the corrected version.

What happens after the interview?

You get a score out of 100 and a full report: every answer graded with a stronger version, how you matched the job requirements, how you used your resume, how you spoke, and a practice plan. It shows up in the app and in your inbox.

What do I need?

A browser, a camera, and a microphone. Both are required. The interview won’t start without them, because the real one wouldn’t either.

Is my video recorded?

No. The camera is there so you practice being seen, like in the real room. Nothing from it is recorded or stored.

How much does it cost after the free ones?

From $1.27 per interview. Plans are $9 a month for 6 interviews or $19 a month for 15, and single interviews are $2.50. Monthly plans cancel anytime, and interviews in your balance never expire.

Your first two interviews are on us.

No card, no commitment. Take it today and see where you stand before the interview that counts.

Start your free interview

Your first two interviews are free. No card needed. Then from $1.27 per interview.