Include: user growth metrics (MAU, DAU, retention rates, activation rates), revenue metrics (ARR, MRR, conversion rates, ARPU), operational metrics (feature adoption, NPS, CSAT, time-on-task), and velocity metrics (cycle time, release cadence). Always tie the metric to a specific decision you made. Source: Lenny's Newsletter; Reforge Product Metrics Guide.
Common paths: transition from software engineering, UX design, or data science (each gives you a natural on-ramp to the PM role); apply to APM programs (such as Google APM or Meta's Rotational Product Manager program, highly competitive and a strong entry point for recent graduates); or find a company where you can move internally from a related function. Cold applications as a first-time PM are extremely competitive. Source: Product School; Reforge PM Career Ladder 2024.
A Product Manager owns a product surface or feature area, working directly with engineers and designers. A Group Product Manager (GPM) owns a larger product area and manages 2-5 PMs. GPMs are accountable for both product outcomes and PM team development. The jump from PM to GPM typically requires demonstrated ability to think at a higher level of abstraction and to develop others. Source: Levels.fyi PM Ladder; Reforge.
Yes. Technical skills signal credibility with engineering teams. Include: SQL (if you can genuinely write queries), familiarity with REST APIs, understanding of system design principles, and any coding ability (Python, JavaScript basics). At engineering-led product companies, PMs who can read code often find it easier to work closely with engineers. Source: practitioner advice; check each company's own job descriptions.
One page for PMs with under 6 years of experience. Two pages for senior PMs and above. Three pages is rarely appropriate. Every bullet must earn its place: 3 to 4 quantified, outcome-focused bullets per role are significantly more compelling than 7 to 8 weak activity-description bullets. Source: Lenny's Newsletter PM Hiring; Product School Career Guide 2024.