Designer Portfolio Tips for AI-Adjacent Roles

How to Position Your Design Portfolio for AI-Adjacent Roles

If you're a product designer, UX designer, visual designer, or researcher trying to pivot, your portfolio usually matters more than your resume. That's especially true for AI-adjacent roles.

Hiring managers are often not looking for someone who can train models from scratch. They're looking for designers who can make AI products usable, trustworthy, and valuable for real people. That means your portfolio has to show more than polished screens. It has to show judgment.

If you're exploring a broader career change first, start with our designers pivot guide. If you're specifically looking at where AI is creating demand, our post on AI jobs for designers is a good companion to this one.

What counts as an AI-adjacent design role?

AI-adjacent roles are jobs where you work on products, workflows, or systems shaped by AI without needing to be an ML engineer.

For designers, that often includes:

• Product designer for AI features
• UX designer for copilots, assistants, or search experiences
• Conversation designer
• Design systems work for AI product patterns
• UX researcher focused on trust, explainability, or human-AI interaction
• Service designer for AI-enabled internal tools
• Content designer for prompts, guidance, and error states

These roles usually reward designers who can simplify ambiguity, design for edge cases, and help users understand what the system is doing.

The biggest portfolio mistake designers make

Most designers present AI-related work the same way they present any other feature launch: problem, wireframes, final UI, outcome.

That structure is still useful, but it misses the questions hiring teams actually have:

• How did you handle uncertainty in the system output?
• How did you design for mistakes, hallucinations, or low-confidence results?
• How did you help users build trust without overpromising?
• How did you decide when AI should act automatically versus ask for confirmation?
• How did you measure whether the feature was genuinely useful?

If your portfolio doesn't answer those questions, your work can look visually strong but strategically shallow.

What hiring managers want to see instead

For AI-adjacent design roles, strong portfolios usually show four things.

1. Clear product thinking

Show that you understand the user problem before you talk about the interface.

Good signals include:

• Why AI was the right tool for the problem
• Why a non-AI workflow wasn't enough
• What user behavior or business constraint shaped the solution
• What tradeoffs you made between speed, accuracy, and control

2. Comfort with ambiguity

AI features rarely behave the same way every time. Your case study should show how you designed around that.

Examples:

• Fallback states when output quality is weak
• Ways users can edit, retry, or reject suggestions
• Confidence indicators or explanation patterns
• Guardrails for sensitive or high-risk actions

3. Collaboration with technical teams

You do not need to be an engineer, but you do need to show that you can work with engineers, PMs, data teams, or researchers.

Mention things like:

• Constraints from model latency or context windows
• Data quality limitations
• Evaluation criteria used by the team
• How prototyping changed after technical feasibility discussions

4. Evidence of outcomes

Outcomes don't have to be dramatic, but they should be concrete.

Useful examples:

• Reduced time to complete a task
• Increased adoption of a new workflow
• Improved user trust or comprehension
• Fewer support tickets or escalations
• Better task success in usability testing

How to rewrite an existing case study for AI-adjacent roles

You do not need to have worked at an AI startup to make your portfolio relevant.

A lot of designers already have case studies that can be reframed around adjacent skills. For example:

• Search, recommendations, or personalization work can demonstrate ranking, relevance, and user control
• Complex B2B workflows can demonstrate information architecture and decision support
• Automation features can demonstrate trust, oversight, and exception handling
• Onboarding or education flows can demonstrate how you explain unfamiliar systems

A simple rewrite framework:

1. Reintroduce the problem in terms of uncertainty or decision support
2. Highlight where users needed transparency, control, or feedback
3. Explain the constraints and tradeoffs
4. Show how you validated whether the experience actually helped

That framing often makes older work much more relevant.

What to include in an AI-adjacent portfolio case study

A strong case study does not need to be long, but it should be specific.

Include:

• The user problem
• Why intelligence, automation, or prediction mattered in the workflow
• Your role and team
• Key constraints
• Alternative concepts you considered
• How you handled trust, accuracy, and user control
• What changed after testing or feedback
• The outcome

If possible, add one short section called something like "What made this hard" or "Designing for uncertainty." That section helps signal maturity fast.

Portfolio language that helps you get interviews

A lot of designers undersell themselves by using generic language.

Weak phrasing:

• Designed an AI feature for users
• Created flows for a chatbot
• Improved the experience of an assistant

Stronger phrasing:

• Designed a review workflow that let users verify AI-generated outputs before publishing
• Reduced ambiguity in an assistant experience by adding source visibility, retry paths, and editable suggestions
• Partnered with engineering to redesign an AI-powered workflow around latency and confidence constraints

The goal is not to sound technical for its own sake. The goal is to show that you understand the product realities of AI-enabled experiences.

What if you don't have direct AI project experience?

That's common, and it's not disqualifying.

You can still build a credible portfolio for AI-adjacent roles by combining three things:

• Existing case studies that show relevant judgment
• A thoughtful speculative project or redesign
• Clear writing about your process and tradeoffs

A speculative project works best when it solves a narrow problem.

Good examples:

• Redesigning an AI writing assistant's review flow
• Improving how a support copilot explains suggested replies
• Creating a safer handoff between AI recommendations and human approval
• Designing a better empty state and feedback loop for low-confidence outputs

Avoid making the project too broad. A focused workflow says more about your thinking than a fake end-to-end startup concept.

How to prepare for interviews after updating your portfolio

Once your portfolio is stronger, interviews usually focus on how you think.

Expect questions like:

• How would you design for incorrect AI output?
• When should a system automate versus ask permission?
• How would you measure trust?
• What would you do if users overrelied on suggestions?
• How would you work with engineering when the model is inconsistent?

Prepare concise stories around:

• Tradeoffs you made
• Constraints you worked within
• How you handled uncertainty
• How you validated decisions

If you can answer those clearly, you'll often stand out from candidates who only show polished visuals.

A practical next step for designers making this pivot

Pick one portfolio project this week and rewrite just the opening and outcome sections.

Ask yourself:

• Does this case study show decision-making, not just deliverables?
• Does it explain uncertainty, trust, or control?
• Does it sound relevant to AI-adjacent product work?

You do not need a full portfolio overhaul to become more competitive. Often, a sharper framing is enough to make your experience legible to the right hiring team.

And if you're still deciding which direction to target, start with roles where your current design strengths already transfer. That's usually the fastest path to a realistic pivot.