Overview
[One-paragraph summary: what the product is, who it’s for, and what changed because of your work.]
Write this last. A hiring manager should get the whole story from this paragraph alone.
The problem
[What was going wrong, and for whom?]
State the user problem and the business problem. Use a real quote, support ticket theme, or data point if you have one.
Context
[Where this sat in the product and the market.]
Who are the users (new traders, active investors, partners)? What did the existing experience look like? Why now?
User friction
[Where people got stuck — and how it felt.]
Describe the moments of confusion, anxiety, or drop-off. Show research: interviews, usability tests, analytics, competitive audit.
Constraints
[What you had to design around.]
Regulation, exchange rules, legacy systems, timelines, engineering capacity, data availability.
Key decisions
[The two or three calls that shaped the product.]
For each: the options you considered, what you chose, and why. Include the trade-off you accepted. This is the most senior part of the story.
Collaboration
[Who you worked with and how.]
Product, engineering, compliance, business, leadership. Where did you lead, influence, or change someone’s mind?
The solution
[What shipped.]
Walk through the key screens and flows. Call out the craft: hierarchy, microcopy, empty/error/loading states, accessibility.
Outcomes
[What changed after launch.]
Metrics if you can share them (adoption, completion, support tickets, time on task), plus qualitative feedback. Only use numbers you’re allowed to publish.
What I learned
[What you’d keep, and what you’d do differently.]
One or two honest reflections. This is where your voice and judgement come through.
