i want to share what worked for me in case it helps others: i was a second-year analyst and realized product would let me build outcomes rather than just advise on them. i picked a tiny, tangible problem at a local startup, built a simple analytics dashboard over weekends, ran one A/B test, and documented the before/after metrics. that one project became my PM narrative in interviews — not a resume line, but a story with numbers. curious to hear what small projects others used to land PM roles and how they framed those projects in interviews.
good move. banks produce candidates who can argue but not ship. building an actual experiment shows you can close the loop. interviews love that because it’s low risk evidence. don’t get cute: present the problem, the metric you moved, the hypothesis, and the tradeoffs. keep it short. fluff gets you ignored.
also, if you did it solo, be ready to answer how you prioritized features and why you didn’t involve users sooner. hiring teams smell manufactured projects a mile away. be precise about decisions and constraints.
- love this. can you share how you found the startup and pitched the dashboard idea? i’m trying to find a tiny project too but don’t know where to start.
- did you put that project on linkedin? curious if it helped get attention.
- how did you measure impact? i’m worried metrics won’t move fast enough.
- brilliant and practical! small projects = big proof. keep sharing your metrics and ask for feedback — people will help!
another tactic: partner with ops or a growth person at a small company — they often welcome help and the work becomes mutualized. you get a real problem, they get execution help, and you get the metrics.
practical checklist: identify a measurable user funnel, run one controlled experiment or implement an analytics dashboard, document pre/post windows of at least 2–4 weeks, and prepare a one-page summary with visuals. this format tends to be most convincing to PM interviewers.