For IT jobs in Uzbekistan, reading English is needed from the first day in almost any role, because documentation, error messages, libraries and most tutorials are in English. Speaking English becomes the deciding factor once you work with foreign clients or an international team, which is common in outsourcing and export-oriented companies in Tashkent. A practical target: comfortable B1 reading for a junior on a local team, B2 speaking for anyone on client calls, and C1 for leads who negotiate scope.
Those levels are our editorial guide, not an official standard; each employer sets its own bar. The rest of this page shows where English appears in a real working week, what to say on a client call, how to write clear async messages and a four-stage learning path.
Where English shows up in a working week
| Task | Skill | Example |
|---|---|---|
| Reading docs and error messages | Reading | "Deprecated since v3; use fetchAll() instead." |
| Searching for solutions | Reading, precise keywords | Typing "react useEffect runs twice strict mode" instead of a vague question |
| Daily stand-up with a foreign team | Speaking, listening | "Yesterday I finished the payment form. Today I'm on the refund flow." |
| Tickets, pull requests, commit messages | Writing, short and exact | "Fix: prevent double submit on checkout" |
| Client demo or requirements call | Speaking, asking questions | "Just to confirm, should guests be able to pay without an account?" |
| Chat messages across time zones | Writing, polite and complete | A message that can be answered without a follow-up question |
| Interview for a foreign client or company | Speaking about your experience | "I led the migration from REST to GraphQL." |
Many Uzbek developers can read documentation fluently but freeze on calls. That gap, reading at B2 and speaking at A2, is the most common one we see, and it is fixable because you already have the vocabulary.
How much English each role needs
| Role | Reading | Writing | Speaking | Why |
|---|---|---|---|---|
| Junior developer, local team | B1 | A2–B1 | A2 | Docs and tickets; meetings in Uzbek or Russian |
| Developer in an outsourcing team | B2 | B1–B2 | B1–B2 | Tickets in English, stand-ups with the client |
| QA engineer | B1–B2 | B2 | B1 | Bug reports must be exact |
| Designer, product manager | B2 | B2 | B2 | Explaining decisions, running calls |
| Team lead, solution architect | C1 | B2–C1 | C1 | Estimates, scope, disagreeing politely |
| Support, customer success | B1–B2 | B2 | B2 | Real-time chat and calls with users |
IT Park Uzbekistan, the state technology park, presents itself with the slogan "START local & GO global" and runs a separate outsourcing portal aimed at foreign companies looking for teams here (it-park.uz). In practice that means many local companies sell their work abroad, and client-facing English is part of the job description.
Words for the tasks around the code
A two-minute client call, line by line
A typical sprint check-in between a Tashkent developer (Jasur) and a client in Berlin (Anna):
Anna: Hi Jasur, can you hear me OK?
Jasur: Yes, loud and clear. Shall I start with the update?
Anna: Please.
Jasur: So, the login and registration screens are done and deployed to staging. The password reset is still in progress. I expect to finish it by Thursday.
Anna: Great. Any blockers?
Jasur: One. The SMS provider needs API keys from your side. Could you send them, or introduce me to the person who manages that account?
Anna: Sure, I'll ask Tom today. What about the design change we discussed?
Jasur: I had a question about that. When you say "make the button more visible", do you mean a different colour, or moving it higher on the page?
Anna: Both, ideally.
Jasur: OK. Moving it is quick. The colour change affects the whole design system, so it would take about a day. Is that still a priority for this sprint?
Anna: Let's leave the colour for next sprint.
Jasur: Got it. I'll move the button now and add the colour change to the backlog. I'll send a short summary after the call.
Four habits in that call are worth copying: offer to start, give status with a date, name the blocker and who can remove it, and ask a clarifying question instead of guessing. The last one saves more time than any framework.
Async messages: three templates
Across time zones, a message that needs a second round of questions costs a whole day. Write so it can be answered in one go.
Status update
Hi team, quick update on the checkout task: payment form done and merged; refund flow in progress (about 60%); blocked on test card numbers for the new provider. @Tom, could you share them? Expected finish: Thursday.
Asking for clarification
Hi Anna, a question on ticket 142 before I start. Should the export include deleted orders? Option A: exclude them (simpler, faster). Option B: include them with a "deleted" label. I'd suggest A unless finance needs the full history.
Reporting a problem you caused
Heads-up: yesterday's release broke the email notifications for new users. Cause: a missing environment variable. Fixed and redeployed at 10:40 Tashkent time; I've added a check so it can't happen again. No data was lost.
For vocabulary on Git, Jira and code review, see IT uchun ingliz tili (in Uzbek); for ready stand-up lines by role, see IT standup English.
A learning path in four stages
| Stage | Goal | Weekly time | Output you can show |
|---|---|---|---|
| 1. Reading base | Read docs without translating every line | 3–4 h | Read one official guide end to end; keep a list of 100 terms with examples |
| 2. Writing at work | Clear tickets, PRs and chat messages | 2–3 h | Rewrite 10 of your old messages; write all commits in English |
| 3. Speaking about your work | Give status, explain a decision, ask questions | 3 h | Record a 2-minute project walkthrough weekly |
| 4. Client-ready | Handle calls, estimates, disagreement | 3–4 h | Run a mock demo; do one mock interview in English |
Stages 1 and 2 can run in parallel with a full-time job. Stage 3 is where most people stall, because there is nobody to talk to; the solution is volume, which is where recordings, a colleague or an AI partner come in.
Mistakes Uzbek developers make in client messages
| Instead of | Write or say | Why |
|---|---|---|
| I did not understood the task. | I'm not sure I understand the task. Could you clarify…? | Grammar, and it points to a next step |
| Please do the review urgently!!! | Could you review this today if possible? It blocks the release. | Give a reason, drop the pressure |
| It is working on my computer. | It works locally. Let me check the staging config. | Present simple for states; shows action |
| We will do it tomorrow maybe. | I expect to finish it tomorrow afternoon. | Clients plan around your estimate |
| I have a problem with the bug. | The export fails when the file is over 10 MB. | Say exactly what fails and when |
| Can you give me the access? | Could you give me access to the repo? | access here takes no article |
| Sorry for late answer. | Sorry for the late reply. | Missing article, better noun |
Practice task: rewrite six messages
Make each message clearer and more professional.
- 1. hello, the site not working
- 2. When you will send the design?
- 3. I fixed. Check.
- 4. Why you changed the requirements again?
- 5. I can't do it on Friday because too many tasks.
- 6. Tomorrow I am not coming.
Answers
Model versions; yours may differ in wording.
- Hi, the site is down: the homepage returns a 502 error since about 9:15 Tashkent time. I'm checking the server logs now and will update you in 30 minutes.
- When do you expect to send the final design? I'd like to start the layout on Monday.
- I've fixed the date filter bug (PR #87). Could you check it on staging when you have a moment?
- I noticed the requirements for the report have changed. Could you help me understand what's behind the change, so I can estimate the extra work?
- I won't be able to finish it by Friday, as I'm also working on the release. Would Monday work, or should I pause the other task?
- Just a heads-up: I'll be off tomorrow. I've handed the open tickets to Dilshod, and I'll be back on Thursday.
The same skills get tested before you are hired; see English job interview tips for Uzbekistan for questions international companies ask.
Rehearsing client calls before the real one
The client call is the part you can't practise by reading. In BandMate you can role-play a stand-up, a demo or a requirements call with Bandi by voice, get your mistakes explained in Uzbek, Russian or English, and repeat the same call until the key sentences come out without searching for words. It is practice, not a certificate, and it won't know your codebase, but it gives you speaking time on exactly the situations that matter.
