A UXE portfolio
Show the interaction, the constraint and the decision.
- Pick projects that show how you think, not just what you shipped
- Present each one as interaction, constraint and decision
- Make your work playable, not just pictured
A UX engineering portfolio has to show something screenshots can't: how things move, respond and fail, and the judgement behind them. Hiring managers want to see how you think as much as what you built.
Interaction, constraint, decision
For each project, tell a short story in three parts:
- The interaction — what the user does and what should happen
- The constraint — what made it hard: performance, accessibility, an API, a deadline
- The decision — what you chose, what you rejected, and why
This structure shows both craft and judgement, and it's easy for a reader to skim.
Make it playable
Interaction work is best shown live. Embed a working demo, link a coded prototype, or at least include a short screen recording. A demo people can poke at is more convincing than any description of it. The breakdowns on this site are one format to borrow.
Depth over breadth
Three projects explained well beat ten thumbnails. Choose work that shows range: one systems piece, one detailed interaction, one where you worked closely with design or product.
Show the details
Include the states most people skip: loading, errors, empty states, keyboard behaviour, reduced motion. Showing that you thought about them signals exactly the kind of care the role needs.
Be honest about your part
Say clearly what you did on team projects. Credit collaborators. It reads as confidence, and interviewers will ask anyway.
Choose one piece of work you're proud of. Write it up in under 300 words using the structure in this lesson, and add a short recording or a live demo. Ask one engineer and one designer what they learned about how you work.