UX/UI designer
You see where users get stuck, build the system in Figma, and hand it off clearly to engineering.
4,000,000–25,000,000 UZS / mo
- Income
- 4,000,000–25,000,000
- Education
- A degree is not required — a portfolio
- Core skills
- Figma · Flow · Case
- Work format
- Office / hybrid; remote needs a portfolio and written English
Income
4M–25M UZS / mo
Education
A degree is not required — a portfolio
Work format
Office / hybrid; remote needs a portfolio and written English
Career path
UI → product designer → lead / research
01
UX designs the path, UI the system. Hiring filters on a case study, not a Dribbble shot.
02
There is no official designer salary series. The role sits inside IT/agencies; do not copy the programmer median.
03
Figma is the core tool, but without research and handoff you stay a “drawer.”
UX and UI — two jobs, one seat
UX designs how a person reaches a goal: conversation, scenario, flow, wireframe. UI is the screen’s visual system: type, color, components, states (empty, error, loading).
In a product team both often sit in one person. In an agency you may “just draw a UI kit.” Graphic design (banners, brand books) is another job — a transfer is possible, but the muscle is different.
A fit if you watch people, accept tradeoffs, and hand engineers a clear brief. A poor fit if you only want “pretty” and hate critique.
Education and growth
A degree is not required. A course (offline Tashkent or Interaction Design Foundation) is a tool. Books: Don’t Make Me Think; official Material / HIG.
Growth: product designer, design lead, UX research, or closer to frontend. From graphic design: flow first, gradients later.
How the work usually goes
01
Read the brief and constraints
02
Wireframe / flow
03
UI and states in Figma
04
Handoff to engineering
Where the work happens
- Product team (fintech, marketplace)
- Agency: speed and visuals
Roadmap
- 01
The tool
Figma: auto-layout, components, variants, proto. Official docs are free. Two weeks of drills.
- 02
Not a copy — a teardown
Open a local app (Click, Uzum, MyGov): where is the friction? Write a one-page teardown.
- 03
Three cases
Mobile + web. Problem, three options, the choice, a proto, what changed. Not a Behance shot.
- 04
A team
One real task with a developer or PM. Mentorship, junior, agency.
Skills
Must-have
- Figma
- Flow, states, components
- Turning a problem into a written case
Useful
- WCAG: contrast, focus, text size
- A short user interview
Later
- Owning a design system
- UX research
Tools
Figma + FigJam (or Freeform)
Component library / design system
Maze, Useberry, or a plain interview recording
WCAG basics: contrast, focus, text size
Income range
4,000,000–25,000,000 UZS / mo
Editorial range•2026 figures•O‘zbekiston (Toshkent va hududlar)
Note: The salary range is an analytical estimate; actual compensation depends on candidate experience, portfolio, language skills, and employer level.
Sources and method
- No official designer salary; the ICT mean does not describe this role
- Figures draw on 2026 sources: Uzbekistan National Statistics Committee (official sector averages, Q1/H1 2026), Flexa and hh.uz vacancy medians, and public IT Park / product-team guides. Not a guarantee — contract type, city, tax, and level change the range. Compare live vacancies yourself.
The Uzbekistan market
Search: hh.uz “UI/UX”, “product designer”, Telegram, LinkedIn, agency books. Language: Figma in English, briefs in Russian/Uzbek. Product (fintech, marketplace) asks for a system and research; agencies ask for speed and visuals.
No official standalone salary. The ICT mean does not describe designers. Junior ads often sit near the programmer mode (8M) or below — compare. English adds leverage in product/outstaff.
Remote: a foreign team wants a portfolio, written English, and overlap. Dribbble alone is not enough.
Portfolio ideas
A real flow: list to payment
Empty, error, and loading states
First job
- Three cases you can explain — not a Dribbble screenshot
- One real task with a developer or PM
Who it fits
May be a good fit
- You write the problem before you draw
- You accept constraints (time, stack, accessibility)
May be a harder fit
- Only dark fancy shots
- No states — “I did Dribbble”
Common mistakes
- Only dark fancy shots, no states
- Handing in an AI sketch without seeing a user
Where AI helps
Where AI helps
- Speeding a sketch and variants
Human responsibility remains
- Problem, choice, accessibility, handoff
- Image rights and system integrity
FAQ
UI is not painting. Type, grid, and contrast are learned. A hand sketch helps; it is not required.