How to Vet an EOR in Belarus: A 12-Question Checklist and 8 Red Flags

Choosing the wrong Employer of Record in most countries means a slightly worse service and a slightly higher invoice. Choosing the wrong one in Belarus means salaries that don’t arrive, source code you don’t legally own, engineers you can’t move, and a sanctions question you can’t answer when your board asks it.

That’s not scaremongering. It’s the actual failure mode, and it happens because most global EOR content treats Belarus as a row in a spreadsheet: 24 days of leave, 40-hour week, done. The things that will actually hurt you here aren’t in that row.

So here’s the checklist we’d run if we were on your side of the table. Twelve questions, eight red flags, and one section on when you shouldn’t hire an EOR in Belarus at all. Every criterion below is one you can verify with a document, precisely so you don’t have to take our word for any of it.

Key takeaways

• A lot of what gets sold as “EOR in Belarus” is actually contractor management. The misclassification risk stays with you.
• Employer social contributions are the biggest line in your budget, and High-Tech Park residency changes how they’re calculated. This is the single largest cost variable and most providers don’t raise it.
• Ask for documents, not assurances. Entity registration, residency certificate, sample contract, IP clause, payment route, liability cap.
• Any provider who tells you employees can be terminated quickly and cheaply in Belarus is either uninformed or planning to break the law on your behalf.
• If your compliance posture can’t tolerate Belarus exposure at all, the honest answer is relocation — not a cleverer EOR.

First: make sure you’re actually buying an EOR

A real Employer of Record signs a Belarusian employment contract with your engineer, becomes their legal employer, registers them with the Social Protection Fund and Belgosstrakh, withholds their income tax, and carries employer liability. That last part is the whole point. You’re paying someone to hold a risk.

What a fair number of providers actually do is engage your people as sole traders or self-employed individuals and invoice you for it. It’s cheaper, it’s faster, and it is not an EOR. There is no employment relationship, no employer liability, and no protection for you — if those engagements get reclassified as employment, the exposure lands on the company that was really directing the work. That’s you.

Fifteen minutes into the first call, ask what your people will actually sign. If the answer involves the word “contractor” in any form, you’re shopping for a different product than the one you think you’re shopping for.

What hiring in Belarus really costs

Before you can compare quotes, you need to know what’s inside them.

Employer social contributions dominate the budget. Contributions to the Social Protection Fund plus Belgosstrakh insurance land in the region of 35% on top of gross salary. Personal income tax is withheld from the employee. Rates get revised, and the Tax Code has been amended more than once recently — so treat any number in any blog post, including this one, as a prompt to demand a written, itemised figure from your provider rather than as a fact you can budget against. Broader context on how employment relationships are structured is set out in the official overview of Belarusian employment law.

Then there’s the provider’s own fee, and this is where quotes stop being comparable. Flat monthly fees usually win on senior engineers; percentage-of-payroll usually wins on juniors. Run the arithmetic against the actual people you plan to hire, not against a hypothetical average, because the two structures can diverge by thousands of dollars a year on the same team.

And then FX. You pay in euros or dollars. Your engineer gets paid in Belarusian rubles. Somebody converts the money, at some rate, with some margin. Two providers with identical headline prices can deliver materially different effective costs once that spread is applied. Ask for the rate and the margin in writing.

The HTP question that quietly changes your payroll bill

This is the Belarus-specific thing that generic global EOR content misses entirely, and it’s worth real money.

For employers that are residents of the High-Tech Park, social contributions on employee income are calculated from the national average salary rather than from the employee’s actual salary. On IT salaries — which are several times the national average — that gap is not a rounding error. It is the difference between two quotes that look similar on the surface.

So: is your provider an HTP resident? If they don’t raise this themselves, they’re either not a resident or don’t understand the market well enough to be trusted with your payroll. The Ministry of Economy’s overview of the Park is a good place to sanity-check what the regime actually confers. If you’re considering setting up your own entity inside the Park instead, that’s a different conversation — we handle HTP residency applications from business project to certificate.

The 12-question vetting checklist

Run this on any provider, including us. The right-hand column is the point: every question resolves to a document, and documents are hard to fake in a sales call.

One honest disqualifier while we’re here. If you’re hiring across fifteen countries and what you actually want is a single dashboard, a global platform will serve you better than any Belarusian specialist — including this one. Accept that they’ll be shallow on Belarus specifically, and budget for local counsel to cover the gap. If Belarus is your engineering centre of gravity, the trade runs the other way. Either way, our HR consulting team is happy to tell you which of those two you are.

Eight red flags

1. They can’t name their own legal entity. If the EOR is subcontracting to an unnamed local partner, you have no contractual relationship with the company that actually employs your people. Ask for the tax number. If it takes three emails to get one, that’s your answer.
2. They propose engaging your team as sole traders and call it EOR. Covered above. This is the most common substitution in the market and the most expensive one to unwind.
3. The quote looks great because contributions aren’t in it. A price that undercuts everyone else by 30% is usually a price with a 35% line item missing. Ask for the itemisation.
4. They can’t explain the payment route. Cross-border payments into Belarus are subject to currency controls and to a sanctions regime that has been evolving since 2020. A provider who waves this away with “we handle it” is a provider who hasn’t thought about what happens when a transfer gets held. Read the relevant restrictions yourself — the UK, for instance, publishes statutory guidance on Belarus sanctions — and make your own compliance team comfortable before you sign anything.
5. No sample employment contract, or one with no IP assignment clause. If the assignment of work product isn’t airtight under Belarusian law, you may not own what your engineers build. This is the highest-consequence item on the list and the easiest to get subtly wrong. Have your own IP counsel read the Russian text, not a summary.
6. Silence on HTP status. See above. Silence here is informative.
7. “We can terminate anyone in two weeks.” No, they can’t. Belarus is a fixed-term contract jurisdiction with limited grounds for dismissal at the employer’s initiative, and a provider who promises casual at-will termination is promising you something they cannot lawfully deliver. Take it as a general indicator of how they treat the rest of the rules.
8. No exit clause. If the contract is silent on what happens when you move to your own entity, switch provider, or relocate the team abroad, then structurally your engineers belong to them and not to you. Walk.

The part everyone forgets: your engineers get a vote

Providers get evaluated on price and compliance. They get chosen or abandoned on something else entirely: whether the people actually transfer.

When you migrate a team from one employment model to another, you are touching things your engineers care about a great deal and you probably don’t think about at all — continuity of their employment record, their accrued leave, their seniority, their net take-home. In Belarus that record matters concretely: it follows them into mortgage applications and future job references. Companies that migrate without explaining any of this lose people. Not one or two. Sometimes a third of the team.

So add a thirteenth question, and ask it in the first call rather than the fifth: what exactly happens to my engineer’s employment record, their accrued vacation, and their net pay on transition day? A provider who can answer that fluently has done this before. A provider who hasn’t thought about it will cost you the team you were trying to keep. If the plan involves changing model — to outstaffing or to a PEO arrangement — the same question applies with knobs on.

When an EOR in Belarus is the wrong answer

Sometimes it is, and any provider unwilling to say so is selling rather than advising.

If your investors, your customers, or your own compliance function cannot tolerate Belarus exposure on the balance sheet, no amount of clever structuring fixes that. The answer is relocation — Poland, Lithuania, Georgia, Kazakhstan — and the sooner you have that conversation, the cheaper it is. If your engagement is genuinely project-based, short, and outcome-defined, a properly documented contractor relationship may be the correct instrument and an EOR is overkill. And if you’re planning fifty-plus hires and a long-term presence, an EOR is a bridge, not a destination; you should be modelling your own entity.

Where an EOR genuinely earns its fee is the middle: you want engineers in Belarus, you want them employed properly, you don’t want to spend nine months and a lawyer’s salary building an entity to find out whether the market works for you. That’s the case it’s built for. And if hiring inside the Park is the plan, our HTP recruitment team can run the search and the employment side together.

The short version

Ask for documents, not adjectives. Entity registration. Residency certificate. Sample contract. The IP clause in the original. The payment route, named. The liability cap, in numbers. Anyone who can produce all six in a week is a serious provider; anyone who can’t is selling you a logo.

And make them answer the awkward question — what happens to my engineers, and my code, and my money, on the day I want to leave. The answer to that one tells you almost everything else.

Weighing up providers, or trying to work out whether an EOR is even the right instrument for what you’re building? Talk to our team — we answer within two hours on any working day, and we’ll tell you if the answer is someone else.

Notice Periods and Garden Leave in Belarus IT Contracts: How to Negotiate a Clean Exit

A developer signs an offer with a company in Warsaw. They tell their new employer, confidently, that they have “a one-month notice period.” Then they walk into their current manager’s office in Minsk, and discover that their contract still has fourteen months to run — and that nobody is obliged to let them out of it.

This happens constantly. Belarusian IT runs on English-language HR vocabulary borrowed from London and San Francisco: notice, garden leave, PIP, non-compete. Belarusian labour law runs on something else entirely. The gap between the two is where offers fall apart, start dates slip, and perfectly good working relationships end badly.

So let’s clear it up. Here’s what the rules actually say, what employers can and can’t do, and how to negotiate an exit that leaves everyone able to work together again. If you’re on the other side of the table and trying to build a team in Belarus, our IT recruitment team deals with these conversations every week.

Key takeaways

• Garden leave, as a legal concept, does not exist in Belarus. What people call “garden leave” here is a negotiated arrangement, not an entitlement.
• Most Belarusian IT specialists work on a fixed-term contract. As a rule, that means you cannot simply hand in your notice and walk after a month.
• The real instrument for a clean exit is termination by mutual agreement. Almost every good exit in Belarus runs through it.
• Non-compete agreements are broadly unenforceable in Belarus — with one big exception for Hi-Tech Park residents, and even then the employer has to pay for it.
• None of this is automatic. It is a negotiation, and how you open it determines how it ends.

First, the uncomfortable part: garden leave isn’t a legal thing here

In the UK and much of the common-law world, garden leave is a recognised arrangement: you’ve resigned, you’re still on the payroll, you’re still bound by your duties of loyalty, but you’re not coming into the office. It buys the employer a cooling-off period and it protects the employee’s income.

Belarusian labour law has no equivalent instrument. There is no statutory mechanism that says “keep paying this person and don’t make them work.” The framework governing employment relationships in Belarus is built around a different set of assumptions, and “paid non-working notice” simply isn’t one of the categories it recognises.

That doesn’t mean the effect is impossible to achieve. It means you have to build it yourself, out of the tools that do exist — accrued annual leave, unpaid leave by agreement, an agreed handover schedule, or simply an earlier release date that both sides sign off on. More on that below.

The two contract types that decide everything

Before you can plan an exit, you need to know which contract you’re actually on. Most people don’t. Check your paperwork, because the answer changes what’s possible.

The fixed-term contract system dates back to 1999 and was folded into the Labour Code in January 2020. It is worth understanding the balance of power it creates: an employer can decline to renew a contract when the term expires without giving a reason, and, at least in principle, can also refuse an employee’s request to leave early — leaving the employee to argue the point in court. The US State Department’s investment climate report on Belarus describes the system in exactly these terms, and notes that the vast majority of Belarusian employees now work on term contracts.

This is the single most misunderstood fact in Belarusian IT hiring, and it catches out foreign employers as often as it catches out candidates. “When can you start?” is not a scheduling question here. It is a legal one.

So what do people actually use instead of garden leave?

In practice, teams improvise something that looks like garden leave out of ordinary components. None of these are rights. All of them are things you ask for.

• Accrued annual leave. Belarusian employees accrue paid holiday, and burning the balance at the end of a contract is the closest thing to a legitimate soft landing. It’s paid, it’s yours, and it doesn’t require anyone’s goodwill — only agreement on timing.
• Unpaid leave by agreement. Useful when you need a gap between roles and your employer would rather not have you in the codebase.
• A reduced handover period. Documentation, knowledge transfer, an offboarding checklist — no new feature work. Most managers will take this deal because it’s the thing they actually need.
• An agreed early release date. The cleanest option, and the one that requires the negotiation we’re about to get into.

If you’re an employer trying to design offboarding that doesn’t leak knowledge or goodwill, this is exactly the kind of thing our HR consulting work covers — building the process before you need it, rather than improvising it in a difficult week.

Termination by mutual agreement: the instrument that actually works

Here is the thing to internalise. Nearly every clean exit in Belarus — the ones where the leaving date is chosen, the handover is orderly, and the two sides still speak afterwards — goes through termination by agreement of the parties.

It works because it is the only route where both sides get something. You get out on a date you can commit to. Your employer gets a controlled handover, no dispute risk, and no surprise about when the seat empties. It can be signed for any date the two of you choose, including tomorrow.

Which means the entire game is making that signature easy to give.

Why employers say yes

• A replacement is lined up, or the search has started.
• The handover plan is already written and credible.
• The relationship is intact and they’d rather keep it that way — Belarusian IT is small, and people come back.
• Holding an unwilling engineer for a year buys them a disengaged year, not a productive one.

Why employers say no

• You’re mid-release, and your leaving blows up a client commitment.
• There’s no backfill and no budget for one.
• They think holding you gives them leverage on a counter-offer.
• It’s personal. This happens more than anyone likes to admit.

The fixable ones are the first two. Which is why timing matters more than eloquence — and why, if you’re the employer facing a wave of departures, the fastest way to unblock everyone is to close the backfill. That’s where outstaffing or a fast targeted search can turn a hard “no” into an easy “yes.”

The six-move playbook for a clean exit

1. Open the conversation before you sign, not after. Once you’ve signed elsewhere, you’ve handed your current employer all the leverage and none of the choice. Sound out the release date first, then commit to a start date you can actually keep.
2. Lead with the handover, not the resignation. Walk in with a written plan — what you’ll document, what you’ll transfer, to whom, by when. You are not asking for a favour; you are offering to solve their problem.
3. Don’t name the new employer unless you have to. It rarely helps you and occasionally hurts you, especially if the new company is a competitor.
4. Get it in writing, and get it signed. A Telegram message from your team lead saying “sure, no problem” is worth exactly nothing on your last day. An agreement signed by whoever is authorised to sign is worth everything.
5. Time the ask to the contract’s expiry window. Non-renewal is dramatically cleaner than early release, for both sides. If your term ends in four months, four months of patience may cost you far less than four months of conflict.
6. Know what you’re owed on the last day. Final settlement, unused leave compensation, any bonus terms. Read the contract before the conversation, not after it.

Non-competes and the Hi-Tech Park exception

Ask a Belarusian lawyer whether a non-compete clause in an ordinary employment contract is enforceable and you will generally get a short answer: no. The right to work is constitutionally protected, and a clause telling an ex-employee where they may not work runs into that head-on.

Then there is the exception, and it matters, because it covers most of the IT sector. Decree No. 8 “On the Development of the Digital Economy”, signed in 2017, imported a set of English-law instruments into Belarusian practice specifically for residents of the Hi-Tech Park — among them convertible loans, option agreements, and, crucially, non-competition and non-solicitation agreements with employees.

Two details do most of the work here:

• The restriction is capped at one year.
• It has to be paid for. For each month the former employee complies, the employer owes compensation of at least one third of that person’s average monthly salary over their final year. An unpaid non-compete is not a non-compete; it’s a piece of paper.

So if you’re leaving an IT company, three questions. Is the company an HTP resident? Did you sign a separate non-compete agreement — not a clause buried in the contract, but its own document? And does it specify compensation? If you’re an employer weighing up whether the regime is worth it in the first place, the Ministry of Economy’s overview of the HTP is a reasonable starting point, and we walk companies through HTP residency from application to certificate.

One more group: contractors and the self-employed

A meaningful slice of Belarusian IT never signed an employment contract at all. If you work as an individual entrepreneur or self-employed specialist on a services agreement, the Labour Code is not your rulebook — civil law is, and your contract is.

That cuts both ways. There is no statutory notice period protecting you, and no obligation on the client to keep paying you through a transition. But equally, there is no contract term trapping you, and the termination clause you negotiated is the whole story. Read it. It is usually two paragraphs long and almost nobody does.

For companies, this is also where classification risk lives. Getting the employment model right — direct hire, EOR and payroll, or a PEO arrangement — is a decision worth making deliberately, before the first offer letter goes out rather than after the first exit goes wrong.

If you’re the employer, read this bit

You can, in many cases, refuse to release someone before their contract expires. The question is whether you should.

An engineer who has mentally left and legally can’t is not an engineer you are getting value from. You get a year of quiet disengagement, a handover done badly on purpose, and a story that travels — because Belarusian IT is a small market with long memories and busy Telegram chats. The people you most want to hire next year are the people who hear that story.

The employers who come out of this well do three things: they backfill early, they treat the exit conversation as a scheduling problem rather than a betrayal, and they keep the door open. The ones who come out of it badly discover that a reputation for holding people hostage is a very expensive form of retention. If you’re hiring inside the Park and want the process to run cleanly from offer to onboarding, our HTP recruitment team can help.

The short version

You cannot rely on the vocabulary you learned from Western job ads. Garden leave isn’t here. Notice periods aren’t what you think they are. And on a fixed-term contract, leaving well is not a right you exercise — it is a deal you close.

Open the conversation early, bring the handover plan, get the agreement signed, and check whether a paid non-compete is sitting in your file. Do that, and the exit is clean. Skip it, and you find out the hard way.

Hiring in Belarus, restructuring a team, or trying to work out which employment model fits? Talk to our team — we answer within two hours on any working day.

EOR vs Setting Up Your Own Legal Entity in Belarus: Break-Even Math and Real Timelines

You’ve decided to hire in Belarus. Now you’re stuck on how. Employer of Record (EOR) providers will tell you to use an EOR. Corporate services firms will tell you to incorporate. Both are pitching the answer their business model prefers, and both are usually right — for some segment of the market.

We’re neither an EOR nor a company-formation firm. We’re recruiters. That means we don’t have a horse in this race: whichever setup you pick, someone still has to find you the people, and that’s where we come in. So this is our attempt at the honest version of the math — the setup costs, the ongoing costs, the real timelines, and the non-cost factors that quietly decide most of these calls.

One finding upfront that will shape the rest of the piece: incorporating a legal entity in Belarus is unusually cheap and fast compared with most jurisdictions. That fact changes the standard break-even calculus you may have seen for other countries.

Quick definitions, so we’re using the same words

Two models, briefly. EOR (Employer of Record) — a third party legally employs your Belarusian hire on your behalf. They own the contract, run payroll, handle statutory benefits and compliance, and carry the employer risk. You direct the work day-to-day. You pay them a monthly fee per employee plus pass-through of gross salary, taxes, and social contributions.

Own legal entity — you incorporate a Belarusian company (almost always an LLC), register with the tax authority and the social protection fund (FSZN), sign employment contracts directly with your team, and run your own payroll. You carry the compliance load; you own the relationship.

A third route people often confuse with these two: hiring your Belarusian specialist as a self-employed contractor (individual entrepreneur) on a B2B basis. It’s cheap and quick, but it’s a fundamentally different relationship — no employment protections, no statutory sick pay, no leave accrual. Used for genuinely independent work it’s fine. Used to disguise a full-time employment relationship, it’s a real misclassification risk. If that’s the direction you’re leaning, worth discussing with a recruiter familiar with the Belarusian IT talent market before you commit.

What setting up a legal entity in Belarus actually takes

Here’s the finding that changes the shape of the argument. Belarus is one of the fastest, cheapest jurisdictions in the region to incorporate. Registration of an LLC completes in a single business day once the paperwork is in order. Minimum share capital is essentially symbolic (you can start with the equivalent of 1 EUR). The state registration fee, if you file electronically through a notary, is zero — in-person filing costs about 10 EUR. 100% foreign ownership is standard, no local partner required, and a foreign national can serve as director without a work permit. For the underlying legal framework and the current investment climate, belarus.by’s business section is a good starting reference.

That said, “registered” isn’t the same as “operational.” The full timeline to your first clean payroll usually runs 3–6 weeks in practice — sometimes longer if founder documents need apostille or translation — because you still need to:

• Draft the charter (Articles of Association) and get founder documents notarised or apostilled in your home country
• Approve a company name and secure a legal address (a virtual address is legal and costs from ~15 EUR/month)
• Complete state registration and obtain the registration certificate
• Register with the tax authority and FSZN
• Open a corporate bank account (usually a day, but international banks take longer for foreign-owned entities)
• Get an electronic digital signature for filing (one-time, ~90 EUR)
• Sign up an accountant (in-house from ~600 EUR/month; outsourced from ~150 EUR/month for small operations)
• Draft compliant employment templates and run the first payroll cycle

Then there’s the HTP question. If your business is in eligible IT activities, applying for Hi-Tech Park resident status can change the tax picture dramatically — the headline being a 1% turnover tax for qualifying residents and a reduced personal income tax rate for their employees. The catch: the application takes additional time (2–4 months of preparation and review is typical), requires meeting activity criteria, and adds ongoing reporting. It’s a significant upside if you qualify, but it doesn’t come free.

Ongoing carrying cost for a small operational entity looks roughly like this: legal address 15–50 EUR/month, bank account fees ~10–30 EUR/month, outsourced accounting 150–600 EUR/month depending on transaction volume, plus periodic legal counsel. For a 3–5 person team, all-in ongoing overhead is realistically 700–1,200 USD/month before you touch salaries.

What using an EOR in Belarus actually takes

On the EOR side, the timeline is shorter and the operational lift is smaller — that hasn’t changed. Onboarding a Belarusian hire through an established EOR typically takes anywhere from 3 to 10 business days once you’ve chosen the provider and the contract is signed. Pricing across the current provider set for Belarus runs roughly $180 to $700 per employee per month on top of the pass-through of gross salary and mandatory contributions. Deel, Remote, Multiplier, RemoFirst, Playroll, Gloroots and several Belarus-native providers all operate here; the Papaya Global Belarus profile is a solid neutral reference for the employer-obligation side of that price.

Two Belarus-specific things to flag before assuming your usual global EOR of choice will handle Belarus:

• Provider availability shifted after 2022. Some global EORs restricted or paused Belarus service, and others price it as a premium market. Check availability and pricing at your specific point in time — don’t assume the vendor you use for Poland or Ukraine will handle Belarus on the same terms.
• Belarusian labour law is not particularly forgiving. Termination requires lawful grounds, notice periods are strict, and statutory severance for certain grounds can run up to three months’ average earnings. A weak EOR that doesn’t know Belarusian labour code will create expensive problems later. Ask for specific Belarus experience, not just “we operate in 150 countries.”

The break-even math, with numbers you can pressure-test

Here’s a working model at typical figures. We use a $400/month EOR fee as a mid-market anchor, and entity ongoing costs that scale realistically with headcount (more transactions, more HR admin, more legal touchpoints). Rounded to keep things directional — you’ll want to tune these against real quotes from two or three providers of each type.

Two observations most articles on this topic don’t give you honestly. First, the break-even in Belarus is unusually low. Because entity setup and ongoing accounting are genuinely cheap here — much cheaper than in Western Europe or the US — the pure-cost break-even often sits around 3–5 hires, not the 10–15 that’s typical elsewhere. Second, that’s not the number most companies actually pivot on. Because time-to-first-hire, management overhead, and reversibility matter more than the spreadsheet, most companies stay on EOR longer than the cost math alone would justify. That’s not irrational — it’s paying a premium for optionality. Just call it what it is when you make the choice.

Real timelines, side by side

Cost is one axis; time is the other. Here’s how the two paths compare when you’re honest about everything between kick-off and the first payroll cycle. For deeper detail on the incorporation steps, VMP’s corporate registration overview is a useful reference:

The often-cited “one business day” registration figure is real, but it’s the fastest possible piece of a longer chain. If someone quotes you 5 days to a running Belarusian entity, they’re either extremely well prepared or leaving out steps.

The non-cost factors that actually decide it

This is where a neutral read genuinely helps, because the standard content on this topic is written by parties with an interest in the outcome. Six factors that reliably tip the decision beyond cost:

• Speed to first hire. EOR still wins by weeks. If you have a candidate you can’t afford to lose and you need them starting next month, an entity isn’t on the table — even in a fast jurisdiction like Belarus.
• Length of commitment to the market. An entity is a signal — to your team, to the market, to your own leadership. Testing Belarus for a year? Don’t incorporate. Building a 30-person delivery centre over three years? Do.
• IP sensitivity. Under an EOR, IP assignment and confidentiality clauses run through a third party’s contract templates. Fine for most software work. Not fine for defence, regulated fintech, or sensitive R&D where clients or investors expect direct chain-of-title. If that’s your world, entity.
• HTP eligibility. If your business qualifies for Hi-Tech Park residency, the tax swing is large enough to flip the entity math even at low headcount — a 1% turnover tax and reduced personal income tax for employees is not a rounding error. Worth a dedicated look before you decide.
• Executive and senior hires. Some senior candidates — particularly C-suite roles or hires where equity is central — prefer a direct employment relationship with the actual company, not a third-party EOR. If you’re building around a senior executive hire, that preference can be strong enough to pull the incorporation decision forward.
• Banking and cross-border payment friction. As of 2025–2026, some international banks are cautious with Belarusian entities, and dividends paid to shareholders in the US, UK, Canada, or EU above roughly $1M annually require special procedure. This is a real operational consideration for entity owners — not a dealbreaker, but something to factor in early rather than discover after registration. For macro context on the operating environment, World Bank country data is a useful starting point.

A decision framework you can actually use

Distilling everything above into a short rule of thumb:

• Go EOR if: you’re hiring ≤5 people, your commitment to the market is under 18 months, speed to hire is critical, you don’t qualify for HTP, or you want to preserve easy exit optionality.
• Go entity if: you’re hiring ≥10 people and growing, your commitment is 3+ years, HTP eligibility is on the table, IP sensitivity is high, or executive/equity hires are central to what you’re building.
• Start with EOR, then transition if: you’re between 5 and 10 hires and want to prove the model before committing operational bandwidth. This is the well-trodden path — not a failure of planning, but a rational hedge. If you’re already thinking about standing up a full IT delivery team, plan the transition point up front so the switch doesn’t catch you at 15 hires with no runway.

The bottom line

For most companies hiring in Belarus, the honest answer is: EOR to move fast, then transition to your own entity once your headcount and commitment justify the operational lift. The pure-cost break-even can sit as low as 3–5 hires here — lower than in most jurisdictions — because Belarus is unusually cheap to incorporate and run. But cost is one input, and the ones that actually decide it are commitment horizon, HTP eligibility, IP sensitivity, and how central senior or executive hires are to the plan.

Whichever path you pick, the hard part isn’t the legal setup — it’s finding people worth hiring. That’s the layer we own. Our recruitment services plug into either model: we work alongside your EOR provider or your in-house HR team to source, screen, and close candidates against current market benchmarks. If you want the up-to-date compensation picture before you finalise your model, our IT salary research is a useful input.

Working out your Belarus setup? Talk to us — we’ll share what we’re seeing across current searches and help you plan the hiring side alongside your entity or EOR decision.

Sick Leave and Short-Term Disability for IT Employment Contracts in Belarus

If you’re hiring IT talent in Belarus for the first time, sick leave is one of those topics that looks straightforward on paper and turns into a compliance headache in practice. The rules feel familiar — people get sick, they take time off, someone pays them — but the mechanics don’t quite match what US, UK, or EU employers are used to. Which is exactly where mistakes happen.

The good news: once you understand how the Belarusian system actually works, it’s not particularly onerous. Sick pay is state-funded through employer social contributions, the calculation is predictable, and the cost is largely baked into what you’re already paying. The bad news: assume it works like your home market and you’ll misjudge total cost of employment, run into documentation issues, and — in the worst case — push candidates toward competitors who present the offer more clearly.

This guide breaks down exactly how sick leave and short-term disability function for Belarusian IT employees on a proper employment contract: who pays, how much, what triggers it, where the caps sit, and what the whole thing means for your budget and your offer.

Employment contract or B2B? The distinction that decides everything

Before you can talk about sick pay, you have to be honest about which working relationship you’re actually in. In Belarus, that matters more than in most markets — and it’s the single biggest reason foreign employers get confused.

Sick-leave entitlements only apply to employees on a proper employment contract governed by the Belarusian Labor Code. If your Belarusian IT specialist is registered as a sole entrepreneur and invoicing you on a B2B basis — which is extremely common in the local IT market — they are not entitled to statutory sick pay, they don’t accrue vacation, and the social protection system doesn’t cover them the same way. That’s not a loophole; it’s a fundamentally different arrangement, and the official employment law overview spells that out plainly.

For years, the sole entrepreneur model was the default in Belarusian IT because of favourable tax treatment. That’s shifted, and more employers now hire through employment contracts — especially those working with candidates who want stability, or those that are residents of the Hi-Tech Park regime. Which model you use should be a deliberate decision informed by tax, compliance, and talent-strategy factors, not a shortcut to avoid statutory benefits. Misclassifying a full-time worker as a sole entrepreneur is a real legal risk, and it’s one of the first things a serious IT recruitment partner will pressure-test with you before you make an offer.

How sick leave actually works in Belarus

For employees on an employment contract, sick pay is a statutory social insurance benefit, not a discretionary employer perk. The mechanics are the same whether your company is a small startup or a large HTP resident.

Three things drive the system:

• The trigger. Sick leave kicks in when a valid medical certificate of temporary incapacity for work is issued by a state-authorised medical institution. No certificate, no statutory sick pay — informal “I’m not feeling great” days don’t count.
• The funder. Payments come from the state Fund of Social Protection of the Population (FSZN). Employers pay ongoing social contributions to FSZN as part of standard payroll taxes, and the fund reimburses sick-pay disbursements. In practice, the employer runs the payment through payroll on the employee’s normal payday and then recovers it from FSZN.
• The scope. Statutory sick pay covers personal illness or injury, caring for a sick child or family member, and a handful of related situations. It’s separate from maternity leave, long-term disability, and annual paid vacation — all of which are governed by their own rules.

There’s no fixed employer-side day cap on illness itself — the medical certificate governs how long the leave lasts — but in practice a single episode is typically covered up to 120 days. Beyond that, the case usually transitions into the disability-assessment track (see below).

Payment rates: what the calculation actually looks like

This is where you get a specific answer to “what will this cost me?” The current formula for general personal illness or injury is: 80% of the employee’s average daily earnings for the first 12 calendar days of the sick-leave episode, then 100% of average daily earnings from day 13 onwards. Multiple international benefits references — including Papaya Global’s Belarus country profile — confirm this structure, and it’s held stable in recent regulatory updates.

Two important nuances:

• Family care leave pays at 100% from day one when the employee is caring for a sick child under 14 or a disabled child under 18, subject to statutory day limits per case.
• The monthly benefit is capped at roughly three times the national average monthly wage. For senior IT engineers earning well above the national average, that ceiling matters: sick pay won’t fully replace their actual salary during the leave. It’s not a compliance risk — it’s a candidate-experience issue, because engineers whose comp gets meaningfully compressed during a long illness will notice.
• Reduced or denied pay applies where the illness resulted from intoxication or the employee violated the prescribed sick-leave regime (e.g., missed follow-up appointments). Edge case, but worth knowing.

A quick worked example to make it concrete. For an engineer with average earnings of 3,500 BYN per month who takes a 14-day sick leave for a common illness:

The precise numbers vary based on the reference period used for the average-earnings calculation, statutory caps, and whether the employer is an HTP resident (in which case some calculations reference the minimum wage rather than average earnings). But the shape of the answer is what matters: this is not a scary line item.

Short-term disability vs. sick leave: the terminology bridge

If you’re coming from a US or UK context, “short-term disability” (STD) usually means a specific insurance product — sometimes employer-sponsored, sometimes voluntary — that pays out when someone can’t work for weeks or months due to illness or injury. That’s not really how Belarus does it.

In Belarus, most of what employers elsewhere would classify as short-term disability sits inside the statutory sick-leave system funded by FSZN. There’s no mandatory private STD insurance for employers to buy, no separate elimination period to navigate, and no external insurer in the loop. The state system covers it. Long-term or permanent disability follows a completely different track: an employee is assessed by a medical panel, assigned a disability group, and moves onto disability benefits paid by the social protection system. That process is out of scope for this guide, but Rivermate’s Belarus leave overview gives a useful side-by-side of all the statutory leave categories if you want the broader map.

Where private insurance does come in is on the voluntary side. Many Belarusian IT employers layer supplemental medical insurance and sometimes income-protection cover on top of the statutory system as a competitive benefit. More on that below.

Documentation, timing, and the payroll process

The compliance side is where foreign employers most often trip up — usually by trying to run a process that would work at home and finding it doesn’t quite fit.

The essentials:

• The medical certificate is non-negotiable. A valid medical certificate is non-negotiable from an authorised medical institution is what triggers statutory sick pay. You can’t waive it in the employment contract, and you shouldn’t try to — without the certificate, you can’t recover the payment from FSZN.
• Notification is on the employee. The employee is expected to notify the employer of their incapacity and submit the certificate when they return. Best practice is to define this notification process clearly in your internal policy: same-day notice by message or email, certificate submitted within a set number of days after returning.
• Payment runs through normal payroll. Once the certificate is in hand, the employer calculates the sick pay per the formula, disburses it on the employee’s next regular payday, and files the appropriate paperwork with FSZN for reimbursement.
• Records matter. Keep every certificate, every calculation, and every reimbursement claim on file. Labour inspections in Belarus are documentation-heavy, and clean records make the difference between a routine check and a costly one — a discipline that also matters when you’re hiring senior technical leaders whose comp packages are more complex.

The single most common foreign-employer mistake is trying to negotiate around the medical certificate, treating it as an inconvenience or a formality. It isn’t. It’s the whole basis on which the state fund reimburses you. Skip it and you’re paying out of pocket — or, worse, discovering during an inspection that you’ve been running an informal system for years.

What this means for total cost of employment

Zoom out to the CFO’s view. Sick leave in Belarus is not a surprise cost item, because you’re already paying for it through the standard employer social contribution to FSZN. That contribution funds sick pay, maternity leave, pensions, and other social benefits collectively. When an employee is out sick, you disburse the payment and get reimbursed. Your ongoing cost is the contribution rate, not the individual event. Standard reference sources such as World Bank country data put Belarus’s overall labour cost load in the moderate range for the region.

Two costs you should actually watch:

• Productivity loss during the illness. Payroll is neutral, but the work isn’t happening. For small teams, a two-week sick leave from a key architect or lead engineer is a real disruption that no reimbursement covers.
• Voluntary benefit spend. If you decide to layer private medical insurance or extra self-certified sick days on top of the statutory package (and to be competitive at senior levels, you probably should), that’s a genuine incremental cost. Budget it deliberately — our IT salary and benefits research gives current benchmarks.

Compared with Western European mandatory sick-pay regimes — where the employer often carries the full cost for weeks before any state support kicks in — the Belarusian model is comparatively employer-friendly. Here’s how it stacks up against two common reference points:

What strong IT employers add on top

Statutory sick pay is the floor, not the offer. In a competitive IT market like Belarus’s — anchored by the Hi-Tech Park regime, which hosts most of the country’s serious IT employers — the benefits package is what separates a mediocre offer from a compelling one. A few things now sit close to table stakes at senior levels:

• Voluntary medical insurance. Increasingly expected at mid and senior IT levels. Employees value faster access to private clinics and broader coverage; employers value the reduced friction of shorter, cleaner absences.
• Extra self-certified sick days. A handful of paid days per year that don’t require a medical certificate, letting people take a day for a bad cold without triggering the full statutory process. Popular with modern IT employers and cheap to offer.
• Mental-health support and flexible/remote arrangements. Not a sick-leave benefit strictly, but part of the same conversation about how you support people through the ordinary friction of being human at work.

These are the levers you’ll pull differently depending on whether you’re hiring one specialist or standing up a full IT team — in the latter case, benefits design is a strategy decision, not a one-off negotiation.

The bottom line

Sick leave and short-term disability for Belarusian IT employees are simpler than they look once you strip out the terminology mismatch. Statutory sick pay is state-funded through FSZN, paid at 80% for the first 12 days and 100% thereafter, triggered by an official medical certificate, and reimbursed to the employer through the normal payroll process. Short-term disability, as most Western employers understand it, is folded into that same system. The real budget items to watch are productivity loss during longer episodes and the voluntary benefits you layer on top to stay competitive at senior levels.

Getting the mechanics right is table stakes; running the whole hiring process compliantly and competitively is where the real work sits. Our IT recruitment services cover sourcing, pre-vetting, and offer construction against local benchmarks, so the specialists who reach your interview stage come with clean expectations and you’re not reverse-engineering compliance under time pressure.

Ready to hire in Belarus? Talk to our team and we’ll walk you through it.

Hiring Solutions Architects: What to Look For and How to Assess Them

Some hires you can afford to get wrong. A Solutions Architect isn’t one of them.

Sitting squarely between your business goals and your engineering team, a Solutions Architect (SA) turns “here’s what we’re trying to achieve” into a technical design your developers can actually build. Get the hire right, and projects ship on schedule, systems scale without drama, and your technical and business teams finally speak the same language. Get it wrong, and the cost shows up slowly — over-engineered systems, runaway cloud bills, integrations that never quite click, and a roadmap that slips quarter after quarter before anyone traces it back to a design decision made months earlier.

Here’s the tricky part: the best Solutions Architects rarely look like the strongest coders in the room, and the interview tactics that work for developers can steer you straight toward the wrong person. A brilliant engineer who can’t walk a CFO through a trade-off, or who reaches for the most elegant design instead of the most appropriate one, will struggle in this seat no matter how clean their code is.

This guide breaks down how to hire a Solutions Architect the right way: how to define the role you actually need, the skills that genuinely predict success, and a repeatable way to assess candidates without falling back on gut feel.

First, get clear on the role you’re actually hiring for

The most expensive mistake in this hire happens before the first interview: the job title does more work than the job description. “Solutions Architect” gets thrown around loosely, and teams end up interviewing for a role no one has actually agreed on. One stakeholder pictures a hands-on technical lead. Another pictures a customer-facing expert who helps close deals. The candidates you attract match neither.

So start here. At its core, a Solutions Architect designs the end-to-end technical solution to a specific business problem. Hand them a requirement — “we need to handle ten times our current order volume” or “we need to merge three legacy systems into one platform” — and they produce a coherent design your engineers can implement. They think in systems: how the pieces fit, where the data flows, how the APIs connect, and what happens to security, scalability, and cost along the way.

That role blurs into several neighbours, though, and picking the wrong template will cost you good candidates while attracting the wrong ones. Before you write the job post, decide which of these you’re really after — and be honest about the level, because a senior architecture hire often sits alongside your other leadership and executive searches, where getting the seniority right matters as much as the title.

A fast way to pin down your version: is the hire delivery-focused (designing what your team builds) or pre-sales-focused (designing what you sell)? Is the work mostly greenfield, or untangling what already exists? Will they live inside one product or stitch many together? Your answers change the seniority you need and how you’ll assess it. If you’re really after organisation-wide technology strategy, you may want an enterprise architect and a framework like TOGAF; if you need one complex application owned end to end, that’s closer to a software architect. Mixing these up is one of the most common — and costly — hiring misses.

What to look for: the skills that actually predict success

Developers are prized for depth. Solutions Architects are prized for breadth — the ability to see a whole system, and everyone who touches it, and make sound calls across all of it. The skills worth screening for cluster into a handful of areas.

Systems design and technical breadth. This is the foundation. A capable SA understands integration patterns, API design, data modelling, event-driven approaches, security, and how systems behave under load. They don’t need to be the deepest expert in any one of these — they need enough command of all of them to design something coherent and spot where it will break.

Cloud fluency. Most modern architecture lives on AWS, Azure, or GCP, so hands-on familiarity with at least one major cloud is close to non-negotiable. A credential like the AWS Certified Solutions Architect is a useful signal that someone has put in the study — but treat it as a starting point, not proof. Plenty of certified candidates have never shipped a production system, and plenty of excellent architects let their certs lapse. Verify the underlying skill directly.

Business translation. This is the defining talent. A great SA moves fluidly between two languages — business and technical — understanding what the company is really trying to achieve, turning it into technical requirements, then explaining the design and its trade-offs back to leaders in the terms they care about: cost, risk, timeline, and outcomes.

Communication and stakeholder management. An architect’s design is only as good as their ability to get people to build it. They spend their days aligning engineers, product managers, and executives — the same cross-functional influence that defines strong Tech Leads and other senior engineers. Clear writing, clear diagrams, and the patience to bring people along matter as much as technical judgement.

Trade-off thinking and pragmatism. There’s rarely one correct architecture, only a set of trade-offs. Strong candidates instinctively weigh the ideal against the feasible — given the budget, the team’s skills, and the timeline. They’re comfortable with “good enough for now, revisit later,” and they reason clearly about build versus buy.

Influence without authority. Solutions Architects usually guide teams they don’t manage. They can’t order people to follow the design — they earn buy-in through credibility and clear reasoning. Probe for real examples of moving an organisation without holding formal power over the people in it.

A learning habit. The technology landscape shifts constantly — a quick look at the annual Stack Overflow Developer Survey shows just how fast tools and preferences move. The best architects are visibly continuous learners who keep their knowledge current, ideally with relevant domain experience (fintech, healthcare, e-commerce) that shortens ramp-up time.

How to assess Solutions Architect candidates: a practical framework

This is where most hiring processes fall apart. Teams either interview an architect like a senior developer — heavy on coding puzzles that reveal little about design judgement — or they run loose conversations and hire on vibes. A structured, multi-stage process is the reliable way to assess candidates, because it tests the things the role actually demands and lets you compare people fairly. If you’d rather not build and run it in-house, this is exactly the kind of process a specialist IT recruitment partner can handle for you.

1. Screen for ownership, not activity. Look past the list of technologies on the CV. What you want is evidence that this person has owned end-to-end solutions and delivered them at real scale. Which business problems did they solve? What did they design, and what happened when it shipped? “Contributed to” many systems is very different from “architected” a few and saw them through to production.

2. Run a system design interview. This is the heart of the assessment. Give an open-ended, realistic prompt — “design a system to handle X” — ideally close to a problem your company actually faces. Then watch how they work, because the process tells you more than the diagram. Strong candidates clarify requirements and constraints before proposing anything. They structure the problem, sketch the major components, and reason out loud about trade-offs, scale, data, security, failure modes, and cost. Push on their choices: “What happens if traffic spikes tenfold?” You’re testing judgement under questioning, not a memorised right answer.

3. Use a scenario or take-home case. For a deeper read, give a realistic business problem and ask for a short written proposal: the architecture, the reasoning, and the alternatives they rejected. This shows how they think with time to reflect — and how clearly they document a design for others to follow. Keep the scope reasonable; a bloated take-home will scare off your strongest candidates, who have options.

4. Test communication directly. Since translating between business and engineering is the job, assess it on purpose rather than hoping it shows up. Have the candidate present a solution to a mixed panel of technical and non-technical people. Can they make an executive grasp the value and the risk, then switch registers and go deep with an engineer? This step catches the technically excellent candidate who can’t carry a room.

5. Interview for behaviour and track record. Use structured, STAR-style questions to probe how they’ve operated in the real world: architectures they’re proud of, decisions that went wrong, and moments a stakeholder pushed back. How they describe failure is especially telling — mature architects talk openly about trade-offs that didn’t pan out, while weaker ones describe every past decision as flawless.

6. Score everyone on the same rubric. Before interviews begin, agree on the competencies that matter and build a shared scorecard. Have every interviewer rate every candidate on the same dimensions. Structured scoring cuts bias, replaces “I liked them” with evidence, and makes the final decision far easier to defend — a practice long championed by bodies like SHRM for exactly that reason.

A starter set of Solutions Architect interview questions

You’ll tailor these to your stack and domain, but this bank consistently separates strong candidates from rehearsed ones:

• Walk me through a system you designed end to end. What was the business problem, and what were the key decisions?
• Design a system to handle [a scenario close to your business]. Talk me through your thinking as you go.
• Tell me about an architecture decision you got wrong. What happened, and what would you do differently?
• How do you decide between building a capability in-house and buying an existing solution?
• Describe a time you convinced a team to adopt a design they initially resisted.
• How do you factor cost into your architecture decisions? Give a concrete example.
• A stakeholder wants a feature that would seriously compromise scalability. How do you handle that conversation?
• How do you keep your technical knowledge current?

Red flags to watch for

Certain patterns reliably predict trouble, and they show up most clearly in the system design and communication stages:

• They jump to a solution before understanding the problem.
• They defend one “right” answer instead of discussing trade-offs.
• They can’t simplify — if a non-technical listener is lost, stakeholder management will be a constant struggle.
• They over-engineer, reaching for maximum complexity when the problem calls for something simpler.
• Buzzwords without substance that dissolve under a couple of follow-up questions.
• They can’t say “I don’t know” — bluffing is riskier in an architect than admitting a gap and reasoning toward an answer.

Common hiring mistakes to avoid

Beyond individual red flags, four process-level mistakes derail otherwise solid searches: over-weighting certifications; interviewing an architect like a developer; skipping the communication assessment; and running unstructured interviews with no shared rubric. Avoid those four and you’ve already outpaced most hiring teams. And if speed matters and you need to stand up a full team quickly, it can be faster to bring in a partner who can assemble an entire IT team than to run every search yourself.

The bottom line

Hiring a Solutions Architect well comes down to three moves: define the specific version of the role you need, screen for the breadth and business-translation skills that predict success rather than raw coding depth, and assess candidates through a structured process that tests design judgement, communication, and track record against a shared rubric. Do that, and you dramatically raise your odds of landing someone who makes your projects faster, your systems sounder, and your roadmap more reliable.

The catch: architects this good are in high demand and rarely browsing job boards, and running the process that identifies them takes real time and technical expertise. That’s where a specialist partner earns its keep. Explore our IT recruitment services to see how we source and pre-vet candidates against exactly the criteria above, so the people who reach your interview stage have already cleared the bar.

Ready to make your next hire? Talk to our recruiters and skip the guesswork.