The conversation usually starts the same way. A senior engineer asks for a one-on-one, closes the door, and says they’ve been talking to another company. Sometimes there’s a written offer attached. Sometimes there isn’t. Either way, the next forty-eight hours will decide whether you keep one of the people your team can’t easily replace — and whether you keep them at a price that doesn’t quietly reset the rest of your compensation grid.
For international employers running engineering teams in Belarus, this moment carries a few extra wrinkles. The talent pool is dense but finite. Senior developers are well-networked and know what the market pays. And the natural reflex — match the offer, add ten percent, move on — is the most expensive option on the table, and usually not the most effective one.
This is a framework for handling that conversation deliberately rather than reactively.
The case against counter-offers is well documented. Most HR leaders have come across the often-cited figure that a high percentage of employees who accept a counter leave within a year anyway — and there’s solid commentary from practitioners reaching the same conclusion in Harvard Business Review’s analysis of counter-offer downsides. The dynamic is consistent: once an employee has gone to market, the trust ledger has already shifted. A pay rise resets the number on the contract, not the reason they were looking.
That doesn’t mean counter-offers never work. It means the ones that work tend to address the actual reason someone was open to another conversation in the first place — and the actual reason is rarely the gap between your salary and the new one.
The Stack Overflow 2025 Developer Survey ranks autonomy and trust, competitive pay, and solving real-world problems as the top three drivers of job satisfaction, with interpersonal factors several places behind. The takeaway is not that pay doesn’t matter — it does, especially when it falls clearly below market. It’s that pay is one of three things doing the work, and when an employee is leaving for the other two, raising the first one doesn’t fix anything. You can read the full breakdown on the official Stack Overflow Developer Survey site.
For senior Belarusian developers specifically, this matches what we see in practice. The engineers walking away from competitive base salaries are usually walking towards scope, leadership, technical challenge, or a specific product they want to work on. The ones walking away from pay are doing so because the pay genuinely lagged.
Before designing a counter-offer, it helps to anchor in the market your employee is actually negotiating against.
The Belarusian senior developer market is shaped by three forces running at the same time. First, High Tech Park residency, which gives accredited employers a 9% personal income tax rate, a simplified currency control regime, and the legal toolkit (option agreements, formal non-competes, indemnification clauses) imported under Decree No. 8. The official HTP overview lays out the broader regime. Second, an active remote market — Belarusian engineers field offers from EU, UK, US, and UAE-based employers, often at headline figures that look high in ruble terms but normalise once tax and cost-of-living are factored in. Third, a meaningful share of the senior population has either relocated or works for foreign employers through an EOR arrangement, which compresses the local supply at the top end.
Net effect: senior Belarusian engineers are price-aware, internationally benchmarked, and rarely surprised by what their own market value looks like. Bluffing on numbers doesn’t work.
This is where a current internal salary benchmark earns its keep. If you don’t already run one, our team publishes the methodology and findings of salary survey work in Belarus — knowing where each role sits against the median and the upper quartile makes the counter-offer conversation faster and more honest in both directions.
The most common mistake employers make is treating a counter-offer as a number problem. It’s a diagnostic problem first, and a number problem second.
Before you put any new figure on the table, sit down with the employee and find out:
Treat this as one conversation, not a single meeting. Senior engineers usually need a day to articulate what’s actually driving the move, and the first answer is almost never the whole answer.
This is the question employers skip. Not every senior departure is worth a counter-offer.
The candidates worth fighting hard for share a few markers: they own institutional knowledge that would take six months and a meaningful salary to replace; they shape the technical culture of the team; their departure would trigger other departures; they hold relationships with clients, regulators, or partners that don’t transfer easily. The candidates not worth a heroic counter share the opposite markers: they’re senior in title but middling in impact, they’ve been signalling disengagement for a while, or the underlying issue is one a higher salary can’t fix.
Saying this clearly inside the management team — before anyone walks into the room with the employee — is half the discipline. It stops the conversation drifting into a reflexive match.
If you’ve decided to counter, the framework that works is roughly this:
Close real pay gaps, ignore artificial ones. If your benchmark puts the employee 15% below market and the new offer is at market, the gap was real and the counter should close it. If they were already at the 80th percentile and the new offer is at the 95th, you’re being asked to overpay against your own grid — and matching it usually destabilises the rest of the team within a quarter when colleagues find out.
Don’t lead with cash if cash wasn’t the issue. If diagnosis surfaced scope, growth, or technical challenge as the real driver, lead with those. A tech lead title, ownership of a specific module, a formal mentorship of two juniors, a budget for conference travel, a 10% time allocation to a project they care about — these often cost less than a 20% raise and move the needle harder.
Use one-off instruments for one-off problems. A retention bonus, paid against a 12-month or 18-month stay, is cheaper and less distortive than a permanent salary increase, and it signals seriousness without resetting the grid. The same logic applies to deferred bonuses tied to a product milestone.
Use the non-cash levers Belarusian law actually supports. For HTP residents, this is where the toolkit gets interesting. Option agreements, phantom equity, SARs, and deferred cash structures are all available, with real preferential tax treatment. We’ve covered the mechanics in the post on equity and long-term incentives for Belarusian IT employees. For senior engineers, a thoughtfully designed phantom equity grant often outperforms a salary uplift on both retention and economics.
Be honest about what you can’t fix. If the employee is leaving because they want to work on autonomous vehicles and you build accounting software, a counter-offer won’t bridge that. Wishing them well, structuring a clean handover, and keeping the door open is the better long-term move.
Patterns we see across HTP residents and IT employers in Belarus:
The shape of the counter matters more than the size. A 12% base increase plus a structured scope expansion plus a phantom grant is more durable than a 25% raise on the same role.
The conversation doesn’t end when the employee accepts. Three things usually decide whether the counter actually holds:
A documented re-engagement plan. What changes about the role over the next ninety days. Who they report to, what they own, what they’re working on. Without this, the original drivers come back within a quarter.
Confidentiality, within reason. The detail of any individual counter-offer doesn’t need to circulate. The principle that the company values senior tenure and rewards it does.
A check-in at six months. The HBR commentary on post-counter attrition is sobering. The mitigation is straightforward: don’t let six months pass without a real conversation about whether the conditions of the original conversation have actually changed.
In most cases, no — at least not as the first move. Matching the headline number treats what’s on the screen and ignores what’s actually going on underneath. Run the diagnosis first. If your benchmark shows the employee genuinely lagging the market, then yes, close the gap and close it cleanly. If they were already paid fairly and the new offer is just an outlier, matching it pulls one person above their cohort and quietly resets expectations across the rest of the team — usually before the next quarter’s salary review. The counters that actually stick are the ones aimed at the real reason the person was open to a conversation in the first place. The number is almost never the whole reason.
Meaningful room, and it shows up in two places. The first is the tax differential: HTP-resident employees pay 9% personal income tax against 13% in the standard regime, with progressive surcharges applying to very high annual incomes. Practically, that means a given net increase for the employee carries a smaller gross cost for the employer — useful when you’re trying to land a counter without distorting the wider compensation grid. The second, and often the more decisive, is structural. HTP residency opens up a set of legal tools that simply don’t have a settled form outside it: formal option agreements under Decree No. 8, phantom equity, SARs, and enforceable non-compete and non-solicitation clauses on senior staff. Those instruments expand the counter beyond “raise the base” into the kind of long-horizon design that actually changes a senior engineer’s calculus.
Yes, for time-bound situations — competing offer, key project, acquisition transition. They’re cheaper over a 12–24 month horizon than a permanent salary increase and avoid resetting the grid. They work less well as a standing instrument; if you find yourself paying retention bonuses every year to the same person, the issue is structural and a permanent solution is overdue.
Honestly, the numbers aren’t flattering. The figure most HR people quote — and one that practitioners keep finding in the wild — is that the majority of employees who accept a counter are gone within a year anyway. The reason isn’t really about the money. Once someone has gone to market, taken interviews, sat through final rounds, and emotionally landed on leaving, a pay rise doesn’t undo any of that. It just delays the conversation. The exception, and it’s a real one, is when the counter actually fixes the thing that drove the search in the first place. A new title, a different scope, a manager change, a clear development path — those stick. A pure cash counter to someone who was bored or stuck rarely does.
Yes, and for a senior hire equity often does more work than another bump on base. If you’re inside the High Tech Park, you’ve got the full set of tools at your disposal: option agreements under Decree No. 8, phantom shares, or SARs, all sitting on top of the 9% personal income tax rate. Outside HTP the path is narrower. Phantom equity and SARs still work fine as ordinary civil contracts, but a Belarusian-law option agreement gets legally shaky in a hurry and rarely earns its keep. There’s also an obvious third route a lot of international groups take: just let the parent grant whatever it normally grants (RSUs, options, the global plan) straight to the Belarusian engineer. That works in nearly every case, provided someone locally is keeping the tax filing and currency control clean.
The counter-offer is one of the most overused tools in IT compensation. Used well, it’s a precise instrument: it closes a real pay gap, addresses a real motivational gap, or buys a specific time-bound outcome. Used reactively, it’s a 20% raise that buys nine months of awkwardness and a re-run of the same conversation next year.
For senior Belarusian engineers, the levers available — HTP’s tax framework, formal equity instruments, structured retention bonuses, scope and title moves — are richer than most international employers initially realise. The framework above puts those levers in the right order: diagnose first, decide whether you actually want to fight for the person, match what’s worth matching, and design the aftermath so the agreement holds.
If you’re working through a specific case and want a second set of eyes on the structure — including market benchmarking, contract drafting, and the HTP-specific instruments — our team handles these conversations regularly through our HR consulting practice. Most cases get clearer in an hour of structured conversation than in a week of internal back-and-forth.
When remote work in Belarus was introduced in the legislation The coronavirus pandemic has made its own adjustments to the life of the state and society, including labor legislation. Remote work has become more in demand and popular. In this regard, amendments were made to the Labor Code of the Republic of Belarus, in particular, […]
The software development career path often follows a clear progression from junior to senior roles, but understanding the distinctions between these levels can be challenging. Whether you’re a fresh graduate wondering about entry-level developer positions or an experienced programmer considering the leap to a senior role, grasping these career stages is crucial for professional growth. […]
Most international groups that own a Belarusian subsidiary aren’t physically in Minsk. The headquarters sits in London, New York, Dubai, Singapore, or Berlin. The CFO checks in over Slack, the board reviews quarterly numbers in a dashboard, and the only people on the ground are the engineering team, an accountant, and whichever statutory officers the […]
