You are three weeks into a senior backend hire in Minsk. The candidate is strong, the offer is drafted, and your recruiter comes back with an awkward message: the standard reference-check request you sent through — the same one you use for every senior hire — is creating friction. The candidate is offering different referees than you asked for. Your recruiter is nervous about how the questions are framed. HR at the last company will not respond to your form.
This is not a communication problem. It is a market you have not calibrated for.
Reference checking works in Belarus — but the mechanics are different from the US, the UK, or continental Europe. Personal data law tightens what you can ask. Cultural norms tighten what referees will say. The IT market itself is small enough that senior candidates track how their names move through it.
This guide shows international HR teams how to run reference checks in Belarus that produce actual signal without creating legal exposure or torching the offer. It is written for teams hiring senior engineers, engineering managers, and country leads — either through their own entity or via EOR — and it is based on what we see running these processes for global clients at Spex Advisers.
Why references in Belarus do not work like they do at home
Three layers of difference matter.
The legal layer. Belarus has active personal data protection legislation. Contacting a candidate’s current or former employer without written consent creates real exposure. The rules are not identical to GDPR, and in some places they are stricter on employer-to-employer information sharing.
The cultural layer. Former employers in Belarus are more cautious than their US or UK counterparts about giving substantive written feedback. Employment confirmation is standard. Qualitative assessment is not — especially in writing, and especially from HR departments.
The market layer. The Belarusian senior IT community is tightly interconnected — a large share of senior engineers cluster around a small number of employers, many of which sit inside the High Tech Park resident registry. Senior candidates know that any reference call may be traced back to them. That shapes who they nominate as referees and how those referees respond.
A reference process built for London or San Francisco copies over some parts of this and breaks on others. You need a different design.
What Belarusian personal data law actually requires
Written consent from the candidate is the entry point to everything else. Not verbal, not implied — written. The consent form should specify who you plan to contact, what you plan to ask, how you will store the answers, and how long you will keep them.
The scope of your questions is bounded by what the candidate has consented to. You can ask about employment history and job performance. You cannot ask about medical information, financial status, family circumstances, or political and religious views. The list is narrower than most international HR templates assume.
Referees also have rights. They can decline to answer — and they often will, particularly if you push past the confirmatory basics. Asking a former employer to disclose information about the candidate that goes beyond what the candidate has authorised can create risk for the referee as well.
Cross-border data transfer is the piece foreign teams miss most often. If your ATS or HRIS sits outside Belarus, moving reference-check data into it may trigger additional documentation requirements. The primary regulator here is the National Center of Personal Data Protection, which publishes clarifications worth checking before you finalise your consent language.
What former employers will actually tell you
Here is the honest picture, before you spend time on a process that will not deliver.
- Will be confirmed on request: dates of employment, position title, sometimes whether the person is eligible for rehire.
- Sometimes shared, depending on the referee: general performance signal, team fit, why the candidate left. Almost always verbal, rarely in writing.
- Almost never shared: specific performance issues, disciplinary history, compensation figures, direct comparisons to peers, or anything that could be legally contested if the candidate saw it.
- Effectively unavailable through HR departments: anything qualitative. HR functions in Belarus have institutional reasons to stay narrow — legal risk, internal policy, and a broader cultural preference for written caution. Line managers who have themselves moved on from the company are a different story.
The practical implication is straightforward. A paper-based, HR-to-HR reference process will produce almost nothing useful. A conversation-based, manager-to-manager process — run by you, your recruiter, or a local partner — is where actual signal lives.
The four reference sources that actually work
Not all references are equal. Here is how we typology them for senior IT hires in Belarus.
Former direct managers who have themselves moved on. The single highest-signal source. Willing to speak candidly because they are no longer at the same employer. Focus questions on delivery under pressure, decision-making, and how the candidate handled ambiguity or setbacks.
Former direct reports. Underused by foreign HR teams and criminally so for engineering manager and lead hires. Direct reports know exactly what the one-on-ones felt like, whether they were coached or ignored, and whether the candidate actually built the team or just managed around it.
Peer collaborators. Product managers, designers, senior engineers, or tech leads who shipped alongside the candidate on the same product. Best source for collaboration style, technical judgment, and dependability under real-world constraints.
Community references. Belarus has an unusually visible senior IT community — meetup organisers, open-source maintainers, conference speakers, and active contributors on dev.by and adjacent platforms. Not a conventional reference, but for staff-plus engineering roles, community peers often know more about a candidate’s technical range than a former line manager does.
You will notice what is not on this list. HR departments of former employers do not produce signal. Chase them for verification, not for judgment.
How to structure the check that actually works
A clean process for senior IT hires in Belarus looks roughly like this.
Get written consent up front — ideally at the offer stage rather than mid-process. Template language should spell out who you plan to contact, what you plan to ask, how you will store the answers, and how long you will retain the data. If your legal team wants to check the underlying legislation directly, the source of record is the official pravo.by portal.
Ask the candidate to nominate three references in specific categories — a former manager, a former report or peer, and a cross-functional collaborator — rather than three names they trust to say nice things. The category framing filters for signal quality.
Run the calls yourself, or through a recruiter with local market credibility. Written questionnaires do not work. Voice or video conversation is the format that produces useful answers.
Use a structured question set, but keep the conversation flexible. Five to seven questions per call, focused on specific situations rather than abstract judgments, is the sweet spot.
Cross-check with public sources. LinkedIn history, GitHub activity, conference talks, open-source contributions. LinkedIn Talent Insights and adjacent tools help triangulate what references tell you — not as a replacement for the calls, but as a sense-check.
Document what you did, not just what you learned. Under Belarusian data protection rules, the audit trail matters as much as the outcome.
Question sets that produce signal locally
A quick tour of what works.
For a former manager on a senior engineer hire, situational and specific beats abstract every time. Something like: «What is the most complex piece of work they owned end-to-end at your company, and what did they do well or badly on it?» A referee who worked with the candidate will answer this. A referee who did not will reveal themselves quickly.
For a former direct report on an engineering manager hire, ground the question in the report’s own experience: «How did they run one-on-ones with you? What did they push you on that helped you grow?» This produces more honest answers than asking the report to grade their former boss on abstract criteria.
For peer collaborators, focus on delivery under real constraints: «Walk me through the hardest sprint you two worked together — what did they own, and how did they show up when things got tight?»
Avoid comparative questions («How did they rank against peers?»), unbounded negative questions («What are their weaknesses?»), and anything about compensation. If you need calibration on comp, use market data — our salary survey in Belarus is one benchmark — rather than trying to extract numbers from references.
Vendor-run background checks: when they help and when they do not
Foreign HR teams often assume they can outsource the whole problem to a background-check vendor. Sometimes true, sometimes not.
Where vendors add real value: verification of education credentials, prior employment dates, and — where legally permitted and consented to — criminal record checks. Universities, courts, and former employers often respond to formal verification requests more consistently than to individual outreach. The output is thin but reliable.
Where vendors do not add value: qualitative reference calls. A vendor calling a former employer on your behalf will get the same «we can confirm employment dates» answer that any external caller gets. The report will look thorough. It will tell you almost nothing you needed to know.
The right split: buy verifications from a vendor, run qualitative references yourself or via a local recruiter who has credibility with the referee pool. The reference stage is also where counter-offer conversations sometimes surface — the referee mentions the candidate is «considering options» — and knowing how to read that signal matters. We have written about the mechanics of it in our counter-offer strategy piece.
Five mistakes foreign HR teams keep making
The same errors show up again and again.
Skipping written consent because «we always just do it this way.» Doesn’t fly locally. Not worth the exposure.
Sending a written reference form and expecting a substantive response. Nobody in Belarus fills these out. You have optimised for auditability at the cost of signal.
Contacting the current employer without explicit permission. A single misjudged call to a candidate’s current manager can burn the offer, the candidate, and your credibility on the local market.
Treating «no red flags» as positive signal. In Belarus, an absence of criticism from a former employer often means the referee is being careful — not that the candidate is strong. Absence of negatives is not presence of positives.
Under-investing in engineering manager reference checks. Foreign teams often run more thorough references on senior ICs than on the managers who will hire and develop them. In Belarus specifically, this is backwards: the senior manager pool is smaller, the market signal available on them is stronger, and the downside of a bad hire is much bigger.
In-house or local support: how to decide
Running references in-house works when your recruiter or HRBP has real Belarus market experience, when your legal team is comfortable operating the consent and cross-border data mechanics, and when your hiring volume justifies keeping the muscle internal. The framework above is enough to run it yourself if those conditions are met.
Bringing in local support pays off when speed matters, when the hire is senior enough that referee access depends on local credibility, or when your team is running its first cohort of Belarusian hires and has not yet built the pattern library. It also pays off when the hire involves designing local incentive structures — long-term compensation for Belarusian teams is a specialised area, and our equity and stock options guide is a starting point for that side of the conversation.
If you want the reference process built and run for you, our recruitment and HR services are designed for exactly this stage of hiring — including consent templates, question banks, and referee outreach through a local team that has credibility with the Belarusian senior IT pool.
FAQ
Yes. Written, specific to the intended contacts and questions, and stored on file. Verbal or implied consent will not hold up if challenged.
Not without explicit, separate permission — and even then, only with awareness that most candidates will refuse. A single unauthorised call can end the hire and damage your reputation on a small, connected market.
Three is standard. What matters more than the number is the mix: aim for one former manager, one former report or peer, and one cross-functional collaborator. Three former managers will underperform this mix every time.
Only in narrow, legally justified cases and always with the candidate’s explicit consent. For most senior IT hires, they are not standard practice and can slow the offer without adding meaningful risk protection.
For verifications — dates, education, credentials — yes, if the vendor can operate in-country or through a Belarusian partner. For qualitative references, no. Vendors calling in cold produce almost nothing useful in this market.
Five to seven business days for a well-run senior IT hire. Anything faster is skipping steps. Anything slower usually means the referee list was not set up correctly at the offer stage.
Ready to build a process that works?
Reference checking in Belarus is not harder than at home. It is structured differently. Teams that copy their home-market process either produce nothing useful or create legal exposure they will regret. Teams that adapt to the local reality make better senior hires faster.
If you are hiring senior engineers, engineering managers, or country leads in Belarus and want a reference process built for the actual market — one that produces signal and stays clean under data protection scrutiny — get in touch with our team. We will walk you through what a reference process for your specific hiring plan should look like and how we run these for international clients every month.