Skip to main content
🎨

Product Designer Interview Prep — UX, portfolio, design critique — for designers in Tashkent and Central Asia

Product design interviews stand on three legs — portfolio walkthrough, live design critique, and a take-home or whiteboard exercise. Practice each on NextSuhbat with real-time AI scoring on communication, design reasoning, problem framing, and stakeholder alignment.

Product designers in Tashkent are hired by IT Park residents, fintechs, and an increasing number of EU remote employers who pay specifically for designers fluent in user research and Figma autolayout — not for visual styling. The bar has moved away from “here is a beautiful screen” toward “here is the problem I framed and the tradeoff I made.”

The questions below are pulled from real Tashkent design interviews. Practice them out loud — most designers underestimate how much of the interview is verbal storytelling rather than visual portfolio.

Core skills tested

  • Figma fluency — autolayout, components, variables, tokens
  • User research basics — interviewing, usability tests, synthesis
  • Information architecture and flow modeling
  • Visual fundamentals — type scale, spacing, contrast, motion
  • Working with engineers — handoff hygiene, design tokens
  • Writing UX copy that respects the user
  • Critiquing your own and others' designs without ego
  • Telling the story of a project in three minutes

Salary ranges in Tashkent (2026)

Approximate. Remote-first European roles typically pay 30–50% above local rates.

Junior

7–11M UZS / month

Mid-level

15–22M UZS / month

Senior

28M+ UZS / month (or EUR remote)

What you will actually be asked

Pulled from real interviews recorded on NextSuhbat. Each item is a question you should expect, plus what the interviewer is really testing.

  1. 1

    Recruiter screen

    Walk me through the project you are most proud of in three minutes.

    Why it is asked: Tests storytelling. Lead with the user problem, not the visuals. End with the metric that moved.

  2. 2

    Technical

    How would you redesign the onboarding for a fintech app with a 35% drop-off on KYC?

    Why it is asked: Tests problem framing. Strong answers ask for context first — what counts as drop-off, who is dropping, why.

  3. 3

    Technical

    Show me one screen from your portfolio and walk me through every spacing decision.

    Why it is asked: Tests autolayout discipline. Designers who hand-place everything fail this question fast.

  4. 4

    Technical

    Critique this screen out loud.

    Why it is asked: Live critique. Order matters: hierarchy, accessibility, copy, edge cases, then visual polish. Skip "I would change the color" first.

  5. 5

    Technical

    How do you balance design system compliance against shipping speed?

    Why it is asked: Tests judgment. Strong answers cite specific tradeoffs — when to override a token, when to escalate.

  6. 6

    Coding

    Walk through how you would structure a Figma file for a multi-team product.

    Why it is asked: Pages, components, variants, tokens, branching. Real working-file hygiene.

  7. 7

    Coding

    Build a responsive card component in Figma with autolayout — title, body, CTA.

    Why it is asked: Tests autolayout fluency. Should take five minutes, not twenty.

  8. 8

    System design

    Design the flow for a user adding a friend via phone number, with privacy edge cases.

    Why it is asked: Cover permissions, contact import, cold start (no friends found), error states, and the “maybe later” path.

  9. 9

    Behavioral

    Tell me about a time engineering pushed back on a design and you changed your mind.

    Why it is asked: Tests humility. Pick a real moment, frame the engineer as right, mention what you learned.

  10. 10

    Behavioral

    Tell me about a project that shipped and underperformed.

    Why it is asked: Wrong answer: never happened. Right: what you assumed, what was wrong, what you would do differently.

Practice these questions out loud — for free

Reading is not practice. Run a 20-minute AI mock interview in English, Russian, or Uzbek and get a scorecard against communication, technical depth, problem-solving, and cultural fit.

Start free mock interview

Built in Tashkent for Central Asia. All practice sessions support English, Russian, and Uzbek voice.