1. LandOffer
  2. Blog
  3. All articles
  4. UX Researcher Jobs: Check Qualitative, Quantitative, and Mixed-Methods Requirements

Job search

UX Researcher Jobs: Check Qualitative, Quantitative, and Mixed-Methods Requirements

Read actual research requirements, separate required methods from preferred tools, and build an evidence packet that preserves ownership and method gaps.

9 min readLandOffer team

“Mixed methods” in a UX Researcher title can still mean independently designing surveys, choosing samples and analyzing uncertainty. A portfolio built around interviews may demonstrate valuable work while leaving those responsibilities unproven. Before adapting an application, identify which study decisions and outputs you would personally own.

This guide checked public role descriptions on October 21, 2026. It compares two currently displayed employer postings and one explicitly closed historical listing; it does not establish a market-wide hiring pattern. LandOffer publishes this guide and offers job-search tools. You can browse recent roles while keeping the method requirements beside your own evidence.

Separate interview, survey and study-planning objects illustrate different research responsibilities.

Read the research responsibility behind the label

Qualitative work can investigate how people understand a workflow, what they try, and where their expectations conflict with the interface. A credible example explains recruitment, the discussion or task guide, observation, analysis and the connection to a product decision. A case study made only of quotations leaves recruitment, analysis and recommendation decisions unexplained.

Quantitative work can involve defining a measure, building a survey instrument, evaluating a sample, auditing behavioral data and selecting an appropriate analysis. An attractive chart does not establish that you designed the question or checked the denominator. State whether you owned those choices, contributed to them or received an already prepared dataset. That distinction helps you choose a defensible work sample before rewriting your resume around the advertised method.

Mixed-method work joins evidence to answer a research question. It might use interviews to develop a survey, or follow a behavioral pattern with a qualitative investigation. Merely placing an interview slide next to a dashboard does not explain how the findings informed one another.

These are ways to inspect responsibilities, not fixed boundaries around every researcher. The same study can involve a researcher, designer, analyst and data scientist. Your application should explain your own decisions and the dependencies that remained with colleagues.

Worked audit: required skills, preferred depth and actual availability

The following completed comparison uses the public descriptions we actually read. The sample was chosen to clarify different requirements, not estimate demand or rank employers. The historical entry is deliberately retained as a closed example rather than recommended as an opening. The two employer pages displayed their full descriptions and application forms during inspection; we did not submit either form. Their continued availability after this check remains unverified.

Source and observed status Method responsibility in the description Completed reading decision
onX, Senior UX Researcher, Mixed Methods, public role displayed Independent qualitative and quantitative studies; survey design, sampling, data quality, descriptive and inferential analysis. R/Python and advanced statistics appear among additional bonuses. Quantitative work is substantive even though particular tools and advanced techniques are bonuses. Check its location restrictions and quarterly travel separately.
OneTrust, Senior Quantitative UX Researcher, public role displayed Required survey-method depth, statistical fluency and SQL plus R or Python. Enterprise experimentation is preferred; the role also audits measurement. An interview portfolio or a dashboard alone would leave major required responsibilities unproven. Verify the Atlanta role's office expectations.
The Mom Project, Qualitative UX Researcher, explicitly Job closed Historical contract description emphasizes independent qualitative studies and vendor management. Broad preferred-skill tags also include quantitative research. Read the detailed responsibilities instead of treating every tag as an equally specific requirement. Do not count this closed listing as a current lead.

The onX description requests work samples demonstrating independent mixed-method execution and integration. Its application asks what the applicant personally owned and which quantitative analysis they performed. That is stronger evidence of the expected scope than the title alone. The published experience requirement is eight relevant years, including at least five in UX, product or consumer research; this is a senior example, not an entry-level template.

OneTrust places sampling limits, nonresponse, scale construction and practical statistical methods in its required section. It lists six or more relevant years, including complex enterprise software. Graduate training and enterprise experimentation are preferred. Keeping those categories separate prevents two mistakes: assuming all quantitative experience is optional, or declaring every preferred credential a universal gate.

The closed qualitative listing also illustrates why current availability must be checked independently of search excerpts. We found other indexed research titles whose original pages no longer supplied that job. A cached description can explain historical wording, but it cannot establish that applications are currently open.

A survey, an experiment and an interview answer different questions

When a description mentions surveys, ask what the researcher must design. Writing questions, selecting response scales, defining the population, evaluating missing responses and interpreting results are distinct tasks. Entering questions into a survey tool does not establish ownership of all of them.

An experiment introduces another set of questions: who defines the intervention, assigns conditions, checks implementation and chooses the analysis? A researcher may collaborate with a product analyst rather than own every step. Do not interpret “quantitative” as proof that randomized experiments are the central responsibility, especially when a role emphasizes observational measurement or surveys.

For interview work, inspect how sessions were selected and analyzed. What did the guide seek to learn? Which observations supported the interpretation? What alternative explanation remained? A polished story needs enough of that reasoning for a reviewer to understand how you reached the recommendation.

The comparison also affects portfolio selection. A moderated usability study can be strong evidence of study design and synthesis while providing little evidence of regression modeling. A statistical notebook can demonstrate analytical work while leaving participant recruitment, consent and moderation unexplained. Preserve both strengths and gaps instead of renaming the project to match every advertised method.

Worked evidence packet: an honest mixed-method gap

This second original asset is entirely fictional. Sora is an invented researcher with three years of qualitative product research. The stipulated history includes interview guides, usability sessions and synthesis, but no independently owned survey sampling or inferential analysis. None of the following records describes real participants, a customer study or an employer assignment.

Sora completes this application-preparation record:

Available evidence in the fiction Claim Sora can support Remaining limit
A permitted case study with a screener, task guide and annotated observations Designed and moderated the documented usability study Does not establish survey design or statistical inference
A synthesis memo showing competing interpretations and an adopted design question Connected observations to a product recommendation Adoption of a question is not proof of improved product outcomes
A team dashboard built by an analyst Used an existing metric to frame follow-up research Did not define its instrumentation, sampling or analysis
The independent synthetic exercise below Practiced joining qualitative codes with descriptive records No recruited sample, fieldwork, validated instrument or production impact

Sora's completed portfolio introduction reads: “My strongest evidence is qualitative study design, moderation and synthesis. I used an analyst's existing dashboard to identify follow-up questions; I did not own that dashboard's measurement design. The separate teaching exercise below demonstrates how I document conflicting signals and missing data. It is not professional mixed-method fieldwork.”

The immediate decision is to prioritize descriptions that explicitly value those demonstrated responsibilities. The two senior employer examples above remain comparisons for identifying gaps, not confirmed matches. Sora will not claim independent quantitative fluency or the years of experience these specific descriptions request.

A synthesis desk keeps qualitative notes, a small bounded sample and a qualified decision memo separate.

Complete the teaching exercise without inventing fieldwork

Sora invents a document-sharing product in which a person chooses whether a link permits viewing or editing. The question is: which parts of the permission choice need further investigation? The completed interview guide contains three neutral prompts: “Show how you would share this document”; “What do you expect the recipient can do?”; and “What would you check before sending?” No session was conducted.

The codebook has two defined codes. Permission uncertainty marks an explicit mismatch or uncertainty about recipient capabilities. Navigation friction marks difficulty finding the relevant control. A record may receive both codes, and neither code implies how common the problem is among actual users.

Here is the complete synthetic joint display. The clarity rating is an invented one-to-five item, with five meaning clearer; it is not a validated UX scale. The quoted statements are original fictional text, not participant quotations.

Invented record Fictional statement and applied code Clarity response Integrated interpretation
A “I cannot tell whether they can edit.” Permission uncertainty 1 Low stated clarity and explicit permission uncertainty point to a follow-up question.
B “I found the button, but I am unsure what the link allows.” Permission uncertainty 2 Finding the control did not resolve the permission question.
C “I looked in the menu twice.” Navigation friction Missing Keep the observation and the missing rating; do not invent a response.
D “The permission is clear, though the control took a moment to find.” Navigation friction 4 A higher clarity rating can coexist with navigation friction.
E “I checked the recipient can only view.” No code assigned 5 One clear invented response does not disprove uncertainty in other records.

An original local Python check was actually executed against these five fabricated records. It found four valid ratings, one missing rating and two valid ratings at or below two. A within-fixture calculation is two out of four valid ratings, or 50%. That denominator excludes the missing item only for this descriptive calculation; the fifth record remains in the joint display. Coding is separate from rating completeness: A and B receive permission uncertainty, C and D receive navigation friction, and E receives neither. No single overall success score is calculated.

The check rejected three deliberately wrong readings: treating the missing rating as zero, reporting all five records as valid responses, and saying a successful structural check establishes a representative sample. It tests our finite synthetic records, not a survey platform, an employer assessment or a research finding about real people.

Sora's finished synthesis memo states: “The fabricated records distinguish permission uncertainty from navigation friction. Record D cautions against treating every navigation complaint as low permission clarity. Preserve C's missing response. A future real study would need an appropriate recruitment plan, instrument review and analysis plan. These invented counts establish neither prevalence nor a causal effect. The immediate output is a better question for study design, not approval to ship a change.”

That memo shows the intended integration: the invented observation in D qualifies how its higher rating should be read. It does not establish that Sora has conducted mixed-method research with people. A toy exercise can make reasoning inspectable while the experience gap remains explicit.

Choose evidence before choosing another course

For each shortlisted role, write down the required action, the artifact that demonstrates it, your personal ownership and the unresolved gap. Finish with one decision: prepare a relevant permitted example, clarify an uncertain responsibility, or leave that role for later. A gap record is useful even when it rules out tailoring another application today. Distinguish required methods from preferred tools, and treat seniority, location and work arrangement as separate questions. A remote label does not resolve state restrictions or travel requirements.

If the missing evidence is survey design, identify the specific part you have not owned before buying broad interview preparation. If it is qualitative synthesis, a new SQL certificate may do little to address it. Learning can develop a capability; completing a course does not retrospectively create professional fieldwork or independent ownership.

Use your own permitted work in an actual application. Keep synthetic examples labeled, retain colleague contributions, and describe recommendations separately from measured outcomes. Review recent roles on LandOffer with those evidence records in hand, then pursue the work you can describe accurately.

Sources and Further Reading