As AI democratizes the act of building, the most crucial skills for product leaders are no longer technical. Instead, vision and judgment become paramount, followed by execution. Deep technical expertise is the least critical component, shifting focus from "how to build" to "what to build and why."

In a highly technical company, having a leader who is not a domain expert is invaluable. This individual can challenge the team's ingrained way of thinking, ask fundamental questions, and ensure the company remains grounded in customer needs rather than getting lost in purely technological pursuits.

The VP of Product overseeing complex hardware, software, and autonomy holds a history degree and started at the company in customer success. This path demonstrates that deep customer empathy and operational experience, gained through non-traditional routes, can be more critical for product leadership in deep tech than a conventional engineering background.

Executives without technical understanding may make impossible requests, like asking why a database can't function like Excel. A product leader who has "gotten their hands dirty" can act as a credible "wall," translating technical complexities and protecting their team's focus and morale.

To be truly successful, a product leader cannot just focus on features and users. They must operate as the head of their product's business, with a deep understanding of P&Ls, revenue drivers, and capital allocation. Without this business acumen, they risk fundamentally undercutting their product's potential impact and success.

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.

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.

In technical product management, deep expertise serves a dual purpose. It's not just about understanding the product; it's a critical tool for building credibility with the engineering team. Engineers are more likely to trust and follow the direction of a PM they respect technically, making this a crucial element of effective leadership.

When leading functions outside your core expertise (e.g., product leading tech and data), credibility cannot come from having answers. Instead, it's built by consistently asking open-ended questions to deeply understand the team's challenges. This approach prevents solutionizing and fosters trust.