Explain scope, not just seniority
A director of product job description should answer what the person is accountable for and what they can decide. I start with the customer and business context, then describe the portfolio decisions the director must make. A title alone does not say whether the role leads one line, several teams, a platform, or a growing function.
Responsibilities I would include
I would cover setting direction across the portfolio, making trade-offs, developing product leaders, improving discovery and planning, and partnering with engineering, design, marketing, sales, finance, and operations. I would be explicit about whether the role manages PMs directly or through managers.
I look for examples of setting direction under uncertainty, coaching people, and changing an operating system. I do not use domain experience or years of experience as a substitute for those capabilities.
Define success carefully
I avoid promising a fixed revenue number or guaranteed transformation. I describe observable signals such as clearer strategic choices, healthier product leadership, stronger customer learning, and progress on outcomes the company actually values. I also state what the director does not own, because shared outcomes need clear decision rights.
A practical check
I would include the leadership team the director joins and the decisions that happen there. A director needs context, access, and a clear mandate. Without those, the description describes responsibility without providing the conditions to succeed.
My bottom line
I use this framework to make the work explicit, not to create ceremony for its own sake. Start with the decision, show the evidence, make ownership visible, and revisit the approach when the product or context changes.
If you are building the fundamentals behind this kind of work, the Product HQ product management certification is a useful next step. I also share practical lessons in the Product HQ newsletter.