UX Data Analyst Job Description Templates for Product Teams
6 free templates covering the standard role, a first data hire, junior, senior, experimentation, and contract engagements, with pay benchmarks and classification notes. Download as DOCX.
The first time I tried to hire someone to make sense of our product data, I wrote a posting that could have described four different jobs. It asked for SQL, usability testing, dashboard design, and experiment analysis, and it attracted a pile of applicants who each matched one quarter of it. That posting was my fault, and the fix was not more requirements. It was deciding what the role was for.
A UX data analyst is a specific hire. This person measures how people actually use your product, owns the instrumentation that makes those measurements trustworthy, and hands design and product a decision rather than a chart. They are not a UX researcher, they are not a general business analyst, and treating the titles as interchangeable is how a small team ends up with an expensive dashboard nobody opens.
At FirstHR we write hiring templates for companies where the founder or the head of product runs the search personally. The six below cover the standard role, a first data hire, junior, senior, an experimentation focus, and a contract engagement, each with the classification and screening notes that generic postings leave out.
TL;DR
A UX data analyst measures how people actually use your product: funnels, event data, experiments, and session behavior. It is a different hire from a UX researcher, who runs interviews and usability studies. No BLS occupation matches the title, so benchmark against data scientists and web and digital interface designers. Six templates below, downloadable as DOCX.
What a UX Data Analyst Actually Does
A UX data analyst turns product usage data into design and product decisions. The work has four parts: defining the events that describe user behavior, building reporting on funnels and retention, running experiments, and translating the results into recommendations a non-technical team can act on.
The part most postings omit is the first one. At a company with a mature data function, the analyst queries a clean warehouse someone else maintains. At a company with under a hundred employees, the tracking is usually incomplete, inconsistently named, and quietly broken by the last release. Somebody has to fix that before any analysis means anything, and that somebody is this hire.
The second omission is the translation work. An analysis that a designer cannot use has not produced value, and this is the most common reason a first analytics hire fails at a small company. Our general guide to writing a job description covers the structure; this page covers what changes when the role is analytical.
Write the Questions Before the Requirements
The strongest opening for this posting is not a company boilerplate paragraph. It is three sentences naming what you cannot currently answer: why new accounts stall in setup, which features actually drive renewal, where the checkout flow leaks. Candidates self-select hard on that, and the applicants you lose are the ones who were going to send a generic resume anyway.
Not a Researcher, Not a Business Analyst
The clearest way to scope this role is by the question it answers. A UX data analyst answers what people did, at scale. A UX researcher answers why they did it. A general data analyst answers how the business is performing. Hiring one while expecting another is the most expensive mistake in this category.
UX data analyst
What people did
Works in behavioral data: events, funnels, retention curves, experiment results, session patterns. Answers questions of scale and frequency. Strong on SQL and instrumentation, and the person who tells you that 41 percent of new accounts never finish setup.
UX researcher
Why they did it
Works with people: interviews, usability sessions, diary studies, surveys. Answers questions of motivation and meaning. Tells you why those accounts stall, which the event log can never explain on its own. A different hire with a different skill set.
General data analyst
How the business is doing
Works across revenue, marketing, operations, and finance data. Owns company reporting rather than product behavior. Overlaps on SQL, but a business analyst who has never instrumented an app will not fix your event taxonomy.
Product designer
What to build instead
Owns the interface and the flow. Consumes what the analyst and the researcher produce. Small teams sometimes ask a designer to cover analytics as a side duty, which usually produces dashboards nobody maintains and decisions nobody can defend.
If the question currently blocking your roadmap is why people behave a certain way, the UX researcher templates are the right starting point instead. If you need company-wide reporting on revenue, marketing, and operations, use the general data analyst templates. Browse the full hiring template library if the role sits somewhere between the three.
What Belongs in the Posting
A job description for this role does four jobs at once: it sells the problem, it filters candidates who lack the depth, it protects you legally, and it closes the person you want. Most postings do only the first, which produces volume without fit. Here is the full inventory.
The parts candidates read first
What the product is and who uses it, in two sentences
The questions you need answered, named specifically
Your actual analytics stack, listed honestly
Whether this is the first data hire or one of a team
The parts that filter applicants
SQL depth, stated as a level rather than a checkbox
Experiment design expectations
Whether instrumentation is part of the job
Remote policy and time zone overlap, stated explicitly
The parts that protect you
FLSA classification stated on the posting
Essential functions written plainly
Equal opportunity statement
Data access and confidentiality expectations
The parts that win the hire
A real salary range, not a placeholder
Who the analyst reports to and partners with
What autonomy over the stack looks like
A named person to apply to and a real deadline
The most common omission at small companies is the stack, stated honestly. Analysts want to know what they are walking into: whether the warehouse exists, whether tracking is trustworthy, whether they will spend the first quarter on taxonomy work. Say it plainly. Candidates who want a greenfield build will take that as an attraction, and the ones who want a clean warehouse will screen themselves out before you spend an interview on them.
6 UX Data Analyst Job Description Templates to Download
Download all six as one file or copy them individually. Each follows the same structure: company overview, position summary, key responsibilities, required and preferred qualifications, a classification and compliance note, an equal opportunity statement, and how to apply. The bracketed fields are the only parts you need to change.
Download All 6 UX Data Analyst Job Description Templates
Standard, first data hire, junior, senior, experimentation, and contract. All in one download.
UX Data Analyst (Standard)
The general product role
The default posting for an established product team: event taxonomy, funnel and retention reporting, experiments, and dashboards other people can read.
First UX Data Hire
No analytics function yet
For the company where usage data lives in spreadsheets and nobody trusts the dashboard. Scoped around building the measurement foundation from zero.
Junior / Associate
Early career, supervised
For a supported first analyst role, with a defined ramp and an honest note on why junior analyst roles are the ones most often misclassified as exempt.
Senior / Lead
Owns the measurement strategy
For the analyst who sets metric definitions, runs the experimentation program, mentors others, and is expected to disagree with the roadmap when evidence warrants.
Experimentation and Conversion
Growth-side focus
For test-heavy teams: funnel quantification, experiment backlog, decision rules written before launch, and honest reporting of flat results.
Contract / Fractional
Project scope, defined end
For a fixed engagement rather than a seat, with deliverables, acceptance criteria, data handling terms, and a direct warning about worker misclassification.
Template 1: UX Data Analyst (Standard)
The default posting for an established product team, covering event taxonomy ownership, funnel and retention reporting, experiments, and dashboards other people can actually read.
UX Data Analyst Job Description (Standard)
UX DATA ANALYST JOB DESCRIPTION
Company: __ ([City, State] / Remote / Hybrid)
Reports to: [Head of Product / Design Director / Analytics Lead]
Employment type: Full-time
FLSA status: Exempt (see classification note)
Compensation: $_ to $_ per year
ABOUT [COMPANY NAME]
[Company Name] builds [product description] for [customer type]. We have
[number] employees and [number] monthly active users. Product and design
decisions here are made by a small group, and we want them made on evidence
rather than on whoever argues hardest in the meeting.
POSITION SUMMARY
The UX Data Analyst measures how people actually use [product], turns behavioral
data into findings the design and product teams can act on, and owns the
instrumentation that makes those measurements trustworthy.
KEY RESPONSIBILITIES
•Own the event taxonomy: define, document, and audit the events and properties
that describe user behavior in [product]
•Build and maintain funnel, retention, and feature adoption reporting
•Analyze drop-off points and surface where users stall, fail, or abandon
•Partner with design on usability findings, pairing behavioral data with
qualitative research rather than competing with it
•Define and track the product experience metrics leadership reviews [cadence]
•Design, size, and read experiments and A/B tests, including the decision rule
agreed before launch
•Build self-serve dashboards so [teams] can answer routine questions themselves
•Present findings to non-technical stakeholders in plain language with a clear
recommendation
REQUIRED QUALIFICATIONS
•[Number] years analyzing product or digital behavioral data
•Strong SQL and advanced spreadsheet skills
•Hands-on experience with a product analytics platform and a BI or dashboard
tool
•Working knowledge of experiment design and statistical significance
•Demonstrated ability to explain an analysis to designers, engineers, and
executives without jargon
PREFERRED QUALIFICATIONS
•Python or R for analysis and automation
•Experience with session replay, heatmap, or survey tooling
•Exposure to accessibility metrics or inclusive design measurement
•Background in [our industry]
CLASSIFICATION AND COMPLIANCE NOTE (read before posting)
This role is written as a salaried exempt position. Exempt status is not created
by the title or by paying a salary: the role must clear both the federal salary
threshold and a duties test, usually the administrative or learned professional
exemption. Analysts whose primary duty is producing routine reports to a fixed
specification, without exercising discretion and independent judgment on matters
of significance, may be non-exempt and owed overtime. Confirm your state rules
as well, since several states set a higher salary threshold than federal law.
This is general information, not legal advice.
EEO STATEMENT
[Company Name] is an equal opportunity employer and provides reasonable
accommodations for the essential functions of this role.
COMPENSATION AND HOW TO APPLY
Compensation: $_ to $_ per year, [bonus / equity], [benefits]
Location and remote policy: [state it explicitly]
To apply, email __ with your resume and one example of an
analysis that changed a product decision.
Template 2: First UX Data Hire, Small Product Team
For the company where usage data lives in spreadsheets and a default dashboard nobody trusts. Scoped around building the measurement foundation from zero rather than maintaining someone else's.
First UX Data Hire, Small Product Team Job Description
UX DATA ANALYST JOB DESCRIPTION (FIRST DATA HIRE)
Company: __ ([City, State] / Remote)
Reports to: [Founder / Head of Product]
Employment type: Full-time
FLSA status: Exempt (see classification note)
Compensation: $_ to $_ per year
ABOUT THIS ROLE
This is our first dedicated analytics hire. Today [product] usage lives in
spreadsheets, a default analytics dashboard nobody trusts, and the memory of
whoever built the feature. You will be the person who fixes that, and you will
own the result rather than inherit someone else's model.
POSITION SUMMARY
The UX Data Analyst builds our measurement foundation from the ground up: an
event taxonomy that matches how the product actually works, reporting the team
believes, and a short list of experience metrics that guide the roadmap.
KEY RESPONSIBILITIES
•Audit current tracking and document what is measured, what is broken, and what
is missing
•Design and implement a clean event taxonomy with [engineering]
•Stand up funnel, activation, and retention reporting for [product]
•Answer the standing questions: where new users stall, which features get
adopted, why accounts go quiet
•Set up a lightweight experiment process the team can actually follow
•Build dashboards non-technical teammates can read without you in the room
•Write short, plain-language findings memos after each analysis
•Recommend the analytics stack and keep the cost proportional to our size
REQUIRED QUALIFICATIONS
•[Number] years in product, digital, or behavioral analytics
•Strong SQL and advanced spreadsheet skills
•Experience instrumenting a product, not only querying data someone else set up
•Comfort with ambiguity and with deciding what not to measure
•Clear writing; most of your output here is a written finding, not a chart
PREFERRED QUALIFICATIONS
•Prior first-analyst or small-team experience
•Python or R for automation
•Familiarity with [our industry] metrics
CLASSIFICATION AND COMPLIANCE NOTE
Written as salaried exempt. A first analyst at a small company usually exercises
real discretion and independent judgment, which supports the administrative
exemption, but the duties test governs, not the title. Confirm the federal
salary threshold and any higher state threshold that applies to you. If the role
is genuinely scoped to routine report production, classify it as non-exempt and
track hours. This is general information, not legal advice.
EEO STATEMENT
[Company Name] is an equal opportunity employer and provides reasonable
accommodations for the essential functions of this role.
COMPENSATION AND HOW TO APPLY
Compensation: $_ to $_ per year, [equity], [benefits]
To apply, email __ with your resume and a short note on the
first thing you would measure at a company like ours.
Still Using Spreadsheets for Onboarding?
Automate documents, training assignments, task management, and track onboarding progress in real time.
For a supported early-career role with a defined ramp, and with a direct note on why junior analyst positions are the ones most often misclassified as exempt.
Junior / Associate UX Data Analyst Job Description
JUNIOR UX DATA ANALYST JOB DESCRIPTION
Company: __ ([City, State] / Remote / Hybrid)
Reports to: [Analytics Lead / Head of Product / Senior UX Data Analyst]
Employment type: Full-time
FLSA status: [Exempt / Non-exempt: decide honestly, see classification note]
Compensation: $_ to $_ per year
ABOUT THIS ROLE
We are hiring an early-career analyst to support product and design with
behavioral data. You will work alongside [role] who reviews your analyses, and
you will have a defined ramp rather than being handed a warehouse and wished
luck.
POSITION SUMMARY
The Junior UX Data Analyst pulls and cleans product usage data, maintains
existing dashboards and reports, and runs scoped analyses on user behavior with
review from a senior analyst.
KEY RESPONSIBILITIES
•Pull, clean, and validate product usage data for scheduled reporting
•Maintain existing funnel, adoption, and retention dashboards
•Run scoped analyses on defined questions and document the method
•Check event tracking after releases and flag anything that broke
•Support experiment setup and pull results under review
•Write up findings in a standard format the team already uses
•Keep the metric definitions document current
REQUIRED QUALIFICATIONS
•[Degree in a quantitative field / bootcamp plus portfolio / demonstrated
skills: set your bar and mean it]
•Working SQL and strong spreadsheet skills
•Basic statistics: averages versus medians, sample size, what significance
means
•Curiosity about user behavior and willingness to ask why three times
•Clear written communication
PREFERRED QUALIFICATIONS
•Exposure to a product analytics or BI tool
•A portfolio project using real or realistic data
•Any hands-on experience with usability testing or survey data
CLASSIFICATION AND COMPLIANCE NOTE
Junior analyst roles are the most likely analyst roles to be misclassified.
Where the primary duty is producing reports to a specification set by someone
else, with limited discretion on matters of significance, the position is
non-exempt: hourly or salaried non-exempt, with overtime past forty hours in a
week. Do not assume a salary makes the role exempt. Check the federal salary
threshold and your state threshold, then apply the duties test to the actual
job. Unpaid internships doing this work are almost never lawful when the company
is the primary beneficiary. This is general information, not legal advice.
EEO STATEMENT
[Company Name] is an equal opportunity employer and provides reasonable
accommodations for the essential functions of this role.
COMPENSATION AND HOW TO APPLY
Compensation: $_ to $_ per year, [benefits], [learning budget]
To apply, email __ with your resume and one project you can
walk us through.
Template 4: Senior / Lead UX Data Analyst
For the analyst who sets metric definitions, owns the experimentation program, mentors others, and is expected to disagree with the roadmap when the evidence warrants it.
Senior / Lead UX Data Analyst Job Description
SENIOR UX DATA ANALYST JOB DESCRIPTION
Company: __ ([City, State] / Remote / Hybrid)
Reports to: [VP Product / Head of Design / Director of Analytics]
Employment type: Full-time
FLSA status: Exempt (see classification note)
Compensation: $_ to $_ per year
ABOUT THIS ROLE
[Company Name] is looking for a senior analyst to set the direction of how we
measure the product experience, not only to answer the questions we already
know to ask. You will influence roadmap decisions and be expected to disagree
with them when the data says so.
POSITION SUMMARY
The Senior UX Data Analyst owns the product experience measurement strategy,
leads the experimentation program, mentors [number] analysts, and represents
user behavior evidence in roadmap and design reviews.
KEY RESPONSIBILITIES
•Define the product experience metrics the company manages against and defend
the definitions
•Own the experimentation program: design, sizing, guardrail metrics, and the
written decision rule
•Lead deep analyses on retention, activation, and feature value
•Partner with research to combine behavioral and attitudinal evidence into a
single story
•Set analysis standards, documentation, and review practice for the team
•Mentor [number] junior analysts and review their work
•Advise on the analytics stack, data quality, and privacy-safe collection
•Present to leadership and to the board where relevant
REQUIRED QUALIFICATIONS
•[Number]+ years in product, digital, or behavioral analytics, including
pitfalls, and how to avoid reading noise as signal
•Track record of analyses that changed a product decision, with the specifics
•Ability to influence senior stakeholders without authority
PREFERRED QUALIFICATIONS
•Experience building an analytics function from scratch
•Causal inference beyond A/B testing
•Familiarity with privacy regulation as it applies to behavioral data
CLASSIFICATION AND COMPLIANCE NOTE
Senior analyst roles almost always satisfy an exempt duties test through the
administrative or learned professional exemption, because the work centers on
discretion and independent judgment about matters of significance. Confirm the
salary threshold, and note that highly compensated employees can qualify under a
relaxed duties test at a much higher pay level. Where compensation includes
equity or bonus, document how the guaranteed salary alone meets the threshold.
This is general information, not legal advice.
EEO STATEMENT
[Company Name] is an equal opportunity employer and provides reasonable
accommodations for the essential functions of this role.
COMPENSATION AND HOW TO APPLY
Compensation: $_ to $_ per year, [bonus], [equity], [benefits]
To apply, email __ with your resume and a written example
of an analysis that changed a decision, including what you got wrong.
Template 5: Experimentation and Conversion Analyst
For test-heavy teams: funnel quantification, an experiment backlog with expected impact, decision rules written before launch, and honest reporting of flat results. Pair it with the marketing analyst templates if the role leans toward channel performance.
Experimentation and Conversion Analyst Job Description
EXPERIMENTATION AND CONVERSION ANALYST JOB DESCRIPTION
Company: __ ([City, State] / Remote)
Reports to: [Head of Growth / Head of Product / Marketing Director]
Employment type: Full-time
FLSA status: Exempt (see classification note)
Compensation: $_ to $_ per year
ABOUT THIS ROLE
We run [number] experiments per [quarter] across [signup, checkout, onboarding,
pricing page] and we need someone who can tell us which ones actually worked.
This role sits between design, marketing, and engineering, and it owns the
question of whether a change earned its place.
POSITION SUMMARY
The Experimentation and Conversion Analyst designs and reads tests across the
user journey, quantifies friction in [funnel], and turns conversion analysis
into prioritized design and copy changes.
KEY RESPONSIBILITIES
•Map [conversion funnel] end to end and quantify drop-off at each step
•Build the experiment backlog with expected impact and required sample size
detectable effect, and the decision rule, all written before launch
•Read results honestly, including the tests that lose or come back flat
•Analyze session behavior, form abandonment, and error rates on key flows
•Segment results by device, channel, and new versus returning users
•Maintain a searchable log of every experiment and its outcome
•Report on conversion performance to [stakeholders] [cadence]
REQUIRED QUALIFICATIONS
•[Number] years in conversion, growth, or digital experimentation analytics
•Strong SQL and hands-on experience with an experimentation platform
•Solid grasp of statistical power, sample size, and multiple comparisons
•Ability to say a test was inconclusive and hold that line under pressure
•Experience working directly with designers and copywriters
PREFERRED QUALIFICATIONS
•Bayesian testing experience
•Familiarity with server-side testing and feature flags
•Accessibility awareness in test design
CLASSIFICATION AND COMPLIANCE NOTE
Written as salaried exempt on the administrative exemption, where the primary
duty is analysis directly related to business operations involving discretion
and independent judgment. Two cautions. First, if the role in practice is
executing test configurations to someone else's specification, that is closer to
non-exempt production work. Second, if any part of the compensation is tied to
conversion outcomes, make the bonus rules explicit in writing and confirm that
guaranteed salary alone clears the applicable threshold. This is general
information, not legal advice.
EEO STATEMENT
[Company Name] is an equal opportunity employer and provides reasonable
accommodations for the essential functions of this role.
COMPENSATION AND HOW TO APPLY
Compensation: $_ to $_ per year, [bonus structure], [benefits]
To apply, email __ with your resume and one experiment you
ran that failed, plus what you learned from it.
Template 6: Contract / Fractional UX Data Analyst
For a fixed engagement rather than a permanent seat, with deliverables, acceptance criteria, data handling terms, and a plain warning about worker misclassification.
Contract / Fractional UX Data Analyst Job Description
CONTRACT UX DATA ANALYST SCOPE AND JOB DESCRIPTION
Company: __ ([City, State] / Remote)
Engagement owner: [Founder / Head of Product]
Engagement type: [Project-based / Retainer, ___ hours per month]
Worker status: [Independent contractor / Part-time employee: see note]
Compensation: $_ per [hour / project milestone]
ABOUT THIS ENGAGEMENT
We do not need a full-time analyst yet, but we do need our product data to make
sense. This engagement covers [scope: instrumentation audit, funnel analysis,
dashboard build, experiment framework] over [duration], with a defined
deliverable rather than an open-ended seat.
SCOPE OF WORK
•Audit current event tracking in [product] and deliver a written gap list
•Define and document an event taxonomy [engineering] can implement
•Deliver [number] written analyses on [named questions]
•Set up an experiment template and decision rule the internal team can run
•Hand over documentation and a recorded walkthrough at the end
DELIVERABLES AND TIMELINE
•Week [1 to 2]: tracking audit and gap list
•Week [3 to 4]: taxonomy documented and implementation supported
•Week [5 to 6]: dashboards live and validated
•Week [7 to 8]: written analyses and handover
•Acceptance criteria: [define what "done" means for each item]
REQUIRED QUALIFICATIONS
•Proven product or digital analytics work with references we can call
•Strong SQL and experience with [our stack or comparable]
•Prior contract engagements with clean documentation and handover
•Availability of [hours] per week during [window]
CLASSIFICATION AND COMPLIANCE NOTE (read carefully)
Worker classification is the real risk in this template. Calling someone a
contractor does not make them one. If you set the schedule, direct the method,
supply the tools, and integrate the person into your team indefinitely, that is
an employment relationship in substance regardless of the agreement you signed,
and misclassification exposes you to back taxes, unpaid overtime, and penalties.
Several states apply a stricter test than federal law for their own wage and
benefit rules. A genuine contract engagement has a defined scope, a defined end,
a worker who controls how the work gets done, and a business that serves other
clients. If what you actually want is an ongoing part-time analyst on your
schedule, hire a part-time employee instead and classify the role honestly. This
is general information, not legal advice.
CONFIDENTIALITY AND DATA HANDLING
•Signed confidentiality agreement before any data access
•Access scoped to the minimum data required, revoked at engagement close
•Written commitment to your privacy policy and applicable data regulations
•Work product and documentation assigned to [Company Name]
HOW TO APPLY
Compensation: $_ per [hour / milestone], invoiced [schedule]
To apply, email __ with your rate, availability, and two
comparable engagements with references.
The Skills Worth Requiring
Four things separate a productive UX data analyst from a technically qualified one: SQL at a stated level, instrumentation experience, experiment literacy, and the ability to translate findings into a decision. Everything else on a typical requirements list is either trainable or decoration.
SQL and data handling: require it, at a level
SQL is the floor for this role, and a posting that says familiarity with SQL tells a candidate nothing. Say what you mean: joins and aggregation for a junior role, window functions and cohort queries for a mid-level role, query performance and modeling opinions for a senior one. The same applies to spreadsheets, which remain the most used analytics tool in every small company regardless of what the stack diagram claims. Ask for a work sample rather than a certificate. A candidate who can walk you through a query they wrote, explain why they chose that approach, and name what it would miss has told you more in ten minutes than any credential list.
Instrumentation is the part people forget to ask for
Most postings for this role describe analysis and forget that somebody has to define the events in the first place. If your tracking is incomplete or inconsistent, and in a small product it usually is, then the first six months of this job are taxonomy work: naming events, defining properties, writing the specification engineering implements, and auditing it after every release. That is a distinct skill from querying a clean warehouse. Ask directly whether the candidate has designed an event taxonomy from scratch, and ask what they would do about a metric that changed the week a release shipped. The answer separates people who build measurement from people who only consume it.
Experiment literacy, including the discipline to call a draw
Experimentation is where analyst quality shows fastest, because the failure modes are subtle and expensive. Ask how they size a test, what a guardrail metric is for, what they do when a result is significant on a secondary metric they did not pre-register, and when they would stop a test early. The most valuable answer is the least exciting one: many tests are inconclusive, and an analyst who reports that plainly under pressure from a founder who wants a win is worth more than one who finds a positive result every time. Write the decision rule before launch, in the posting and in practice.
Translation to design, which is the whole point
The output of this role is a decision, not a dashboard. An analyst who produces technically correct work that designers cannot use has failed at the job, and this is the single most common reason a first analytics hire does not work out at a small company. Screen for it directly: give a real anonymized dataset or a short scenario, ask for a written recommendation to a product team, and judge the writing as hard as the analysis. Look for a clear finding, a stated confidence level, an explicit recommendation, and an honest account of what the data cannot tell you. Charts are easy to teach. That structure of thought is not.
Requirement
How to state it in the posting
SQL
Name the level: joins and aggregation, window functions and cohorts, or modeling and query performance
Instrumentation
Say whether the analyst defines the event taxonomy or inherits a clean one
Experiment design
Ask for sizing, guardrail metrics, and a written decision rule, not just familiarity with testing
Analytics stack
List the actual tools, including what is broken; skip the aspirational stack
Communication
Screen with a written recommendation exercise, not a line item in the requirements
Python or R
Preferred rather than required for most roles below senior level
Degree
State the field if it matters; demonstrated work outranks credentials for this role
Remote policy
State it explicitly with time zone overlap; the analyst talent pool is heavily remote
Keep the requirements list short enough that a candidate can tell what actually matters. A posting listing fourteen tools reads as a company that has not decided, and strong analysts treat it as a warning. Our take on skills-based hiring covers how to build the work sample and the rubric that replace most of that list.
Exempt or Non-Exempt
Most UX data analyst roles are exempt, but the title does not decide it and neither does paying a salary. Exemption requires clearing the federal salary threshold of $684 per week, which is $35,568 per year, and satisfying a duties test on the work the person actually performs.
Two exemptions typically apply. The administrative exemption covers office work directly related to business operations where the primary duty includes the exercise of discretion and independent judgment on matters of significance. The learned professional exemption covers work requiring advanced knowledge in a field of science or learning, customarily acquired through prolonged specialized instruction.
Junior Analyst Roles Are the Ones That Get Misclassified
The risk is not the senior analyst who sets metric definitions and influences the roadmap. It is the junior analyst producing scheduled reports to a specification someone else wrote. The Department of Labor treats routine data compilation without discretion on matters of significance as non-exempt work, whatever the salary. If that describes the role you are posting, classify it non-exempt, track hours, and pay overtime past forty in a week. Reclassifying later costs far more than getting it right in the posting.
The Department of Labor sets out the administrative test in Fact Sheet 17C, and it is worth reading before you write the classification line. Our breakdown of exempt versus non-exempt classification works through both tests with small business examples. Several states set a higher salary threshold than the federal one, so confirm yours before posting. This is general information, not legal advice.
What to Pay a UX Data Analyst
There is no Bureau of Labor Statistics occupation for UX data analyst, so no official median exists for the title. Benchmark against the nearest classifications instead, and treat the spread between them as your realistic band rather than picking one number and defending it.
The Nearest Official Benchmarks
According to the Bureau of Labor Statistics Occupational Employment and Wage Statistics survey (May 2025), national median annual wages were $120,230 for data scientists, $105,650 for statisticians, $104,000 for web and digital interface designers, $88,940 for operations research analysts, and $78,760 for market research analysts and marketing specialists. For data scientists, the percentile ladder runs from $67,240 at the 10th percentile to $199,130 at the 90th (U.S. Bureau of Labor Statistics, OEWS national estimates).
Nearest classification
SOC code
National median (BLS OEWS, May 2025)
Why it maps
Data scientists
15-2051
$120,230 per year
Where senior product and behavioral analysts are typically counted
Statisticians
15-2041
$105,650 per year
Closest match for experiment design and inference-heavy roles
Web and digital interface designers
15-1255
$104,000 per year
The digital product side of the role, including UX titles
Operations research analysts
15-2031
$88,940 per year
Analytical problem solving without the product specialization
Market research analysts and marketing specialists
13-1161
$78,760 per year
Where conversion and funnel analysis often lands in survey coding
In practice a UX data analyst prices between the market research analyst and data scientist medians. Junior roles sit near or below the lower figure, mid-level roles in the middle, and senior analysts owning an experimentation program approach or exceed the upper one. Publish the range: pay transparency laws increasingly require it, and experienced analysts skip postings without one. If the role leans toward reporting infrastructure, the business intelligence analyst templates may fit the scope better.
Companies Using FirstHR Onboard 3x Faster
Join hundreds of small businesses who transformed their new hire experience.
Small team analytics hiring fails in three predictable places: the posting is assembled from other companies' listings, the process moves slower than the competition, and the new analyst spends three weeks waiting for data access. Each one has a fix that costs nothing but attention.
You are writing a posting for a role you have never held yourself
The founder or head of product usually writes this job description, and usually without having done the job. The result is a posting assembled from other companies' listings: a wall of tool names, a vague line about data-driven decisions, and no statement of what you actually need answered. Strong analysts screen those out immediately, because the posting signals that nobody has decided what the role is for. The fix is to write the questions before the requirements. Name the three things you cannot currently answer about your product, name your real stack including the parts that are broken, and say whether this person is building measurement or maintaining it. That posting attracts fewer applicants and better ones.
You are competing for analysts against companies with real data teams
Analyst talent is heavily remote and heavily courted, and you will not win on base salary against a company with a fifty-person data organization. Compete on the things a small team genuinely has: direct access to the founder, visible impact on the roadmap within weeks rather than quarters, ownership of the whole stack instead of one dashboard, and a decision timeline measured in days. Say those in the posting rather than saving them for a second interview. Then move fast, because a good analyst in an active search typically has two other processes running, and speed is one advantage a small employer can actually spend.
The hire lands and spends three weeks waiting for access
An analyst without data access is an expensive observer. The first month of this role is decided before the start date by two things: access and context. Access means accounts in the product database, the analytics platform, the BI tool, the CRM, and the ad platforms, all provisioned on day one with someone accountable for each approval. Context means the questions leadership cares about, who owns which numbers today, and the spreadsheets currently running the business, handed over deliberately rather than discovered by archaeology. FirstHR runs that as a repeatable workflow: task workflows for each access-granting step across your systems, e-signature for the confidentiality and IP agreements that must be signed before any data access, and document management holding the signed records against the employee profile. Applicant tracking is coming soon to FirstHR.
Once the offer is signed, the work shifts to a repeatable onboarding template, and for a data role specifically the access sequence matters more than anything else. Our guide to IT onboarding covers provisioning accounts and permissions so day one is productive rather than administrative.
Key Takeaways
A UX data analyst answers what users did at scale; a UX researcher answers why. Hiring one while expecting the other is the most expensive mistake in this category.
At a company without a data function, the first months of this role are instrumentation work, so say in the posting whether the analyst defines the event taxonomy or inherits a clean one.
Four requirements matter: SQL at a stated level, instrumentation experience, experiment literacy including the discipline to call a draw, and translation into a decision a designer can use.
Most analyst roles are exempt, but exemption needs both the $684 per week federal salary threshold and a duties test; junior roles producing routine reports are the ones most often misclassified.
No BLS occupation matches the title, so benchmark against the nearest classifications (BLS OEWS, May 2025): $78,760 for market research analysts up to $120,230 for data scientists.
Screen with a short written recommendation exercise scored against a fixed rubric, and provision every data account before the start date so the first month is analysis rather than waiting.
An analyst hire lives or dies on what happens before day one. FirstHR runs the same onboarding sequence every time, with e-signature on confidentiality and IP agreements, task workflows for each data access approval across your systems, and document management holding the signed records against the employee profile. Applicant tracking is coming soon to FirstHR.
Frequently Asked Questions
What does a UX data analyst do?
A UX data analyst measures how people actually use a product and turns that behavior into decisions the design and product teams can act on. The day-to-day work is defining and auditing the event taxonomy that describes user actions, building funnel, activation, and retention reporting, analyzing where users stall or abandon a flow, designing and reading experiments, and presenting findings to people who do not write SQL. The role sits between analytics and design, which is what distinguishes it from a general data analyst working on revenue and operations reporting. At a small company the same person usually owns instrumentation as well as analysis, because there is nobody else to define the events in the first place, and that combination should be stated plainly in the posting.
What is the difference between a UX data analyst and a UX researcher?
A UX data analyst answers what people did; a UX researcher answers why they did it. The analyst works in behavioral data at scale: events, funnels, retention curves, experiment results, and session patterns, using SQL and analytics tooling. The researcher works with people directly through interviews, usability sessions, diary studies, and surveys, producing motivation and meaning that no event log contains. They are complementary rather than interchangeable, and hiring one expecting the other is a common and expensive mistake at small companies. If you need to know that 41 percent of new accounts abandon setup, hire the analyst. If you need to know why, hire the researcher. Teams that can only afford one hire should choose based on which question is currently blocking decisions.
Is a UX data analyst exempt or non-exempt under the FLSA?
Usually exempt, but the title does not decide it and neither does paying a salary. Exempt status requires clearing the federal salary threshold of $684 per week, which is $35,568 per year, and satisfying a duties test, most often the administrative exemption for work directly related to business operations involving the exercise of discretion and independent judgment on matters of significance, or the learned professional exemption. Senior analysts who set metric definitions, own an experimentation program, and influence roadmap decisions clearly meet that standard. Junior analysts producing routine reports to a specification set by someone else may not, and those roles are the most commonly misclassified in analytics. Several states set a higher salary threshold than federal law, so check yours. This is general information, not legal advice.
How much does a UX data analyst make?
There is no Bureau of Labor Statistics occupation for UX data analyst, so benchmark against the nearest classifications rather than a single number. According to the Bureau of Labor Statistics Occupational Employment and Wage Statistics survey (May 2025), the national median annual wage was $120,230 for data scientists, $105,650 for statisticians, $104,000 for web and digital interface designers, $88,940 for operations research analysts, and $78,760 for market research analysts and marketing specialists. A UX data analyst role typically prices between the market research analyst and data scientist medians, with juniors near or below the lower figure and senior analysts owning an experimentation program approaching or exceeding the higher one. The data scientist percentile ladder runs from $67,240 at the 10th percentile to $199,130 at the 90th, which shows how wide the real range is. Adjust for your market and remote policy, and publish the range.
Do I need a UX data analyst or can my designer handle analytics?
Ask what you need answered before you decide. A designer can read a dashboard someone else built and can run simple usage checks, and at very early stage that is often enough. What a designer generally cannot do is define an event taxonomy, validate that tracking survived the last release, size an experiment correctly, or defend a metric definition to leadership. If your questions are currently unanswerable because the data is missing or untrusted, that is an instrumentation problem and it needs an analyst. If the data exists and is trusted and you simply need someone to look at it more often, you may not need a full-time hire yet. The contract template on this page exists for exactly that middle case: a defined engagement that builds the foundation without adding a permanent seat.
What should I ask for in a UX data analyst work sample?
Give a realistic scenario and judge the writing as hard as the analysis. A good work sample is short: hand over an anonymized or synthetic dataset with a real-shaped question, such as why activation dropped after a release, and ask for a one-page written recommendation aimed at a product team rather than a technical audience. Look for four things in the response: a clear finding stated up front, an explicit confidence level, a concrete recommendation, and an honest statement of what the data cannot tell you. Candidates who produce technically correct work that a designer cannot use are the most common failure mode for a first analytics hire. Keep the exercise under two hours, pay for it if it runs longer, and use the same scenario for every candidate so the comparison is fair.
How do I hire a UX data analyst without an HR department?
Run a fixed, short sequence and prepare the start date before you make the offer. Write the posting around the questions you need answered and your real stack rather than a wall of tool names. Screen with a two-hour work sample scored against a written rubric. Interview for translation ability by asking the candidate to explain a past analysis to you as if you were a non-technical stakeholder. Check references from a product or design partner who consumed their work, not only from a manager. Then close fast, because analysts in an active search usually have parallel processes running. Before day one, provision data access across every system and prepare the context handover. FirstHR handles the onboarding side: e-signature on confidentiality and IP agreements, task workflows for each access approval, and document management with the signed records on the employee profile. Applicant tracking is coming soon to FirstHR.
