🛠️ Shipped beats perfect. Documented beats shipped.

PM Side Projects Guide
(2026 Edition)

6 side project ideas that demonstrate PM judgment, why they work, and how to document your PM thinking so interviewers actually see it.

Build PM Intuition in Parallel — Free →

Why Side Projects Move the Needle

1. Shipped evidence of PM judgment

Anyone can claim they think like a PM. A side project shows you actually made user, scope, and prioritisation decisions.

2. Interview-proof stories

'Tell me about a time you shipped something' is hard to answer without a PM title. A side project gives you a fresh, owned story.

3. Domain depth

Side projects in a domain you care about (fintech, AI, learning) accelerate your domain expertise faster than reading about it.

4. Network expansion

Shipping something public attracts other operators, gets you invited to chat, and builds signal that compounds over months.

6 Side Project Ideas

Chrome Extension

20–40 hours

Clear user problem, small scope, fast feedback loop. Great for showing how you define user needs and measure success.

💡 Examples: A tab manager, a reading tracker, a meeting prep assistant. Use Chrome Web Store reviews as user research.

Notion Template / System

10–20 hours

Forces you to design for a workflow, not just a UI. Good for demonstrating systems thinking without needing to code.

💡 Examples: PM career tracker, interview prep system, product roadmap template. Sell on Gumroad or give away free.

Bot (Telegram, WhatsApp, Slack)

15–30 hours

Highly usable platform, low friction to build, immediate feedback from real users. Great for showing iteration thinking.

💡 Examples: A Hindi news bot, a PM interview practice bot, a habit tracker bot. Start with 10 friends and iterate.

No-Code Web App

30–60 hours

Bubble, Softr, Glide let you ship real products without coding. Proves you can scope and ship, which is the core PM skill.

💡 Examples: A niche job board, a community platform for a specific persona, a directory or comparison tool.

Newsletter / Substack

4 hours/week, 3+ months

Writing publicly forces you to develop a point of view. PMs who write well often outshine PMs who just ship.

💡 Examples: A weekly PM teardown, a deep-dive on a specific industry, commentary on Indian tech. Publish weekly for 3 months minimum.

AI / LLM Product

25–50 hours

AI is hot and you don't need to train models — you just need the OpenAI/Anthropic API and a real user problem. Hugely credible for AI PM roles.

💡 Examples: A niche AI tool (AI code reviewer for a specific language, AI study buddy, AI-enhanced journaling app).

6 Things to Document About Your Side Project

Writeups beat repos. Include these in a 1-page doc.

1.

Problem you identified and how you found it

2.

Target user — who specifically, with one or two real user interviews if possible

3.

Why you picked THIS solution over alternatives you considered

4.

Success metric you defined (and what you'd learn if it doesn't move)

5.

Post-launch learnings — what users actually did vs what you expected

6.

What you'd do differently or build next

FAQ

Do I really need to code to build a side project as a PM?

No — no-code tools (Bubble, Softr, Glide, Zapier, Retool) can ship real products. What matters for PM credibility isn't the tech — it's evidence that you scoped, shipped, measured, and iterated. A Notion-based product with 200 active users shows more PM skill than a beautifully coded app with zero users.

How do I pick what to build for a side project?

Pick a problem you personally have or genuinely understand. Building for a persona you can't talk to or empathise with rarely works. The best PM side projects solve a problem you have, for people like you, with a tight scope you can ship in under 50 hours. Scope creep is the #1 reason side projects die before shipping.

How should I talk about my side project in a PM interview?

Treat it like you would a real product. Walk through: the user problem you identified, the decisions you made, the metric that mattered, what you learned, and what you'd do next. Interviewers don't care about user count — 20 real users is enough. They care about whether you made thoughtful decisions, measured results honestly, and learned from what happened.

Build PM Skills While You Build Your Project

Daily 2-minute PM scenarios — keep your product thinking sharp while you ship.

Start Free Trial →