What Does It Take to Become a Product Manager? (Honest Answer)
What does it take to become a Product Manager?
Let me answer from my experience. Not from a framework. Not from a "5 steps to PM" listicle. From what actually happened and what I've observed hiring PMs over the years.
TL;DR: There are no strict prerequisites for becoming a PM. You can learn the skills on the job. But there's one real prerequisite: don't jump on the bandwagon without knowing what it really takes. Focus more on learning about PM and why you want to be a PM, rather than just how to become one.
Why I became a Product Manager
"I studied Technology for my bachelor's degree and worked in software for three years. I've always enjoyed designing things and using design tools like Photoshop. I even led the Design Committee in college. During my MBA, I gained a deeper understanding of business. Since product management is at the intersection of Tech, UX/Design, and Business, it was the perfect fit for me."
If that sounds like a good explanation, thank you. But it's just an answer I prepared for my first-ever product interview.
While these are all facts, I didn't actively pursue product management. I just got lucky. The right role appeared at the right time. I said yes without fully understanding what I was signing up for.
The honest truth: most PMs I know didn't follow a planned "path to PM." They stumbled into it through a combination of curiosity, opportunity, and willingness to figure things out.
The real prerequisites (there's only one)
I don't think there are any strict prerequisites. You can learn the skills on the job. Seriously.
Product sense? Develops with exposure. Stakeholder management? Develops with practice. Technical knowledge? Develops with curiosity. User empathy? Develops with customer conversations.
But there's actually one real prerequisite: don't jump on the bandwagon without knowing what it really takes.
Many aspiring PMs say things like:
- "It would be cool to build products"
- "I want to make decisions and climb the ladder"
- "I like being at the intersection of business and tech"
- "Product managers have influence without needing to code"
Those reasons aren't bad. But they're not enough. They describe the shiny side without acknowledging the daily reality.
When I ask PM aspirants about the challenges in Product Management, hardly anyone has an answer. They've studied the "how to become a PM" content. They haven't studied the "what it actually feels like to be a PM" content.
So, focus more on learning about PM and why you want to be a PM rather than just on how to become one.
Practical tips from experience
While there's no substitute for talking to an experienced PM for personalized guidance, here's what I've observed works:
If you don't have a tech background
Start developing an interest in technology. Not coding (that's a different conversation), but understanding how software works, how products are built, what APIs do, how databases store information, what makes things fast or slow.
Books like "Swipe to Unlock" can be a good start. They explain technology concepts in plain language without requiring you to write code.
Why this matters: You'll work with engineers daily. You don't need to build software. But you need to speak enough of the language to have productive conversations and make informed trade-off decisions.
If you don't have an MBA
Learn about business from a top-down perspective. How do companies make money? How do startups find product-market fit? What drives growth? What kills companies?
Solve entrepreneurial case studies. Read about how startups become successful companies. Understand unit economics, competitive strategy, and go-to-market.
Why this matters: PM decisions always connect to business outcomes. If you can't think in terms of revenue, retention, and market dynamics, your product decisions will lack strategic grounding.
If you have a tech background but no MBA
This is actually a strong position. Many companies prefer tech-savvy people with good business knowledge over an MBA without technical depth.
Highlight your tech skills. Learn business fundamentals on your own. The combination of "I understand how things get built AND why they should be built" is powerful.
If you're a tech entrepreneur
Focus on your ability to get things done no matter what in interviews. Entrepreneurial experience is gold for PM roles because it demonstrates:
- Ownership and initiative
- Working with ambiguity
- Making decisions with limited data
- Wearing multiple hats
- Understanding the full stack of building a product
The right role for your starting point
Remember: to stay motivated, focus on roles where you have a higher chance of success.
Don't aim to become a PM for a complex enterprise product at a large company if you're just starting out in the tech world. The learning curve will be overwhelming, and the competition is fierce.
Better starting points:
| Your background | Good first PM role |
|---|---|
| Engineering (2-3 years) | Technical PM at a startup or internal tools PM |
| MBA (fresh grad) | APM program or junior PM at a growth-stage startup |
| Sales/Consulting | PM at a company where you know the domain |
| Design | PM at a product-led company that values UX |
| Entrepreneur | PM at an early-stage startup (familiar chaos) |
The goal isn't to land the perfect PM role first. It's to land any PM role where you can learn the craft. Once you have 1-2 years of PM experience, doors open much more easily.
What I wish someone told me before I started
1. You don't need permission to think like a PM. Start now, in whatever role you're in. Observe how products work. Think about why decisions were made. Question user experiences.
2. The "intersection" framing is overrated. PM isn't about being at the intersection of three circles. It's about owning outcomes when you don't control any of the inputs.
3. The first year is the hardest. You'll feel like you don't know enough about technology, business, or users. That's normal. It takes 12-18 months to feel competent. Give yourself that time.
4. Every PM path is unique. There's no "correct" background. Engineers, designers, MBAs, analysts, teachers, and musicians have all become great PMs. What matters is how you think, not what you studied.
5. Talk to actual PMs. Not PM content creators. Not career coaches. Actual working PMs. Ask them about their Tuesday afternoon. That'll tell you more than any blog post.
The bottom line
What does it take to become a Product Manager?
Honestly? Curiosity, willingness to learn on the job, and the maturity to know what you're signing up for. There's no gatekeeping background. No mandatory degree. No certification that guarantees success.
But the one real prerequisite stands: understand what PM actually involves. The loneliness. The context-switching. The thankless coordination. The decisions under uncertainty. And if that still excites you, you'll do fine.
How ProductResume helps
When you're ready to apply for PM roles, your resume needs to communicate readiness even without extensive PM experience. Focus on transferable skills: problem-solving, cross-functional work, data-driven decisions, and ownership of outcomes. Score your PM resume to see how your background translates to PM hiring criteria, especially if you're transitioning from another function.