What Does It Take to Become a Product Manager? (Honest Answer)

···9 min read
product managementcareer advicecareer transitionjob search

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.

Here is the difference when I ask "What's the hardest part of being a PM?"

A common answer: "Probably managing so many stakeholders. But I'm good with people, so I think I'd handle it."

A grounded answer: "Being accountable for a launch date when engineering, design, and legal each own a piece of it. I watched our PM spend two weeks renegotiating scope after a compliance review. I'd want to learn to spot that risk earlier."

The second answer comes from someone who has watched the job up close. You can get there by spending a few weeks near a working PM before you apply.

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.

Try this: find a page in a product you use at work that loads slowly, and ask an engineer why. You'll hear about database queries, caching, or a call to another service. Then ask what it would take to fix and what else would wait. That one conversation teaches you how engineers weigh tradeoffs, which is the part PMs need.

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.

Try this: work out the economics of one food delivery order with made-up but realistic numbers. The basket is $30 and the platform keeps $6 in commission. It pays the courier $4 and spends $1.50 on payment fees and support. That leaves 50 cents before marketing, and now you know why a "free delivery" promotion is a serious product decision.

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 teams value a tech-savvy PM with solid business knowledge as much as an MBA, especially for technical products.

Highlight your tech skills, and learn business fundamentals on your own. Then show both in interviews: you know how things get built, and you can explain why a feature should be built at all. Technical PM roles look for exactly that pairing. One interview line can carry both:

"I suggested caching search results, which cut load time in half. I pushed for it because our data showed users who waited more than three seconds rarely searched again."

The first sentence is how. The second is why, and it's the one PM interviewers remember.

If you're a tech entrepreneur

In interviews, focus on how you got things done with limited people, money, and data. Running a venture gives you direct examples of several things PM interviewers probe:

  • Ownership and initiative
  • Working with ambiguity
  • Making decisions with limited data
  • Wearing multiple hats
  • Understanding the full stack of building a product

The framing matters more than the venture's size:

Before: "I founded a startup, raised a small seed round, and ran everything from sales to product."

After: "With two engineers and six months of runway, I had to choose between a mobile app and fixing web checkout. Customer calls showed checkout was losing orders, so we fixed that first and paused the app."

The after version gives the interviewer a decision, a constraint, and evidence to ask about.


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. For many PMs, it takes a year or more 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. Three questions that get past the polished version:

  • "Walk me through yesterday. What took the most time?"
  • "What's a decision you made last month that someone pushed back on?"
  • "Which part of the job would you hand off if you could?"

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.


This post sits before the job search starts: deciding whether PM is for you. If the answer is yes, the next read is how to transition to product management, which walks through the full path for switchers.

Once you decide, the search itself has six stages:

  1. Fix the resume so a recruiter can tell in a 7-30 second first pass where you're heading and what you've done. Reframe your current work around users, problems, and decisions.
  2. Target the right roles. Use the starting-point table above, and favor an internal move or a domain you already know.
  3. Tailor 3-5 bullets for each job description, using its language where it is true.
  4. Get in front of people. Product-adjacent work in your current role, a PM who will vouch for you, then referrals and direct messages to hiring managers.
  5. Prepare for the interview loop. A clear "why PM, why now" answer, case practice, and the full story behind each bullet.
  6. Evaluate the offer and the level. An associate or junior title is often the right first step if the role has real decisions and someone to learn from.

For background-specific versions, see engineer to product manager and business analyst to product manager.


How ProductResume Helps

When you're ready to apply, your resume needs to show PM readiness without a PM title. Two tools fit the early stages:

  • Fixing the resume: Resume Score checks your resume against a universal PM bar for your level, including career transitions, and shows which dimensions need work. Bullet Analysis rates each bullet strong, needs work, or weak.
  • Checking a specific role: Job Fit Check compares your resume with one job description, so you can see which roles your background supports today.

How does your PM resume score?

Get scored across four PM-specific dimensions in 2 minutes. Free, no signup required.

Score your resume free