Product Design Manager Job Description Template

In plain language: States the official job title, the team or function it sits within, and a two-to-four sentence overview of why the role exists and what it is accountable for.

Common mistake: Using an inflated or non-standard title (e.g., 'Design Ninja Lead') that does not match internal leveling or market benchmarks — this creates compensation disputes and confuses candidates comparing offers.

In plain language: Specifies who the manager reports to and how many direct reports the role carries, establishing organizational authority and budget accountability.

Common mistake: Omitting team size or leaving it vague. Candidates use this to evaluate scope and compensation expectations; a mismatch discovered after an offer leads to renegotiation or rejection.

In plain language: Lists the primary duties the role is expected to perform day-to-day, written in active voice with measurable outcomes where possible.

Common mistake: Writing responsibilities so broadly that they could apply to any design role — 'create excellent user experiences' gives neither candidate nor manager a clear performance baseline.

In plain language: Defines the people-management dimension of the role: hiring, coaching, performance management, and team culture responsibilities.

Common mistake: Listing management duties identically to those of a senior IC. If the role is truly a people manager, performance management and hiring accountability must be explicit — otherwise the hire may resist management responsibilities post-onboarding.

In plain language: States the non-negotiable education, experience, and skill requirements a candidate must meet to be considered for the role.

Common mistake: Setting degree requirements (e.g., 'Bachelor's degree required') that are not genuinely predictive of job performance — this can constitute unlawful screening under anti-discrimination law in several jurisdictions and narrows the candidate pool unnecessarily.

In plain language: Describes additional skills or experience that differentiate strong candidates from minimally qualified ones, without excluding candidates who lack them.

Common mistake: Copying preferred qualifications from the required list with minor wording changes — this wastes candidate attention and signals the hiring team hasn't prioritized what actually matters.

In plain language: Lists the specific software, platforms, and workflows the role is expected to use, distinguishing between required proficiency and exposure.

Common mistake: Requiring proficiency in every tool the company uses, including legacy or rarely used platforms. Over-specifying tools signals organizational dysfunction and discourages strong generalist candidates.

In plain language: States the salary band, bonus eligibility, equity structure (if applicable), and key benefits — providing enough transparency for candidates to self-qualify.

Common mistake: Omitting compensation entirely or stating 'competitive salary.' Pay transparency laws in California, New York, Colorado, and other jurisdictions now require salary ranges on job postings — non-compliance carries fines and reputational risk.

In plain language: Specifies whether the role is fully remote, hybrid, or on-site, the expected in-office cadence, and any time-zone requirements.

Common mistake: Posting a role as 'remote-friendly' without clarifying geographic restrictions. Hiring remotely in a new state or country creates payroll tax, benefits, and employment-law obligations the company may not be set up to meet.

In plain language: Affirms that the company makes hiring decisions without regard to protected characteristics and offers reasonable accommodation to applicants with disabilities.

Common mistake: Including a boilerplate EEO statement that does not match the company's actual jurisdiction — an EEO clause drafted for US federal law may omit protected classes required by California, UK Equality Act, or EU member-state statutes.

A Product Design Manager leads a team of product designers and, often, UX researchers — responsible for both the quality of design work and the professional development of the team. They typically own the design process for one or more product areas, partner with product managers and engineers in planning cycles, and represent the design perspective to senior stakeholders. The role splits time between people management (coaching, hiring, performance reviews) and hands-on design leadership (critique, strategy, systems).

Most companies require five to eight years of product design experience, including at least two years managing a team of two or more designers. A strong portfolio of shipped consumer or enterprise product work is non-negotiable. Proficiency in Figma or an equivalent design tool, experience working in Agile environments, and demonstrated ability to influence cross-functional stakeholders are standard requirements. Formal education is increasingly treated as optional in this role; portfolio and demonstrated leadership track record carry more weight.

A Product Design Manager typically owns the design process and team performance for one product area or a defined scope — managing individual contributors directly. A Design Director manages multiple design managers or leads design across the entire product portfolio, and is accountable for design strategy at the organizational level. The distinction is primarily one of scope, headcount, and organizational influence. Some companies use the titles interchangeably at different company sizes.

A job description is generally not a standalone contract, but it can create legal exposure in several ways. Inaccurate or inflated descriptions can support misrepresentation claims if the actual role differs materially from what was advertised. Required qualifications that have a disparate impact on protected groups can form the basis of a discrimination claim. Pay transparency laws in multiple jurisdictions make salary range disclosure on job postings a legal obligation. For these reasons, HR or employment counsel review before publishing is strongly recommended.

In a growing number of jurisdictions, yes. California, New York, Colorado, Washington, and several other US states require employers to include a salary range on job postings. In the UK, while not yet mandated, pay transparency is increasingly expected under gender pay gap reporting obligations. In the EU, the Pay Transparency Directive (effective 2026) will require employers to disclose pay ranges before the first interview. Even where not legally required, published salary ranges consistently produce more and better-qualified applicants.

You can, but you must include geographic restrictions if your company is not registered to employ in every state or country where candidates may apply. Hiring a remote employee in a new jurisdiction triggers employer registration, payroll tax withholding, unemployment insurance, and benefits compliance obligations from day one of employment. Consult your payroll provider or employment counsel before posting without geographic restrictions.

The job description defines the role's scope and expectations during recruiting. The employment contract formalizes the binding obligations — compensation, IP assignment, confidentiality, non-compete, and termination terms — once a candidate accepts. In most jurisdictions, the employment contract supersedes the job description as the governing document. However, if the contract incorporates the job description by reference, the description's language becomes part of the binding agreement — making accuracy and legal review more important.

Figma is the current industry standard for product design tooling and is expected at most companies. Beyond tooling, the role requires proficiency in Agile or continuous-delivery workflows, familiarity with product analytics platforms (Amplitude, Mixpanel), and experience facilitating design reviews with executive stakeholders. For managers leading research-integrated teams, experience with usability testing platforms such as UserTesting or Maze is commonly expected at the preferred level.

Specific enough that a candidate can estimate how they would spend a typical week, and specific enough that a manager can evaluate performance against documented expectations. Vague language like 'drive design excellence' creates ambiguity in performance reviews and makes it harder to justify a termination or performance improvement plan if the hire underperforms. Six to ten responsibility bullets with active verbs, named stakeholders, and explicit cadence or scope references is the target level of specificity.