How to build your product team from scratch, attract top product talent, go multi-product, and more

Rohini Pandhi Interview Summary

Key Concepts:

• Product Management Roles: Pioneer, Town Settler, City Planner
• Product Team Building: Career Ladder, Interview Process, Defining PM Responsibilities
• Signs for Hiring PMs: Bottlenecks, Scaling, Complexity, New Product Areas
• Attracting PM Talent: Understanding Candidate's S-Curve, Challenging Problems, Transparency
• Multi-Product Strategy: Organizational Structure, Seedling Product Areas, Core Product Areas

The Evolution of Product Management at Mercury

• Initial Resistance: Mercury's CEO initially resisted hiring product managers, believing engineers and designers could handle PM duties.
• Early Success Without PMs: This was possible due to:
  • Founders acting as PMs, being close to customers and solutions.
  • Hiring product-minded engineers and designers.
  • Autonomous teams making local decisions.
• The Turning Point: The need for PMs became apparent due to:
  • Scale: The founders couldn't handle the increasing workload.
  • Complexity: Fintech requires cross-functional collaboration with compliance, legal, and risk teams.
  • Bottlenecks: Decisions were delayed, and engineers/designers were burdened with PM tasks.
• Initial Solution: Business Leads: Generalists were hired as "business leads" to handle cross-functional collaboration and project management.
• Transition to PMs: Business leads were transitioned to PM roles, but lacked formal PM training, struggling with strategic planning, road mapping, prioritization, and customer research.
• Key Takeaway: The transition to PMs should have happened sooner.

Building the Product Team at Mercury

• Defining the PM Discipline: The first step was to define the expectations of a PM at Mercury.
• Creating a Career Ladder: A matrix outlining roles, expectations, and skills at different levels.
  • Core Values: Humility, low ego.
  • PM-Specific Values: Building products customers love, positive business impact, long-term vision, cross-functional collaboration.
• Updating the Hiring Process: The interview process was aligned with the career ladder criteria.
  • Skills Tested: Product sense, customer and quality obsession, analytical skills, strategic/system-wide thinking.
  • Future Consideration: Adding a written element (essay) to assess in-depth thinking and communication skills.
• The Mercury Presentation: A generic prompt ("talk about something you're interested in") to test attention to detail, craft, and passion.
  • Example: A candidate presented a detailed analysis of an Airbus/Boeing plane, from structure to bolts.

When to Hire Product Managers

• Don't Hire Too Early: Founders should act as PMs until they can no longer handle the workload.
• Signs It's Time:
  • Work isn't getting done without the founder's direct involvement.
  • Engineers/designers are spending too much time on PM tasks.
  • The founder can't scale decision-making or cross-functional collaboration.
  • Moving into adjacent product areas with different customer segments.

The Value of Product Managers

• Different Flavors of PMs: The right type of PM depends on the company, industry, and role.
• Pioneer, Town Settler, City Planner Framework:
  • Pioneer: Good at 0 to 1, creating something from nothing.
  • Town Settler: Good at growth, building infrastructure and experimenting.
  • City Planner: Good at mature products, driving efficiencies at scale.
• Key Takeaway: Founders often resist PMs because they envision a "city planner" when they need a "pioneer" or "town settler."

Attracting Great Product Managers

• Table Stakes: Viable company, market rates, good culture fit.
• Understanding the Candidate's S-Curve:
  • S-Curve: A framework representing career progression based on ambiguity (Y-axis) and scale (X-axis).
  • Stages:
    • One project, low ambiguity.
    • Multiple projects, low ambiguity.
    • One ambiguous problem.
    • All ambiguous problems at scale.
• Key Considerations for Senior PMs:
  • Is the problem area big enough and challenging?
  • Who will they be working with?
• Transparency and Honesty: Communicate the good, the bad, and the ugly.
• Sell the Dream: Explain why you're excited about the company and the opportunities.

Multi-Product Strategy

• Organizational Structure: The organizational structure is crucial for new product areas.
• Seedling Product Areas: New product areas should not be too closely integrated with core product areas.
• Reason: Close integration can hinder the growth of new products.

Conclusion

The interview provides a detailed account of Mercury's journey in building its product management team, highlighting the importance of understanding the different types of PMs, defining clear roles and responsibilities, and attracting talent by offering challenging opportunities and a transparent work environment. The S-curve framework and the Pioneer/Town Settler/City Planner analogy offer valuable tools for assessing candidate fit and structuring product teams effectively.