Как открыть R&D-центр в Беларуси: от нуля до 30 сотрудников

A 30-person R&D center in Minsk can be fully staffed in 12 to 15 months. When the schedule slips, it is rarely because of hiring. It slips because of paperwork and decisions that nobody made on time at headquarters.

This guide walks through the process in order: deciding whether you need your own center, choosing a legal setup, getting Hi-Tech Park residency, hiring the first team and scaling it to 30. The timings and figures below are typical benchmarks, not guarantees. Your numbers will depend on the seniority of the team and how fast your own side makes decisions.

When a captive R&D center makes sense

Many software companies grow engineering through outsourcing vendors. That works until it doesn’t. These are the usual signs it’s time for a center of your own:

• Vendor engineers rotate every few months, and product knowledge leaves with each of them.
• Your roadmap depends on long-lived core work, such as a new product module or a platform, that needs a stable team.
• Hiring at headquarters is slow and expensive, and senior roles stay open for months.

A captive center means your own legal entity, your own employees and all code owned by the group.

Write the brief first

Before choosing a country or a setup, agree a short brief with the CTO, the VP of Engineering and the CFO. It should fix:

• Headcount and deadline, for example 30 people in 12 to 14 months.
• Team structure, for example two product teams with shared QA and DevOps.
• Cost ceiling per head, agreed with the CFO up front.
• Relocation: whether anyone from headquarters will move.
• Headquarters involvement, for example a monthly visit from the VP of Engineering for the first six months.

Why companies choose Belarus

• Time zone. Minsk is one hour ahead of Central European Summer Time and two hours ahead in winter. A 10 a.m. standup at headquarters lands at lunchtime in Minsk, so nobody joins calls late at night.
• Hi-Tech Park benefits. A resident company pays no profit tax on qualifying activity, its social contributions are capped at the national average wage, and it can hire foreign specialists without work permits. For a team made up mostly of senior engineers, the contribution cap alone makes a real difference to the budget.
• Talent you may already know. Companies often discover that some of their best vendor engineers already live in Minsk, which gives them a realistic view of the local market.

Choose your legal setup

For most companies the last option works best. Hi-Tech Park benefits apply only to a Belarusian company with resident status, but you don’t have to wait for that status to start hiring.

Step 1: Write a half-page charter

Start with one workshop with the CTO, the VP of Engineering and the CFO. The output is half a page that says what the center will own in its first six months, who it will work with day to day and which stack it inherits.

Use that text in every job ad and recruiter brief. It also settles later arguments about what the team is actually for.

Step 2: Run three tracks in parallel

The biggest time saver is not waiting for one track to finish before starting the next. If you wait for Hi-Tech Park status before looking for a head of R&D, reaching 30 people will likely take two or three months longer.

Track 1: Register the company and open a bank account

• Documents. Founding documents are signed at headquarters, notarized, apostilled and couriered to Minsk. Check the customs paperwork before shipping: one missing form can hold documents at a depot for days.
• Registration. Registering the LLC usually takes less than a week once the documents arrive.
• Bank account. This is the slow part, often about five weeks. Banks typically ask for a group structure chart, details on every beneficial owner and proof of where the charter capital comes from, sometimes in more than one round. Collect these documents on day one instead of waiting to be asked.

Track 2: Prepare the Hi-Tech Park business project

The business project for the Hi-Tech Park is the document the Supervisory Board actually reads. It describes what the company will do, how many people it will employ, how much it will invest and how it will earn money.

A captive center usually bills the parent for development work at cost plus a markup. Agree that intercompany markup with the group’s tax adviser before anyone starts writing, because waiting for the number can easily cost two weeks. The Supervisory Board usually decides four to six weeks after filing, so expect two to three months for residency from scratch.

Track 3: Start the head of R&D search in week one

This is the slowest hire everywhere, and Minsk is no exception. Strong candidates usually have a bonus they’re waiting for, a release they don’t want to abandon and a couple of other offers. A realistic benchmark is an accepted offer around week six and a start date around week ten, after a month’s notice.

Step 3: Hire your first people through an Employer of Record

While your company can’t employ anyone yet, the first hires can join through an Employer of Record. Legally they work for the provider; in practice they work full time for you. A typical first group is the head of R&D, two senior engineers and a DevOps engineer.

• Say it in the offer letter. State up front that people will move to your own company after a few months, in the same role and on the same salary. Learning about a change of employer in month four, even one only on paper, makes people nervous.
• Make the transfer seamless. Once residency is granted, sign the new contracts and personnel orders on the day the old ones end, so pay doesn’t skip a beat.
• Keep the workspace simple. A coworking space with a few reserved desks is enough for the first handful of people.

Step 4: Hire in the right order

The order that works for most first teams is the lead first and seniors before middles, then the roles that keep delivery steady:

1. Head of R&D.
2. Senior engineers and a first DevOps engineer.
3. QA and a second DevOps or platform engineer.
4. Middle developers.
5. Junior developers, once seniors have time to mentor.
6. A product owner, once backlog questions start waiting for calls with headquarters.
7. An HR and office generalist, at about ten people rather than twenty.

Step 5: Shorten the interview process

Copying the headquarters interview loop is a common mistake. Five rounds, three of them with people abroad, stretched over a month, will lose strong candidates in Minsk. With a loop like that, offer acceptance can sit around 55%.

A process of about ten days typically pushes acceptance to around 80%:

1. A recruiter call.
2. A technical interview run locally.
3. A 45-minute conversation with an engineering leader at headquarters.

Step 6: Protect accepted offers from counteroffers

Senior engineers in Minsk often get a matching offer from their current employer during their notice period. A few simple habits keep accepted offers from falling through:

• The head of R&D calls every new hire at least once during their notice month.
• Laptops go out a week before the start date.
• New hires are invited to a team lunch before they officially join.

Step 7: Move into a proper office before you reach ten people

Coworking rarely works beyond about ten people, so start viewing offices early. A ready, fitted-out office only needs furniture, network and access control, and a team can move in about four weeks after signing. A bare shell can take three months or more.

As a sizing benchmark, about 280 m² holds 32 desks. If you can, negotiate first refusal on the unit next door.

Step 8: Turn onboarding into a system

Once new people arrive every two or three weeks, onboarding can’t be improvised. Give every new hire:

• a buddy;
• a written plan for the first week;
• a one-on-one with their manager within the first five days.

The last item is the first to slip when a lead spends half the week interviewing. Microsoft’s people analytics team found that new hires who meet their manager in their first week build their internal networks noticeably faster. With this setup, most middle engineers can merge production code on their own within about two months.

Step 9: Scale from 15 to 30

• Promote the second team lead from within. A senior engineer who already knows the codebase and has the team’s trust is often a better choice than another external search. It also shows everyone there is room to grow, which helps with retention.
• Expect referrals. After about six months, roughly a third of new hires can come through employee referrals.
• Add juniors, a product owner and HR as described in Step 4.
• Outsource the back office. A management company in Belarus can handle accounting, payroll, tax and Hi-Tech Park reporting, HR records and supplier contracts. That lets a 30-person center run with a single non-technical person on site.

Step 10: Build a culture that works across borders

How people behave on calls matters as much as headcount. Practices that work well in distributed teams:

• blameless incident reviews from day one;
• a demo every other Friday that anyone at headquarters can join;
• the right to challenge any architecture decision, as long as you bring an alternative.

New teams are often too polite with headquarters, and they need to learn to argue. Google’s research on its own teams found psychological safety to be the strongest predictor of team effectiveness. In a distributed setup, where people disagree with colleagues they have never met, it probably matters even more.

Over time, aim to move the center from receiving tickets to setting its own quarterly goals with the product director. At that point, regular trips from headquarters can usually stop.

Step 11: Budget for the predictable risks

• The DevOps bottleneck. When two teams share one DevOps engineer, releases back up. Plan a second platform engineer before the second team is fully staffed.
• Salary drift. Senior salaries in Minsk can move faster than an annual review cycle. Build a mid-year salary adjustment into the budget from the start. Raising someone’s pay three months early costs far less than replacing them.

A realistic timeline from 0 to 30 people

For reference, one 30-person launch on this timeline averaged 31 days from opening a role to an accepted offer, and about seven weeks for leads. First-year spending came within 5% of budget, and the fully loaded cost per person was roughly 40% of the same grades at headquarters.

Common mistakes to avoid

• Leaving the intercompany markup undecided until the business project is being written.
• Waiting for the bank to ask for compliance documents. It always asks.
• Copying the headquarters interview loop.
• Not telling EOR hires about the transfer at the offer stage.
• Hiring the HR and office person at twenty people instead of ten, which leaves the head of R&D ordering chairs instead of interviewing.
• Letting one DevOps engineer serve two teams.
• Skipping the mid-year salary buffer.

Conclusion

Thirty people in about 13 months is achievable, and most delays come from paperwork and internal decisions rather than hiring. Register the company, apply for Hi-Tech Park residency and start recruiting at the same time. Hire through an EOR until your entity is ready, keep the interview process short and agree the hard decisions, such as the intercompany markup, in the first week.

If you’re planning an R&D center in Belarus and want a second opinion on your timeline and budget, get in touch.