How to Show AI Work in Your UX Portfolio (For Jobs and Freelance)

Recruiters and freelance clients both want the same proof in 2026: where AI helped, where you made the calls, and what shipped. A case study structure that works for hiring and client trust.

If you are job hunting or pitching freelance work in Hong Kong, your portfolio is doing two jobs at once. Hiring managers ask whether you are hireable on a product team. Clients ask whether you can deliver without a full-time seat. Both now also ask how you used AI—not whether you used it at all. This is the case study structure I use on johnny-chan.com and in client decks when AI is in the toolchain.

Lead with the problem, not the tools

Open with users, constraints, your role, and timeline. Then name where AI helped (research synthesis, copy drafts, exploration) and what you rejected, edited, or validated with real people. Employers want to see judgment. Freelance buyers want to see you will not disappear behind generated screens.

Show validation, not just output

Usability tests on shipped flows—not only AI wireframes.
Accessibility and edge states you fixed after automated suggestions.
Outcomes: metrics, quotes, or honest qualitative results.

Handle NDAs without hiding your craft

When you cannot show proprietary UI, describe the workflow: “LLM-assisted thematic coding on anonymized interviews,” “agent-assisted implementation with design QA on PRs.” Never pass raw model output off as final design without saying what you changed.

The story that wins work: AI made me faster; I stayed accountable for what users see.

Make it easy to scan in 60 seconds

Recruiters skim fast. Founders skim between meetings. Use clear headings, plain outcomes, and named tools (Figma, Claude, Cursor, Perplexity) so your expertise is obvious. Strong structure also helps search and AI citations—but write for humans first.

Let's work together

Open to UI/UX projects, collaborations, and product design support in Hong Kong and remotely.

Let's Connect