When your resume lists actual studies, not just roles
Your resume names a checkout redesign you led, a specific usability study you ran on an onboarding flow, and an accessibility audit you completed at a former job. Upload it, and the questions that follow reference those specific lines, what the onboarding study actually found, what changed after the accessibility audit, rather than a generic prompt to describe a usability test you've run.
That specificity matters because a hiring manager reading that same resume is usually forming their whole impression of your rigor from exactly those named projects.
What gets covered
Expect specific follow-ups on the actual work listed, a methodology choice on a named study, what a redesign changed and why, a finding from an audit that shaped a later decision. The resume library lets you keep more than one version, useful if you want a session weighted toward research-heavy projects versus more visual or interaction-design work.
This differs from job-description practice, which reads a posting instead of your resume, and from the technical type, which hands you a fresh logic problem rather than asking about anything you've already shipped. It also differs from general practice, which stays at the level of process questions regardless of what's actually on the page.
Scoring
What scoring weighs here
Scoring reflects how specifically and clearly you can talk through your own studies and shipped projects, not how polished the resume itself reads. A study explanation that lands on an actual methodology decision and what it revealed scores better than one that stays at the level of a resume bullet restated out loud.
Communication carries real weight too, since explaining a specific finding clearly to someone who wasn't in the room for the study is a distinct skill from having run the study well in the first place.
Frequently asked questions
Will it reference a specific study or project by name?
Yes. Questions come from what's actually listed on your uploaded resume, not a generic usability-testing prompt written for no particular project.
Does it work if my resume leans more visual than research-heavy?
Yes. It works from whatever real work is on your resume, so a resume weighted toward visual and interaction design gets questioned on that work specifically rather than being pushed toward research it doesn't reflect.
Can I run this from a resume version built for a research-focused role?
Yes. The resume library holds a master live resume plus a versioned library, so a session can pull from whichever version emphasizes the projects you want to be asked about.
How is this different from the comprehensive interview type?
Comprehensive works through a hypothetical research scenario end to end. Resume-based questions you on studies and projects you've actually already shipped.
Does it work if I only have one strong project on my resume?
Yes. Even a single well-documented study or redesign gives the session enough to build specific, real follow-up questions from, useful for a candidate earlier in their career without a long list of shipped work yet.
Related pages
Get questioned on your actual studies and projects
Upload your resume and run a session built from your real research and shipped work, not a generic usability-testing question.