Software developer
You turn a business question into working software. Hiring looks at shipped code, not a course certificate.
5,000,000–40,000,000 UZS / mo
- Income
- 5,000,000–40,000,000
- Education
- University or course + portfolio
- Core skills
- Git · SQL · JS/Python
- Work format
- Office / hybrid; fully remote junior seats are rare
Income
5M–40M UZS / mo
Education
University or course + portfolio
Work format
Office / hybrid; fully remote junior seats are rare
Career path
Junior → middle → senior
01
A developer turns a business question into working software. Hiring filters on shipped work, not course certificates.
02
In 2026 vacancies the programmer median is about 10.1M UZS and the most common offer about 8M; the official ICT average (~17.4M) answers a different question.
03
In Tashkent a first role is usually below the vacancy median; growth accelerates after the first commercial projects. English adds leverage on foreign-client teams.
What a software developer does
A software developer writes programs that run on a computer, phone, or server. The job is not “how to type code” — it is understanding a fuzzy request, splitting it into testable pieces, and shipping a working solution with a team.
In Uzbekistan the role most often means web (sites and admin panels), mobile apps, banking/fintech systems, or building software for another company (outsource/outstaff). “IT” is a wide label: testers through DevOps land in the same official average. Do not read the ICT sector mean as your junior offer.
The work fits people who can turn ambiguity into a written plan, hunt their own bugs, and want others to read their code. It is a poor fit if you only want “sitting at a laptop” or a fast-wealth story: year one is practice, rejections, and small tickets.
Specializations
Tracks that show up often in Uzbekistan vacancies in early 2026 (public boards and IT Park teams). Not a complete list.
| Track | What you do | Entry note |
|---|---|---|
| Frontend | UI in the browser, Figma to HTML/CSS/JS | React/Next.js is common in ads; portfolio is visible |
| Backend | APIs, data, payments, queues, security | Node/Nest, Java/Spring, Python; SQL is expected |
| Mobile | iOS/Android or Flutter/React Native | Flutter is common locally; native often pays more |
| QA automation | Writes tests, catches regressions | Wider junior door; then move to automation |
| DevOps / SRE | CI/CD, servers, observability | Narrow junior door; pay can be higher later |
| Data / ML | Pipelines, models, analytics infra | Start with SQL and Python; do not grab the ML-engineer title early |
How long it takes
At 1–2 hours a day, “ready for a job” often takes 9–18 months. Full-time intensity can be 4–8 months, but burnout is easy. Parallel with school is often 1.5–2 years. That is an average, not a promise: prior Excel/math or English shortens it; watching videos only lengthens it.
Learning does not stop at the offer. Year one on the job is the real course.
Interviews and typical questions
Local product: live coding (arrays, strings), SQL, “walk through your last project,” sometimes a real bug instead of system design. Outsource: an English self-intro, algorithms, sometimes a take-home.
Questions: let vs const; HTTP 401 vs 403; why an index; how you would see a race; why that database. Answer short, then an example. If you do not know — say so, and say how you would look it up.
Do not turn a take-home into six hours of free work. Ask the timebox, write a README.
English, education, certificates
English: docs, error text, Stack Overflow. B1 can be enough for a local team; foreign outstaff usually interviews at B2+. IELTS is not required.
University helps (math, networks, a diploma filter in some banks) but is not mandatory. INHA, WIUT, TUIT, and specialist centers are different roads. A course (Najot Ta’lim, PDP, and others) is a tool; employers ask about the final project.
AWS/GCP certs rarely help a junior. FreeCodeCamp or an official language cert is optional. GitHub activity speaks louder.
The international path
Three paths: 1) remote from Uzbekistan (currency, tax, and a contract with a lawyer); 2) outstaff onto an EU/US team; 3) relocation (visa and work permit — that country’s law). Do not convert a US/EU salary at the FX rate and say “I should get that” — the market, tax, and costs differ.
To compete: Git, tests, written English, overlapping hours, security basics. LeetCode appears in some foreign loops; less often in local product. Portfolio and referrals still travel.
Future, risks, myths
Demand is not vanishing, but the junior door can narrow because AI shrinks simple tasks. Risks: burnout, sitting injuries, always-on culture, sticking to one stack, working without a contract.
Myths: “$2000 in six months”; “a degree is mandatory”; “no algorithms, no job”; “AI replaces everyone.” Reality: time, a portfolio, a team, reading the market.
A typical workday
09:30
Daily standup
Yesterday, today, blockers — 10–15 minutes.
10:00
Focused work
A feature or a bug: the request, code, self-test.
13:00
Lunch
14:30
Code review
PR notes or pair-debug.
16:00
QA or a short sync
17:30
Merge a PR or plan tomorrow
Where the work happens
- Local product team (IT Park, fintech, marketplace)
- Outsource / outstaff team
- Small studio or startup
Career path
01
Junior
Small tickets under review; 0–2 years commercial.
02
Middle
Owns a feature, estimates, reviews others.
03
Senior / lead
Architecture, risk, mentoring, production ownership.
Roadmap
- 01
Months 1–2: foundation
HTML/CSS, Git, language syntax. A small exercise every day. Watching videos is not learning — write code.
- 02
Months 3–5: first project
A CRUD app: list, edit, delete. Write to a database. Deploy it (Render, Railway, or a simple VPS).
- 03
Months 6–9: simulate a team
A second project + tests + README. A PR in OSS or with a friend. A resume and 20 applications — do not wait for a perfect portfolio.
- 04
Months 10–18: first job
Internship, junior, or a modest first offer. A team with code review beats a loud brand name.
Skills
Must-have
- One language in depth (JS/TS, Python, or Java)
- Git and code review
- HTTP basics and debugging
- SQL: tables and JOIN
Useful
- Linux basics, logs, ssh
- Written English
- Writing tests
Later
- Docker, Kubernetes
- System design
Tools
Git + GitHub/GitLab: branch, PR, conflict
VS Code or JetBrains + a debugger (console.log is not your only tool)
Browser DevTools or Postman/Insomnia
PostgreSQL or MySQL — past a simple SELECT/INSERT
Linux basics: folders, logs, ssh (Docker later)
Income range
5,000,000–40,000,000 UZS / mo
Vacancy median•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
- Flexa: programmer vacancy median ~10.1M, mode ~8M (Jan–Jul 2026)
- Uzbekistan National Statistics Committee, Q1/H1 2026
- 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
Where to look: hh.uz, LinkedIn, Flexa, IT Park / resident career pages, Telegram vacancy channels. Language: ads in Uzbek/Russian, code and docs in English. Stacks in ads: React/Next, NestJS, Java Spring, Python (Django/FastAPI), Flutter; DevOps is a narrow junior door.
Employer layers (public guides): local product (Uzum, Click, Payme, TBC Uzbekistan, Anorbank, and others), outsource/outstaff, startup/studio. Product interviews harder and often pays more; outsource is friendlier to juniors and cares about English.
Region: Tashkent’s average wage is about 12.01M (H1 2026) versus about 7.09M nationally; IT seats cluster in the capital. In the regions you more often see remote or a small studio and a lower range.
Portfolio ideas
Stock and receipts for a local shop
A timetable for a tutoring center
A family budget with categories and a chart
First job
- One-page resume, a clear stack, links
- Three running projects (repo, README, live link)
- 20–40 targeted applications — do not wait for a perfect portfolio
- Practice explaining what you built in three minutes
Who it fits
May be a good fit
- You like turning a fuzzy request into a written plan
- You hunt your own bugs
- You want others to read your code
May be a harder fit
- You only want “sitting at a laptop” or a fast-wealth story
- A new tool every day and never going deep
Common mistakes
- Twenty courses and zero finished repos
- A resume that lists 15 technologies
- Submitting AI code you cannot explain
- Waiting for “FAANG pay” in Tashkent and not applying
- Taking review as a personal attack
Where AI helps
Where AI helps
- Boilerplate and a first test
- Explaining an error message
Human responsibility remains
- Deciding what to build
- Security, performance, production ownership
- Team agreement and review
FAQ
No. Being late is six months of videos and no code. People start after 30; their edge is usually domain (finance, teaching) and discipline.