Skip to content

Free resources · Product management

Product management resources

Everything here is built to help you break into product management or grow in it: interview questions with worked answers, original product teardowns, portfolio patterns and a curated reading list. Start with the interview questions if you have a loop coming up, the teardowns if you want to sharpen product sense, and the portfolio patterns if you need proof of work for applications.

Last reviewed

Frequently asked questions

How do I prepare for a PM interview?

Prepare by round, not by topic. Most loops test product sense, metrics, prioritisation, estimation, execution and behavioural stories. Practise each with a clear framework, say your assumptions aloud and time yourself to around 20 minutes per case. Build six to eight reusable stories from your own work, and do mock interviews with someone who will push back on weak reasoning.

Can I become a product manager without an MBA or engineering degree?

Yes. Hiring managers mostly look for evidence that you can understand users, make sound trade-offs and work with engineers and designers. You can show this through adjacent work experience, a written case study, a teardown with proposals or a small shipped side-project. A degree can help with some shortlists, but clear proof of product thinking usually matters more in interviews.

What should a product management portfolio include?

Two or three pieces of work that show how you think, not just what you made. A strong set usually combines one problem-to-solution case study, one teardown with concrete proposals and, if possible, something you shipped. Each piece should state the problem, the user, the options you considered, the decision you made, how you would measure success and what you learned.

How technical does a product manager need to be?

Technical enough to have a useful conversation with engineers. You should understand how clients, servers, APIs and databases fit together, why some changes are expensive, and how to read a basic system diagram. You do not need to write production code. What matters is asking good questions about trade-offs, risks and effort, and respecting the engineering team's judgement on implementation.

Want structure and feedback?

Product Management Fellowship

Learn to find the right problem, ship the right solution, and prove it worked.