To quickly gain a broad, foundational understanding of an adjacent field, read their interview prep books. An engineer reading a PM interview book will get a superficial but wide-ranging grasp of product thinking. This builds empathy and enables more productive conversations with cross-functional partners.
Related Insights
A product manager is ready for leadership not just by mastering their domain, but by demonstrating three key traits: understanding how all parts of the platform connect, being effective in customer-facing roles (sales, roadmap talks), and proactively building cross-team relationships.
Engineering often defaults to a 'project mindset,' focusing on churning out features and measuring velocity. True alignment with product requires a 'product mindset,' which prioritizes understanding the customer and tracking the value being delivered, not just the output.
To move from engineering to product, don't just ask for the role. Proactively demonstrate PM skills by systemizing learnings from customer interactions. Starting an internal 'customer insight newsletter' based on your debugging work proves your value and builds an undeniable case for the transition.
Building your own product forces you to confront technical realities like database migrations and architectural trade-offs. This firsthand experience provides deep empathy for engineering challenges, which in turn builds crucial credibility and improves collaboration with development teams.
Product management "range" is developed not by learning domain-specific facts, but by recognizing universal human behaviors that transcend industries—the desire for simplicity, convenience, or saving time. Working across different verticals hones this pattern-matching skill, which is more valuable than deep expertise in a world of accessible information.
Beyond speaking the same language as developers, an engineering background provides three critical PM skills: understanding architectural trade-offs to build trust, applying systems thinking to break down complex problems into achievable parts, and using root-cause analysis to look beyond user symptoms.
It's not enough for platform PMs to interview their direct users (developers). To build truly enabling platforms, you must also gain wider context by sitting in on the developers' own customer interviews. This provides deep empathy for the entire value chain, leading to better platform decisions.
Contrary to the popular belief that it's always detrimental, for product managers, context switching is a core strength. Fluidly moving between customer, engineering, and marketing conversations is essential for integrating diverse perspectives to bring a product to life.
To effectively apply AI, product managers and designers must develop technical literacy, similar to how an architect understands plumbing. This knowledge of underlying principles, like how LLMs work or what an agent is, is crucial for conceiving innovative and practical solutions beyond superficial applications.
Great PMs excel by understanding and influencing human behavior. This "people sense" applies to both discerning customer needs to build the right product and to aligning internal teams to bring that vision to life. Every aspect, from product-market fit to go-to-market strategy, ultimately hinges on understanding people.