Why references in Belarus do not work like they do at home<\/strong><\/h2>\n\nThree layers of difference matter.<\/p>\n\n
The legal layer. <\/strong>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.<\/p>\n\nThe cultural layer. <\/strong>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 \u2014 especially in writing, and especially from HR departments.<\/p>\n\nThe market layer. <\/strong>The Belarusian senior IT community is tightly interconnected \u2014 a large share of senior engineers cluster around a small number of employers, many of which sit inside the High Tech Park<\/a> 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.<\/p>\n\nA reference process built for London or San Francisco copies over some parts of this and breaks on others. You need a different design.<\/p>\n\n
What Belarusian personal data law actually requires<\/strong><\/h2>\n\nWritten consent from the candidate is the entry point to everything else. Not verbal, not implied \u2014 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.<\/p>\n\n
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.<\/p>\n\n
Referees also have rights. They can decline to answer \u2014 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.<\/p>\n\n
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<\/a>, which publishes clarifications worth checking before you finalise your consent language.<\/p>\n\nWhat former employers will actually tell you<\/strong><\/h2>\n\nHere is the honest picture, before you spend time on a process that will not deliver.<\/p>\n\n
\n- Will be confirmed on request: <\/strong>dates of employment, position title, sometimes whether the person is eligible for rehire.<\/li>\n\n\n\n
- Sometimes shared, depending on the referee: <\/strong>general performance signal, team fit, why the candidate left. Almost always verbal, rarely in writing.<\/li>\n\n\n\n
- Almost never shared: <\/strong>specific performance issues, disciplinary history, compensation figures, direct comparisons to peers, or anything that could be legally contested if the candidate saw it.<\/li>\n\n\n\n
- Effectively unavailable through HR departments: <\/strong>anything qualitative. HR functions in Belarus have institutional reasons to stay narrow \u2014 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.<\/li>\n<\/ul>\n\n
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 \u2014 run by you, your recruiter, or a local partner \u2014 is where actual signal lives.<\/p>\n\n
The four reference sources that actually work<\/strong><\/h2>\n\nNot all references are equal. Here is how we typology them for senior IT hires in Belarus.<\/p>\n\n
Former direct managers who have themselves moved on. <\/strong>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.<\/p>\n\nFormer direct reports. <\/strong>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.<\/p>\n\nPeer collaborators. <\/strong>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.<\/p>\n\nCommunity references. <\/strong>Belarus has an unusually visible senior IT community \u2014 meetup organisers, open-source maintainers, conference speakers, and active contributors on dev.by<\/a> 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.<\/p>\n\nYou will notice what is not on this list. HR departments of former employers do not produce signal. Chase them for verification, not for judgment.<\/p>\n\n![\"\"](\"https:\/\/spex.by\/wp-content\/uploads\/2026\/07\/headhunters-interviewing-female-job-candidate-1024x683.jpg\")
<\/figure>\n\nHow to structure the check that actually works<\/strong><\/h2>\n\nA clean process for senior IT hires in Belarus looks roughly like this.<\/p>\n\n
Get written consent up front \u2014 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<\/a>.<\/p>\n\nAsk the candidate to nominate three references in specific categories \u2014 a former manager, a former report or peer, and a cross-functional collaborator \u2014 rather than three names they trust to say nice things. The category framing filters for signal quality.<\/p>\n\n
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.<\/p>\n\n
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.<\/p>\n\n
Cross-check with public sources. LinkedIn history, GitHub activity, conference talks, open-source contributions. LinkedIn Talent Insights<\/a> and adjacent tools help triangulate what references tell you \u2014 not as a replacement for the calls, but as a sense-check.<\/p>\n\nDocument what you did, not just what you learned. Under Belarusian data protection rules, the audit trail matters as much as the outcome.<\/p>\n\n
Question sets that produce signal locally<\/strong><\/h2>\n\nA quick tour of what works.<\/p>\n\n
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.<\/p>\n\n
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.<\/p>\n\n
For peer collaborators, focus on delivery under real constraints: «Walk me through the hardest sprint you two worked together \u2014 what did they own, and how did they show up when things got tight?»<\/p>\n\n
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 \u2014 our salary survey in Belarus<\/a> is one benchmark \u2014 rather than trying to extract numbers from references.<\/p>\n\nVendor-run background checks: when they help and when they do not<\/strong><\/h2>\n\nForeign HR teams often assume they can outsource the whole problem to a background-check vendor. Sometimes true, sometimes not.<\/p>\n\n
Where vendors add real value: verification of education credentials, prior employment dates, and \u2014 where legally permitted and consented to \u2014 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.<\/p>\n\n
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.<\/p>\n\n
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 \u2014 the referee mentions the candidate is «considering options» \u2014 and knowing how to read that signal matters. We have written about the mechanics of it in our counter-offer strategy piece<\/a>.<\/p>\n\r\n HR Consulting in Belarus<\/div>\r\n Professional HR consulting and recruitment for your it company in Belarus!<\/div>\r\n\t \r\n \r\n\t\t\t\tMore <\/span>\r\n <\/a>\r\n <\/div>\r\n\t<\/div>\nFive mistakes foreign HR teams keep making<\/strong><\/h2>\n\nThe same errors show up again and again.<\/p>\n\n
Skipping written consent because «we always just do it this way.» Doesn’t fly locally. Not worth the exposure.<\/p>\n\n
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.<\/p>\n\n
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.<\/p>\n\n
Treating «no red flags» as positive signal. In Belarus, an absence of criticism from a former employer often means the referee is being careful \u2014 not that the candidate is strong. Absence of negatives is not presence of positives.<\/p>\n\n
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.<\/p>\n\n
In-house or local support: how to decide<\/strong><\/h2>\n\nRunning 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.<\/p>\n\n
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 \u2014 long-term compensation for Belarusian teams is a specialised area, and our equity and stock options guide<\/a> is a starting point for that side of the conversation.<\/p>\n\n
The cultural layer. <\/strong>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 \u2014 especially in writing, and especially from HR departments.<\/p>\n\n The market layer. <\/strong>The Belarusian senior IT community is tightly interconnected \u2014 a large share of senior engineers cluster around a small number of employers, many of which sit inside the High Tech Park<\/a> 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.<\/p>\n\n A reference process built for London or San Francisco copies over some parts of this and breaks on others. You need a different design.<\/p>\n\n Written consent from the candidate is the entry point to everything else. Not verbal, not implied \u2014 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.<\/p>\n\n 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.<\/p>\n\n Referees also have rights. They can decline to answer \u2014 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.<\/p>\n\n 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<\/a>, which publishes clarifications worth checking before you finalise your consent language.<\/p>\n\n Here is the honest picture, before you spend time on a process that will not deliver.<\/p>\n\n 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 \u2014 run by you, your recruiter, or a local partner \u2014 is where actual signal lives.<\/p>\n\n Not all references are equal. Here is how we typology them for senior IT hires in Belarus.<\/p>\n\n Former direct managers who have themselves moved on. <\/strong>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.<\/p>\n\n Former direct reports. <\/strong>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.<\/p>\n\n Peer collaborators. <\/strong>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.<\/p>\n\n Community references. <\/strong>Belarus has an unusually visible senior IT community \u2014 meetup organisers, open-source maintainers, conference speakers, and active contributors on dev.by<\/a> 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.<\/p>\n\n 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.<\/p>\n\n A clean process for senior IT hires in Belarus looks roughly like this.<\/p>\n\n Get written consent up front \u2014 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<\/a>.<\/p>\n\n Ask the candidate to nominate three references in specific categories \u2014 a former manager, a former report or peer, and a cross-functional collaborator \u2014 rather than three names they trust to say nice things. The category framing filters for signal quality.<\/p>\n\n 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.<\/p>\n\n 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.<\/p>\n\n Cross-check with public sources. LinkedIn history, GitHub activity, conference talks, open-source contributions. LinkedIn Talent Insights<\/a> and adjacent tools help triangulate what references tell you \u2014 not as a replacement for the calls, but as a sense-check.<\/p>\n\n Document what you did, not just what you learned. Under Belarusian data protection rules, the audit trail matters as much as the outcome.<\/p>\n\n A quick tour of what works.<\/p>\n\n 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.<\/p>\n\n 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.<\/p>\n\n For peer collaborators, focus on delivery under real constraints: «Walk me through the hardest sprint you two worked together \u2014 what did they own, and how did they show up when things got tight?»<\/p>\n\n 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 \u2014 our salary survey in Belarus<\/a> is one benchmark \u2014 rather than trying to extract numbers from references.<\/p>\n\n Foreign HR teams often assume they can outsource the whole problem to a background-check vendor. Sometimes true, sometimes not.<\/p>\n\n Where vendors add real value: verification of education credentials, prior employment dates, and \u2014 where legally permitted and consented to \u2014 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.<\/p>\n\n 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.<\/p>\n\n 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 \u2014 the referee mentions the candidate is «considering options» \u2014 and knowing how to read that signal matters. We have written about the mechanics of it in our counter-offer strategy piece<\/a>.<\/p>\n The same errors show up again and again.<\/p>\n\n Skipping written consent because «we always just do it this way.» Doesn’t fly locally. Not worth the exposure.<\/p>\n\n 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.<\/p>\n\n 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.<\/p>\n\n Treating «no red flags» as positive signal. In Belarus, an absence of criticism from a former employer often means the referee is being careful \u2014 not that the candidate is strong. Absence of negatives is not presence of positives.<\/p>\n\n 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.<\/p>\n\n 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.<\/p>\n\n 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 \u2014 long-term compensation for Belarusian teams is a specialised area, and our equity and stock options guide<\/a> is a starting point for that side of the conversation.<\/p>\n\nWhat Belarusian personal data law actually requires<\/strong><\/h2>\n\n
What former employers will actually tell you<\/strong><\/h2>\n\n
\n
The four reference sources that actually work<\/strong><\/h2>\n\n
<\/figure>\n\nHow to structure the check that actually works<\/strong><\/h2>\n\n
Question sets that produce signal locally<\/strong><\/h2>\n\n
Vendor-run background checks: when they help and when they do not<\/strong><\/h2>\n\n
Five mistakes foreign HR teams keep making<\/strong><\/h2>\n\n
In-house or local support: how to decide<\/strong><\/h2>\n\n