Interaction Design Portfolios: Key Facts

An interaction design portfolio is a curated collection of your projects that demonstrates how you approach user-centered problems, make design decisions, and create usable digital products. It answers one core question for hiring managers: Can this person improve the way people interact with technology? Unlike a graphic design portfolio that focuses on visual output, an interaction design portfolio must show process, reasoning, and measurable outcomes.

Formula

Portfolio readiness score = min(100, (projects × 15) + (years × 5))

This is a rough heuristic, not a real industry metric. It weighs the number of case studies (each worth 15 points) and years of professional experience (5 points per year) to give you a quick sense of whether your portfolio has enough substance. The formula caps at 100 because that is the practical maximum for a self-assessment. The recommended projects output simply clamps your current count between 3 and 6, which is the typical range hiring managers expect.

Worked Example

Using the default values: 5 projects and 3 years of experience.

1. Projects contribution: 5 × 15 = 75
2. Experience contribution: 3 × 5 = 15
3. Total: 75 + 15 = 90
4. Capped at 100, so score = 90

The calculator shows a score of 90/100, which suggests a solid portfolio. The recommended projects output stays at 5 because it is already within the 3–6 range.

What Interaction Design Portfolios Actually Show

Interaction design (IxD) is the practice of designing the dialogue between a user and a system: taps, swipes, clicks, voice commands, and the feedback that follows. A portfolio in this field must prove you can handle that dialogue. The key facts recruiters look for are:

• Process over pixels – how you went from a vague problem to a concrete solution matters more than polished mockups.
• User research evidence – interview quotes, survey data, or usability test findings that show you didn’t guess.
• Iteration – show at least one major pivot or refinement based on feedback, with before/after screenshots.
• Scope and constraints – mention timeframes, team size, and technical limitations you worked within.
• Outcome metrics – even a simple “task success rate went from 61% to 84%� is powerful.

A common misconception is that an interaction design portfolio is just a collection of app screens. In reality, the screens are the output; the thinking is the product. A case study that explains why you chose a bottom navigation bar over a hamburger menu, backed by a card-sorting exercise, is far more convincing than a beautiful but unexplained flow.

How Many Projects and What Types?

Most hiring managers and design educators recommend 3 to 6 in-depth case studies. Fewer than 3 makes it hard to show range; more than 6 risks diluting quality. The projects should demonstrate variety:

• One mobile app (iOS or Android) with a complete flow
• One responsive web application or dashboard
• One project with a novel interaction (voice, gesture, AR, or wearable)
• One project where you worked within a real technical constraint (legacy code, API limits, accessibility standards)

If you are a junior, you can include a well-executed student project or a redesign of an existing app—just be honest about the context. If you are senior, replace one case study with a project where you led the design process or mentored others, because that shows leadership.

Structure of a Strong Case Study

Each case study should follow a clear narrative arc. A proven structure is:

1. Problem statement – one paragraph on the user need and business goal.
2. My role – what you personally did, not the team.
3. Research – methods used and key insights (with artifacts like affinity diagrams or journey maps).
4. Ideation – sketches, wireframes, or storyboards that show exploration.
5. Prototype and test – what you built, what you tested, and what changed.
6. Final design – high-fidelity screens or a clickable prototype.
7. Outcome and reflection – metrics, what you learned, and what you would do differently.

Keep each case study to 500–800 words. Use annotated screenshots rather than long paragraphs. A video of a user interacting with your prototype is often more effective than a static image.

Common Mistakes and How to Avoid Them

Many portfolios fail for avoidable reasons. The most frequent problems are:

• Showing only final screens – without process, it reads as decoration, not design.
• Hiding the mess – if you only show the clean path, reviewers suspect you skipped the hard parts.
• Too much text – walls of text get skimmed; use visuals and bullet points.
• Ignoring accessibility – not mentioning contrast ratios, touch target sizes, or screen reader support is a red flag for IxD roles.
• No measurable outcome – “users liked it� is weak; “task completion rose 22%� is strong.

Another subtle mistake is overusing buzzwords like “intuitive� or “seamless� without evidence. Instead of saying “I made it intuitive,� say “I reduced the onboarding steps from five to three, and 90% of test users finished without help.�

How to Choose What to Include

Quality beats quantity. For each project you consider, ask:

• Does it show my best thinking, or just my best visuals?
• Does it involve a real user, a real constraint, or a real outcome?
• Can I explain the decisions clearly in under a minute?
• Does it represent the type of work I want to do next?

If a project fails any of these, cut it. Recruiters spend an average of 30–60 seconds on an initial portfolio scan, so your first case study must be your strongest. Order them with the most impressive or most relevant project first, not chronologically.

Digital Format and Presentation

Your portfolio can be a custom website, a template on Squarespace or Webflow, or a PDF. The key facts are:

• Load speed matters – compress images; a portfolio that lags will be closed.
• Navigation is part of the design – the portfolio itself is an interaction design artifact; make it easy to browse.
• Mobile responsive – many reviewers will open it on a phone.
• Contact info visible – one click from any page.
• PDF for applications – keep it under 10 MB and use a clear filename like “JaneDoe_IxD_Portfolio.pdf�.

A common question is whether to include personal projects. Yes, if they show skills relevant to the job. A personal project that explores a new interaction pattern (e.g., a gesture-based timer for runners) can be more memorable than a client project with strict branding.

Frequently Asked Questions

Should I include failed projects or ones that never shipped?

Yes, if you can articulate what you learned. A project that was cancelled due to technical constraints still shows your ability to navigate reality. The key is to frame it as a learning experience: state the problem, what you built, why it stopped, and what you would do differently. This honesty often impresses reviewers more than a flawless fake project.

How long should a case study be?

Aim for 500–800 words per case study, plus visuals. That is enough to explain context, process, and outcome without losing the reader. If you have more to say, put it in an appendix or a separate “deep dive� page. Remember that reviewers skim; use headers, bold key findings, and annotated images to make the story scannable.

Do I need to show coding or prototyping skills?

Not necessarily, but it helps. Interaction designers often use Figma, Framer, or ProtoPie to create high-fidelity prototypes. Basic HTML/CSS is a plus but not required for most IxD roles. What matters is that your prototypes actually demonstrate interaction—clickable flows, micro-interactions, or state changes—not just static screens.

How do I show accessibility in my portfolio?

Mention specific choices: contrast ratios that meet WCAG AA, touch targets of at least 44×44 pixels, and keyboard navigation support. If you tested with screen readers, include a quote from that test. Even one paragraph on accessibility per case study signals that you design for all users, which is a core IxD principle.

Should I use a custom domain or a free portfolio site?

A custom domain (e.g., yourname.com) looks more professional and is easy to set up for about $10–15 per year. Free sites like Behance or Dribbble are fine for sharing work, but they do not allow the same level of narrative control. If you are applying to agencies or tech companies, a dedicated site is strongly recommended.

How often should I update my portfolio?

Update it whenever you complete a significant project or learn a new skill, but at minimum once a year. Remove outdated work that no longer reflects your level. Keep a “recent work� section fresh, and archive older projects rather than deleting them entirely—you never know when a past project might be relevant for a new role.

Related

• Xiaomi 17T vs 17T Pro: Worth the Extra Cost?
• Ctrl Alt Del Remote Desktop: Fixes & How-To
• Cross-Generational Workplace Gaming: Measurement Plan

in t | Projects shown | count | 5 | 1 | 10
in y | Years of experience | years | 3 | 0 | 40
out score | Portfolio readiness score | /100 | min(100, (t * 15) + (y * 5)) | 0
out projects_needed | Recommended projects | count | max(3, min(6, t)) | 0