Three Dubai Candidates Took the Counteroffer in One Quarter: the 7 Steps I Use Now

Last quarter we lost three Dubai candidates at the same point in the process. All three had signed. All three resigned. All three were still at their old desk a week later, on more money.

I went back through the files expecting to find three different stories and found one. In none of the three had anyone, at any stage, asked the candidate a direct question about what would happen when their employer tried to keep them. We had run a careful process right up to the moment it mattered and then relied on hope.

What follows is the method I run now. It is not a persuasion technique for the resignation meeting, because by then the useful work is already done or it is not.

Step 1: Put the Counteroffer Question in the Screening Call

Raise it early, while nothing is at stake. First or second conversation, before the candidate is invested enough to manage their answer.

The wording matters more than you would expect. "Would you accept a counteroffer?" produces a reflexive no from almost everyone, which is worthless. What works is making the scenario concrete and giving them permission to be honest:

You hand in your notice. Your manager asks for a day, comes back with a title change and fifteen percent. Walk me through what goes through your head.

Listen for whether they have thought about it. A candidate who answers instantly and vaguely has not. A candidate who pauses, then tells you what their manager would probably say, has already imagined the conversation, which is the answer you want. Write down what they say, in their words, and keep it. You will use it in step five.

One thing I will not do is make the candidate promise. Extracting a commitment this early just teaches them which answer gets them to the next round.

Step 2: Separate the Stated Reason from the Operative One

Everybody says the same three things: growth, challenge, a new sector. Those are not reasons, they are the polite surface over a reason. The operative reason is the specific thing that happened, and it has a date attached to it.

The question that gets there is not "why are you looking?" but "when did you start looking, and what happened that month?". Somebody got promoted over them. A project they built was handed to another team. A manager changed. A visa or relocation plan shifted. There is nearly always an event.

This matters because the operative reason tells you exactly what a counteroffer can and cannot repair. Money fixes money. It does not fix a technical ceiling, a manager, or a product the person stopped believing in. When a candidate tells me the real reason is that they are the only senior engineer on a team of four and nobody reviews their code, I know that a counteroffer is a weak threat, whatever the number on it. When the real reason is that they are underpaid against the Dubai market, I know the opposite.

Step 3: Benchmark the Offer Against the Market, Not Against Their Current Salary

The most common way UAE employers set up their own counteroffer problem is by anchoring on what the candidate earns today and adding a percentage. That method guarantees the incumbent can beat you cheaply, because the incumbent knows the base number better than you do and only has to clear your increment.

Benchmark against what the role is worth in Dubai for the level you are hiring at. Then look at the gap between that number and the candidate’s current package and ask yourself what a rational employer would pay to keep them. If your offer sits inside what the incumbent can comfortably match, you do not have an offer. You have an opening bid in a negotiation you are not even present for.

Build the package where it cannot be matched line for line. In the UAE that usually means the parts that are structural rather than cash: the scope of ownership, the stated review cycle, remote or hybrid terms in writing, allowances that are actually in the contract. An incumbent can find a salary increase in an afternoon. Rewriting someone’s role takes a quarter, and most of them will not do it.

Step 4: Shrink the Gap Between the Verbal Yes and the Signature

This is the first of the two moments where offers are lost, and it is entirely self-inflicted.

A candidate says yes on a call. The written offer goes out two days later because someone was travelling. The candidate takes it to a spouse, a friend who works at the incumbent, a former manager. By the time it comes back signed, four days have passed and the enthusiasm has been through three other people’s opinions.

Issue the paperwork the same day. If your approval chain cannot produce a written offer in a day, that is the process problem to fix before you fix anything else in this article, because every other step is downstream of it. Set an explicit acceptance window, say it out loud, and keep it short enough to be a decision rather than a deliberation.

On the content: our breakdown of what belongs in a Dubai developer offer letter covers the MOHRE contract mechanics, and negotiating developer salaries in Dubai covers the number itself. Both are worth reading before you issue, not after.

Step 5: Rehearse the Resignation Before It Happens

Most candidates have resigned perhaps twice in their life. They are about to walk into a conversation with someone who has handled dozens of them and has a prepared playbook. That asymmetry is the whole game, and it is fixable in twenty minutes.

Three things to do with the candidate before resignation day.

Agree the date and the format. A resignation that happens "sometime next week" drifts, and drift is where the incumbent gets organised. A resignation delivered in writing, in a scheduled meeting, on a named day, does not.

Tell them what they are going to hear. Name the moves in advance: the request for a day to think, the senior leader who suddenly has time, the counter that arrives in two parts with the better half held back. Nothing defuses a retention pitch like having been told the running order a week earlier.

Give them their own answer back. This is why you wrote down what they said in step one. "When we first spoke in September, you said the thing that had stopped you growing was that nobody had reviewed your code in a year. If they offer you money tomorrow, that is the question to ask them." You are not arguing with them. You are handing them the sentence they already wrote.

Step 6: Run a Deliberate Cadence Through the Notice Period

The second moment, and the longer one. UAE notice periods commonly run a month, and three months is routine for senior engineering roles. That is up to twelve weeks in which your new hire sits inside a building that wants to keep them, surrounded by colleagues, while you are a PDF in their inbox.

What does not work is checking in. "Just seeing how you’re doing" is a message that creates obligation without giving anything, and after the third one it reads as anxiety.

What works is giving them something to belong to, on a schedule you set in advance and tell them about:

• Week one. An introduction to their future lead, scheduled by you, with a stated purpose rather than a welcome chat. Something to discuss, so there is a reason to talk again.
• Mid-notice. Access to something real: the architecture document, the roadmap for their area, the repository read-only if your security posture allows it. A person who has read your codebase has already started working for you.
• An invitation to one thing. A team lunch, a demo day, a release call as an observer. One is enough. Three is pressure.
• Final two weeks. The practical sequence: visa and documentation steps, start date confirmation, first-week plan sent in writing. Logistics are reassuring precisely because they are boring.

Tell the candidate this schedule exists at the point they sign. Predictability does more work here than warmth.

Step 7: Debrief Every Loss, Then Fix the Stage That Failed

When you lose one, ask where they landed and write it down. Not as a post-mortem ritual, but because the pattern across four or five losses points at a specific stage, and the stage is almost never the one people blame.

Three patterns and what each one means:

• They stayed for money. Your benchmarking is off, or your offer was anchored on their current salary. This is step three, and it is the cheapest to fix.
• They stayed for a new role or manager. You never found the operative reason, so you could not tell whether the incumbent could address it. This is step two.
• They went quiet during notice and then withdrew. Nobody held the relationship. This is step six, and it is the one employers consistently misdiagnose as the candidate being flaky.

Running this across a year changed where we spend effort. Our losses were concentrated in the notice period, not at the offer, which is the opposite of what the team believed. We had been refining offer letters to fix a problem that lived six weeks later.

When to Stop Trying

Not every offer is worth defending. If a candidate goes back and forth twice, if they ask you to beat a number that you know is above market, or if they start negotiating terms that were settled a month ago, the counteroffer has already done its work. What you are being offered at that point is the chance to overpay for someone whose first loyalty is demonstrably elsewhere.

Close it warmly and diarise them. A good number of counteroffer acceptances come apart inside a year, because the thing that made the person start looking was rarely the salary, and the raise does not change the work. The employers who get those people on the second pass are the ones who did not take the first no personally.

For the earlier parts of the funnel, our guide to hiring developers in Dubai covers sourcing and screening, and the full-stack hiring page sets out what the profiles look like at each level in the UAE market.

Frequently Asked Questions