The article is a great read. Unfortunately, the author has chosen to prohibit any derivative works (see license), so I unable to precise the article and highlight my favorite parts.
Instead, I point my favorite parts out. Do read the introductory section in which Ken compares Product Management in a large company vs PM in a small company.
Ken's article divides his hiring requirements in six major attributes:
- Hire all the smart people
- Strong technical background
- "Spidey-sense" product instincts and creativity"
- Leadership that's earned
- Ability to channel multiple points-of-view
- Give me someone who's shipped something
I would like to rename it: "Have a good nose to appreciate and understand how other business functions operate".
Ken highlights the point that a Product Manager plays a devil advocate role and representing all (or as many as possible) interests in any discussion. Ken lists pre-sales engineering, support, developer relations, business development, legal, or customers. Of course there are many more.
A product manager has to have a good nose to understand the impact of their decisions on other functions, as product decisions impact many other business functions and processes. For example, choosing to sun set a product (a product management decision ultimately) might have a radical impact on one sales person's commission (sales and sales operations). Before you announce that PM is jettisoning a product, has the impact to that sales person / manager / director / VP been thought through?
- Are you familiar with the Pragmatic Marketing Framework? How was it / have you applied it in your previous career history?
- What business functions did you do that were missing from the Framework and why?
- Can you describe an example of unintended consequences of one of your decisions? What could you learn from it?
- Can you give me an example of how you achieved an objective at the second attempt?