Software developer

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.

A typical day orbits a ticket (Jira, YouTrack, Linear): read the request, ask about the unclear part, write code, self-test, open a pull request, fix review notes. Much of the time is not a “new feature” — it is reading old code, logs, and why staging fails while production does not.

There is writing too: a short comment, a changelog, sometimes a tech spec. Standup is 10–15 minutes: yesterday, today, blockers. In a small team a developer may also cover design or QA — useful for a junior, if you still keep a boundary.

09:30 standup. 10:00–13:00 deep work (feature or bug). Lunch. 14:30 review or pair-debug. 16:00 QA questions or a short PM sync. 17:30 merge a PR or plan tomorrow. A late deploy can happen before a release — a healthy team does not do that every day.

Remote days look emptier on the calendar, but writing must be stricter: “done” is not enough; you need a screenshot, a log, and acceptance criteria. In an office it is easier to ask quickly, but noise cuts deep work. Try both before you decide.

Hard: one language in depth (JS/TS, Python, or Java), Git, HTTP basics, SQL (what a table and a JOIN are), debugging. Contest medals are not required — but arrays, maps, and a feel for complexity show up in interviews.

Soft: ask about the unclear part, do not lie about dates, review the code not the person. In Uzbekistan teams the work language is often Russian or Uzbek, with English mixed into docs. Staying silent in the team chat slows a junior down.

Do not learn every stack at once. One path first, then SQL and Git beside it.

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.

Doors in Tashkent: IT Park residents, outsource (EPAM and other vendors), local product (Uzum, Click, Payme, bank digital teams), small studios. Internships appear on hh.uz, Telegram, campus fairs, and through people you know.

Apply even when the ad says “2 years” — sometimes that is a template. Eighty applications and zero projects will not work. Long unpaid “experience” is a red line: a short practicum is fine, six unpaid months is not.

Three pieces are enough if they run and you can explain them. Not a Dribbble screenshot: a repo, a README, a live link.

Ideas (do not copy — put your own topic): 1) stock and receipts for a local shop; 2) a timetable for a tutoring center; 3) a family budget (categories, a chart); 4) a small API plus a simple front end. A ChatGPT “Twitter clone” you cannot explain will hurt you.

For each project: the problem, the choice, where you were wrong. That is the case study.

First job: a one-page resume, a clear stack, links, 20–40 targeted applications. Closed roles move through Telegram and people you know. Practice explaining what you built in three minutes.

Freelance (Upwork, local Telegram) is hard for a junior: the client, a fuzzy brief, payment risk. One or two small paid jobs help the portfolio — do not treat them as your main income yet.

Remote: a foreign team usually wants B2+ English and overlapping hours (Europe/US). Local hybrid is common. Fully remote junior seats are rare; office/hybrid is more realistic first.

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.

A fit: you like turning a problem into writing, you can sit with ambiguity, you will hunt one bug for an hour (and still know when to stop). Games, Excel, or olympiads are not required.

A poor fit: you only want the status; you dislike explaining in writing; you chase a new tool every day and never go deep. If your eyes or back already hurt, do not sit long without setup and breaks.

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.

Path: junior → middle (own a feature) → senior (the system) or staff/architect, or EM (people). A move to PM or analytics is real if you like writing and stakeholders.

From another job: accountants arrive with SQL; teachers with explanation; marketers with metrics. One stack first — not “I quit everything.”

Do not mix two numbers. Flexa (updated 3 August 2026): programmer vacancy median about 10.1M UZS/month (Jan–Jul 2026), most common offer about 8M. The statistics committee ICT average is about 17.41M (H1 2026); information services sit higher (~21.4M), and software development is cited around 22.23M in sector write-ups. The industry mean includes telecom and a long right tail.

There is no official junior rate. Flexa warns that “junior” samples are tiny and often hide mid-level requirements. A first job is usually below 8M. Public Tashkent-team guides (for example NextSuhbat, 2026) give a community range of about 6–12M junior, 15–30M middle, 30M+ senior — not a government series, a mix of ads and conversations.

Factors: production experience, stack (mobile/backend/data often above generic web), English, product vs agency, IT Park / FX-linked contracts. Personal income tax is 12% and the employer pays social tax — ask what you take home.

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.

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.

Today AI (Copilot, ChatGPT, Cursor) speeds boilerplate, a first test, and “what is this error.” It does not replace: deciding what to build, security, performance, team agreement, production ownership.

Learn: a short prompt, reading the answer, writing a test, licenses/secrecy (do not paste private code into a public model). The skill that rises in value is seeing the system and saying “this is unsafe.”

“The job dies” is a weak forecast. Clearer: a junior without AI is slower; a junior who only uses AI and cannot explain it fails the interview.

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.