Lakshya

Product Design & UX

Product Designer

Design · the core title

End-to-end: the problem, the flow, the interface, and the argument for why it should be this one.

End-to-end: the problem, the flow, the interface, and the argument for why it should be this one.

A day that is actually representative

TimeWhat you are actually doing
09:30Sitting in on a support call. The cheapest research there is and the most skipped.
11:00Flows on paper before pixels, because the expensive mistake is structural.
13:30A critique where the useful feedback is about the problem framing, not the spacing.
15:00Working through the states nobody asks for: empty, loading, error, too much data, offline.
16:30Sitting with the engineer who has to build it, before it is 'finished'.

The decisive round

“Walk me through a project.”

Interviewer: “Take one from your portfolio.”

A weak answer. “The team wanted to redesign onboarding. I did competitive research, created user personas, mapped the journey, produced wireframes and then high-fidelity designs, ran a usability test, and we shipped. Completion went up.” A process recital. Every designer does these steps, so listing them differentiates nothing, and 'completion went up' with no number is the tell that it was never measured.

A strong answer. “Our onboarding completed at 34%, and the assumption in the company was that it was too long — seven steps — so the brief I was given was 'make it shorter'.

I pushed back on that brief for a week, which is the part of this project I'd defend hardest. I watched twelve session recordings, and people weren't dropping out from fatigue — they were dropping out at step three, which asked them to connect a data source. They didn't have the credentials. They weren't the person who had them.

So the problem wasn't length. It was that we'd designed a flow for one person when the job needed two.

What I designed: step three became skippable, with a 'send this to your admin' path that generated a link. Everything after it worked in a sample-data mode so the product was usable before the connection existed. That's a harder build than deleting steps, and I had to argue for it.

Completion went to 61% over six weeks. But the number I care more about is that week-two retention went up more than completion did, because the people who now got through were people who could actually use it, not people we'd pushed through a shorter funnel.

What I got wrong: my first version of the admin hand-off email was written by me, and it was terrible — a 4% click rate. Our lifecycle marketer rewrote it and it went to 19%. I should have brought her in at the start.”

Rejecting the given brief with evidence, a redesign that was harder rather than easier, a second-order metric, and a genuine mistake with someone else credited. This is the answer that gets a design hire.

What to build or bring

  • Three case studies, deep rather than pretty. Problem, evidence, what you rejected, what you shipped, what it did, what you got wrong.
  • Show the states nobody shows — empty, error, loading, permission-denied. Senior reviewers look for these first.
  • Bring the research artefact, not just the conclusion.
  • Be ready for a live exercise — 45 minutes on a problem you have not seen, thinking out loud.

Compensation

MarketBandNotes
United States$120k – $200kHigher at product-led companies
India₹15L – ₹45LStrong and growing at product companies and GCCs

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 2Designing for systems that are sometimes wrongNamed in 93% of postings. The genuinely new design problem, and almost nobody's portfolio shows it.READ THE CHAPTER →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 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.

Discovery before solutionThe decisive round in three separate archetypes, with the lowest pass rate of any stage.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 →The controlOne habit separates strong candidates from plausible ones more reliably than any technical depth.READ THE CHAPTER →

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