Are You Technical Enough?

Cagan asks how much technical competency a product manager really needs, noting that managers and candidates alike are unsure where the bar sits. He argues technology knowledge matters because great products pair a real problem with what has just become possible, and because PMs must earn engineers' respect and speak their language. He then argues the requirement is often overrated: user experience and design usually matter more, and the real bottleneck is usually imagination rather than engineering capacity. The useful standard, he says, is the ability to learn new technologies quickly and apply them by understanding their strengths and limits, not to code them. Exceptions include platform and developer-facing products and companies whose culture is built on engineering, such as Google.

01Key takeaways

• Learn new technologies well enough to judge their strengths, weaknesses, and limits, even if you never write code with them.
• Treat engineers as partners: understand their constraints, such as scalability or maintainability, and how those affect feature delivery.
• Do not assume engineering is the bottleneck; often the real limit is the team's ability to conceive compelling product ideas.
• Spend regular time with engineers and ask about the technologies they are exploring, as an ongoing habit like customer contact.
• If you are targeting an engineering-driven company, a few years as a developer can build the cultural credibility the role requires.

02Key sections

Why technology competency matters

Cagan argues that spotting what is newly possible and earning engineering respect are both core to effective product management. Without an engineering team and a clear product direction, neither side delivers value.

Why it is often overrated

Most products are judged on user experience, which is a design skill more than a technical one. In many companies the bottleneck is the team's imagination and ability to define compelling ideas, not engineering limits.

What technology competency actually means

PMs do not need deep knowledge of language features or build tooling, but they do need to understand scalability, availability, and maintainability issues and grasp what new platforms enable and cannot do.

How to develop it

PMs should build technical knowledge continuously through reading, experimenting, and spending time with engineers, just as they spend time with customers, since what is possible changes constantly.

Exceptions to the rule

Platform and developer-tool products require deeper technical sophistication, and engineering-centric cultures may set a higher bar for credibility even when the job itself does not demand it.

03From the post

“A partnership dedicated to teaching best practices to product teams and product leaders”

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.