How to Practice a Mock Interview Based on Your Resume (Free)

You can practice a mock interview based on your resume for free in three ways: with a friend who interviews you from it, with a general AI assistant you prompt with it, or with a resume-based mock interview tool such as Devana, whose Free plan includes 3 interviews a month of up to 20 minutes, any of which can be built from your resume. Whichever you choose, a useful session asks about specific lines, follows up at least twice on each, and ends with a review of where you hesitated.

What a useful resume mock interview does

• It quotes your resume. "Tell me about yourself" is not a resume question; "at your last job you moved payouts to a queue, why?" is.
• It follows up. The first answer is the rehearsed one. The second and third follow-ups find the gaps.
• It runs like the real thing: out loud, one question at a time, with a clock.
• It covers the round you will face: behavioral stories, coding problems close to your stack, or a design close to what you have built.
• It leaves a record you can review afterwards: notes, a transcript or a scored report.

What a follow-up sounds like

One exchange, written for this guide, on a resume line that reads "Reduced cloud costs by 30% by right-sizing services":

• Interviewer: "You reduced cloud costs by 30%. What did you change?"
• First answer: "We looked at our services and right-sized a lot of them, and the bill came down by about 30%."
• Follow-up: "Which services, and how did you decide what size was right?"
• Better answer: "The three biggest: our API, the search indexer and a batch worker. I pulled two weeks of CPU and memory use per service and found the API peaked at about 15% CPU, so I halved its instance size behind the autoscaler. The 30% is the monthly bill for those three, the month before against the month after. The batch worker I'd do differently: I shrank it too far and we rolled half of that back."

The second answer is longer, but every sentence carries something an interviewer can write down: what changed, how it was decided, how it was measured, and a mistake owned. That is what the second and third follow-ups are for, and why a practice session without them teaches the wrong habit.

Option 1: a friend with a script

The cheapest option, and a good one if your friend is an engineer. Give them your resume and this script:

1. Pick the three lines that look most impressive and the one that looks least clear.
2. For each, ask: what was the problem, what did you personally do, and how do you know it worked?
3. Ask "why?" about one decision, and "what would you do differently?"
4. Ask about anything unusual: a gap, a short stint, a change of field.
5. Write down every moment the candidate hesitated, said "we" instead of "I", or gave a number without saying where it came from.

The limits: friends are kind, rarely push past the second follow-up, and are hard to book every few days. Save them for a final run-through rather than every repetition.

Option 2: a general AI assistant

A general AI assistant in voice mode can play the interviewer. Before you share anything, remove your phone number, email and address from the copy you paste, and check what the provider does with what you upload. Then start from a prompt like this:

You are interviewing me for a [role] position. Here is my resume:
[paste it, without your phone number, email or address]

Ask me one question at a time about specific lines on it. After each
answer, ask at least two follow-up questions that test what I personally
did, how I measured the result and why I made the decisions I did. Do not
praise my answers or answer for me. After 20 minutes, list my three
weakest answers and say why each one was weak.

The limits: general assistants tend to agree with you and accept answers a real interviewer would push back on, nothing keeps time unless you do, they do not run your code, and the review at the end is only as good as your prompt.

Option 3: Devana's resume-based round, step by step

1. Open the interview setup and choose Resume-Based. You can start before you have an account.
2. Upload your resume: PDF, DOCX or TXT, up to 5 MB. It needs real text in it, so export a text-based PDF rather than a scan. If you are not signed in yet, the file waits in your browser and is read as soon as you sign in.
3. Choose the focus. Behavioral asks three questions, each naming a real role or project from your resume and aimed at a different competency. Coding gives you two problems framed in the domain of your work, in Python, JavaScript, TypeScript, Java or C++. System design picks the design problem closest to systems you have built.
4. Pick the difficulty and the interviewer's style, from friendly to strict.
5. Talk it through. Josh, the AI interviewer, opens by asking for your background, connects each question to your resume, and if an answer does not match what the resume says, or stays vague about something it lists, he asks about it directly.
6. Read the report. The round is scored out of 100 like any round of its type, with a list of what raised and lowered the score.

The file is read in memory and its text goes to the AI model that writes your questions; neither the file nor the text is stored, though the interview's scores are saved to your account. The Free plan includes 3 interviews a month of up to 20 minutes; the Sprint Pass and Pro allow up to 60 minutes, or 30 for a behavioral round. The resume-based mock interview page shows examples of the questions it writes.

No partner and no tool: ten minutes alone

Pick one line from your resume, start a voice recorder, and answer three questions about it out loud: what did you do, how do you know it worked, and what would you change. Play it back once. If you said "we" more than "I", or never said where a number came from, you have found this week's fix, and it took ten minutes.

A three-session plan for one free month

• Session 1, behavioral. Its job is to find the lines that do not survive follow-ups. Afterwards, list every question where you hesitated and the resume line it came from.
• Between sessions, fix them. Rewrite the bullet, or prepare the story behind it. How to prepare for interview questions about your resume has a one-page template for each project.
• Session 2, the round you face next. Coding if your loop is coding-heavy, system design if you are senior; both are built from your resume.
• Session 3, behavioral again, on the rewritten resume, to check the fixes held.

Three sessions with a rewrite after each beat ten with nothing changed in between. If you have more time than that, alternate resume rounds with standard coding and behavioral rounds, which cover the questions that do not depend on your background.

How to review a session

The score matters less than the moments behind it. After each session:

1. For each question, write down the resume line it came from and one sentence on what went wrong: too long, no "I", no number, no decision.
2. Sort what you found into resume problems (the line claims more than you can explain) and story problems (the line is fine, the telling is not). The first are fixed in the document, the second out loud.
3. Change one habit for the next session, not five. How to read mock interview feedback goes through a fuller review.

Mistakes that waste a practice session

• Reciting memorized answers. The follow-ups will break them; know the stories, not the sentences.
• Talking for five minutes. Aim for one to two, and let the interviewer pick the next thread.
• Defending a line you should rewrite. If it fell apart twice in practice, change the line.
• Only ever practicing behavioral. If your loop is mostly coding, practice the coding round built from your resume too.
• Practicing once, the night before. The point is to find what breaks while there is still time to fix it.

To know what to expect in the room, fifteen resume-based interview questions for software engineers, with example answers shows the common ones and what each is testing. And if the resume is not getting you interviews yet, start with why resumes get rejected in 6 seconds.

Frequently asked questions