Skip to main content
11 min read0

The Tech CV for Uzbek Developers Applying Abroad (and at Home): What to Cut, What to Add

The CV that gets you hired at Click is not the CV that gets you past a FAANG ATS. They are optimised for two completely different readers — one human, one machine — and the conventions that help locally (a photo, a full Tashkent address, marital status, a grade average for every course) actively hurt you abroad. This guide is the playbook for both versions, in order: what to cut for international applications, what to keep, what to add, and at the end a separate section for the local version.

The advice here is grounded in a real Tashkent backend CV that has cleared automated screens at FAANG-tier employers and several US/EU product companies. The patterns matter, not the person.

Part 1 — The CV for applications abroad

The reader is a machine first, a recruiter second

For 80% of large international companies, your CV is parsed by an Applicant Tracking System (Greenhouse, Workday, Lever, Ashby, iCIMS) before a human ever sees it. The ATS turns your PDF into structured text and tries to extract: name, contact, employers, dates, titles, education, skills. Anything that breaks that extraction is silently dropped — the recruiter sees a half-empty profile and moves on. Your job is to make extraction trivial.

That single constraint dictates almost every other rule below.

Cut these — they belong on a local CV, not an international one

  • Photo.US and UK companies discard CVs with photos by policy (anti-bias). Many EU companies do the same. A photo also breaks layout parsing in two-column templates — the ATS reads it as a content block and misaligns the rest.
  • Date of birth, marital status, nationality, gender. All illegal to ask in US/UK and most of the EU. Listing them voluntarily marks you as inexperienced with the conventions of the market you are applying to.
  • Home address.“Tashkent, Uzbekistan” is enough — one line, in the header. Street and apartment number do nothing.
  • Soviet-style language proficiency.“English: with dictionary” or “Russian: free” is meaningless abroad. Use CEFR (A1–C2) or a recognised test score (IELTS, TOEFL). If you cannot honestly claim B2 English, omit it — a blank is better than a flag.
  • Every course you took at university. List the degree, institution, dates, and one line of focus area. Nobody cares about your Discrete Mathematics II grade.
  • Hobbies, unless they ship things.“Reading” is a void. “Maintainer of an open-source library with 600 stars” is a hire signal. If the hobby does not produce evidence, drop it.
  • The objective / summary paragraph.Three lines of “motivated engineer seeking opportunities” is filler. Replace it with a one-line headline that names your role, your stack, and your location: Backend Engineer | Tashkent, Uzbekistan.
  • References available on request. Assumed. Costs you a line.

Add these — they are what the ATS and the recruiter actually want

  • A clean, single-column, plain-text-friendly layout. One column. Standard section headings (Experience, Projects, Education,Skills). Standard fonts (Latin Modern, Computer Modern, Calibri, Helvetica, Arial). No tables, no text boxes, no icons-as-text. The cleanest path is a LaTeX or Markdown-based template — it produces a PDF whose text layer is literally the content, in order, with no parser surprises.
  • One page.If you have less than ten years of experience, one page. Two pages is forgiven; three is not. The discipline of cutting is the point — what survives is what mattered.
  • Plain English keywords for your stack. Write TypeScript notTS. Write PostgreSQL not Postgres. Write Amazon S3alongside AWS S3 the first time. The ATS keyword match is literal; expand acronyms on first mention.
  • Metric-driven bullets (the formula is below).
  • Links that work.GitHub and one personal site or LinkedIn, clickable, in the header. No QR codes. Make sure the GitHub has at least two pinned repos with real READMEs — an empty GitHub is worse than no GitHub.
  • An explicit location and timezone-friendliness if you want remote.Tashkent, Uzbekistan (UTC+5, available 09:00–19:00 CET) is one extra line that does a lot of work for EU remote applications.

The bullet formula that survives a 20-second skim

A recruiter spends six to twenty seconds on your CV in the first pass. The bullet has to communicate scope and impact in that window. The formula:

Strong verb — what you built — for whom or at what scale — with what result, in numbers.

Each bullet should be parseable on its own. Three test questions per bullet:

  • What did you do? Not the team. The verb has to belong to you.
  • What was the scope or scale?Concurrent users, monthly requests, devices managed, tests served, hours of manual work removed. A number is required. “Many users” is invisible.
  • What changed because of you?Latency, error rate, uptime, throughput, cost, time-to-task, revenue. If the answer is “nothing measurable,” either you are underselling or the work was not worth a bullet.

A weak bullet:

Worked on backend APIs using NestJS.

What did you do? Vague. Scale? Unknown. Result? None. The recruiter has already moved on.

A strong bullet:

Built and maintained NestJS REST APIs handling over 1M monthly requests at 99.9% uptime.

You built it. The scale is 1M/month. The result is the SLA. Three seconds, three signals.

If you cannot put a number on a bullet, work for one. Ask your tech lead. Pull metrics from Grafana. Estimate conservatively from your own knowledge of the system. “1000+ devices managed,” “780+ students,” “5000+ flashcards generated” are estimates and they are honest — the plus sign does the work.

Stack lines: list what you ship, not what you have heard of

The Skills section is not a personality test. Two practical rules:

  • Group by category, not by years.“Languages & Databases” / “Tools & Infrastructure” is enough. Years-of-experience tags are self-reported noise.
  • Everything in this list must appear in a bullet above. If you list Kafka in skills but no bullet mentions Kafka, you will be asked about it in the screen and the gap will surface. Skills are an index of your experience section, not a wishlist.

Projects: where Tashkent CVs win

One of the few asymmetric advantages a Tashkent engineer has when applying abroad: a strong side project signals far more than another year at a local employer the recruiter has never heard of. A Projectssection with one or two real shipped things — with a live URL, a GitHub link, and a metric-driven bullet set — can carry a CV with only two years of formal experience past the screen.

Treat your projects with the same bullet formula as employers. “Built X”is not enough. “Launched X, serving Y users, built with Z, achieving W”is the standard.

File, format, and filename

  • PDF, not DOCX. PDF preserves layout across the ATS upload and the recruiter's screen. DOCX renders differently across versions.
  • Selectable text. Open your PDF and try to select all the text. If any section is unselectable, you exported as an image and the ATS sees nothing.
  • Filename: FirstName_LastName_CV.pdf. Not cv_final_v3.pdf. The filename is shown to recruiters.
  • Under 500 KB. No embedded high-resolution photos, no scanned certificates, no decorative graphics.

A note on the cover letter

For 80% of engineering applications, the cover letter is not read — a strong CV plus a referral or a thoughtful application question response does more work. The exception is applications to a small company (under ~50 people) or a role explicitly asking for one. In those cases write four short paragraphs: why this company, why this role, the one achievement that matches the job description, and a single line of availability.

Part 2 — The CV for the local Tashkent market

The local market is more permissive about format and more demanding about completeness in a different direction. What changes:

  • Photo is acceptable, sometimes expected. Especially at older Uzbek companies and at fintechs hiring through HR-led pipelines. Keep it neutral, recent, neutral background. Not optional at most state-adjacent employers.
  • Russian-language version is the default. A Russian CV with an English summary line at the top is the safest single document for IT Park residents, fintechs, and the EPAM Tashkent / Exadel / Andersen ecosystem. Submit the English version too if the job posting is in English.
  • The university name still carries weight.Webster, Inha, TUIT, INHA, Westminster, AKFA, the Singapore institute. List it prominently — in some local pipelines the university is a hard filter the way it is not abroad.
  • Local certifications matter more.IT Park courses, Mohirdev, Najot Talim, Astrum — if they are recent and the program is well-known, add them underEducation or a dedicated Certifications section. For an international CV, leave only the major ones.
  • The same bullet formula still wins.Local recruiters do not require it the way international ATS does, but it works anyway — a CV with metric-driven bullets stands out in a stack of “participated in development of...” lines. The formula is universal; only the format around it is local.
  • Salary expectations are sometimes expected on the CV.At a minority of local employers, especially state-adjacent ones. For private IT companies, do not include it — it gives away leverage. (See the separate negotiation guide for why.)

One CV or two?

If you apply both locally and abroad, maintain two versions in parallel: aninternational CV (single column, no photo, English, ATS-clean) and a localCV (Russian primary, photo optional, with locally-relevant certifications). They share the same experience bullets — only the surrounding wrapper differs. The discipline of keeping both up to date forces you to write bullets that are strong enough to survive in either context.

The seven-day CV rebuild

If your current CV is the local format and you want to apply abroad next week, here is the sequence:

  • Day 1: Move to a single-column LaTeX or Markdown-based template. Strip the photo, the address line, the date of birth, the marital status, the objective.
  • Day 2: Rewrite every employer bullet using the formula. Force a number into each one. Cut bullets that do not survive the formula.
  • Day 3: Add one or two projects with live URLs and metric-driven bullets. If they are not on your GitHub yet, push them today.
  • Day 4: Compress to one page. The first thing to cut is the oldest employer. The second is bullets that duplicate scope across roles.
  • Day 5:Run the PDF through three tests. (1) Open in Preview and select all the text — can you select everything? (2) Copy-paste the text into a plain editor — is the order correct, are the section headings clear? (3) Upload to a free ATS preview tool (resumeworded, jobscan) — does it parse all your jobs?
  • Day 6: Show it to two people who have themselves landed roles abroad. Not to your manager. Not to your parents. To peers who have done it.
  • Day 7: Apply.

The single biggest mistake

The single biggest mistake is treating the CV as a static document you write once and reuse. The CV is a hypothesis about which signals matter to a specific reader. Adjust the headline, adjust the order of the skills list, adjust which bullets sit at the top of each role — in fifteen minutes per application — based on the job description. Companies that ask for Go get the Go bullet at the top. Companies that emphasise scale get the 1M-requests bullet at the top. The body of the CV barely changes; the framing always does.

Once the CV is doing its job, the next bottleneck is the interview. The same discipline that makes a bullet land in six seconds — verb, scope, number, result — is the discipline that makes an answer land in a phone screen. Practise both in the language the real call will be in.