At first glance, Belarusian employers should not have this problem. Junior and general roles attract plenty of applications. But the candidates companies actually compete for, experienced engineers and specialists in DevOps, data or mobile development, usually have several options at the same time, and they choose the process that respects their time.<\/p>\n\n\n\n
Global research shows how much the process itself affects their decisions. In a 2024 Monster survey cited by SHRM<\/a>, 47% of candidates said they had withdrawn from a hiring process because of poor communication, and 36% because they felt they were being asked to jump through too many hoops.<\/p>\n\n\n\n Every finalist who leaves means going back to sourcing, which for a senior role can easily add another four to eight weeks to the search.<\/p>\n\n\n\n Senior specialists are also the most expensive to lose, since their pay is rising faster than at other levels. Our developer salary benchmarks for 2026<\/a> show current ranges by role and seniority.<\/p>\n\n\n\n <\/p>\n\n\n\n <\/p>\n\n\n\n The first message decides whether a passive candidate replies at all. Experienced Belarusian specialists receive a steady stream of messages through LinkedIn and Telegram, and most of them look alike: a vague description, no project details and no salary range. These are the easiest to ignore.<\/p>\n\n\n\n Salary is the single most useful thing to add. According to LinkedIn research<\/a>, 91% of job seekers said that seeing a salary range affects their decision to apply. In Belarus it also helps to know that many candidates think about pay in net terms and in dollar equivalent, so a range stated that way is easier for them to compare.<\/p>\n\n\n\n A short personal message with the stack, the type of project, the work format and the salary range will usually get a much better response than a long generic one.<\/p>\n\n\n\n Long application forms and silence after applying are the main problems here. A candidate who applies and hears nothing for a week will usually assume the answer is no, and move on. Replying within one or two working days, even with a short \u201cthank you, we will get back to you by Friday\u201d, keeps them interested.<\/p>\n\n\n\n Candidates often drop out after the first call because something important comes up too late: the salary is lower than they expected, the office attendance requirement does not suit them, or the stack is different from what the vacancy suggested. Another common reason is a recruiter who cannot answer basic questions about the project or the team.<\/p>\n\n\n\n The fix is to settle the key conditions in the first conversation. Salary, work format, stack and the next steps of the process should all be clear before the candidate spends time on tests and interviews.<\/p>\n\n\n\n For middle and senior candidates, this is one of the most common points of drop-off. The typical complaints are tasks that take a whole working day or more, tasks that have little to do with the actual job and, most of all, receiving no feedback after spending hours on the work.<\/p>\n\n\n\n A survey by interviewing.io<\/a> gives a good picture of how engineers see take-home assignments. More than 80% preferred tasks that take four hours or less, 58% believed they should be paid for this work, and only 4% had actually received payment.<\/p>\n\n\n\n Keeping tasks to two or three hours, explaining in advance how long they should take and always giving feedback reduces drop-off considerably. For senior candidates, it is worth offering an alternative, such as reviewing existing code together or a live technical session instead of a take-home task.<\/p>\n\n\n\n The format should also suit the role. For QA automation engineers<\/a>, for example, reviewing an existing test framework and discussing its weak points is often more informative and less time-consuming than writing a new one from scratch.<\/p>\n\n\n\n Candidates judge the company by the people who interview them. In the same Monster survey, 46% of respondents said an interviewer\u2019s attitude or behaviour had made them withdraw. Interviewers who arrive unprepared, check their phones or ask puzzle questions unrelated to the job leave a poor impression, especially with experienced specialists.<\/p>\n\n\n\n A short briefing for interviewers, a structured list of questions and a clear scorecard make interviews more consistent and more pleasant for candidates. When hiring for senior roles such as a tech lead<\/a>, it also helps if the interviewer can talk about the team\u2019s real challenges, because that is what strong candidates want to hear.<\/p>\n\n\n\n Four or five interview rounds spread over several weeks is one of the surest ways to lose good candidates. While one company is arranging the next meeting, another has already made an offer. Long pauses between stages are just as harmful as the number of rounds.<\/p>\n\n\n\n As a rule, three stages and about two weeks from the first call to the offer is a realistic target for most IT roles. When a role is urgent and a full search would take too long, IT outstaffing<\/a> can be a faster way to bring a specialist into the team.<\/p>\n\n\n\n Candidates who have come this far can still drop out at the offer stage. The most common reasons we see are an offer below the range discussed earlier, confusion between net and gross figures, unclear conditions such as bonuses or the review schedule, and long waits while the offer is approved internally.<\/p>\n\n\n\n A verbal offer first, followed by a written offer within one or two days, works well. Showing the salary in both net and gross terms avoids misunderstandings, and it helps to explain any conditions that differ from what the candidate might expect.<\/p>\n\n\n\n This stage is where Belarus differs most from many other markets. An employee on an open-ended employment agreement can resign with one month\u2019s notice, but many people work under fixed-term contracts of one to five years, where leaving early is possible only in specific situations, as the Sorainen employment overview<\/a> summarises. A candidate on such a contract may need to negotiate their exit with the current employer, which takes time and sometimes fails.<\/p>\n\n\n\n It is worth asking about the type of contract and the expected exit date early in the process, not after the offer has been accepted.<\/p>\n\n\n\n Counteroffers are the other risk. Employers often respond to a resignation with a raise, and some candidates accept. Research by Robert Half<\/a> in the UK found that 53% of employees who received a counteroffer accepted it, but 74% of them still left within a year.<\/p>\n\n\n\n Staying in regular contact during the notice period, discussing the possibility of a counteroffer openly and reminding the candidate why they decided to move in the first place all reduce the risk of losing them at the last moment.<\/p>\n\n\n\n Some candidates technically join but leave within the first month or two, usually because the job turns out to be different from what was described. An honest description of the role and the project during the process, and some contact before the start date, such as introducing the team or sharing onboarding materials, help prevent this.<\/p>\n\n\n\n <\/p>\n\n\n\n <\/p>\n\n\n\n Every company loses candidates at slightly different points, so it is worth measuring your own process. Track how many candidates move from each stage to the next, how long each stage takes and how much time passes between the first contact and the offer. A short, anonymous survey of candidates who withdrew or declined an offer often explains more than any internal discussion.<\/p>\n\n\n\n![\"\"](\"https:\/\/recruitment.by\/wp-content\/uploads\/2026\/10\/business-man-working-office-desktop-1-1024x683.jpg\")
<\/figure>\n\n\n\nThe hiring process, stage by stage<\/strong><\/h2>\n\n\n\n
1. First contact<\/strong><\/h3>\n\n\n\n
2. Application and first response<\/strong><\/h3>\n\n\n\n
3. Recruiter screen<\/strong><\/h3>\n\n\n\n
4. Test task<\/strong><\/h3>\n\n\n\n
5. Technical interview<\/strong><\/h3>\n\n\n\n
6. Too many rounds and long pauses<\/strong><\/h3>\n\n\n\n
7. Offer<\/strong><\/h3>\n\n\n\n
8. Notice period and counteroffers<\/strong><\/h3>\n\n\n\n
9. The first weeks<\/strong><\/h3>\n\n\n\n
Summary table<\/strong><\/h2>\n\n\n\n
Stage<\/strong><\/th> Why candidates drop out<\/strong><\/th> What helps<\/strong><\/th><\/tr><\/thead> First contact<\/strong><\/td> Generic message, no salary range<\/td> Personal message with stack, project and range<\/td><\/tr> Application<\/strong><\/td> Long forms, no response<\/td> Reply within one or two working days<\/td><\/tr> Recruiter screen<\/strong><\/td> Key conditions discovered too late<\/td> Settle salary, format and stack in the first call<\/td><\/tr> Test task<\/strong><\/td> Long, unrelated tasks with no feedback<\/td> Two to three hours, clear scope, feedback, alternatives<\/td><\/tr> Technical interview<\/strong><\/td> Unprepared or disengaged interviewers<\/td> Briefing, structured questions, scorecard<\/td><\/tr> Rounds and pauses<\/strong><\/td> Too many stages, long gaps<\/td> About three stages and two weeks to offer<\/td><\/tr> Offer<\/strong><\/td> Low or unclear offer, slow approval<\/td> Verbal offer, written offer within two days, net and gross<\/td><\/tr> Notice period<\/strong><\/td> Fixed-term contracts, counteroffers<\/td> Ask early, stay in touch, discuss counteroffers<\/td><\/tr> First weeks<\/strong><\/td> Job differs from expectations<\/td> Honest description, contact before start date<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n How to find the leaks in your own process<\/strong><\/h2>\n\n\n\n