Lakshya

Product Design & UX

UX Researcher

Design · evidence over opinion

The person whose job is to find out that the thing everyone believes is not true.

The person whose job is to find out that the thing everyone believes is not true.

A day that is actually representative

TimeWhat you are actually doing
09:30Writing a screener, because the wrong participants make the whole study worthless.
11:00Moderating. The skill is silence — most researchers talk far too much.
13:30Analysis with someone else, because a single coder finds what they expected to find.
15:00Presenting a finding that contradicts a decision already made.
16:30Building a repository so the next person does not re-run this study in a year.

The decisive round

“Your research contradicts a decision leadership has already made.”

Interviewer: “The roadmap is committed. What do you do?”

A weak answer. “I'd present the findings clearly and objectively and let the data speak for itself, and trust leadership to make the right call with the new information.” 'Let the data speak' is what researchers say before being ignored. Data does not speak; it gets interpreted by whoever is most invested in the existing decision.

A strong answer. “First I'd interrogate my own study honestly, because contradicting a committed decision has a high evidential bar and it should. How many participants, how were they recruited, could the finding be an artefact of my task design? If I found this in five sessions with people recruited from our own power users, I should say so.

Then I'd separate what I know from what I infer. 'Eleven of fourteen participants could not complete the primary task without help' is an observation. 'We should not build this' is a recommendation, and mixing them is how research gets dismissed as opinion.

Then I'd go to the decision-maker privately, before any group setting. Nobody changes their mind in a room with their peers watching. And I'd frame it as risk rather than as error: 'The plan may still be right, and here's what would have to be true for it to work. My data suggests it isn't. Here's the cheapest way to find out before we spend two quarters.'

Then I'd offer a path that isn't 'stop'. Ship it to 5%, instrument the specific behaviour, and set the threshold now. Leadership will accept a test far more readily than a reversal, and a test they agreed to in advance is one they'll act on.

And if they proceed anyway — which happens and is sometimes correct, because they know things I don't — I'd write it down with the prediction and the date. Not to be proved right, but because the second time research is ignored and turns out to have been right, the third study gets taken seriously.”

Auditing your own study first, separating observation from recommendation, going privately, and offering a test rather than a reversal. The written prediction is the move that builds a research function's standing.

What to build or bring

  • A study that changed a decision, and the mechanism by which it changed it.
  • A study that was ignored, and what you learned about your own framing.
  • Your screener and discussion guide — the craft is visible here.
  • Both qual and quant. Survey design and basic statistics are increasingly expected.

Compensation

MarketBandNotes
United States$120k – $190kFewer roles than product design, and more competitive
India₹14L – ₹38LSmaller market; strongest at GCCs and large product companies

The book for this field

Product Design & UX

What design postings ask for, designing for systems that are sometimes wrong, research at real sample sizes, design systems and accessibility, and the portfolio review that decides the loop.

CHAPTER 3Research at the sample sizes you actually getExpected in 83% of postings, and almost never with the sample size the textbooks assume.READ THE CHAPTER →CHAPTER 1What design postings ask for185 postings, and AI appears in 93% of them — the highest share of any field measured here.READ THE CHAPTER →CHAPTER 5The design loop and the portfolioThe portfolio review decides it, and it is judged on reasoning rather than on visuals.READ THE CHAPTER →

All 5 chapters in Product Design & UX →

Cross-cutting

Skills every archetype tests

These are shared across every field on this site — the same question asked in different vocabulary — so preparation here compounds rather than being spent once. The book above is specific to your field.

The controlOne habit separates strong candidates from plausible ones more reliably than any technical depth.READ THE CHAPTER →Measuring what resists measurementTested in every field on this site under a different name — evals, SLOs, DORA, ablations. Named in 59% of AI and 42% of platform postings, and almost nobody studies it deliberately.READ THE CHAPTER →Discovery before solutionThe decisive round in three separate archetypes, with the lowest pass rate of any stage.READ THE CHAPTER →

Practice the 10 Design questions →  ·  Back to Product Design & UX →