UX Designer Job Description Template

In plain language: States the official job title, the department the role sits within, and the manager or team lead the employee reports to directly.

Common mistake: Using an informal title like 'designer' that differs from payroll records — mismatches complicate visa sponsorships, background checks, and W-2 reporting.

In plain language: A 3–5 sentence paragraph defining the purpose of the role, the problems it solves, and how it contributes to the company's product or business goals.

Common mistake: Writing a generic role summary copied from a job board without referencing the company's actual product or user base — candidates disengage and the document provides no performance baseline.

In plain language: A prioritized list of the employee's primary duties — what they are accountable for producing, maintaining, or improving on a regular basis.

Common mistake: Listing responsibilities so broadly (e.g., 'own all design') that there is no measurable basis for performance review or evidence of role misalignment during a dispute.

In plain language: Distinguishes the minimum qualifications that make a candidate eligible (required) from the experience that would make them competitive (preferred).

Common mistake: Marking every desirable qualification as 'required,' which narrows the candidate pool unnecessarily and can create disparate-impact liability if the requirements lack business justification.

In plain language: States the salary range or hourly rate, FLSA classification (exempt or non-exempt), payment frequency, and reference to the company's benefits program.

Common mistake: Omitting the salary range in jurisdictions that legally mandate pay transparency (Colorado, California, New York, Washington) — non-compliance triggers regulatory penalties and reputational damage.

In plain language: Assigns to the employer all design work, prototypes, research deliverables, and other creative output produced by the employee in connection with their role.

Common mistake: Limiting IP assignment to work created 'on company premises' — remote UX Designers routinely work on personal devices, leaving designs, Figma files, and research data outside the clause's reach.

In plain language: Prohibits the employee from disclosing unreleased product designs, user research data, customer information, and business strategy during and after employment.

Common mistake: Failing to specify that user research data — which may include personal data of study participants — is covered, creating GDPR or CCPA compliance gaps when research participants' information is mishandled after departure.

In plain language: Restricts the departing employee from recruiting the company's employees or soliciting its clients or design partners for a defined period after leaving.

Common mistake: Using a non-solicitation period longer than 12 months for a design role without documented justification — courts in several jurisdictions reduce or void excessive durations, potentially voiding the clause entirely.

In plain language: Sets the standards against which the employee's performance will be measured and states when formal reviews occur.

Common mistake: Leaving performance standards entirely undefined in the job description — without documented benchmarks, it becomes legally difficult to justify a performance-based termination.

In plain language: Specifies which jurisdiction's law governs the document and requires any changes to be made in writing and signed by both parties.

Common mistake: Treating the job description as a standalone contract without referencing the governing employment agreement — courts may treat inconsistencies between the two documents as grounds for the employee to claim the more favorable terms.

A UX designer job description template is a structured document that defines the scope, responsibilities, qualifications, compensation, and legal obligations of a UX Designer role. It functions both as a recruitment posting and, when signed, as a binding schedule to an employment contract. A well-drafted template covers role-specific details — design tools, research methodologies, sprint workflows — alongside standard legal clauses for IP assignment, confidentiality, and non-solicitation.

At minimum: official job title and reporting structure, a role summary tied to the company's actual product, prioritized core responsibilities, separated required and preferred qualifications, a compensation range, FLSA or equivalent employment classification, IP assignment language covering design files and research data, confidentiality obligations, non-solicitation terms, and a performance expectations section with a review cadence. Missing any of these creates gaps that surface during hiring disputes or post-employment IP claims.

A signed job description is generally enforceable as a schedule to an employment contract when it contains consideration (compensation), mutual obligations, and is executed before the employee begins work. On its own, a job description may not constitute a complete contract, but when incorporated by reference into a formal employment agreement and signed by both parties, it creates binding obligations — particularly for IP assignment, confidentiality, and non-solicitation clauses.

In California, Colorado, New York, and Washington state, employers are legally required to include a salary range in job postings. Several other US states and Canadian provinces are introducing similar requirements. Even where not legally mandated, including a salary range typically reduces time-to-fill by 20–30% by filtering mismatched candidates early and accelerating offer negotiations with qualified applicants.

A job description defines the scope of the role — responsibilities, qualifications, tools, and performance expectations. An employment contract is the comprehensive legal governing document that covers salary, benefits, IP assignment, non-compete, termination, severance, and governing law in full legal detail. Best practice is to execute both: the employment contract as the primary agreement and the job description as a signed schedule incorporated by reference.

Include a broad IP assignment clause in both the job description and the employment contract. The clause should cover all design files, prototypes, wireframes, user research recordings, and related materials created in connection with the company's business — regardless of what device was used or where the work was performed. For remote designers using personal Figma accounts, add language explicitly addressing cloud-stored files and personal device output.

A standard employee job description is not appropriate for freelance engagements and can contribute to misclassification risk if the contractor is later treated as an employee. For freelance UX work, use an Independent Contractor Agreement that defines the project scope, deliverables, timeline, payment terms, and IP assignment. Misclassifying a UX Designer as a contractor when the working relationship looks like employment can trigger back taxes, benefit liability, and penalties in most jurisdictions.

Required qualifications should reflect the minimum skill set without which the person cannot perform the core duties — typically a portfolio demonstrating end-to-end UX process, proficiency in the design tool your team uses (e.g., Figma), and a minimum years of relevant experience. Preferred qualifications cover specialized skills that improve performance but can be learned on the job — WCAG accessibility expertise, experience with a specific platform type, or familiarity with quantitative research methods. Listing too many items as required can create disparate-impact liability if the bar lacks business justification.

Review the job description annually or any time the role scope changes materially — new product lines, a shift from generalist to specialist responsibilities, or a change in reporting structure. When updates are significant, have the employee acknowledge the revised description in writing. Outdated job descriptions that no longer reflect actual duties create ambiguity in performance reviews and can undermine termination proceedings if the employee argues they were evaluated against undisclosed expectations.