Getting asked about the project you listed two lines down
Your resume mentions a groundwater monitoring project you led at a former employer, three sentences describing scope and outcome that you wrote in under a minute a year ago. The interview doesn't skim past it. It asks how many sampling locations were involved, what you did when one of them came back with an anomalous reading, and what changed about your approach on the next site because of what you learned there.
If your resume also lists a permitting case you supported, expect a follow-up about what specifically you contributed versus what the broader team handled, since resumes tend to compress a group effort into first-person language and the interview is checking whether that compression holds up under a direct question. This isn't a hypothetical field scenario. It's your own claimed work, examined.
What the interview pulls from your resume specifically
The session reads whichever resume version you have set as your current live resume, so a version built for a consulting posting versus a general master version can produce a meaningfully different interview, since the emphasis differs between them.
Expect follow-up on named projects, listed certifications, and specific tools or methods you claimed familiarity with, a stated water quality model, a named regulatory framework you cited experience with. If a listed project sounds unusually senior for the amount of experience described elsewhere on the resume, the interview is likely to probe that gap directly rather than let it pass.
The goal is catching the difference between what a resume implies and what you can actually explain in detail.
Scoring
How scoring reflects the gap between claim and detail
Technical carries real weight here, and the written reasoning behind the score often turns on whether your explanation of a listed project matched the specificity the resume implied, not just whether you could describe the project's general shape.
A vague answer to a direct follow-up about your own claimed work reads worse in this session than it would in a general interview, since there's no ambiguity about whether the topic was fair game: you wrote it yourself.
Calibration floors and caps apply the same way across dimensions, and Cultural Fit and Behavioral pick up signal too if your resume lists team leadership or client-facing work that the interview then asks you to walk through in more depth.
Frequently asked questions
Which resume does the interview read if I have more than one version?
It reads whichever version you have set as your current live resume in your library. If you've built a version for a specific type of posting, that version's emphasis is what the interview draws its questions from, so keep the one you want questioned set as current before starting.
Will it ask about a project from years ago that I barely remember writing about?
It's likely to, especially if the project is described in specific terms on your resume. Reviewing your own resume closely before the session, not just your recent work, is worth doing since the interview treats every listed claim as fair ground.
What if I exaggerated my role on a team project on my resume?
A direct follow-up asking exactly what you personally did, versus what the broader team handled, is a common way this session tests that gap. It's better to find that gap in practice than in a real interview where the stakes are higher.
Does this replace practicing against a specific job posting?
No, they test different things. Resume-based checks whether you can defend your own claimed history in detail, while the job-description type builds questions from a posting's requirements. Running both covers more ground than either alone.
Related pages
Practice defending the projects you already claimed
Run a resume-based AI interview to work through follow-up questions on your own listed field studies and projects before a real interviewer asks.