Как белорусским IT-специалистам подготовить резюме и LinkedIn под компании из ЕС и США в 2026 году

Over the course of six weeks, a senior backend engineer with EPAM training submitted 35 applications to foreign businesses using the same resume. He got three first interviews. After a 30-minute conversation with us about format and a redrafted CV, the next 35 applications turned into eight first interviews. The engineer, projects, and experience are all the same. distinct presentation.

We see this pattern often enough that it deserves a proper guide.

This post is the CV and LinkedIn playbook we’d want every Belarusian IT specialist to read before applying to EU or US companies. It covers what international recruiters actually want to see, the patterns in Belarusian-style CVs that quietly hurt your chances, the real differences between EU and US conventions (bigger than most candidates think), and the LinkedIn settings that decide whether you show up in international recruiter searches at all.

Why this matters in 2026

International tech hiring in 2026 is competitive. A fully remote backend role attracts hundreds of applications. The first screen is fast — 8 seconds is the working number for how long a recruiter spends on a CV before moving on. That’s not a metaphor; it’s the operating reality.

A CV that doesn’t pass that first scan never gets to the part where your skills matter. And the Belarusian IT talent pool, while strong, is now competing globally with Polish, Romanian, Ukrainian, Portuguese, and increasingly Latin American engineers — all of whom send CVs in formats Western recruiters are used to reading. For context on how the Eastern European tech labour markets compare in 2026, see our Belarus, Poland, Ukraine, and Romania comparison. The format gap is real. It’s also fixable in an afternoon.

EU vs. US: they read CVs differently

«International» is treated as a single category in the majority of generic CV recommendations. It isn’t. There is still significant variance within Europe, and the difference between US and EU norms is more than most applicants realize. Here’s what actually matters for the markets you’re most likely targeting.

United States. One page, enforced more strictly than candidates expect — especially at FAANG, high-growth tech, and most well-known startups. No photo, no date of birth, no marital status, no full address (city + state for relocations only). Achievements over responsibilities. Metrics on everything you can quantify. Summary section is optional and, if you include one, keep it to two or three lines.

United Kingdom. There is still a lot of variation within Europe, and most candidates are unaware of how much US and EU norms differ.

DACH (Germany, Austria, Switzerland). More formal expectations. The traditional Lebenslauf still influences hiring at non-tech companies, with structured layout and full work history. Photo is technically still acceptable but is increasingly avoided, especially at tech-forward employers. If in doubt, skip it.

Netherlands and Nordics. Closer to UK conventions. Photo uncommon. 1–2 pages. Casual-professional register is fine. Strong English expected and assumed.

France. Photo still common. 1–2 pages. More formal language. CVs in English are accepted at most tech companies.

Eastern Europe (Poland, Czech Republic, Baltics). Mixed. Local conventions still hold at non-tech companies, but tech hiring is increasingly Western-style. Default to the US template for tech roles in these markets and you’ll be fine in most cases.

Making a single, robust worldwide CV that complies with US standards and localizing it for various EU markets only when a job requires it is the sensible course of action. The Europass template is sometimes requested explicitly by EU public-sector or institutional roles; keep it in reserve but don’t make it your default for tech.

Belarusian CV patterns that quietly hurt your international applications

Eight specific patterns we see in Belarusian-style CVs that work against you in international applications. None of them are fatal. All of them are fixable.

1. Photo at the top of the CV. Near-universal «no» in the US, UK, and Nordics. Mixed signal in DACH and France. Default to removing it for international applications unless you specifically know the local market expects it.
2. Date of birth, marital status, family status, full home address. Illegal to ask about in the US and UK. Awkward in most of the EU. Recruiters will silently move past CVs that include them. Cut all of it.
3. Skill bars and visual rating widgets. Common in Russian-language CV templates. International recruiters dislike them. For them, «75% Python» simply indicates a foreign template style. Substitute with skill lists that are categorized.
4. Company descriptions assumed to be known. EPAM, IBA, Itransition, Wargaming, Viber, Game Stream — these names carry weight locally. International recruiters often don’t recognize them. Add a one-line context: industry, size, what they do. «EPAM Systems — global IT services firm, 60,000+ engineers across 50 offices» takes ten seconds to write and saves the recruiter a Google search you can’t be sure they’ll bother with.
5. Responsibilities instead of achievements. «Developed REST APIs» is a responsibility. «Built REST APIs powering 50M requests/day across 12 microservices, reducing average response time from 800ms to 120ms» is an achievement. Default to achievements with metrics wherever you can. If you can’t quantify it, describe scope and outcome instead.
6. English-level descriptors that don’t translate. For local recruiters, «Upper-Intermediate» signifies anything, but for foreign recruiters, it means nothing. Use the B2, C1, and C2 CEFR codes. They are instantly readable and well-known around the world.
7. Generic soft skills lists with no proof. «Team player, communicative, results-oriented, fast learner.» Every CV says this. None of it counts. Replace with concrete examples in your experience bullets — a soft skill demonstrated is worth ten soft skills claimed.
8. Project sections that don’t link out. Provide a link to the GitHub repository, the live demo, or the article if you discuss a personal project, side project, or donation. It is invisible if it is not connected, and worse, it appears to be a claim that the candidate is unable to support.

What to include and what to cut

The clean-up checklist. Run through this once and your CV will outperform 80% of the ones in any given pile.

Include:

• Summary (optional, 3–4 lines). Target the role you want, name the stack and seniority, name the impact you want to have. Skip this section entirely if you can’t make it specific.
• Experience. Company name + one-line company description (if not internationally recognized) + your role + dates + 3–5 achievement bullets with metrics where possible.
• Skills. Categorized without ratings or visual bars (Languages, Frameworks, Infrastructure, Tools, Databases).
• Projects (selective). Only those that are pertinent, with links. Generally speaking, senior resumes don’t require a separate projects section unless the projects are very outstanding or you’re changing careers.
• Education. Just one or two lines. Only give priority to things that are current or directly related to the position.
• Languages. CEFR levels for non-native, «native» for native.
• Contact. Email, LinkedIn URL, GitHub URL, city + country. That’s it.

Cut:

• Photo
• Date of birth, marital status, family status, full home address
• «Objective» statements that aren’t specific to the role
• Hobbies (unless directly relevant — a side project that proves a skill counts as a project, not a hobby)
• «References available upon request» (wasted space; recruiters will ask if they want them)
• Skill rating widgets, visual bars, percentage scores
• Generic soft skills lists without supporting evidence

Tailoring for ATS vs. the human recruiter

Your CV has to work for two different readers, and they want different things. The good news: a clean structured CV satisfies both if you build it right.

ATS preferences. Plain text-readable structure. Standard section headings («Experience,» not «Career Journey»). Keywords from the job description woven into your experience naturally. No tables, no columns, no graphics that break parsing. PDF is generally fine; some systems prefer .docx — check what the application portal requires. Modern ATS platforms like Greenhouse and Lever are now reasonably good at parsing, but they still fail on heavily designed CVs.

Human preferences. Clean visual structure. Achievements that stand out. A document that’s genuinely scannable in 8 seconds — bold the right things, leave whitespace, don’t crowd. Length appropriate to seniority: 1 page for junior and mid-level, 2 pages maximum for senior and above.

Strategy of two versions. Keep both a little more refined visual version and a clean, ATS-friendly version with a simple structure and no design frills. When applying via portals, use the ATS version; when submitting directly to recruiters or referrals, use the visual version. Don’t give up on formatting.

LinkedIn: the structural setup that gets you found

The other half of the application equation. LinkedIn is where international recruiters source — and your settings here decide whether you appear in their searches at all.

Profile language. English as primary. Russian or Belarusian as secondary if you want to keep visibility in local markets. A LinkedIn profile in Russian only is invisible to most international recruiter searches, regardless of how strong your actual experience is.

Photo. Professional, recent, shoulders-up, neutral background. No vacation photos, no group photos cropped, no profile pictures from five years ago that no longer look like you. This sounds obvious but the volume of LinkedIn profiles where it isn’t followed is genuinely large.

Headline. More than the title of your position. Add your value and your stack. «Senior Backend Engineer | Python · Go · Kubernetes | Scalable fintech systems» beats «Senior Backend Engineer at X Corp» every time. The headline is strongly weighted in LinkedIn searches.

About section. 3–4 paragraphs. Lead with what you do, then what you’re working on, then what you want to do next if you’re open. Mention your stack. Mention what kind of company or problem space interests you. Don’t write a memoir. Don’t write three lines either — both extremes hurt.

Experience. Mirror the CV but with slightly more breathing room. Each role should have at least 3–5 lines of substantive description. Bullet points are fine. Same achievement-over-responsibility principle as the CV.

Skills. Prioritize the top 10 skills that match the roles you’re targeting. LinkedIn search algorithms weight these heavily. Pin your three most important skills at the top.

Location. This is delicate and important. Set Belarus if you’re looking for remote positions from Belarus, but be aware that some employer filters will automatically exclude that area. The LinkedIn location settings guide walks through the options. Whatever you choose, be consistent across LinkedIn and your CV.

Open to Work. Use it. Set specific roles and target locations. This setting is visible to recruiters with LinkedIn Recruiter accounts even if you don’t display the public green frame, and it materially increases inbound.

Featured section. Pin your portfolio pieces, published articles, talks, or links to your best work. This section is the closest thing LinkedIn has to a personal landing page; most candidates underuse it.

Showing technical credibility on LinkedIn

Particularly important at mid and senior level. These signals are used by recruiters looking through hundreds of profiles to determine who is genuinely reputable and who is merely polished.

Link your GitHub from the profile. And make sure the GitHub profile itself is clean — the GitHub profile docs cover the basics on README files, pinned repositories, and profile customization. A linked GitHub with no recent activity is worse than no linked GitHub. Make sure what’s visible is what you want recruiters to see.

Public activity matters. Participate in open debates in your field, leave comments on technical topics, and occasionally provide pertinent stuff. Recruiters look at this. An active-but-thoughtful profile signals you’re engaged with your craft; a profile with no activity in two years signals the opposite.

Recommendations from international colleagues. Even one or two carry weight if they’re specific. Generic «great engineer to work with» recommendations help less than «shipped the migration to Kubernetes in six months and trained the rest of the team on it.»

Posts and articles (optional but high-leverage). A single strong technical post in your area of expertise can be more powerful than a dozen recommendations. Don’t force this if writing isn’t your thing — but if you have a sharp take or a deep technical learning, sharing it pays back.

Common mistakes by experience level

Four buckets, with the most common pattern in each.

Junior (0–2 years). Trying to look senior. Enumerating every piece of technology you’ve ever used.  Project descriptions that are 100% boilerplate and 0% specific. The fix: focus on 2–3 strong projects with real depth, show learning trajectory, demonstrate one core strength clearly. Better to be obviously a junior with one strong area than a fake mid-level with no clear story.

Mid-level (3–5 years). Listing responsibilities instead of impact. No signal of ownership. Descriptions that could apply to any backend engineer at any company anywhere. The fix: show what you owned. What shipped because of you. What got measurably better when you were on the team. This is the seniority where specificity differentiates most.

Senior (5–8 years). Too much detail on roles from six years ago. Missing strategic narrative. Weak signal on technical leadership and decision-making. The fix: condense your earliest roles to one or two lines. Lead with what you’ve owned recently. Show the decisions you made, the trade-offs you weighed, the team you worked alongside or led.

Lead / Principal. Missing scale signals altogether. No clear thesis on the kind of work you want next. Weak narrative on technical direction. The fix: lead with scope and decisions. Name the systems and the scale (requests per second, team size, business impact). Articulate the kind of role you’re optimizing for. At this level, recruiters need to know what to put in front of you — make it easy.

Whatever your level, our guides on tools for finding IT jobs and platforms for finding IT jobs in Belarus cover the channel side once your CV and LinkedIn are ready to go out.

FAQ

Should I include a photo on my CV for US or EU applications?

Default to no for any US, UK, Nordic, or Dutch application. Skip it for tech roles in DACH unless the specific employer is older-school. France is more photo-friendly. When in doubt, leave the photo off your standard CV — adding one for a specific market takes 60 seconds; rebuilding a CV without one takes longer.

One page or two pages?

One page for junior and mid-level applications, especially to US companies. Up to two pages for senior and above. If you’re targeting US tech specifically, lean toward one page even at senior level — Western tech recruiters expect it and reward it. If your career genuinely doesn’t fit one page at the senior level and you’re not targeting strict-one-page US tech, two pages is fine.

How do I display my English level on a CV?

Use CEFR codes (B2, C1, C2). They’re internationally recognized and don’t require interpretation. «Upper-Intermediate,» «Pre-Intermediate,» and similar local descriptors don’t translate well — international recruiters either ignore them or quietly downgrade what they think they mean. If you have a TOEFL or IELTS score, include it; otherwise CEFR alone is fine.

Should I list my location as Belarus on LinkedIn?

It depends on what’s accurate and what you’re targeting. If you currently live and work in Belarus — particularly at a Hi-Tech Park resident company — list Belarus, but be aware some employer filters will automatically exclude that location for compliance or operational reasons. If you’ve legally relocated, update. The wrong move is misrepresenting your location to game the filter; recruiters notice the inconsistency between your LinkedIn, CV, and call introductions, and it damages trust.

Do I need separate CVs for EU and US applications?

Usually one well-built international CV (following US conventions) works for both. Localize only when a specific market or role demands it — for example, an EU institutional role explicitly requesting Europass format, or a French employer expecting a photo. Don’t maintain six versions; maintain one clean version and customize the summary and emphasis for the role.

How long should my LinkedIn About section be?

Three to four paragraphs. Around 150–250 words is the sweet spot. Less than three lines reads thin. More than five paragraphs reads as a memoir. Lead with what you do and the value you bring, then what you’re currently working on, then what you want to do next if you’re open to opportunities.

How do I handle gaps in my CV?

Don’t hide them — recruiters spot gaps within seconds, and unexplained gaps create suspicion. Brief explanations work: «Parental leave,» «Relocation,» «Sabbatical / focused study,» «Career break — completed cloud certifications.» One line is enough. Gaps are normal in 2026; pretending they aren’t there is what creates the problem.

Want a recruiter’s read on your CV and LinkedIn?

If you want a candid 15-minute read from people who place Belarusian IT specialists at international companies every week, send your CV and LinkedIn over. We’ll tell you what’s helping you and what’s quietly working against you. No charge, no obligation — it takes us 15 minutes and can save you weeks of applications that aren’t landing. Get in touch and we’ll set it up.