HS
Harshit Singh
Say hi

๐Ÿ’ชCore PM Skills

The five skill areas hiring managers actually filter on โ€” and where to invest your practice time.

foundationskills
Why it matters

PM is a wide role. You can't be great at everything in year one. Knowing the five core skill areas and which ones to prioritize stops you from spreading your learning too thin.

The core idea

PMs are evaluated on five buckets: Product Sense (you have opinions about products), Execution (you ship), Analytical (you reach for data), Strategic (you see the longer arc), and Leadership (you make the team better). Junior PMs should over-index on Execution and Product Sense; senior PMs need all five.

The five buckets

Product Sense. You have informed opinions about products. Given a screen, you can tell what the team optimized for and what they got wrong. You spot the user problem inside a feature request. Build this by analyzing 2-3 products a week โ€” open them, use them, ask 'what's the JTBD here? what would I change?'

Execution. You ship things. You take an ambiguous goal and turn it into a launched feature with metrics. Build this by leading small projects end-to-end โ€” even sub-features count. The skill is in managing scope, unblocking the team, and not letting the project drift.

Analytical. You reach for data before opinions. SQL, basic stats, A/B testing, funnel analysis. Build this by writing a SQL query every week and reading at least one piece of experiment analysis from your team's history.

Strategic. You see how this quarter's work ladders into a multi-year arc. You can write a one-pager that frames a problem in terms of company strategy. Build this by reading your CEO's recent all-hands transcripts and 10-K (if public) โ€” strategy literacy compounds.

Leadership. You make the team better. Engineers want to work with you because you're clearer than your peers; designers want to work with you because you respect the craft. Build this by being honest in retros, giving real feedback (positive and negative), and removing one obstacle per sprint that nobody asked you to remove.

What to prioritize when

  • APM / first 6 months: Execution + Product Sense. Ship things. Form opinions.
  • PM, year 1-3: Add Analytical. Most junior PMs lose offers on the metrics interview, not product sense.
  • Senior PM, year 3-6: Add Strategic. You stop being measured on shipping; you start being measured on judgment.
  • GPM / Director: Leadership becomes the dominant filter. Can you make a team of PMs better?

The fatal gap

Most PMs who plateau are missing one of these five and don't know it. The most common gap is Analytical for design-background PMs, and Product Sense for technical-background PMs. Take stock honestly โ€” your manager probably already knows which one is yours.

Real-world examples

Google APM Program
Google APM Program
Skill development by rotation

Google's APM program rotates new PMs through 2-3 teams over 2 years specifically to build all five skill areas. You'll do a consumer team (product sense), a growth team (analytical), and often a platform or infra team (execution + strategic). The structured exposure is the whole point.

Go deeper โ€” recommended reading

Interview questions (1)

Q1
What's your weakest skill as a PM, and what are you doing about it?
behavioralmid
โ–ผ

Pick a real weakness โ€” not 'I'm too detail-oriented.' The interviewer wants to see self-awareness and growth.

A strong structure: "My weakest area has been [X โ€” e.g., quantitative analysis]. Specifically, I noticed [evidence โ€” last quarter I had to ask the analyst for help defining the success metric on launch Y]. I've been working on it by [concrete action โ€” taking the Reforge analytics course, writing one SQL query per week, pairing with our DS on every experiment design]. Here's the proof it's working: [recent example where you led the analytical work yourself]."

Pick a weakness that's adjacent to the role you're interviewing for, not central to it. Don't admit to weak product sense in a product sense interview.

Related concepts