How to become a product designer
Product design is the craft of deciding how software behaves and feels, then proving it works. You don't need a computer-science degree or a decade of experience — you need a portfolio that shows judgement: a few real problems, the decisions you made, and what happened. Here's the honest path in.
- 1
Learn the fundamentals
Interaction patterns, information hierarchy, type and layout, and a working grasp of how the thing gets built. Rebuild a product you use daily and write down why each screen is the way it is.
- 2
Build three real projects
Not dribbble shots — end-to-end cases with a problem, constraints, iterations and an outcome. Redesigns are fine if you show the reasoning. Depth beats breadth.
- 3
Write your process down
Hiring teams read for judgement, not pixels. Each case should answer: what was the problem, what did you try, what did you ship, what did you learn.
- 4
Apply direct and iterate
Target roles at the level you're actually at (junior first — see the level pages), tailor the portfolio to each, and treat rejections as portfolio feedback.
What you'll want in your toolkit
- Figma
- prototyping tools
- a note-taking habit
- basic HTML/CSS literacy