Article
A 30-day plan for your product design interview
With a month to go, the trick is not to learn everything. Spend each week on one thing: foundations, product thinking, your portfolio stories, then out-loud practice.
You have an interview in a month. The temptation is to read everything, redo your portfolio and memorise a hundred questions. That plan fails, because nothing gets deep enough to say out loud under pressure.
Give every week a single job instead.
The four weeks
- Foundations. Refresh how you frame a problem, map a journey, sketch a screen and keep a design accessible.
- Product thinking. Practise choosing what to build, tying design to business goals, and defining what success looks like.
- Your stories. Pick two portfolio projects and learn to explain every decision and trade-off in them.
- Out loud. Present, get interrupted, answer behavioural questions and work to a clock.
How to use the month
- Short and daily beats long and rare. An hour a day for thirty days outperforms two weekends of cramming.
- Write things down. Notes made this month are what you will reread the night before.
- Do not chase everything. If a topic is not on this list, it can wait. Depth in a few areas is more convincing than shallow knowledge of many.
- Keep one running document. Questions that stumped you, phrases that worked, numbers you can quote from your own projects.
The questions themselves, with how to answer each, are in the pinned guide “Top 20 UX interview questions and how to answer them” in Community, under Career Advice. This series is the plan around them. The next four guides take the weeks in order. Read each at the start of its week, then spend the days doing, not reading.
- UX Design
- Product Design