Background and Reference Checks for Belarusian IT Hires: What’s Legal, What’s Useful, What’s Wasted Effort

You’re three interviews deep with a strong senior backend candidate. The hiring manager wants an offer out tomorrow. Your CFO wants proof the person is who they say they are. And somewhere in the back of your mind is that new personal data law that took effect in late 2021.

Sound familiar?

Vetting IT candidates in Belarus sits in an awkward spot. The Personal Data Protection Law is more stringent than most recruits understand. Since 2020, the Belarusian IT diaspora has stretched its job history to half a dozen jurisdictions. And a lot of the “standard” checks HR teams still run are either legally shaky, functionally useless, or both.

This guide sorts every common check into three buckets — legal, useful, and wasted effort — so you can vet faster and cleaner without stepping on the law.

The legal frame in 60 seconds

Belarus’s Law No. 99-Z of 7 May 2021 “On Personal Data Protection” came into force on 15 November 2021 and reshaped how employers collect candidate data. According to DLA Piper, it is the first Belarusian legal act specifically regulating personal data. The framework borrows heavily from GDPR but is stricter in one important way: legitimate interest is not a broad legal basis for processing personal data. In most cases, you need written consent.

The National Personal Data Protection Center enforces the law, and — as Grata Net notes in its overview of employee privacy — the standard for cross-border data transfers is tighter than under GDPR’s legitimate-interest tests. Violations carry both administrative and criminal liability. That’s not a theoretical risk — it’s a real one, especially if a rejected candidate decides to file a complaint.

Three rules you need to hold in your head:

1. Get written consent before you run any check. A signed offer letter or CV is not enough on its own.
2. Only collect data you actually need for the role. Data minimization is a legal requirement, not a best practice.
3. Have a retention policy. Keeping rejected candidates’ background reports on a shared drive “just in case” is a violation.

If you’re building a hiring pipeline from scratch, this is where to start — well before you argue about ATS features. For teams weighing where HR expertise itself comes from in the local market, this overview of where HR is trained in Belarus is a useful reference.

Checks that are legal and worth running

Here’s what truly gives you signal with reasonable effort:

Identity check. Passport check against the name on the CV. Straightforward, always legal with consent, catches the small number of candidates who are misrepresenting who they are. Do this on every hire.

Education verification. Confirms diploma authenticity with the issuing institution. Cheap, fast, and worth it — inflated or fabricated degrees are common enough that a five-minute check pays for itself. If the candidate studied at BSUIR, BSU, or another major Belarusian institution, verification is usually straightforward.

Employment history verification. Confirm job titles and dates with past employers. In Belarus, this is simpler than in many other countries because the workbook offers a written record. For candidates who have relocated abroad, expect more manual back-and-forth.

Public professional footprint. GitHub commits, Stack Overflow reputation, published talks, open-source contributions. This is high signal for engineers and costs you nothing. A senior developer who claims deep Kubernetes experience but has no public evidence anywhere is not automatically a red flag — but it’s a conversation you want to have. If you’re looking for candidates in these communities in the first place, this roundup of top IT job resources in Belarus is a solid starting point.

Structured reference checks with candidate-provided referees. Only useful if you ask behavioral questions with follow-ups. “Would you hire them again?” and “What would they need to develop to be effective at the next level?” beat “Were they a good team player?” every time. Deel’s guide to international reference checks is a good primer on staying compliant when referees are in different jurisdictions.

Criminal record checks — but only for specific roles. This is where a lot of employers get it wrong. Belarusian law permits criminal record checks only for positions with a legitimate need: finance roles with access to funds, positions handling sensitive personal or state data, roles with security clearance requirements. Blanket criminal checks on every hire — including your junior QA engineer — are not allowed.

Checks that are legal but usually wasted effort

Not everything you can do is worth doing. These come up often and rarely earn their cost:

Credit checks for standard IT roles. Common in the US, uncommon and low-signal in Belarus. Unless the role directly involves financial authority, skip it.

Deep social media archaeology. A quick look at public profiles is fine. Scrolling through six years of someone’s VKontakte or Instagram is a bias factory. Document what you’re looking for before you look, or don’t look at all.

Polygraph tests. Employers with a strong focus on security may occasionally request this. Questionable predictive validity, sensitive treatment under the PDP Law, and it makes candidates dislike you. There are better ways to assess trust.

Handwriting analysis, personality typing as a hiring filter, “loyalty tests.” No predictive validity. Real legal exposure if a rejected candidate finds out. Just no. As Chambers’ analysis of the personal data law explains, collecting data beyond what the role objectively requires is precisely the kind of processing the law is designed to prevent.

Reference calls without structure. The referee has been prepped by the candidate. The questions are soft. Everyone says nice things. You learn nothing. If you can’t invest in a structured protocol, don’t do the call.

Handling the Belarusian IT diaspora

Since 2020, a significant share of the Belarusian tech workforce has relocated — to Poland, Lithuania, Georgia, Cyprus, Serbia, and beyond. That changes the vetting calculus in ways worth planning for.

Employment history now frequently includes numerous jurisdictions. A candidate might have worked in Minsk until 2022, then in Warsaw, then remotely for a US company through an EOR structure. Verification standards vary by jurisdiction. Some employers prefer that your request be in the local language. Some will not answer at all.

The practical move is to prioritize verifying the two most recent roles as well as the ones with the strongest signal (for example, their claimed lead engineer post at a well-known firm). Do not attempt to verify a summer internship from 2016.

For candidates who’ve stayed in Belarus, remote work for foreign clients has become the norm. That is not a red flag in and of itself, but it does mean the “employer” on the CV may be a self-employment or personal contract arrangement, not a company entity. Ask immediately and document it.

A 20-minute vetting checklist for a mid-level IT hire

Remember this for the next time you’re screening a shortlist:

1. Cross-check CV with LinkedIn for titles, dates, and gaps (2 minutes)
2. GitHub / portfolio review — is the claimed skill visible in real work? (5 minutes)
3. Consent form signed and stored — before any check runs (1 minute)
4. Passport ID confirmed — matches CV, no obvious anomalies (2 minutes)
5. Education verification initiated — via institution or third-party service (2 minutes)
6. Two structured reference calls booked — behavioral questions ready (5 minutes)
7. Public footprint scan — professional only, documented criteria (3 minutes)

Twenty minutes of recruiter time, ninety percent of the signal you actually need. For a deeper look at the top layer — how to attract senior candidates before you even get to vetting — see this guide to building a LinkedIn employer brand for Belarusian IT talent.

Common mistakes that result in legal exposure

The four most commonly mentioned are:

• Running checks before consent is signed. The signed offer does not constitute authorization for background checks. You require a separate, detailed permission agreement that names what you will verify and how.
• Keeping candidate data indefinitely. After a rejection, most candidate data should be deleted or anonymized within your defined retention window. “The recruiter’s inbox forever” is not a retention policy.
• Contacting former employers with questions the candidate didn’t authorize. The scope of your reference authorization matters. If the candidate authorized verification of dates and title, you can’t turn it into a character interview. Lexology’s overview of Belarusian data security obligations spells out the third-party disclosure rules in more detail.
• Using check results as the sole basis for rejection. Adverse findings should trigger a conversation, not an automatic no. Give the candidate a chance to respond to and correct inaccurate information.

Bottom line

Good vetting for Belarusian IT candidates isn’t about running more checks — it’s about running the right ones, with proper consent, and dropping the ones that add compliance risk without adding signal. The great majority of hires will be assessed based on their identity, education, work history, structured references, and public footprint. Criminal checks only when the role warrants them. Everything else should earn its place.

For teams building a repeatable IT hiring process in Belarus, the harder problem is usually not the checks themselves — it’s finding candidates who make the vetting worth doing. If that’s where you are, our IT recruitment services in Belarus cover sourcing, screening, and offer support.

Conclusion

The Belarusian market is no longer an exception in which basic worldwide hiring strategies are sufficient. The country’s personal data regulation has altered how applicant screening works, the talent market has become more worldwide, and experienced engineers’ careers now frequently cross numerous nations and employment patterns.

As a result, the best background check is not the most exhaustive one—it is the most purposeful. It answers the questions that genuinely matter for the role, complies with applicable data protection requirements, and does not turn the hiring process into an unnecessary obstacle for candidates the company ultimately wants to hire.

If you need help designing a compliant candidate screening process or building your hiring framework in Belarus, get in touch with our team. We’ll help you find the approach that best fits your business and hiring goals.