Technical Product Management in the age of Artificial Intelligence by Hamza Mobeen - HTML preview
Download the book in PDF, ePub, Kindle for a complete version.
Chapter 2: Types of Product
Managers
Technical Product Manager
A Technical Product Manager (TPM) is a Product Manager who works on technically complex products and must deeply understand the underlying systems.
They are not engineers.
But they must think like one.
What Makes a PM “Technical”?
A Technical PM typically works on:
● APIs
● Infrastructure
● Platforms
● Developer tools
● AI/ML systems
● Data products
● Internal systems
These products are often not customer-facing in a traditional sense.
The users might be:
● Engineers
● Data scientists
● Other internal teams
● External developers
The problems are more architectural than visual.
Core Responsibilities of a Technical Product Manager
In addition to normal PM duties, a Technical PM must:
● Understand system architecture
● Translate business needs into technical requirements
● Evaluate technical tradeoffs
● Discuss constraints intelligently with engineering
● Manage dependencies across systems
● Think about scalability, latency, reliability You don’t just ask, “Will users like this?”
You ask:
● Will this scale to 10x traffic?
● What are the performance risks?
● How does this integrate with existing systems?
● What technical debt are we creating?
Do You Need to Code?
This is the common question.
You usually do not need to write production-level code.
But you must understand:
● APIs
● Databases
● System flows
● Data structures (at a conceptual level)
● How software is built and deployed If engineers explain a tradeoff, you should follow the logic.
If you cannot understand technical discussions, you will lose credibility.
Who Should Become a Technical Product Manager?
This path is ideal for:
● Engineers who enjoy strategy more than coding
● Developers tired of pure execution
● Data professionals who want broader ownership
● Highly analytical thinkers
It is harder for pure non-technical backgrounds, but not impossible with focused learning.
Key Skills for a Technical Product Manager
Beyond standard PM skills, you must be strong in:
● Systems thinking
● Structured problem solving
● Technical literacy
● Risk assessment
● Clear documentation
Communication is still critical — but your audience is often engineers.
Fluff won’t survive in technical conversations.
How are Technical Product
Managers different?
A Product Manager typically focuses on delivering user-facing features that directly impact customers, working closely with UX, growth, and business teams to ensure the product solves the right problems and drives measurable outcomes. In contrast, a Technical Product Manager operates closer to the system layer, dealing with infrastructure, architecture, and performance considerations, and collaborating more deeply with engineers and developers. While both roles require strong strategic thinking and alignment with business goals, the key difference lies in the depth of technical involvement with Technical PMs requiring a higher level of technical understanding to make informed decisions
around scalability, system design, and long-term platform health.
The Honest Reality
Technical PM roles are:
● Fewer in number
● Higher barrier to entry
● Often better compensated
● More respected in engineering-heavy companies But they are also:
● More complex
● Less visible to end users
● Less design-focused
If you love deep systems thinking, this role is powerful.
If you prefer customer psychology and market strategy, a general PM or Growth PM may fit better.
Should a Career Switcher Target Technical PM?
Be honest with yourself:
If you don’t enjoy understanding how things work under the hood, don’t force it for prestige.
Technical PM is not “better.”
It’s different.
Choose based on interest, not salary assumptions.
Growth Product Manager
A Growth Product Manager focuses on one core objective:
Driving measurable user and revenue growth through product experimentation.
While traditional PMs may focus on building core features, Growth PMs focus on improving metrics across the user lifecycle.
They don’t just ask:
“What should we build?”
They ask:
“How do we increase activation, retention, and revenue?”
What Does a Growth PM Actually Own?
Growth PMs typically work on:
● User acquisition flows
● Onboarding experience
● Activation funnels
● Retention mechanics
● Referral systems
● Monetization experiments
● Conversion optimization
Their success is tied directly to metrics.
The Metrics That Matter
Growth PMs live inside dashboards.
They obsess over:
● Conversion rate
● Customer acquisition cost (CAC)
● Lifetime value (LTV)
● Retention rate
● Churn
● Daily/Monthly active users
● Revenue per user
Every initiative must tie back to a measurable outcome.
If it doesn’t move a metric, it doesn’t matter.
The Experimentation Mindset
Growth PMs operate on rapid experimentation.
They:
● Form hypotheses
● Design A/B tests
● Launch experiments
● Analyze results
● Iterate quickly
It’s less about building big features.
It’s more about optimizing systems continuously.
Speed matters.
How Growth PM Differs from Traditional PM
A Traditional Product Manager focuses on building and evolving core product features with a long-term roadmap in mind, ensuring the product delivers value, usability, and sustained user satisfaction. In contrast, a Growth Product Manager is more focused on optimizing the user lifecycle through continuous experimentation, working in shorter cycles to test, measure, and iterate rapidly. While both roles require strategic thinking, their success metrics and approach differ, traditional PMs prioritize adoption and overall product quality, whereas Growth PMs are driven by measurable outcomes such as user acquisition, retention, and revenue. Ultimately, the Growth PM operates with a more analytical and experiment-driven mindset, placing stronger emphasis on quantifiable impact and rapid iteration.
Who Should Consider Becoming a Growth PM?
This role suits people who:
● Love numbers
● Enjoy data analysis
● Think in funnels
● Care about measurable impact
● Like running experiments
● Are comfortable with iteration It’s ideal for professionals coming from: ● Performance marketing
● Analytics
● Consulting
● Revenue operations
● Data roles
Skills That Matter Most for Growth PM
Beyond standard PM skills, you need:
● Strong analytical thinking
● Comfort with SQL or analytics tools
● Deep understanding of funnels
● Statistical literacy (basic experiment design)
● Rapid prioritization
You must be comfortable killing ideas fast if data doesn’t support them.
The Pressure Factor
Growth PM roles are often high pressure.
Why? Because growth metrics are visible.
When numbers drop, leadership notices immediately.
There is nowhere to hide. But that visibility also creates fast career acceleration if you perform well.
The Honest Tradeoff
Growth PM roles are:
● Highly data-driven
● Impact-focused
● Fast-paced
● Performance-measured
But they can feel:
● Less visionary
● More metric-obsessed
● Constantly under scrutiny
If you enjoy winning through numbers, this role is powerful. If you prefer long-term product vision and deep feature strategy, traditional PM may suit you better.
Strategic Advice for Career Switchers Growth PM can be:
● Easier entry point for analytical backgrounds
● Faster path to proving impact
● Highly respected in startups
But don’t chase it purely for the title.
Choose it if you genuinely enjoy measuring and optimizing systems.
Platform Product Manager
A Platform Product Manager builds products that enable other products.
Instead of serving end users directly, Platform PMs create the foundation that other teams build on top of.
They don’t focus on features customers see.
They focus on systems that power those features.
What Is a “Platform”?
A platform is a shared infrastructure, system, or capability used by multiple teams or products.
Examples include:
● Authentication systems
● Payment infrastructure
● Internal APIs
● Developer tools
● Data platforms
● Machine learning platforms
● Messaging or notification systems These systems may never be visible to customers, but without them, the product cannot function at scale.
Who Are the “Users” of a Platform PM?
The users are often:
● Internal product teams
● Engineers
● External developers (if APIs are public)
● Data teams
Instead of optimizing user onboarding flows, Platform PMs optimize developer experience.
Their job is to make it easier for other teams to build.
Core Responsibilities of a Platform PM
Platform PMs typically focus on:
● Scalability
● Reliability
● Performance
● System integration
● Standardization
● Reusability
They ask questions like:
● Can this system handle 10x growth?
● How do we reduce duplication across teams?
● How do we improve developer productivity?
● What technical debt are we creating?
● How do we make this platform flexible but stable?
This role requires long-term thinking.
How Platform PM Differs from Other PM Roles A Traditional Product Manager primarily focuses on delivering end-user features that enhance customer experience and drive overall product value, typically working within a medium to long-term roadmap. A Growth Product Manager, on the other hand, is centred around optimizing metrics such as acquisition, retention, and revenue through rapid experimentation and shorter feedback cycles. In contrast, a Platform Product Manager operates at a deeper system level, focusing on infrastructure, internal tools, and enablement of other teams rather than direct customer-facing features. Their primary users are internal stakeholders such as engineers and developers, and their work is often aligned with long-term architectural decisions. While Traditional and Growth PMs require moderate technical understanding, Platform PMs demand a higher level of technical depth, as they work much closer to engineering to ensure scalability, reliability, and system efficiency.
Do You Need to Be Technical?
In most cases, yes - more than average.
You don’t need to code daily.
But you must understand:
● System architecture
● APIs
● Data flows
● Dependencies
● Technical constraints
If you can’t follow architectural discussions, you will struggle.
Platform PM credibility comes from technical understanding.
Who Should Consider Becoming a Platform PM?
This role suits people who:
● Think in systems
● Enjoy complexity
● Care about scalability
● Prefer infrastructure over UI polish
● Like long-term architecture decisions It’s ideal for:
● Former engineers
● Technical analysts
● Data professionals
● Systems thinkers
It’s harder for pure marketing backgrounds without technical exposure.
The Challenges of Platform PM
Platform work is often invisible.
If it works, no one notices.
If it fails, everyone notices.
You must:
● Justify investments without flashy features
● Communicate value clearly
● Show impact through efficiency, reliability, and enablement
Your wins are often indirect.
The Strategic Advantage
Platform PM roles can be:
● Highly respected in engineering-driven companies
● High leverage
● Complex and intellectually demanding
● Strong stepping stone to technical leadership roles
But they are less customer-facing and less “glamorous.”
If you enjoy building foundations instead of features, this role is powerful.
Honest Advice for Career Switchers Don’t choose Platform PM because it sounds impressive.
Choose it if you genuinely enjoy:
● Architecture
● Systems thinking
● Technical tradeoffs
● Long-term scalability problems If you love customer psychology and market positioning, this may not energize you.
B2B vs B2C
At a high level:
● B2B (Business-to-Business) products are sold to companies.
● B2C (Business-to-Consumer) products are sold directly to individual users.
But the real difference isn’t just the customer.
It’s the mindset, metrics, and pressure environment.
B2B Product Management
Who Is the Customer?
Other businesses.
Examples:
● SaaS tools
● CRM systems
● HR software
● Enterprise platforms
● Developer tools
The buyer is often:
● A manager
● A department head
● Procurement
● Executive leadership
And the end user may be different from the buyer.
That complexity matters.
What B2B PMs Focus On
● Solving specific business pain points
● Increasing efficiency
● Reducing cost
● Improving ROI
● Supporting sales deals
● Customization and integrations B2B products often require:
● Deep domain knowledge
● Strong stakeholder alignment
● Long-term contracts
● Complex feature sets
Sales Involvement Is Higher
In B2B, product and sales are closely linked.
You’ll often hear:
“We need this feature to close a deal.”
As a B2B PM, you must balance:
● Long-term roadmap integrity
● Short-term revenue pressure
This is a constant tension.
Metrics That Matter in B2B
● Annual recurring revenue (ARR)
● Customer retention
● Expansion revenue
● Contract value
● Sales cycle length
Growth is often slower but more predictable.
B2B Environment Feels Like:
● Fewer customers
● Larger deal sizes
● Longer decision cycles
● More structured conversations
● High stakeholder complexity
B2C Product Management
Who Is the Customer?
Individual users.
Examples:
● Mobile apps
● E-commerce platforms
● Social media
● Consumer fintech
● Streaming services
The user and the buyer are often the same person.
Volume is high.
What B2C PMs Focus On
● User experience
● Activation
● Retention
● Engagement
● Viral loops
● Monetization
B2C is often:
● Data-heavy
● Experiment-driven
● Fast-moving
You’re optimizing behavior at scale.
Metrics That Matter in B2C
● Daily/Monthly active users
● Conversion rate
● Retention rate
● Churn
● Revenue per user
● Engagement time
Small percentage improvements can mean millions of users.
B2C Environment Feels Like:
● Large user base
● Rapid experimentation
● Short feedback loops
● Heavy A/B testing
● Intense competition
The Key Differences
B2B and B2C product environments differ significantly in terms of customer type, decision-making, and execution speed. B2B products are built for businesses, where the sales cycle is typically longer and involves multiple stakeholders, making decision-making more complex and structured. As a result, success is often measured through revenue, retention, and long-term value, with features designed to handle complex workflows and enterprise needs. In contrast, B2C products target individual users, where the sales cycle is shorter or even self-serve, and decisions are more straightforward. The focus here shifts toward growth, engagement, and user experience, with features being more intuitive and easy to adopt. Consequently, experimentation and iteration tend to happen much faster in B2C environments compared to the more deliberate pace of B2B.
Which One Should You Choose?
Choose B2B if you:
● Enjoy structured conversations
● Like solving operational problems
● Don’t mind longer decision cycles
● Are comfortable working closely with sales
● Prefer fewer, high-value customers Choose B2C if you:
● Enjoy behavioral psychology
● Like fast experimentation
● Care about user experience deeply
● Prefer quick feedback loops
● Love optimizing numbers at scale The Honest Truth
B2B can feel political and sales-driven.
B2C can feel chaotic and metric-obsessed.
Neither is better.
They reward different strengths.
If you're serious about switching into PM, don’t just ask:
“Where are the salaries higher?”
Ask:
“Where would I actually perform better?”
Because performance drives salary, not environment alone.
Startup vs Enterprise PM
Both roles carry the title “Product Manager.”
The experience is not the same.
Startup Product Manager
In a startup, speed is survival.
You are building while figuring things out.
Nothing is fully defined.
What Startup PMs Actually Do
You will likely:
● Wear multiple hats
● Handle strategy and execution
● Talk directly to customers
● Write requirements
● Support marketing
● Help sales
● Make rapid decisions with limited data In early-stage startups, you might be: ● The only PM
● The de facto Product Owner
● Part-time Project Manager
Structure is minimal.
Ownership is high.
Environment Feels Like:
● Fast-moving
● Unpredictable
● Resource-constrained
● Ambiguous
● High pressure
You will ship fast.
You will make mistakes fast.
You will learn fast.
Advantages of Startup PM
● Massive ownership
● Broad exposure
● Direct access to founders
● Faster career acceleration
● Opportunity for equity
If the company succeeds, the upside can be large.
Challenges
● Limited mentorship
● Less process clarity
● Constant firefighting
● Job instability
● High emotional pressure
Startups reward self-starters.
They punish people who need structure.
Enterprise Product Manager
In an enterprise company, scale is already established.
Your job is to improve and optimize, not invent from scratch.
What Enterprise PMs Actually Do
You will likely:
● Own a defined product area
● Work within established processes
● Navigate multiple layers of stakeholders
● Coordinate across departments
● Operate within budget frameworks
● Follow governance structures
There is more structure.
Less chaos.
More politics.
Environment Feels Like:
● Slower decision cycles
● Defined hierarchy
● Cross-department coordination
● Formal planning cycles
● Heavy stakeholder management
You won’t move as fast, but impact can be large due to scale.
Advantages of Enterprise PM
● Stability
● Strong brand name
● Clear career ladder
● Formal mentorship
● Defined growth framework
It’s easier to learn structured product thinking here.
Challenges
● Slower innovation
● Bureaucracy
● Decision delays
● Limited ownership early on
● More meetings
You need patience.
And political awareness.
The Core Differences
Startup and Enterprise Product Management environments differ fundamentally in how work is executed and decisions are made. In startups, Product Managers operate in a fast-paced, low-structure environment where speed is critical and risk is inherently higher. They typically have broad ownership across multiple areas, often working with limited mentorship and navigating relatively lower levels of organisational politics. This setup offers flexibility but comes with lower stability. In contrast, Enterprise Product Managers work within more structured and mature environments where processes are well-defined, and stability is higher. While the pace is generally slower due to governance and scale, the depth of ownership within specific areas is greater. Enterprises also tend to provide stronger mentorship and clearer career progression, although navigating internal stakeholders and organisational politics becomes a more significant part of the role.
Which Should You Choose?
Choose Startup if you:
● Thrive in ambiguity
● Move quickly without full information
● Want high ownership early
● Are comfortable with risk
● Prefer building from scratch
Choose Enterprise if you:
● Prefer structured environments
● Value stability
● Want strong mentorship
● Like defined processes
● Are comfortable navigating stakeholders The Honest Advice for Career Switchers If you are new to Product Management: Enterprise can be safer for learning fundamentals.
A startup can be faster for proving its capability.
But don’t chase a startup for glamour.
And don’t choose enterprise out of fear.
Choose based on how you operate under pressure.
The Bigger Strategy
Your first PM job does not define your entire career.
Many professionals:
● Start in enterprise → move to startup later
● Start in startup → move to enterprise for scale What matters most early on is: Where will you perform best?
Because performance compounds.