Back to Blog

Director of Product Job Description Template 2026

HiringIT HiringLeadership

Last updated: October 5, 2026

By Jennifer Burdick, Recruiting Manager, KORE1

A director of product job description should state the team size, the decisions the director owns, what the roadmap already promises, the reporting line, and a base range, typically $195,000 to $325,000 in 2026. Most postings describe a senior product manager and add a sentence about leading a team. Strong directors read that sentence and keep scrolling, because it says nothing about how much of the job they would control.

I have read a great many director of product postings over the years, most of them on our director of product staffing desk in the week a client calls to ask why theirs is not working. The trouble is rarely length. It is rarely tone. Nobody wrote down what the director gets to decide.

A dental practice software company in Ann Arbor, Michigan, brought us in last February. About 140 people, four product managers, two designers. Its Director of Product posting had been up for nine weeks. Under Responsibilities it listed fourteen bullets, starting with “Own the product vision and strategy” and ending with “Foster a culture of innovation.” It had drawn 263 applicants. The CEO forwarded me the shortlist his head of people had built, and eleven of the twelve names belonged to senior product managers who had never managed anyone.

Not their fault. The posting read like a senior PM job with a promotion stapled to it, so senior PMs who wanted a promotion applied.

The two experienced directors who did reach a first call asked the same three things inside ten minutes. Could they hire? Could they move a PM from one product line to another? Could they tell the head of sales no? The CEO had founded the company as its first product manager, and he is a thoughtful man, but he answered each question with some version of “we would figure that out together.” Both withdrew within a week. Both politely.

So we sat down with him and a whiteboard and listed the product decisions that come up in a normal month. Hiring a PM. Moving one. Setting the quarter. Promising a date to a customer. Killing a feature. Pricing. For each, we asked who decides today and who would decide once the director started. Some answers surprised him. A few surprised me. He had never meant to hold on to pricing approval. He had just never handed it to anyone. The finished list went into the posting as a short table, the title stayed the same, and the fourteen bullets became five.

Ninety-one people applied over the next four weeks, about a third of the earlier count, and six of the shortlisted names had run product teams before. The company hired a director from a fleet-management software company in Kalamazoo at $214,000 base, inside the area director band in our salary guide. She has since hired two PMs of her own. The CEO still sits in on pricing, by her invitation now, and he says it is the meeting he would miss most.

CEO in a navy sweater and a product director in an orange blazer sorting blank index cards into piles on an oak table

Our recruiters hear some version of the Ann Arbor story in most first conversations with a new client. Whether you need a director at all, or a group product manager with a bigger title, is a separate question, and our director of product management hiring guide works through it. This page assumes the decision is made. It covers the document, the one a candidate reads before anyone at your company has a chance to explain.

Now the part about money. KORE1 gets paid only after a director we introduced accepts an offer and starts work, so naturally I would like you to call us. I would still rather you had a posting good enough that you might not need to.

Most Duties Lists Describe the Same Job

A director of product leads a team of product managers and owns the results of a product area through them, not through specs of their own. The work is mostly decisions about people, priorities, and money, made alongside an engineering peer and reported to a VP, a chief product officer, or the CEO.

Pull up five director of product templates and you will find the same dozen duties in each. Set the vision. Own the roadmap. Partner with engineering, design, marketing, and sales. Define KPIs. Mentor product managers. None of it is wrong. Every director does those things, which is exactly the trouble, because a list that fits every director cannot tell a candidate anything about yours. Our own product manager job description template leans on duties for good reason, since an individual contributor’s work mostly is the duties. A director’s is not.

Product directors have no Bureau of Labor Statistics occupation of their own. The nearest category, computer and information systems managers, had a median annual wage of $175,140 in May 2025, and its job profile describes CIOs, CTOs, IT directors, and IT security managers, not product leaders. Fine as a floor. Not much use past that.

An experienced director reads your posting for four things the duties list never says. How big is the team? What can I decide without asking? What has already been promised? Who do I answer to, and what do they keep? Everything below is about getting those four onto the page.

Put a Decision Table Where the Bullets Were

Paul Rogers and Marcia Blenko, two partners at Bain, whose firm teaches a decision-roles method called RAPID, wrote about this in Harvard Business Review back in 2006. Their point was that decisions stall when nobody is sure who owns them. Who recommends? Who has to agree? Who signs? They were writing about big companies. A director search is the same problem, smaller. The candidate wants to know where the final say sits, and most postings make them wait until the last round to find out.

Eight rows cover almost every first or second director seat we fill. The middle column shows what we usually find when we ask. It is not always pretty.

DecisionWhere it often sits todayHow it reads in the posting
Hiring and letting go of product managersDirector decides, CEO or VP approves the offer“You will fill two open PM roles in your first quarter. Offers are approved by the CEO.”
Which PM works on which product lineDirector decides“You decide how the PM team is assigned across our three product lines.”
The quarter’s prioritiesDirector proposes, leadership team signs off“You set the quarterly roadmap with the Director of Engineering and present it to the leadership team for approval.”
Delivery dates promised to customersSales, more often than anyone admits“Sales does not commit a delivery date without your agreement.”
Sunsetting a feature or productDirector recommends, CEO decides“You recommend sunsets. The CEO approves any change that touches more than $500,000 in annual revenue.”
Pricing and packagingVaries more than any other row“Pricing changes are set by you and the CFO together.”
Research and tool budgetDirector decides within a fixed amount“You own a $60,000 annual budget for research, analytics, and design tools.”
PM ratings and promotionsDirector decides, calibrated with HR“You run calibration for the product team and approve promotions through senior PM.”

Copy the third column. Change the numbers. Keep it honest, too. If the CEO signs every offer, write that. A good director can live with an approval step. Finding it in month two is what sours them.

Watch two rows in particular. Customer dates. Pricing. Both drift to sales or finance by accident, and a director who finds that out after accepting the job spends half a year clawing them back. Say where they sit today. Planning to move them? Say that as well.

Team size goes near the top of the posting, in numbers, not in this table. Our page on staffing a director of product seat explains why the count of PMs and product surfaces decides which seat you are really hiring, and that argument does not need repeating.

The Roadmap Somebody Already Sold

A company in Sacramento that builds case-management software for county and state agencies posted a director role last year with a line I see constantly. “Own the product roadmap end to end.” About 210 employees. Five PMs. Government buyers. That means long contracts, and long contracts often carry feature commitments with dates attached.

Nobody had added them up. Not once. When we did, after the fact, signed contracts committed the company to nineteen specific features over the next three quarters, each with an acceptance date. Roughly 65 percent of engineering capacity through the following spring was spoken for before any director walked in.

The finalist found out the way finalists usually do. In her last interview, with the chief revenue officer, she asked what next year’s roadmap looked like, and he slid a contract appendix across the table. She was gracious about it. She also withdrew two days later, and her note said she had applied to own a roadmap and been offered the job of delivering one.

I could not argue with that.

The fix was two sentences and a fraction. “About two-thirds of our engineering capacity through next spring is committed to features in signed public-sector contracts. You will own the remaining third, and you will own the process for what we commit to next.” The next shortlist was smaller. Stronger, too. One finalist, who had run product at a tax software vendor, said the committed-capacity line was why she applied, since it was the first posting she had seen that admitted the problem she was good at fixing. She accepted at $236,000.

Stack of five gray bound documents held with orange binder clips beside a black pen on a walnut conference table

Committed work is nothing to hide. Every company with enterprise or government customers carries some. Most carry a lot. A rough share is fine, and it will do more to attract the right director than any sentence about vision. If the honest number is zero, print that too. To a director who has spent three years delivering someone else’s promises, an empty quarter is the most attractive line in the posting.

Whose Name Sits Above the Box

Rochester, Minnesota, is a small city with a lot of health technology in it, and one of our clients there makes scheduling and patient-intake software for specialty clinics. The founder had been a product manager before starting it and had run product himself for six years. By last spring the company had 38 people and three PMs, and he wanted to hand product to someone else.

The posting said “Reports to the CEO.” True. Incomplete. In the second interview a strong finalist asked who would make the call if she and the CEO disagreed about the roadmap. He answered plainly. He would, for at least the first year.

Nothing is wrong with that answer. Wrong place, that is all. We moved it into the posting. “Reports to the CEO, who founded the company as its first product manager and will keep final say on the annual roadmap through next year. Quarterly priorities, the PM team, and research are yours from the first day.” The applicant count dropped. Everyone still on it was comfortable with the arrangement, and two of them said they would rather work for a founder who said so than one who claimed to have let go.

Write the reporting line by title, and say what the boss still owns. “Reports to the VP of Product” means one thing where the VP runs only product and another where the VP also runs engineering and has not been in a product review in a year. Candidates will ask either way. Answer in writing. Answer first. If the product org is still being drawn, our product team org chart guide shows where directors tend to sit at each stage of growth.

How Much of the Week Is Still Hands-On

Most first director seats are partly hands-on. The posting should say how much, because directors read a missing number as a warning, and they are right more often than not. “Player-coach” in a posting usually means a full PM workload plus three direct reports.

A rough split does the job.

  • “About 70 percent leading the team and 30 percent owning the onboarding product yourself until we hire a fourth PM.” That one line tells a candidate what the job is now and when it changes.
  • Fully managerial? Say so. Some candidates want exactly that, and the ones who do not will rule themselves out before the first call.
  • If the honest split is the other way round, mostly hands-on with one or two reports, you may be writing a group product manager posting, and the pay will differ.

Directors also look for the size of the hiring plan in this part of the posting. Open PM seats are part of the workload, and two open seats in the first quarter is a lot of interviewing on top of everything else.

Pay Comes From the Tier, and Minnesota Wants It Printed

With the team size and the decisions on paper, the tier usually picks itself. The bands below are lifted word for word from KORE1’s director of product salary guide, so the numbers match across both pages.

TierWhat the seat coversBase, 2026Total comp, typical
Area director (just up from GPM)One product area, 3 to 6 PMs$195K to $240K$260K to $430K
Portfolio director (established)A product line or several areas, manages PMs and a GPM or two, carries a number$230K to $285K$350K to $650K
Senior director (near-VP scope)A whole product domain or a P&L, top product seat below the VP$260K to $325K$450K to $1M+

Look at the last column. That is where offers come apart. Equity does most of the swinging at this level, so a posting that prints a base and stays silent on equity tells a senior candidate roughly half of what they need. If you grant equity, say so, even without a number.

The Rochester client had no choice about the base. Minnesota’s salary range statute, in force since January 1, 2025, covers any employer with 30 or more employees at one or more sites in the state and requires each job posting to show the starting salary range plus a general description of the benefits and other compensation. The range has to be a good-faith estimate, and it may not be open-ended, so “$210,000 and up” does not qualify. The company had 38 people. Its first draft said “competitive.” That had to go.

Several other states have similar laws. Even where none applies, a director posting without a range mostly draws people who are guessing, and people who guess high tend to leave at the offer stage. To price one seat in one metro, the KORE1 salary benchmark tool gives finance a defensible starting number in a few minutes.

Five-person product team standing around a tall round table in a glass-walled room, listening to a director in an orange cardigan

Director of Product Job Description Template

Copy this and replace every bracket. Most of what goes inside them already lives on your org chart, in your signed contracts, and in last quarter’s plan. Bracketed lines that begin with “Internal” are notes for you, and they come out before anything goes live.

Job Title

Director of Product[, product area or line] ([N] product managers, reports to [title]) [Internal: the parenthetical filters harder than any other line. Use “Senior Director” only if the scope matches the senior tier above.]

The Product and the Team

[Company] makes [product] for [customers], and [one sentence on stage, such as revenue range, customer count, or growth]. The product team is [N] product managers and [N] designers, working with [N] engineering teams led by [title of the engineering peer]. [N] of the PM seats are open today, and filling them is part of this role.

What Is Already Committed

[About [N] percent of engineering capacity through [month] is committed to [contracted features / a platform migration / a regulatory deadline]. You will own the rest, and the process for deciding what we commit to next.] [Internal: if nothing is committed, write that instead. It sells the job.]

Decisions This Role Owns

  • You decide [hiring for open PM roles / how PMs are assigned across product lines / quarterly priorities, set with the engineering director].
  • You recommend, and [title] approves, [feature and product sunsets / pricing changes / offers above $N].
  • Delivery dates promised to customers [require your agreement / are set by sales today, and changing that is part of the job].
  • You own [a $N annual budget for research, analytics, and design tools / no separate budget yet].

Reporting Line

Reports to the [CEO / VP of Product / Chief Product Officer][, who will keep final say on [the annual roadmap / pricing] through [date]]. Your peers are the [Director of Engineering] and the [Head of Design].

How the Week Divides

About [N] percent leading the product team and [N] percent owning [a specific product area] yourself until [the next PM hire / a date].

The First Two Quarters

  • Hire [N] product managers and build a PM interview process the team can run without you
  • Set up quarterly planning with [engineering peer] and publish the first plan by [month]
  • Deliver or renegotiate the [N] customer commitments due in [quarter]
  • [A product outcome with numbers, such as moving onboarding completion from N to N percent]

What We Are Looking For

  • [N] or more years managing product managers, not only mentoring them
  • A roadmap you owned that included work already promised to customers
  • [B2B SaaS / regulated / marketplace / consumer] product experience [if it matters for this product]
  • People you hired who were later promoted
  • Comfort explaining a product call to a CFO in terms of revenue and cost

Not Required

  • An MBA [Internal: very few director searches we run turn on this, and requiring it removes strong people]
  • A computer science degree, unless the product is a developer tool
  • Experience in [your industry], if someone on the team already knows it well

Pay and Location

Base salary of $[minimum] to $[maximum], a bonus target of [N] percent[, plus equity in the form of [type], vesting over [N] years]. [A sentence or two about medical, dental, 401(k), and paid leave.] [Remote within [states or time zones] / hybrid, in the [city] office [N] days weekly.] [Internal: Minnesota and several other states require the starting range and a general description of benefits in the posting itself, and an open-ended range does not count.]

Arguments From the Approval Thread

Should the title read head of product or director of product?

Director of product draws a more predictable pool because it maps to a known tier and pay band, while head of product can mean anything from a startup’s first PM to a VP in all but name.

Use head of product when the seat sits at the top of product with nobody above it. If you do, put the team size right beside the title, or the applicants will come from both extremes.

Our founder plans to keep the last word on the roadmap. Does the posting have to say so?

Put it in one plain sentence, with an end date if there is one, because experienced directors ask about it by the second interview and read a late answer as a sign that other surprises are coming.

The Rochester posting lost a few applicants this way and gained a better shortlist. Worth it. Almost always.

How many years of experience should we ask for?

Ask for years spent managing product managers, usually three or more for a first director seat, rather than total years in product, which rewards long individual careers that may include no management at all.

Ten years as a PM and one as a manager is a different person from six as a PM and four running a team. The second is usually your director. Not always.

Does the team count really belong in the first paragraph?

“Four product managers, two open seats, and two designers” is the kind of line that belongs up top, because team size tells a candidate which director tier the seat falls in faster than any list of duties.

When the number is about to change, give both. “Three PMs today, five by June” is a real piece of information. “Lead a growing team” is not. It is filler.

What base range fits a first director of product?

$195,000 to $240,000 base fits most first director seats in 2026, which is the area director tier, with total compensation of $260,000 to $430,000 after bonus and equity are added in.

Portfolio directors with several product areas and a revenue number run $230,000 to $285,000 base. If your seat falls between the two, price the scope you wrote down, not the title.

Do we need a scorecard as well as the posting?

Two documents work better than one, since the posting is written to persuade a stranger and the scorecard is written so every interviewer grades the same things.

Put the decision table in both. Our director of product interview questions test the very decisions a good posting promises, and a scorecard that mirrors the posting keeps the debrief short.

Give the Candidate the Decisions

The Ann Arbor director ran her first planning cycle in her sixth week. In it she moved a PM from the imaging product to billing, something nobody there had been allowed to do before, and the CEO learned about it by reading the plan rather than being asked. He told me later that this was when he knew the posting had worked. He had written down that she could do it. So she did. No meeting needed.

A director of product posting is a list of decisions with a team attached. Write the decisions first, in a table if you can bear to, then the team, then what has already been promised, then whose name sits above the box. The duties go last. Candidates skim them anyway. For the seats on either side, the senior product manager job description template covers the level below, our VP of product recruiting page takes the one above, and the broader product manager staffing team handles everything in between.

When your draft has a decision table in it, send it to our product recruiting team. We will mark it up the way a finalist would, line by line, before you spend a month reading applications. We fill director seats almost entirely as direct hires, and of the people we place, 92 percent are still with the client when their first year is up.