How Designers Can Update Their Portfolio for AI-Adjacent Roles

A lot of designers are curious about AI-adjacent roles, but many get stuck on the same question: what should my portfolio actually look like if I want to make that pivot?

If you're coming from product design, visual design, brand, UX, or research, the good news is that you usually do not need to start over. In most cases, you need to reframe your experience so hiring teams can quickly see how your skills transfer into newer roles.

This matters because AI-adjacent design jobs often sound more technical than they really are. Teams still need people who can simplify workflows, improve trust, shape user behavior, and make complex systems usable. That's already familiar territory for many designers.

If you're still exploring where your background fits, start with our guide to AI jobs for designers. This article focuses on the next step: making your portfolio and interview story match the roles you want.

What hiring teams want to see

For AI-adjacent design roles, employers usually care less about whether you've built a model yourself and more about whether you can design around ambiguity.

They want evidence that you can:

turn messy problems into clear user flows
work with technical partners without getting lost in jargon
design for trust, accuracy, and edge cases
improve adoption of new tools or workflows
explain tradeoffs clearly

That means your portfolio should emphasize decision-making, not just polished screens.

A strong portfolio for this kind of pivot often shows:

how you framed the problem
what constraints existed
how you collaborated with PMs, engineers, researchers, or data teams
what changed because of your work
what you learned from uncertainty or imperfect information

The biggest portfolio mistake designers make

The most common mistake is presenting work exactly the same way you would for a traditional product design role.

That usually means:

too much emphasis on final UI
not enough explanation of system behavior
little discussion of risk, trust, or failure states
weak articulation of business impact

For AI-adjacent roles, hiring managers often want to know how you think when the product is not fully predictable.

For example, if you worked on search, recommendations, onboarding, automation, internal tools, content systems, or workflow optimization, you may already have relevant material. You just need to highlight the parts that map to AI-era product problems.

How to reposition existing case studies

You do not need every case study to be about AI.

Instead, choose 2 to 4 projects that demonstrate adjacent strengths and rewrite them with a sharper lens.

1. Lead with the problem, not the deliverable

Instead of opening with "I redesigned the dashboard," open with the underlying challenge.

Examples:

users didn't trust the output
teams couldn't interpret recommendations
a workflow had too many manual steps
important information was buried or inconsistent
adoption was low because the tool felt confusing

This framing makes your work feel more strategic and more relevant to AI-adjacent teams.

2. Show how you handled ambiguity

AI-adjacent products often involve incomplete requirements, changing capabilities, and unclear user expectations.

If you've worked through uncertainty before, say so directly.

You can describe:

how you tested assumptions
how you narrowed scope
how you prioritized what mattered most
how you balanced speed with quality

That kind of judgment is valuable even if the project itself was not branded as AI.

3. Add trust and edge cases

Many designers under-explain what happens when a system is wrong, unclear, or inconsistent.

If relevant, include:

error states
confidence indicators
fallback paths
review or approval steps
ways users could verify outputs

These details signal maturity. They show you think beyond the happy path.

4. Quantify outcomes where possible

Even simple metrics help.

Examples:

reduced time to complete a task
increased adoption or engagement
fewer support tickets
improved conversion or retention
faster internal operations

If you don't have exact numbers, use directional outcomes carefully and honestly. Don't invent precision.

What to include if you have no direct AI project experience

That's normal.

Most designers making this pivot are not coming from a company where they owned a dedicated AI feature set. You can still build a credible portfolio by emphasizing adjacent experience.

Good source material includes projects involving:

search and discovery
recommendations or personalization
workflow automation
data-heavy interfaces
internal tools
complex onboarding
content moderation or review systems
experimentation and iteration under uncertainty

You can also create one thoughtful speculative case study, but only if it's grounded in a realistic problem. A weak concept project won't help much. A strong one can show how you think.

If you go this route, keep it practical:

pick a narrow user problem
define clear constraints
show where the system could fail
explain what the human should still control
avoid flashy mockups without reasoning

How to talk about your work in interviews

Your portfolio gets attention, but your interview story closes the gap.

For AI-adjacent roles, prepare concise answers to questions like:

How do you design for trust?
How do you handle unclear requirements?
How do you work with technical stakeholders?
How do you evaluate whether a workflow is actually helping users?
How do you decide when automation should stop and a human should step in?

You do not need to sound like an ML engineer. You do need to sound comfortable operating in a changing environment.

A good answer often includes:

the user problem
the constraint or uncertainty
your approach
the tradeoff you made
the result

That structure works especially well for designers trying to pivot into adjacent roles without overselling technical depth.

Roles this portfolio strategy can support

This approach can help if you're targeting roles such as:

product designer on AI-enabled products
conversation designer
UX designer for internal AI tools
design strategist for automation workflows
content designer for AI experiences
researcher focused on trust, usability, or human-AI interaction

Not every company will use the same titles, which is why it's useful to optimize for the underlying problems rather than the label alone.

A simple portfolio checklist

Before you apply, review your portfolio against this checklist:

Does the first sentence of each case study explain the real problem?
Did you show ambiguity, constraints, or tradeoffs?
Did you explain collaboration with technical partners?
Did you include trust, review, or failure-state thinking where relevant?
Did you connect the work to an outcome?
Would a hiring manager understand why this project matters for AI-adjacent work?

If the answer is no on several of these, you probably don't need new projects. You likely need better framing.

Final thought

The best portfolio for an AI-adjacent design pivot is usually not the most futuristic one. It's the one that makes your existing strengths legible to the right hiring team.

If you can show that you solve messy problems, design for trust, and help users navigate complexity, you're already closer to these roles than you might think.

And if you're still deciding which direction fits best, take the career pivot assessment to compare paths based on your current background and goals.