The email arrived on a Tuesday and used the word pause. Five open engineering roles, two of them at offer stage, and a roadmap that had been built on all five being filled by the end of the quarter. The freeze ran for five months. We shipped the two things that mattered and we lost one engineer, which in hindsight was one more than we needed to lose. This is the method I use now, in the order I would run it, written for the version of me who spent the first three weeks of that freeze doing the wrong things politely.
Nothing here requires a budget you do not have. Six of the seven steps are conversations and documents. The seventh is the only one that costs money, and it is the one most likely to be approved if you ask for it correctly.
Why Week One Decides the Whole Quarter
A hiring freeze is a budget instruction that arrives as a sentence. By the time it reaches an engineering lead it has usually passed through two or three people, each of whom rounded it in the safe direction, and what lands on your desk is stricter than what finance wrote. I have now seen this often enough to treat it as the default assumption rather than the exception.
The practical consequence is that teams stop doing things they were never asked to stop doing. They cancel contractor renewals that were funded from a project line. They withdraw an offer that had a pre approved requisition behind it. They stop talking to candidates entirely, which costs nothing today and costs two months on the day the freeze lifts.
So the work of week one is not acceptance. It is scoping. Everything that follows depends on knowing exactly what has been closed and exactly what has not.
The 7 Steps, in Order
Step 1: Get the freeze defined in writing within 48 hours
Go to whoever owns the instruction, not to whoever forwarded it, and ask six questions. Does it cover backfills for people who have already resigned. Does it cover contractors and services engagements funded outside headcount. Does it cover offers already extended and accepted. Does it cover requisitions approved before the freeze date. Who can grant an exception, and what evidence does an exception request need. Is there a review date, even a provisional one.
Ask for the answers in an email you can forward, because you will be asked the same questions by six people over the next fortnight and the alternative is six slightly different versions of the rule circulating in your team. If the answer to the review date question is that there is no date, that is itself useful information: it tells you to plan for two quarters rather than one.
The single most common surprise in this conversation, in my experience, is that backfills and contractor lines are open when everyone assumed they were shut.
Step 2: Re-rank every open requisition by what breaks without it
Open roles accumulate a kind of seniority by age. The one that has been open longest feels the most urgent, and it is usually the least important, because a team that has survived six months without someone has already adapted.
Score every open role on one question instead: what specifically breaks if this seat stays empty for another six months. Four categories rank above everything else.
- Single owner roles. One person knows a system and there is no second. This is a continuity risk, not a capacity one, and it is the only category I will spend an exception on.
- Compliance and obligation roles. Anything where not having the person creates an exposure you would have to disclose.
- Hard dependency roles. A named commitment to a customer or regulator that cannot be delivered without this skill.
- Growth roles. Everything else. Valuable, and genuinely deferrable for two quarters.
If your five open roles turn out to be five growth roles, the honest conclusion is that the freeze costs you speed rather than stability, and you should say so rather than fighting it. If one of them is a single owner role, you have found the role to fight for. Our method for engineering headcount planning in Dubai covers how to build this ranking before a freeze rather than during one, which is considerably less stressful.
Step 3: Convert the one role you cannot lose into a non headcount line
Here is the asymmetry worth understanding. A freeze is almost always written against permanent headcount, because headcount is the line that carries end of service liability, visa cost and a long commitment. Project engagements, dedicated team contracts and freelance arrangements sit on different lines with different approvers.
That gives you a route for exactly one role. Not five. The moment you submit a list of conversions, the request reads as an attempt to route around the instruction, and a reasonable finance director refuses it on principle. One conversion, with the continuity risk written out in a paragraph and a cost comparison against the permanent role, reads as a lead managing a constraint. I have had that version approved more often than refused.
Three mechanisms are worth knowing in the UAE specifically. A freelance permit arrangement lets you engage an individual without a headcount line. A dedicated offshore team engagement puts capacity on a services line with a defined term. And a straightforward project contract works where the need is bounded, for example a migration with an end date.
One honest caveat: converting a permanent role to a contract usually costs more per month and buys you less loyalty. Do it for continuity risk, not to save money, and do not pretend to the business that it is a permanent solution.
Step 4: Run a capacity audit before you promise the business anything
The instinct after a freeze is announced is to reassure people. Resist it for a week and do arithmetic instead.
Count what you actually have. Current engineers, minus anyone serving notice, minus accrued leave that will be taken this quarter, minus the real proportion of time going to unplanned work. That last figure is the one teams guess and get wrong. Look at the last two months and measure it: in most teams I review, between a quarter and a third of engineering time goes to interruptions, incidents and support, and during a freeze that proportion rises because deferred maintenance generates its own work.
Come out of this with one number you are willing to defend in a steering meeting, expressed as engineer weeks available this quarter. Then look at the roadmap in the same unit. The gap is your descope list, and it is much easier to discuss a gap than a feeling.
If you have never calculated what a vacancy actually costs you, our walkthrough of cost per hire for developers in Dubai gives you the other half of the arithmetic, which is useful ammunition when the freeze is reviewed.
Step 5: Cut scope out loud, in a document someone signs
This is the step that separates a freeze that costs a quarter from a freeze that costs your credibility.
The default behaviour of a good engineering team under constraint is to absorb it silently. The roadmap stays the same, the deadlines stay the same, there are fewer people, and the slack comes out of the invisible work first: code review depth, documentation, test maintenance, on call recovery. Nobody writes it down, so when something slips four months later the explanation sounds like an excuse rather than a prediction.
Instead, publish a dated list titled what will not happen because of the hiring freeze. Put a name against each item. Send it to the people who were expecting those things and ask one of them to acknowledge it. The conversation is uncomfortable for about ten minutes and it buys you the entire rest of the freeze.
A freeze is also, genuinely, the best window you will get for the maintenance work that never wins a prioritisation argument. If you are going to spend capacity on something unglamorous, a technical debt audit pays twice: it reduces the interruption load now, and it makes the first new hire productive faster when the freeze lifts.
๐ก Our Expert Take
The descope document has a second function nobody mentions. It is the single most effective argument for ending the freeze early. When the review meeting happens, the lead who says the team is stretched gets sympathy. The lead who opens a dated list of four named commitments that were deliberately not delivered, each with the person who acknowledged it, gets a requisition. Finance teams do not respond to effort, they respond to consequences they can see. Write the consequences down while they are still predictions and you will be the one person in the room with evidence.
Step 6: Protect the engineers you already have
This is the step teams skip, and it is where the real cost of a freeze lands. The load that was going to be carried by five new people gets carried by the people who stay. The person most likely to leave is the one carrying the most of it, which is to say the person you can least afford to lose, and when they go you cannot replace them, because there is a freeze.
The salary lever is closed. Several others are not, and they are cheaper than a replacement in any case.
- Rebalance on call immediately. A rota designed for a team of nine does not work for a team of six, and the person who notices first is the one paged at 3am.
- Cancel the lowest value project outright rather than slowing everything down equally. Teams tolerate doing less. They do not tolerate doing everything badly.
- Get the non monetary levers approved now. Title changes, scope and ownership increases, conference and certification budget, a formal mentoring arrangement, flexibility on hours. Most of these sit outside the frozen line, and they are far easier to approve during a freeze precisely because they cost almost nothing.
- Have a direct conversation with your top two engineers. Not a reassurance conversation. Tell them what you are protecting, what you are cutting, and ask what would make them consider leaving. They know the answer and almost nobody asks.
Expect counter offers from outside during this period, because a frozen team is a known source of movable talent and the market in Dubai reads signals quickly. Our guide to handling a developer counter offer is worth reading before you need it rather than on the morning you do.
Step 7: Keep the pipeline warm for the day it lifts
Freezes end abruptly. Somebody signs something, and on Monday you have three requisitions and a board expectation that they fill quickly.
The team that stopped sourcing entirely starts that Monday from nothing: write the brief, open the channels, wait for applications. In the Dubai market that adds roughly six to eight weeks before a first interview, which means a quarter of your post freeze year is spent recovering from the freeze rather than from the hiring.
The version that works is small and honest. Keep a shortlist of a handful of people you genuinely want. Speak to them every few weeks. Tell them the truth: there is no funded role right now, you do not expect them to wait, and you would like to stay in touch. Some will take other jobs, which is fine and expected. Two will still be reachable, and two is the difference between starting from shortlist and starting from zero.
What does not work is running a full interview process with no funded end point. It wastes the candidate time, it burns your reputation in a market where engineers talk, and it produces offers you cannot make.
Need capacity while headcount is closed?
HireDeveloper.ae works with Dubai employers on exactly this constraint: identifying which single role is worth an exception, putting capacity on a services line instead of a headcount line when that is the honest answer, and keeping a shortlist alive for the day the freeze lifts. If the right answer is that you should defer and descope rather than spend, we will tell you that too.
Get startedThe Two Timelines I Have Watched Play Out
Same freeze, same length, two different five month periods. The difference is almost entirely whether steps 1, 5 and 6 happened in the first fortnight.
๐ก Our Expert Take
If you only have the appetite for one of these seven steps, do step 1, and do it badly rather than not at all. Every other step gets easier once you know precisely what has been closed, and in roughly half the freezes I have worked through, the written answer was less restrictive than the version circulating in the team. Teams have withdrawn pre approved offers, cancelled funded contractor renewals and stopped talking to candidates entirely on the strength of a rule nobody had actually read. An email with six questions in it is a cheap way to find out that one of your five roles was never frozen.
FAQ: Running Engineering Through a Hiring Freeze
Does a hiring freeze in Dubai usually cover contractors and backfills?
Not automatically, and clarifying this is the highest value thing you can do in the first two days. A freeze is a budget instruction, and budgets distinguish between permanent headcount and project or services lines. Many freezes apply only to permanent headcount, leaving backfills, contractor engagements, dedicated team contracts and freelance permit arrangements available under normal approval. Some cover everything. Get the scope in writing from whoever owns the instruction, not from whoever relayed it to you.
Can you still make an offer to a candidate who is mid process?
It usually depends on whether the requisition was approved before the freeze date, which is a documented fact rather than a matter of opinion. Where the approval predates the freeze, many organisations honour it. Where it does not, tell the candidate the position has changed instead of keeping them in a process with no funded end point. Engineers in this market talk to each other, and a team that strings people along during a freeze pays for it in the next hiring round.
What is the biggest mistake engineering leads make during a freeze?
Absorbing the gap quietly. The roadmap stays, the deadlines stay, the people are fewer, and the slack comes out of code review, documentation, test maintenance and on call recovery before it comes out of anything visible. Nobody records the trade, so when delivery slips the explanation sounds like an excuse. Publishing a dated descope list with a name against each item is the difference between a freeze costing you a quarter and a freeze costing you a senior engineer.
How long should you keep a candidate pipeline warm?
As long as you can do it honestly, which means a small number of people you genuinely want and are willing to be straight with. A short conversation every few weeks, no implied offer, no expectation that they stay available. The alternative is that on the day the freeze lifts you start from sourcing rather than from shortlist, which in the Dubai market typically adds six to eight weeks before a first interview and turns a hiring problem into a recovery problem.
Ready to run step 2 properly?
Send us your open requisitions and we will rank them with you on consequence rather than on age, tell you which one is worth an exception argument, and set out the realistic options for the rest. Get the triage done now and the review meeting goes very differently.
Start the conversation