If you're new here, here are a few past posts you might find useful:

• LLM, ML, AI: What’s the Difference — and Why It Matters for Product Managers?

• What is Product Management all about?

• From Features to Problem-Solving. 4 Steps to Mature Product Work

• How to Turn Your Metrics into a Product Growth System

Hit subscribe if not on the list yet— and let’s roll 👇

Subscribe now

When I first started working in product, I thought a Product Manager was just the person who decided which features to build next.
Pick the important stuff, hand it over to the dev team — done.

But then came the Product Owner. Then the Program Manager. Then Project. Then the Product Marketing Manager.

And suddenly you’re not sure anymore:
Are you still managing the product — or just running between meetings, taking stakeholder requests, and assigning tasks?

It’s funny, but even in 2025, people still confuse these roles — and it’s not just a terminology issue.
It’s about focus, ownership, and all the places where things can go wrong.

In one case, the backlog is empty because no one wrote the tasks.
In another, the roadmap is filled with features someone saw in a competitor’s LinkedIn post.
And in a third — the product is live, but no one knows how to sell it.

This article is for anyone who wants to finally make sense of who’s responsible for what.
If you’re a new PM, prepping for interviews, building a team, or just trying to clear the fog in your head — welcome.

We’ll keep it simple:
Five roles. Five key questions they answer. And one table you’ll probably want to bookmark.

Read more

If you're new here, here are a few past posts you might find useful:

• Design Thinking: How to Think Like a Product Manager

• Product Hypotheses ≠ Ideas — Or Why You’re Not Seeing Results

• User Interviews: How To Understand Users And Avoid Building The Wrong Product

• How to Prioritize When Everything Looks Important

Hit subscribe if not on the list yet— and let’s roll 👇

Subscribe now

Advice on how to grow in product is everywhere — maybe more than actual product managers.
Read books. Watch videos. Learn by doing. Take ownership. Build your own product. Go to meetups. The list goes on.

These are all good suggestions. But they can be noisy and overwhelming.
The real problem? You still don’t know what you should do next.

– If you're already a PM but feel stuck — how do you figure out where to grow?
– If you're just getting started — what should you learn first, and how?

This article isn’t about motivation. And it’s not another philosophy piece.
It’s a hands-on map: where to look, how to plan your growth, what tools to use — and how to get better in real life, not in theory.

You’ll find:
– Curated links to books, courses, blogs, and tools I wish I had at the beginning
– A few practical ways to build a learning plan (and actually stick to it)
– And some underrated ideas for growing as a PM — even without a “perfect” project

This is not “the ultimate truth.”
Think of it as an entry point — into the profession, into this blog, and into a more systematic approach to growth.

Bookmark it. I’ll keep updating the guide with new materials over time.

Step one: Understand where you are

Learning everything all at once doesn’t make you better. Before building a plan, you need to know where you're starting from.

You might be:
• just exploring product management and not sure where to begin
• a working PM stuck at a plateau
• a mid-level PM aiming for CPO but unsure what’s missing
• even a senior with years of experience, yet struggling to grow “horizontally”

Wherever you are — the starting point is always the same: build a map of your territory.
Figure out what you already know — and where the gaps are.

🔍 How to start

1. Get the big picture
If you haven’t read it yet — start with this article:
→ What is Product Management all about?

It covers:
• how different companies define the PM role
• how your tasks depend on the product’s stage (from discovery to decline)
• and which skills remain core no matter where you work

This matters. Without a clear view of the whole landscape, you can’t choose your next step.
A product career isn’t a ladder — it’s more like a maze. You need to know what wing you’re in.

2. Assess your current skillset
Pick any framework — from the Mind the Product model to my simplified version.
It typically includes blocks like:
• Product Discovery
• Research & Analytics
• Stakeholder Communication
• Roadmapping
• Delivery & Team Process

Go through each block and ask yourself honestly:
– Can I do this?
– How confident am I?
– Do I use this in real work?

🎯 You can just score each from 0–3 in Excel or Notion. Even better — write down real examples.

3. Connect it to your career goals
Want a raise? A lead role? A switch to AI products?

Your growth priorities will change depending on where you’re headed.
The article above breaks down how the PM role shifts by product stage — check where you are, and what you’re missing.

Next step?
Don’t try to “level up everything.” Build a personal plan — even if it’s just scribbled on a napkin.

Step two: Build your PDP (and not abandon it a week later)

PDP is your way of staying afloat in the chaos of tasks, courses, and ideas.

Most PMs walk around with a brain full of thoughts like:

“I want to improve my metrics — but no clue where to start”
“There’s just too much — Discovery, UX, analytics, strategy…”
“I feel like I’m constantly busy — but not really moving forward”

But here’s how a PDP can actually help.

🔹 What is it, really?

PDP = Personal Development Plan.
In practice, it’s a simple tool to:

• Define what skills you want to level up

• Understand why they matter to you

• And attach concrete steps to each one

💡 It’s not “take a course for the sake of it.”
It’s your answer to:
“What do I want to be able to do — and how will I actually learn it?”

🔹 How to build your PDP in 5 steps

1. Pick 2–3 focus areas per quarter
   Don’t try to improve everything at once. Fewer goals — deeper growth.

2. Describe what exactly you want to improve
   Not just “analytics,” but “I want to learn how to formulate hypotheses and validate them using SQL + Amplitude.”

3. Assess your current level (scale: 0–3)

• 0 — “Heard about it, never touched it”

• 1 — “I get the basics, but don’t use it”

• 2 — “I use it sometimes”

• 3 — “I use it confidently and help others”

4. Write down your plan — how will you learn it?
   For example:

• Take a course (and specify which one)

• Build a mini-project

• Discuss it with a mentor

• Apply it in a real work project

5. Set a deadline and a checkpoint
   e.g. “By the end of the quarter” or “First user interviews by end of the month”

🔹 What if you have zero time?

If you’re in “firefighting mode” and can’t sit down even for 30 minutes, just answer these 3 questions:

• What do I want to be able to do in 3 months?

• What’s stopping me from doing it now?

• What’s one step I could take this week?

Sometimes that’s enough to shake off the paralysis and get moving again.

How to Actually Grow as a Product Manager

There’s too much content. Too little time. Courses, books, podcasts, interviews, meetups, certifications… It’s easy to get lost.

But there’s one mental model that helps cut through the noise.

🔄 The 70:20:10 Model — A Practical Way to Grow as a PM

Many people think product growth = a bunch of courses and certificates. But real growth works differently.

The 70:20:10 model, used in corporate learning programs, offers a more grounded approach:

• 70% — Learning by doing
  That’s the core. Growth happens when you run discovery, write hypotheses, ship features, make mistakes, and try again.

• 20% — Learning through others
  Team retros, peer feedback, mentoring, stakeholder reviews — all help you see blind spots and sharpen your thinking.

• 10% — Formal learning
  Courses, books, lectures, articles. Still useful — but don’t overestimate it. You can finish every Reforge and Product School course and still write weak specs with zero hypotheses.

Use this model to structure your development. Real growth starts not with “one more course” — but with changing how you think and work.

When theory becomes practice — and sticks.

How to Build Product Skills (with Tools & Resources)

Let’s break down what you can actually do — and where to learn it.
This is not a checklist. Choose what fits your goals, budget, and context.

📚 Must-Read Books to Build Product Thinking

Books aren’t just inspiration — they offer structure, logic, and mental clarity.
No podcast can match that depth. But good books? They change how you think.

Start here:

• Inspired by Marty Cagan
  The PM bible. Why discovery matters — and how great products are really built.

• The Lean Product Playbook by Dan Olsen
  From idea to launch — with metrics, MVPs, and practical examples.

• The Mom Test by Rob Fitzpatrick
  How not to get lied to in user interviews. The best no-fluff guide to discovery.

• Continuous Discovery Habits by Teresa Torres
  How to make discovery a habit — not a quarterly ritual.

• Escaping the Build Trap by Melissa Perri
  Features ≠ value. This one’s about culture, outcomes, and product strategy.

👉 Bonus list: 14 Must-Read Books for Every Product Manager

Tip: Don’t binge-read.
Highlight insights. Apply them. Re-read next year — and notice how your lens changes.

🎥 YouTube & Podcasts That Actually Make You Smarter

Not all learning happens in courses.
Top PMs share real insights on YouTube and in long-form podcasts.
Pick a few, watch during commutes or lunch breaks — and treat them as micro-trainings.

Here are some worth your time:

• Dan Olsen – Product-market fit, metrics, feedback loops.

• Lenny’s Podcast – Deep convos with PMs from Airbnb, Figma, Stripe.

• Pawel Huryn – Strategy, discovery, roadmaps. Fast, clear, and practical.

• Mind the Product – Talks, trends, and case studies.

• Product School – Free webinars with PMs from Google, Meta, Amazon.

• Productized – Interviews with global experts. Less fluff, more substance.

• Diego Granados – How to land a PM job in Big Tech.

• Dr. Bart Jaworski – Culture and strategy, explained through real cases.

• Strategyzer – Deep dives on customer jobs and value props.

• Atlassian – How they build Jira, Confluence, Trello. Learn from toolmakers.

Tip: Pick 2–3 channels. Watch 1 video per day.
Even one good idea can shape your next retro, roadmap, or user flow.

💻 Best Free Courses for Product Managers

No budget? No problem.
There are great free courses out there — but choose them based on your real needs.

📍Just starting out? These will build your foundation.
📍Already working as a PM? Pick one to sharpen a specific skill.

Top picks:

• Product Analytics Certification — Mixpanel
  Metrics, retention, funnels, A/B tests — all signal, no noise.

• Google Data Analytics — Coursera
  Intro to analytics, SQL, and visual storytelling.

• IBM Product Manager Certificate — Coursera
  A structured intro to the PM craft.

• Design Thinking — Great Learning
  Learn how to build user-centric solutions with case-based thinking.

• Micro-Certifications — Product School
  Quick wins on topics like prioritization, JTBD, and KPIs.

• Product-Led Certification — Pendo
  Learn how to grow through product, not just sales — a must for modern PMs.

📎 Full article: Top 28 Free PM Courses in 2025 (link is coming soon 😉 )

Tip: Don’t collect certificates.
Ask yourself: What skill do I need right now? Then pick one course that helps build it.

Free ≠ useless. It’s all about how you apply what you learn.

💰 Paid Schools That Are Actually Worth It

There’s no shortage of courses on the market — but let’s be honest: most of them are fluff wrapped in shiny packaging.

If you’re going to invest, choose schools that teach you to think and do, not just memorize frameworks.

Here are three I can genuinely recommend:

• Product School
  Great for beginners or people transitioning from adjacent roles (design, analytics, engineering). Lots of foundational content, real-world tasks, and case studies. Especially useful if you need to close basic gaps fast.

• Reforge
  This is next-level stuff. Programs are led by active product leaders from Meta, Uber, Figma. No one explains what a backlog is here — they dive into growth systems, discovery ops, and how PMs can impact the P&L.

• SVPG (Silicon Valley Product Group)
  The team behind Inspired and Empowered. This is the closest thing to a true school of product thinking. Less about frameworks — more about how to think, set bold goals, and lead without fear. Best for those who want to go beyond “just running the process.”

💡 Pro tip:
Don’t take everything just because it’s popular. Figure out your growth gap — and choose the course that helps you practice in that exact area.

Otherwise, you’ll end up a theory collector. Real growth comes not from knowing — but from doing things differently.

🎯 Preparing for PM Interviews?

Don’t wait until you start job hunting.

Interviews are not events — they’re skills.
And like any skill, you should train regularly, not cram.

Write answers. Say them out loud. Record yourself. Ask a friend for feedback.

Start here:

• Interviewing.io — mock interviews with real PMs. The closest simulation to the real thing.

• Exponent — peer practice, video lessons, and coaching sessions.

• PM Exercises — daily prompts for product, feature, and analytics challenges.

• Daily Product Prep — bite-sized daily questions to sharpen your thinking.

• HelloPM — templates, guides, and problem sets for structured prep.

• Product Manager HQ — questions for all interview types + walkthroughs.

• Product School Interview DB — one of the biggest interview databases, filtered by company and question type.

📌 Weekly practice beats “reading one more article.”
Set a goal: one question or mock task per week — with reflection and feedback.
When your real shot comes — you’ll be ready.

🛠 Real-World Practice at Work (The Missing 70%)

This is the most powerful growth lever — and the most underrated one.

We often think “learning” means signing up for a course.
But in reality, it’s doing — inside the mess of real product work — where real skills form.

And the best part?
You don’t need a promotion, a new job, or permission to start.
Here’s what you can do right now — no budget, no title, no perfect timing:

• Write hypotheses for every task — even if no one asks you to.
  Not “add a button,” but:
  “If we simplify the first step of sign-up, we’ll increase CR by 10%.”
  This mindset shifts how you see the backlog — and your role in it.

• Launch a side project using Notion, Glide, n8n, Tally, or Webflow.
  Could be an internal tool or a mini-product for friends.
  Just going from idea to MVP is more valuable than ten tutorials.

• Ask for reviews and feedback — even if it’s not expected.
  Ask your analyst to walk you through a funnel.
  Share your user story draft with a designer.
  Discuss with an engineer how to simplify the build.
  That’s growth.

• Run a user interview — formal or informal.
  Even if you’re not the PM.
  Ask support what users complain about most.
  Run a quick discovery using The Mom Test script.
  Any real user contact = levelling up.

• Build a dashboard if it doesn’t exist. Or improve the current one.
  Goal: Understand what’s happening in the product without asking your analyst.
  Even if it’s just a Google Sheet or Amplitude chart — it matters.

• Do a monthly retro — for yourself.
  What did you learn?
  Which bets flopped?
  What will you try again?
  Without reflection, self-growth is just busywork.

• Write.
  Doesn’t matter if it’s a Notion doc, LinkedIn post, or email to a friend.
  Writing your product thinking makes it sharper.

📌 Here’s a simple rule:
If you regularly stretch beyond your comfort zone — you’re growing.
If you’re only closing Jira tickets — you’re working, not developing.

🚫 Don’t wait for “the right moment.”
Growth doesn’t start when someone gives you a title.
It starts the moment you act like a product manager — even if your job title says otherwise.

🚀 Final Thoughts

It doesn’t matter where you are right now:

– Just starting out and unsure where to begin
– Feeling stuck in PM routine
– Wanting to level up but lacking confidence

What matters is this: don’t wait for perfect conditions.

Pick 1–2 areas. Add practice. Start moving.
Even 15 minutes a day can shift your entire trajectory.

Write notes. Analyze other people’s decisions.
Form hypotheses even when no one asks you to.

You don’t need a new job to get stronger.
Get stronger — and the right job will find you🫵

Keep reading Atomic Product!

A blog that cuts through the BS and speaks product in practical terms.

— Dmytro

Share

If you're new here, here are a few past posts you might find useful:

• What is Product Management all about?

• B2B or B2C PM? Take the checklist and choose your side

• Double vs. Triple Diamond: Why two Product Diamonds aren’t always enough

• Design Thinking: How to Think Like a Product Manager

Hit subscribe if not on the list yet— and let’s roll 👇

Subscribe now

You open LinkedIn for the fifth time today.
Another rejection. Another recruiter who never replied.
Another job that looked perfect — and just disappeared.

If you’ve ever tried to break into international product management — or shift into a PM role from another background — you know the feeling.

The doubt. The noise. The pressure to “sell yourself” while trying to stay sane.

A year and a half ago, I was there too.

Despite years of experience, launching a funded startup, and building a strong career in my local market — abroad, none of that mattered.
New rules. New expectations. New speed.
And a lot of moments where I thought: “Maybe I’m not cut out for this.”

I kept going. I adapted. I made mistakes, fixed them, made new ones — and eventually landed a role as Product Manager at a large international company.

This article is not a feel-good story.
It’s not about “believing in yourself” or “manifesting success.”
It’s what actually helped me — practical things I learned, applied, and still use today.

If you’re serious about getting into product management internationally — keep reading.
I wrote this for you.

1. Set up your LinkedIn and CV properly

Let’s start with the foundation — because if this part isn’t right, everything else gets harder.

A few years ago, a solid CV could carry you.
Today? It’s just the starting point.

Your LinkedIn profile is your storefront, your pitch deck, your SEO layer — and often, your first filter.

More than 70% of the roles I applied for came through LinkedIn.
So don’t treat it as a digital version of your resume. It’s something else entirely — and you need to approach it that way.

What are my key takeaways here?:

🔹 CV ≠ LinkedIn

Your CV should be short. 1–2 pages PDF max. Focused on the last 3 roles or the past 10 years.

But LinkedIn - that’s where you show the whole story.
Your career arc. The pivots. The side quests. The glue between roles.

📌 Before publishing it, take a step back and ask:

“Does this show a coherent path — or just a list of jobs?”
“Would someone who doesn’t know me see what I’m good at — and where I’m headed?”

Don’t assume recruiters will Google your past companies. They won’t.
Always add one line explaining what each company does.

🔹 Use the XYZ formula

When describing past roles, don’t list responsibilities. Show impact.

Use this format:

Achieved X, measured by Y, through Z

Example:
Increased retention by 17% (X), measured over 3 months (Y), by revamping the onboarding journey (Z).

This simple structure makes results easier to scan and remember.

🔹 No PM title yet? That’s fine

I didn’t have it either when I started. But product work doesn’t start with the title.
If you’ve done anything related to discovery, prioritization, experimentation, or working with devs — it counts.

Don’t invent things. But don’t hide the product-shaped parts of your experience either.

You can absolutely tell a PM-shaped story — even if you were a BA, designer, marketing lead, or founder.

🔹 Fill out the “About” section

Most people skip it. You shouldn’t.

Keep it short and informative. Include:

• Your domain (e.g., SaaS, marketplaces, fintech)

• Your industry

• Your specialization (e.g., B2B growth, onboarding, retention)

• Your current focus and responsibilities

• A solid list of relevant skills

📌 The more relevant skills you add, the more visible you become in recruiter searches. LinkedIn's algorithm works like a search engine.

🔹 Add a clear one-liner under your name

This helps recruiters understand who you are at a single glance.

For example:

Product Manager • E-commerce | SaaS | PLG | Monetization | Retention

It doesn’t have to be flashy — just accurate and keyword-aware.

🔹 Skip the “Open to work” badge

Yes, really.

It might feel like a helpful signal, but it often backfires.
Some recruiters skip profiles with the badge — assuming the candidate is too junior or too desperate.

Instead:

• Add your email to the About section

• Include a line like “Currently open to new opportunities”

That’s more than enough. And it keeps the tone on your terms.

📎 At the end of this article, I’ll share the exact CV I used during my job hunt — feel free to steal what works.

2. Apply smart

At some point, you realize: sending out 50 applications is easy.
Getting even one meaningful reply — that’s the hard part.

But here’s the thing: you don’t need to become a full-time cover letter writer.
You just need to stop doing it blindly.

Here’s the approach that worked for me — and kept me (mostly) sane.

🔹 Personalize just enough

Everyone says, “Write a personalized cover letter for each role.”

Sure. Sounds noble. But if you’re applying to 20+ jobs a week, that advice will crush your soul.

What I did instead:

• Wrote one solid base letter in my voice

• Tweaked 1–2 sentences depending on the company

• Always updated names and context

That was enough to show I cared — without burning out after the third application.

🔹 Don’t rewrite your CV — just reframe it

I never built a new CV from scratch. But I always adjusted the focus:

• Moved up the most relevant bullets

• Reworded key lines using phrases from the job description

• Highlighted results that matched what the company clearly cared about

You’re not “optimizing for ATS.” You’re making it easy for humans to see the match.

🔹 Start networking before you need a job

When I first got serious about the international market, my LinkedIn felt like a museum — polished, but quiet.

So I started connecting. Not spamming — just reaching out to PMs, recruiters, team leads. People whose work I respected. People I wanted to learn from.

Networking isn’t asking for favors. It’s showing up consistently — with curiosity, not an agenda.

A few weeks in, people started replying.
A few months in, some of them became interviewers. Or referrals.

🔹 Why networking actually boosts visibility

LinkedIn is a visibility game.

The more 1st-degree connections you have, the higher you appear in recruiter searches.
It’s not just about who you know — it’s about who can see you.

Engage with people. Comment on posts. Add context when you connect.
You don’t need to be loud — just present.

🔹 Don’t be afraid to reach out

Frankly, this was a game-changer for me. I used to hesitate: “Why would they reply to me?”

Then I tried. Once. Twice. Dozens of times.
And they did reply. PMs. Recruiters. Founders. People I’d never met.

If you’re polite, specific, and not pushy — your odds are better than you think.

From personal experience, I got replies in about 60–70% of cases.
Not always long answers. But often helpful. Occasionally, transformative.

📌 At the end of the article, I’ll share my exact stats:
How many applications I sent, how many interviews I had, and how many responses came through cold outreach or networking.

3. Prepare for interviews

Here’s something that genuinely surprised me - A lot of people don’t prepare at all.
They show up to the interview, open Zoom, and just… wing it.

They think, “I’ve got experience — I’ll improvise.”
Spoiler: that usually doesn’t go well.

Because interviews — especially in product — aren’t about dumping your resume.
They’re about narrative clarity, strategic thinking, and self-awareness under pressure.

And all of that? It’s trainable.

You wouldn’t launch a product without testing it, right?
So why would you launch yourself without prep?

Here’s what worked for me — not just in theory, but in real interviews:

🔹 Read: Cracking the PM Interview

It’s a classic for a reason. It's an absolutely must-read book and industry standard.

The book breaks down the whole process:

• Interview stages

• Typical PM questions

• How to structure product cases

• What good answers actually sound like

🎯 Don’t just read — practice out loud.
There’s a huge difference between knowing what to say and being able to say it smoothly when the pressure’s on.

🔹 Watch: YouTube mock interviews

My favorite channel: @tryexponent

They publish real mock interviews with PM candidates for companies like Google, Amazon, and Meta.

Watching them helped me:

• Spot common patterns

• Learn how top candidates think

• Understand where people stumble

It’s like watching game replays before a big match.
The more you observe, the sharper your instincts get.

🔹 Practice: Pramp.com

Yes, it’s awkward at first.
Yes, it’s 100% worth it.

Pramp pairs you with other job-seekers for live peer interviews. It’s free for the first few sessions.

I did 5-6 in total. By the third, I noticed something shift —
I stopped panicking. I started flowing. I began to recognize question types and structure my thoughts faster.

It wasn’t magic. It was muscle memory.

🔹 Build your prep doc — and use it

Just a simple Word document or piece of paper.

Mine included:

• A “Tell me about yourself” script

• STAR-format stories from real experience

• Answers to 10+ common PM questions (I always update it when I see more patterns)

• Specific product examples I could reference

• A few notes on each company I applied to

I reviewed it before every call. Sometimes for 3 minutes, sometimes for 10. And here’s why:

Because the real secret to nailing interviews is to stay calm, focused, and well-prepared.

Normal life is already chaotic. Your prep doc becomes your anchor. This is your personal command center.

Believe me, that one habit made a huge difference. I didn’t sound robotic — I sounded ready.

4. What does the hiring process actually look like?

When the interviews started rolling in, I didn’t feel confident. I felt disoriented.

“What do they expect? Where are we in the process? What’s coming next?”

I knew there were resources out there. YouTube is full of mock interviews. Books like Cracking the PM Interview break the whole thing down stage by stage.

But what I really needed back then was clarity — a sense of what actually matters.

In reality, the process almost always boils down to three core stages.
Sure, companies might split them into more steps, shuffle the order, or add their own flavor depending on size and maturity — but the essence stays the same.

This is how it usually worked for me — and what I learned at each point.

🔹 Stage 1 — Intro call with HR

Think of this as the first gate. You don’t need to prove you’re a product genius here — but you do need to come across as sharp, structured, and credible.

They’ll ask you to walk through your experience. They’ll ask why you applied.
Sometimes, they’ll throw in light product questions like:

• “How do you define a successful product?”

• “How do you prioritize features?”

One recruiter even asked me to explain what a product manager actually does —
not because she didn’t know, but to see if I could explain it clearly.

📌 My takeaway: This call isn’t just a “formality.” It’s a screen.
And they’re often talking to dozens of candidates. You need to stand out — fast.

What helped me:

• Having a clear, practiced intro

• Showing curiosity about the product (even from a user’s point of view)

• Researching the company’s latest news, blog posts, or funding updates before the call

🔹 Stage 2 — Deep dive with a PM, CPO, or CTO

This is where it gets real.

You might be asked to walk through a past project. You might get a product case. You might get hit with a take-home assignment and 48-hour deadline.

They’re trying to understand:

• How you approach ambiguity

• How you break down complex problems

• How you think about users, teams, data, and priorities

• And whether you can explain your decisions clearly

Some interviews were more conversational. Others were structured like exams.
One even asked me to critique their own onboarding flow — live.

What helped me:

• Building 3–4 strong product stories (with real metrics, not fluff)

• Speaking in structure, but not sounding rehearsed

• Saying, “Let me take a second to think,” instead of panicking

And the big one:

I stopped trying to impress — and focused on showing how I think (but more on that later).

🔹 Stage 3 — Final call with hiring manager or executive

This one’s different.

Here, they’re not testing your frameworks. They’re trying to feel the fit.

Would they trust you in a high-stakes meeting? Would they enjoy working with you every day? Would you mesh with the team and culture?

Sometimes it’s warm and friendly. Other times it’s quiet and intense.
A few of mine felt more like long coffee chats. Others? Straight-up curveball hour.

I’ve been asked:

• “Tell me about a failure you never talk about.”

• “What’s something you’ve built that no one asked for?”

• “What frustrates you about product management right now?”

📌 The goal here isn’t perfection — it’s presence.
They want to see if there’s energy, honesty, and depth behind the title.

🔹 And yes — “Tell me about yourself” always comes first

Please, don’t underestimate it. This isn’t a warm-up. It’s your moment to shape the rest of the conversation.
In 3–5 minutes, you need to show:

• What drives you

• What connects your experience

• And why you’re a match — now

I iterated mine over and over. Practiced it like a mini-pitch. Not robotic — just fluent.

If you fumble here, the interview never really recovers.
If you nail it, everything else flows.

This is your moment to shine, so make it count!

🧭 Final note — don’t try to be perfect

Sounds weird, but there are no right answers in most PM interviews.
Seriously.

Interviewers aren’t looking for rehearsed scripts. They’re trying to understand how you think — how you weigh trade-offs, navigate ambiguity, make decisions under pressure. Just like in real product work.

And for that, showing your thought process is way more powerful than delivering the “perfect” answer.

So here’s my advice:

• Pause when you need to

• Ask for clarification if needed

• And most of all: be yourself.

If you get hired pretending to be someone else, you’ll either burn out — or have to maintain a role that doesn’t fit you. Neither ends well.

The best interviews I had felt like real conversations — because I wasn’t trying to pass a test. I was trying to find the right fit.

5. Run a retro after every interview

Here’s something no one told me when I started:

The best way to get better at interviews… is to treat them like product sprints.

You don’t need to guess what went wrong. You can learn what worked — and what didn’t — if you actually take the time to look back.

So after every interview, I did a quick retro. Nothing fancy. Just 10–15 minutes with a blank doc and a few key questions.

What I wrote down:

• What questions did they ask?

• How did I answer them?

• How did they react?

• Where did I feel strong?

• Where did I hesitate or ramble?

• Did I prepare enough — or miss something obvious?

Sometimes I wrote bullet points. Sometimes just messy thoughts.
But after a few rounds, patterns started to emerge — and that changed everything.

One time, I realized I always fumbled when asked about cross-functional collaboration.
Another time, I noticed I gave the same example three interviews in a row — and it was starting to feel thin.

By reviewing each round, I stopped repeating mistakes.
I got faster at spotting weak points.
And my answers started feeling more grounded — less like guesses, more like practiced judgment.

Not everything is in your control — but reflection is

You can’t control if a company ghosts you.
You can’t control if they already had an internal hire in mind.

But you can control how you show up next time.
And that starts with seeing each interview not as a pass/fail moment — but as a step in a bigger loop.

PMs run retros after every sprint.
This is the same mindset — just applied to yourself.

6. Avoid common mistakes

After enough interviews — both good and bad — I started noticing a strange pattern.

Some people with less experience got through.
Others, with great backgrounds, dropped out early.

Why?

Often, it came down to simple, fixable things.
So before we move on, here’s a quick list of the most common mistakes I saw (and made).

🔻 1. Not reading the job description carefully

It sounds basic. But I’ve seen candidates jump into interviews without even knowing which product line the role was for.

One time I asked a recruiter, “So… what’s the product exactly?”
She blinked and said, “It’s in the job post. Line three.”

Lesson learned.

🔻 2. Talking about salary too early

Bringing up compensation too soon can shift the tone.
Unless they ask — don’t make it the headline.

When they do ask (usually at the end of stage 1), it helps to:

• Research via Glassdoor, Levels.fyi, or local benchmarks

• Give a reasonable range, not a fixed number

• Be honest about flexibility, but don’t undersell yourself

This isn’t a trap. But it is a test of how you handle negotiation and uncertainty.

🔻 3. Freezing on curveball questions

Every PM interview will have one unexpected moment.

Something like:

“How would you improve our onboarding flow — assuming you had no dev resources?”

Or:

“What would you do if your team completely disagreed with your roadmap?”

There’s no perfect answer. But panicking and blurting out “I don’t know” — that’s where most people lose the thread.

📌 Better approach:
Take a breath. Say: “Let me think this through.”
Then walk them through your reasoning — even if you’re unsure.
Interviewers don’t expect certainty. They want to see how you explore ambiguity.

🔻 4. No prep, no post-mortem

We already covered this in the last section, but it’s worth repeating:

Walking into an interview without prep is like launching a product without a prototype.
And skipping the retro after? That’s just leaving insight on the table.

🔻 5. Trying to be someone else

And let me also repeat this one. This one’s subtle and dangerous.

It’s tempting to perform. To sound like the “perfect PM.”
But here’s the truth: you’re not just interviewing for them. You’re testing the match for yourself.

If you show up as someone else and get the job, guess what?
You now have to be that version of you. Every day.

That’s exhausting. And unnecessary.

The best interviews I had were the ones where I was clear, honest, and relaxed —
not flawless, just real.

7. My path, in numbers (no sugarcoating)

This whole journey took 58 weeks — just over a year.

In that time, I:

• Sent 599 applications (mostly via LinkedIn)

• Got 233 responses

• Took part in 38 interviews

• Completed 9 take-home tasks

• Got 3 offers — 2 full-time, 1 part-time

• And finally chose one — the right one

That’s it. No overnight success story.
No lucky break. No, “I just knew a guy.”

It was a strategy. Persistence. Growth.
And more than once — it was just about showing up again the next day.

✅ CV I used during my job hunt → [link]

Before we wrap — one last thing

Before you send out your 200th application, take a moment and ask yourself:

“Do I actually meet the core requirements for this PM role?”
And if not — what am I doing about it?

It’s okay to admit gaps. Everyone has them.

What matters is what you do next.

📌 If you’re light on product analytics or Agile — study it.
📌 If English isn’t your first language — get a tutor. I used Preply and italki.
📌 If you’ve never touched a roadmap — start one. Even as a side project.

And when it gets frustrating — because it will — remember this:

Think of yourself as a product.
You’re iterating toward product-market fit.

Every application is top-of-funnel.
Every interview is a conversion point.
Every rejection is feedback — not a verdict.

Your job search is a product.
Test. Analyze. Improve.

📚 And while you’re doing that — keep sharpening your skills.

Not just tools or certifications, but actual product thinking.
Read books. Watch breakdowns. Join communities. Build tiny things.
Talk to users, even if they’re imaginary.
Think in hypotheses, not assumptions.

This mindset doesn’t just get you hired — it makes you better once you are.

And above all — don’t quit too soon.

Even when it feels like nothing’s working, momentum is quietly building.
Every action counts. Every attempt matters.

You’re not lost. You’re in progress.
Stay with it.

And keep reading The Atomic Product.

— Dmytro

Share

If you're new here, here are a few past posts you might find useful:

• Design Thinking: How to Think Like a Product Manager

• What is Product Management all about?

• B2B or B2C PM? Take the checklist and choose your side

• User Interviews: How To Understand Users And Avoid Building The Wrong Product

Hit subscribe if not on the list yet— and let’s roll 👇

Subscribe now

If you want to level up your PM career, ship smarter, and stop spinning your wheels — here’s your chance. No courses, no certifications, no LinkedIn buzzwords. Just one thing:

📵 Mute the noise.
🧠 Focus your mind.
📚 Read these books.

Everything you need is already here — if you’re ready to put in the work. Missed a few? That’s fine — but don’t sleep on them. This year is your year. Let’s go.

FOUNDATIONS: Think Like a Product Manager

Books 1–5 — Build the mindset.

1. INSPIRED by Marty Cagan

🎉 The bible of product management. Learn how to craft products that don’t just work but captivate users. A must-read for every PM.

2. EMPOWERED by Marty Cagan & Chris Jones

🌟 Want to create a high-performing product team? This book teaches you how to build a culture of trust, ownership, and speed, enabling teams to make bold decisions independently.

3. Outcomes Over Output by Josh Seiden

🔄 Features don’t matter — outcomes do. Shift your mindset from "more" to "better". This book will transform your approach to product success.

4. Escaping the Build Trap by Melissa Perri

🔗 Stuck in an endless feature-release cycle? Learn how to break free from the build trap and focus on delivering real user value.

5. Decisive by Chip & Dan Heath

🧠 Want to make smarter product decisions? This book unpacks how to overcome biases, think clearly, and avoid falling into decision-making traps.

EXECUTION: Validate, Test & Learn

Books 6–10 — Build smarter.

6. Continuous Discovery Habits by Teresa Torres

🔍 The best PMs are always learning. This book teaches a structured approach to user interviews, rapid iterations, and continuous product improvement.

7. The Mom Test by Rob Fitzpatrick

💡 Want honest user feedback? This book will teach you how to extract real insights instead of polite but useless responses.

8. Sprint by Jake Knapp

⏱ Describes a specific Product Discovery technique invented in Google. Learn how to solve complex problems and test ideas in just 5 days.

9. Testing Business Ideas by David Bland & Alexander Osterwalder

🧪 Start from an idea, then use the design loop to improve it. This book gives you dozens of tools and techniques to examine your assumptions quickly and cheaply.

10. Jobs to Be Done by Tony Ulwick

🛠 People don't buy products. They "hire" them to do jobs. Learn how to define and prioritize customer needs using this practical framework.

IMPACT: Lead with Strategy & Growth

Books 11–14 — Think big.

11. Product-Led Growth by Wes Bush

🔍 Want your product to sell itself? Learn how to create experiences that attract, retain, and monetize users without aggressive sales tactics.

12. Radical Focus by Christina Wodtke

🎯 Select only one OKR. Their goal is to create focus on what's not urgent yet critical for the long-term growth of the business (strategy). OKRs work perfectly with Teresa Torres’s Opportunity Solution Tree.

13. LOVED by Martina Lauchengco

📣 The best tech products can still lose in the marketplace. Why? They’re beaten by stronger product marketing. This book will teach you everything you need to know about it.

14. The Product Book by Product School

📘 A compact and accessible overview of product management fundamentals — ideal for beginners and career switchers who want a solid foundation.

BONUS: Hooked by Nir Eyal

🔁 Learn the psychology behind habit-forming products. A must-read if you're building B2C tools or want to understand user behavior on a deeper level.

Quick Check: How Product Fluent Are You?

🤔 How many of these books have you read?

• 0–3 — Junior PM / Career Switcher — Welcome! This year is the perfect time to level up.

• 4–7 — Senior PM Material — You’ve got the mindset. Now sharpen your craft.

• 8–10 — Ready to Lead — Start mentoring others and leading discovery processes.

• 11+ — Founder/Head of Product Vibes — Time to build your own framework and maybe your own company 😎

📢 Your turn!

What’s your must-read PM book that didn’t make the list? Drop it in the comments — let’s grow this stack together.

AND Thanks for reading and growing together with The Atomic Product.
Keep asking better questions — and building better things.

— Dmytro

Share

If you're new here, here are a few past posts you might find useful:

• Design Thinking: How to Think Like a Product Manager

• What is Product Management all about?

• Double vs. Triple Diamond: Why two Product Diamonds aren’t always enough

• User Interviews: How To Understand Users And Avoid Building The Wrong Product

Hit subscribe if not on the list yet— and let’s roll 👇

Subscribe now

I once met an HR manager at an IT event. We had a nice chat, and at the end she asked, “So, you said you work with a B2B product. But what does a Product Manager even do in that space? I’ve heard that a B2B PM is more like an Account Manager than a real product person.”
At first, I was surprised — but then it made me think.

Since I’ve worked with both B2B and B2C products, I thought: why not unpack this a bit? Let’s dive into what exactly a B2B Product Manager does, how this role differs from a B2C PM, and what unique demands each environment places on product professionals.

At the end, you’ll be able to see which path fits you best — with the help of a quick mini-checklist.

But before we go any further, let me ask you a quick question.

If you picked the fourth — congrats, you're thinking in the right direction!

Common Misconceptions About B2B Products

Here are some of the most common misconceptions I’ve personally encountered in my work or conversations with others:

Myth 1: A B2B Product Manager is just an Account Manager
One of the most persistent myths is that a B2B PM simply collects client requests and passes them along to engineering. This view oversimplifies and undervalues the actual role. In reality, being a B2B Product Manager means taking full ownership of the product — from strategy development and market analysis to working with data, defining value, and prioritizing features. Yes, B2B comes with its own specifics: you're closer to the client, customization matters more, and stakeholder alignment is trickier. But these are added layers of responsibility, not a substitute for strategy — and we’ll get into them later.

Myth 2: UX/UI doesn’t matter in B2B the way it does in B2C
There’s a widespread belief that B2B products lag behind B2C when it comes to design and usability — as if “business only cares about functionality.” That mindset is stuck in the past. Back in the day, enterprise tools were clunky and hard to use, but today’s users expect the same smooth, intuitive experiences they get in banking apps or social media. After all, business users are just people. They want clean interfaces, easy navigation, and visual clarity. In modern B2B products, great design isn’t a nice-to-have — it’s a competitive edge.

Read more

If you're new here, here are a few past posts you might find useful:

• Design Thinking: How to Think Like a Product Manager

• B2B or B2C PM? Take the checklist and choose your side

• User Interviews: How To Understand Users And Avoid Building The Wrong Product

• B2B or B2C PM? Take the checklist and choose your side

Hit subscribe if not on the list yet— and let’s roll 👇

Subscribe now

If you ask ten product managers what product management is, chances are you’ll get ten different answers. Sure, there’ll be a lot of overlap — but everyone has their own way of defining it.

To make things more confusing, there’s a whole bunch of roles that sound similar: product owner, product manager, CPO, head of product, and so on. And it’s just as important to understand where the product manager’s responsibilities end and those of project managers, marketing managers, and other roles begin.

So yeah, there are a lot of questions. Let’s try to answer the most important ones — in a way that even my mom could get it. :)

So what does a Product Manager actually do?

Here are some of the most popular answers:

1. One of the most well-known definitions comes from Marty Cagan in his book INSPIRED (which I highly recommend — here’s the link). He says the main goal of a product manager is to discover a product that is valuable, usable, and feasible. Of course, the final product is a result of the whole product team’s effort, but the PM is responsible for value and viability risks. Still, if you haven’t read the book, this definition might feel a bit abstract.

2. Another simple take: a product manager is someone who comes up with new ideas and makes sure they get built. Sounds clear, right? Take Juicero, for example. In 2013, they had a new idea for a juicer, launched it in 2016, and raised $120 million (even Google backed them!). But by 2017, they shut down and filed for bankruptcy. The idea was interesting. The execution was fine. The only problem? Nobody actually needed the product.

3. Some say the product manager is a strategist — someone who drives the planning, development, and launch of a product or service. Another solid definition. Remember MySpace? It was the world’s biggest social network from 2005 to 2009, and News Corporation bought it for $580 million. But by 2011, it had lost most of its users to Facebook and was sold for a fraction of the price. The CEO of MySpace, Chris DeWolfe, later admitted: “Fox Interactive Media tried to monetize the site without understanding the user experience.”

4. One more take: the PM is the bridge between development, marketing, and sales. They research the market, talk to users, study their needs, and define the product’s direction. Now we’re getting somewhere. Take Zappos, the online shoe retail giant. It launched in 1999 and was later acquired by Amazon for $1.2 billion. But in 2003, it was this close to going under. Sales and product-market fit matter, sure — but so does unit economics. If you want to learn more about how Zappos survived and became a billion-dollar company, check out Tony Hsieh’s book Delivering Happiness (link here).

As you can see, all of these definitions are both accurate and not quite — at the same time. Even if we boil it down to something simple, like:
"A product manager’s main job is to deliver the biggest business impact (measured in metrics and ultimately, money) with the least amount of resources" — we’d still leave room for debate.

Why? Because companies (and their products) go through different life stages. And the role of a PM changes depending on what stage the product is in, what the team looks like, and what strategic goals the company is aiming for.

Product Lifecycle and the Evolving Role of a PM

1. Product Introduction / Go-to-Market Stage (Startup mode)

• Goal: Build the product and launch it.

• PM’s Role: Gather context. Understand the market. Figure out what’s even going on and where the business should grow (what niche to target). This means a ton of customer research, digging into pain points, experimenting with MVPs, and quickly adapting to real-world feedback.
  👉 This is where Design Thinking skills really shine (check out my article on that).
  🔍 Focus: Opportunity Discovery
  Main question: What are we building, and why?

2. Growth Stage

• Goal: Scale fast and expand.

• PM’s Role: Now we know the game we’re playing. We understand our market and our audience. There’s a vision, a strategy, and a list of initiatives that should take us to our desired future. Key focus areas now are acquiring new users, retaining existing ones, and staying ahead of the competition.
  👉 You'll need Roadmapping and Prioritization skills (articles on those coming soon 😉).
  🔍 Focus: Product Planning
  Main question: How are we building it, for whom, and when?

3. Maturity Stage

• Goal: Maintain market share.

• PM’s Role: At this stage, the company may not just have one product, but an entire portfolio. Still, the core product has a stable audience and a clear business model. The job now is to maximize profit while defending market position and fighting off declining interest. It’s all about cutting through the noise, focusing on what matters most, and delivering efficiently.
  👉 Expect to spend time on both roadmaps and backlogs. You'll also lean heavily on Product Delivery skills and tools (again, see my article for more).
  Main question: How can we hit our business goals while spending as little as possible?

4. Decline Stage

• Goal: Find the smartest path forward.

• PM’s Role: There’s no universal playbook here. As Tolstoy put it, “All happy families are alike; each unhappy family is unhappy in its own way.”
  You might need to revisit any of the skills above — searching for untapped opportunities, testing wild new hypotheses, pivoting the product, or tweaking the business model to fix the unit economics. Anything goes.

All of this, of course, is a simplification — every company is unique, and context matters a lot. My goal here isn’t to give you a rigid framework, but to show how dramatically different the PM role can be depending on the product's lifecycle stage.

And if you’re wondering what exactly I mean by terms like Opportunity Discovery, Product Planning, or Product Delivery, check out my article

👉 Double vs. Triple Diamond: Why two Product Diamonds aren’t always enough — it breaks them down in detail.

Core Competencies of a Product Manager

While the tasks and responsibilities of a product manager may shift depending on a company’s stage of growth, there are some core competencies that are essential no matter where you work:

1. Prioritization – The ability to identify what matters most and focus your team’s energy on the highest-impact tasks.

2. Customer Research/Development – Understanding customer needs, behaviors, and pain points through interviews, surveys, and observation.

3. Strategy & Vision – Defining long-term product goals and connecting them to a clear roadmap.

4. Product Discovery – Spotting opportunities, testing hypotheses, and validating new ideas.

5. Analytical Thinking – Making sense of data and using it to drive smart decisions.

6. Communication Skills – Collaborating with cross-functional teams, aligning stakeholders, and clearly articulating the “why” behind every decision.

I go into more detail on each of these in my blog — feel free to check it out!

But here’s the thing: while these competencies are critical, how you apply them depends a lot on the company’s size, hierarchy, market, and product portfolio. That’s why product roles can look so different from one company to another — just like I mentioned at the beginning of this article.

If you're curious about all the nuances — and especially about how to break into product management and build a successful career — don’t miss my deep dive on this topic (link coming soon).

And finally, if you’ve ever wondered about the differences between Product Manager vs Project Manager vs Marketing, you’ll want to read my article about the “horizontal hierarchy” in tech companies — it breaks it all down in a way that actually makes sense (link coming soon too 😉).

What are the key skills every product manager needs?

Traditionally, this skillset is split into two big buckets: Hard Skills and Soft Skills.

🧠 Hard Skills (What you do)

1. Data Analysis – Knowing how to work with data and interpret insights using different analytics tools.

2. UX/UI Design Basics – Understanding the fundamentals of user experience and interface design.

3. Technical Literacy – Grasping the basics of how software is built, including architecture and development flow.

4. Financial Modeling – Understanding unit economics and being able to forecast outcomes.

5. Product Management Tools – Confident use of tools like Jira, Trello, Asana, and more.

6. Customer Research – Knowing how to run and apply different types of user research in real scenarios.

🧑‍🤝‍🧑 Soft Skills (How you work)

1. Communication – Clearly conveying your ideas to the team and stakeholders.

2. Leadership – Inspiring and aligning the team around a common goal.

3. Problem Solving – Navigating ambiguity and solving complex challenges.

4. Adaptability – Embracing change and quickly learning new tools or approaches.

5. Empathy – Understanding the needs and emotions of both users and teammates.

6. Creativity – Staying open to new ideas and exploring unconventional solutions.

A product manager’s toolkit is diverse. Here’s a quick snapshot of popular tools I’ve personally used throughout my career:

Each team and company uses a different mix — the key is to stay flexible and learn the ones that matter most in your context.

Wrapping up

Product management is a dynamic and multi-faceted profession that requires a mix of skills and competencies.

The role of a product manager evolves with the product’s life cycle and the company’s context, but the core mission always stays the same:
build a product that solves real user problems and drives business success.

• In the early startup stage, a PM is more like a researcher — exploring markets, testing hypotheses, and quickly adapting.

• In the growth phase, the PM becomes a strategist — shaping direction, setting priorities, and building scalable plans.

• During maturity, the focus shifts to retaining market share, optimizing processes, and maximizing profit.

• And when the product hits decline, the PM often takes on a crisis-manager role — searching for pivots, improvements, or new opportunities.

To do all this well, you need a blend of technical know-how, analytical thinking, leadership, and emotional intelligence. That’s what makes product management one of the most challenging and rewarding careers in modern business.

If you want to succeed as a product manager, you have to stay curious, keep learning, and be ready to evolve. But most importantly — you have to love your product and truly believe in its potential.

In the end, product management is both an art and a science. It’s a profession for people who thrive at the intersection of data and human behavior, who take ownership, and who are always pushing for better.

Thanks for reading — and for being part of Atomic Product.

Keep building, stay kind, and catch you soon 🫶

— Dmytro

Share