# Interview practice built from your own resume and project history

The resume-based interview reads your own uploaded resume and asks about the actual client sites, freelance projects, or in-house work listed on it, rather than a generic portfolio question that could apply to anyone's site.

A web developer's resume is often more a list of shipped projects than job titles, several client sites, a redesign, a specific feature built for a former employer. This type questions from those exact items instead of an abstract version of them.

## When your resume is really a list of shipped work

Your resume lists three client sites you built as a freelancer, a redesign you led at a former agency, and a specific e-commerce feature you shipped. Upload it, and the questions that follow reference those specific lines, the redesign by name, what the e-commerce feature actually involved, rather than a generic prompt to walk through a project. That specificity matters because a hiring manager is usually forming their whole impression of your range from exactly that handful of shipped items, and a session built around them gets closer to how that conversation will actually go.

## What gets covered

Expect specific follow-ups on the actual work listed, a technical choice you made on a particular client site, what a redesign involved end to end, a tradeoff on a shipped feature you'd handle differently now. The resume library lets you keep more than one version, useful if you want a session built from a resume weighted toward client work versus one weighted toward in-house product experience. This differs from job-description practice, which reads a posting instead of your resume, and from the technical type, which hands you a fresh coding problem rather than asking about anything you've already shipped.

## What scoring weighs here

Scoring reflects how specifically and clearly you can talk through your own shipped work, not how polished the resume itself reads. A project story that lands on an actual decision, why one approach was chosen over another, scores better than one that stays at the level of a resume bullet restated out loud. Communication carries real weight here too, since explaining a client project clearly to someone who never saw the original brief is its own skill, separate from having built the thing well in the first place.

## Frequently asked questions

### Will it reference a specific client project by name?

Yes. Questions come from what's actually listed on your uploaded resume, not a generic portfolio-walkthrough prompt written for no particular project.

### Does it work if most of my experience is freelance rather than a full-time job?

Yes. It works from whatever real work is on your resume, freelance client sites included, which for many web developers make up most of the actual project history.

### Can I run this from a resume weighted toward a specific kind of project?

Yes. The resume library holds a master live resume plus a versioned library, so a session can pull from whichever version emphasizes the work you want to be asked about.

### How is this different from the technical interview type?

Technical hands you a fresh coding or debugging problem to solve live. Resume-based asks about work you've already shipped, listed on your own resume.

### What if a project on my resume was a team effort, not solo work?

That's worth naming directly. Being clear about your specific role and contribution on a team project tends to read better than describing shared work as if you built it alone.

## Related pages

- [Web developer interview questions](/interviews/web-developer)
- [Resume-based AI interviews](/features/resume-based-interviews)
- [Browse open roles](/jobs)

## Get questioned on your actual shipped work

Upload your resume and run a session built from your real client sites and projects, not a generic portfolio question.

Start practicing free: https://www.intervieux.ai/register · Hire with Intervieux: https://www.intervieux.ai/employers/signup