PM Domain Knowledge Guide
(2026 Edition)
The 4 levels of domain depth, 6 learning habits that compound, and what you need to know for every major PM domain.
Build Domain Depth Daily — Free →The 4 Levels of PM Domain Depth
Level 1 — Vocabulary
1 month of deliberate studyYou know the terms. You can read industry content without looking up every word.
Level 2 — Frameworks
3–6 monthsYou understand the mental models the industry uses. You can explain why things work the way they do.
Level 3 — Operator intuition
1–2 years in the spaceYou know the typical metrics, benchmarks, and what 'good' looks like. You can sniff out BS.
Level 4 — Strategic view
3+ years, often needs cross-company exposureYou see the industry's future dynamics — regulatory shifts, competitive threats, where value will migrate.
6 Habits That Build Domain Depth
1. Read the industry canon
Every industry has 5–10 books/essays everyone in it has read. Find them and read them. For fintech: 'Payments Systems in the US'. For SaaS: 'Behind the Cloud', Lenny's Newsletter back catalog.
2. Follow 10 operators on Twitter/LinkedIn
Not influencers — actual operators. PMs, founders, practitioners who share real lessons. Twitter lists work well. Update the list quarterly as you learn who's signal and who's noise.
3. Read 1 earnings call transcript per quarter
If you work in a public industry (fintech, e-commerce, SaaS), read your company's earnings calls AND your top 2 competitors'. You'll learn how executives frame strategy, challenges, and priorities.
4. Interview users outside your usual persona
Most PMs talk to the same users over and over. Deliberately interview users at the edges of your persona — new users, power users, lapsed users, users who rejected your product. Each conversation adds a dimension.
5. Spend 30 min/week in your support queue
The support ticket queue is the most underrated source of domain insight. You see raw user friction, unexpected use cases, and edge cases that never surface in user research. Block this time weekly.
6. Write publicly about your domain
Blog posts, LinkedIn long-forms, Substack — publishing forces you to crystallise your thinking. You also build a reputation and attract experts who correct your mistakes.
Must-Know Knowledge for 6 PM Domains
Payments / Fintech
UPI flow, NPCI rules, MDR economics, reconciliation, chargeback dynamics, fraud taxonomy, KYC levels
E-commerce
Marketplace vs inventory, take rate, return economics, logistics unit economics, buyer-seller dynamics
Food delivery / Quick Commerce
3-sided marketplace dynamics, dark store economics, rider utilisation, SLA breach drivers, fill rate
B2B SaaS
ARR, NRR/GRR, CAC payback, PQL/MQL, expansion mechanics, enterprise sales cycles
Social / Creator
Engagement types, creator economics, feed ranking signals, virality vs retention trade-offs, community health metrics
AI / ML Products
Model evaluation methods, precision/recall, hallucination risk, data labelling flows, cost per inference, guardrails
FAQ
How long does it take to build real PM domain expertise?
12–24 months of focused work in a domain to reach operator intuition. You can reach working vocabulary and basic frameworks in 3–6 months — enough to be credible. But the pattern recognition that lets you spot BS, predict problems, and make non-obvious bets typically takes a full product cycle (often 18+ months) in the space. Hopping between unrelated domains every 12 months prevents this depth from forming.
Should PMs specialise in one domain or stay generalists?
At early-career levels, variety is valuable — you learn faster across contexts. After 4–5 years, specialisation pays off disproportionately. A Senior PM with 5 years of deep fintech experience outperforms a generalist Senior PM applying to fintech roles, by a wide margin. That said, 'specialisation' can mean domain (fintech), function (growth, platform), or user type (enterprise, consumer) — pick the axis that most interests you.
How do you evaluate domain knowledge in PM interviews?
Interviewers probe for depth through specific questions: 'explain how X works,' 'what are the failure modes of Y,' 'how does this industry's unit economics work?' Candidates with genuine domain depth give precise, specific answers. Candidates who've only read surface content give vague, generic ones. If you can't explain payment success rates, recon, and MDR economics in a fintech interview, you haven't earned domain depth yet.
Build Domain Intuition in 2 Minutes a Day
Daily PM scenarios across fintech, SaaS, e-commerce, AI, and more.
Start Free Trial →