How to Prepare a Portfolio Walkthrough for an Interview

Your portfolio walkthrough needs more than a sequence of finished images. Prepare to explain what each sample shows, which parts you did, and why you made a particular choice. Follow the interviewer's brief first: this guide offers a rehearsal structure, not a rule about how every employer interviews.

CareerOneStop describes a portfolio as a collection of work samples showing your skills and qualifications. Here, the focus is the conversation around a sample, not building a portfolio website or choosing a design template.

Confirm the brief before choosing samples

Ask whether a walkthrough is expected, how long you have, and whether the interviewer wants a particular project or format. Check whether you may share your screen or bring a document. Do not assume you should send files in advance.

You can adapt this request: "Would you like me to prepare a portfolio walkthrough? If so, how much time should I allow, and is there a project or skill you would like me to focus on?"

Choose what to show

Choose a small set of samples that covers the relevant skills and fits the time you have. For each one, check:

• Does it relate to something the job description asks for?
• Can you explain every part you show?
• Can you say which parts were yours and which were not?
• Are you permitted to share it?
• Is its context clear: paid work, course project, personal exercise or volunteer project?
• Could you explain it if the file failed to open?

A course project, personal exercise or volunteer project can be used as evidence of what you have done. Label its context clearly. Do not present an exercise as paid client work. If you have no sample you may share, say so and ask whether you can describe your approach to a relevant task instead.

Build a one-page walkthrough card

This card links your explanation to a piece of work you are showing, rather than a general interview story. For each selected sample, write short notes under these six prompts:

• Purpose: What problem or task were you working on?
• Context: Who was it for, and what constraints mattered?
• Contribution: What did you personally do? What did others do?
• Decision: Which choice can you explain? If you considered an alternative, what was it?
• Evidence: What does the sample actually demonstrate? Which result, if any, can you substantiate?
• Reflection: What would you change or investigate next?

Point to something visible when you explain a decision. For a spreadsheet, that might be a formula or validation check; for a design, a layout choice; for writing, a revision that addresses the brief. These are suggestions, not requirements for every role.

Keep three things apart when you speak:

• Contribution: what you personally did.
• Output: what was produced.
• Outcome: what changed afterwards. Claim an outcome only if you can substantiate it.

Completing a prototype does not establish that customers used it. If you have no adoption or performance data, say so. Do not add a percentage to make the story sound stronger.

Practise a short opening and a deeper explanation

Prepare a brief overview, then a longer version that fits the time you were given. Leave room for questions rather than filling the whole slot with a memorised script.

Fictional illustration, not a real candidate or project: A learner built a sample event-registration spreadsheet using invented entries. They might say: "This was a personal exercise, not a client project. I built the input fields, added checks for missing entries and wrote short instructions. I chose a simple layout so I could explain how each field was used. I tested it with invented records, but I have not tested it with an event team. My next step would be to ask someone unfamiliar with it to try the instructions."

Every detail in that illustration is fictional. Use only your own true experience in an interview. The useful structure is the distinction between what was built, what was tested and what remains unknown.

Rehearse follow-up questions such as "Why this approach?", "What was your part?" and "What did not work?" If you cannot remember a detail, acknowledge the limit instead of improvising a result.

Check what the interviewer will see

Use only material you have permission to share. If permission is unclear, choose another sample or explain your approach without showing it.

Open the exact file or link you intend to use. Check text size, navigation and access permissions without making a private folder public. Close unrelated tabs and notifications before screen sharing. If allowed, keep an offline copy of material you are authorised to show, and practise a spoken explanation in case the file will not open.

Finish with an honest link to the role

Close by naming the relevant skill the sample demonstrates and the limit of that evidence. For example, a practice exercise may show how you organise information; it does not prove experience managing a client's live system.

Before the interview, check that you can explain the purpose, your contribution, one decision and the evidence without reading every sentence. Our job interview preparation checklist can help you organise the wider preparation. A clear walkthrough makes your work easier to discuss; it cannot guarantee an offer.