I Promoted 2 Engineering Managers in Dubai and Lost Both in 11 Months — the 7-Step Method That Finally Worked

Both of them were excellent engineers. Both wanted the role. Both came back to me within a year asking to return to an individual contributor position, and in both cases I said yes because they were right. Neither of them failed at management. I had promoted them into a job that needed repairing and given them the support appropriate to a job that needed growing.

What follows is the method that came out of that, refined across eleven engineering manager searches in the UAE since. It is specific to Dubai, it assumes you are hiring your first or second manager rather than filling a slot in an established org, and it is deliberately boring in places where being interesting costs you a hire.

Step 1 — Decide whether you need an engineering manager or a tech lead

Do this before writing anything, because getting it wrong wastes the entire cycle and costs you a good engineer as well as a bad manager.

A tech lead owns technical direction. Architecture, standards, review quality, sequencing of technical work. Success is measured in what the system becomes.

An engineering manager owns people and delivery. Hiring, performance, growth, headcount planning, and the commitments the team makes to the rest of the business. Success is measured in what the team becomes.

Many organisations blur the two, and that works up to roughly six engineers, because one strong senior can carry both. Beyond that it stops working, and the failure mode is always the same: the people work gets deprioritised because it has no deadline. Nobody escalates a one-to-one that did not happen.

The cleanest test is authority. Can the role open a requisition, decline a candidate, or place someone on a performance plan? If the answer is no to all three, it is a tech lead role regardless of what the contract says. Hiring an experienced manager into it produces a resignation inside a year, which is exactly what happened to my second promotion.

Step 2 — Write a mandate, not a job description

Standard engineering manager job descriptions are interchangeable. They list one-to-ones, career development, agile ceremonies and stakeholder management. Every strong candidate has read four hundred of them and none of them help either side decide anything.

Replace it with a mandate that answers four questions honestly:

How big is the team, and what state is it in? Not “a growing team of talented engineers”. Write: seven engineers, two of whom joined in the last quarter, one long-standing performance issue nobody has addressed, delivery predictability currently poor. Strong candidates find this attractive because it is real. Weak candidates disappear, which is the point.

What authority does the role carry? Hiring, firing, budget, roadmap influence, technical veto. Write the answer for each. Ambiguity here is the single most common cause of manager attrition in the UAE market.

What is the one problem this hire exists to solve? Every manager hire has one. Delivery predictability, attrition, scaling from one team to two, or repairing a relationship with the commercial side. Naming it changes who applies.

How much hands-on work is expected? Be specific and be honest. “Twenty percent hands-on” that turns out to be sixty percent is the fastest route to a resignation. In UAE startups this number is almost always higher than the job description claims.

Step 3 — Source from senior engineers who already do the work

Searching Dubai for the engineering manager title returns a pool that is small, largely employed, and heavily weighted toward people managing at large enterprises where the job is meaningfully different from managing seven engineers at a scale-up.

The pool that produced our strongest candidates was staff and principal engineers who were already doing the work informally: running planning, mentoring juniors, owning delivery commitments, sitting in the meetings nobody else wanted. Roughly half of the credible candidates across eleven searches had no management title on their profile.

The signals worth searching for are behavioural rather than titular: has run hiring loops, has mentored named engineers who were promoted, has owned a delivery commitment to a customer, has represented engineering to a commercial audience.

On geography, the pools that produced our strongest UAE manager candidates were engineers already in the Gulf who had reached the ceiling of an individual contributor track, followed by senior engineers relocating from Egypt, Jordan, India and Pakistan, and a smaller stream of Europeans. This tracks the broader market, where 80 to 85% of UAE tech hires come from international pools. Budget for relocation from the start.

Step 4 — Screen on a real performance conversation

This is the step that changed our hit rate, and it is one question asked properly:

“Walk me through a time you managed someone who was underperforming — from the first conversation to the outcome, whatever it was.”

Then stop talking. Listen for four things.

Did they name the problem out loud, early? Weak answers describe months of hoping it would resolve. Strong answers include a specific conversation with a specific date, usually uncomfortably early.

Did they write anything down? Managers who have genuinely done this describe documentation almost automatically, because they have learned what happens without it. In the UAE this matters more than elsewhere, since employment terminations interact with visa status and end-of-service entitlements, and undocumented performance decisions become legal exposure.

Do they distinguish capability from motivation from fit? These require completely different responses and conflating them is the most common management error. Strong candidates diagnose before acting.

Are they honest about the outcome? A candidate who says “I handled it well and they turned around” every time is describing a career that did not happen. The best answer I have heard included the sentence “I left it eight months too long and by then the rest of the team had stopped trusting me to act”.

Nineteen of thirty-one candidates failed this conversation across our searches, several with strong CVs and real management titles. What they had was exposure to the role, not experience of its hardest part.

Step 5 — Run a 60-minute team-scenario exercise

Not a case study from a book. Take a situation your team is actually in, anonymise it lightly, and hand it over with the real constraints.

Ours is usually a version of: a team of seven, delivery slipping, one senior engineer whose technical judgment is excellent and whose code review comments are making two juniors miserable, and a commercial deadline in nine weeks that leadership considers non-negotiable. What do you do in week one, and what do you deliberately not do?

What we grade is not the answer. It is sequencing and restraint. Strong candidates spend week one gathering information and explicitly name what they are choosing not to touch yet. Weak candidates arrive with a reorganisation. The single best signal is a candidate who asks four or five clarifying questions before proposing anything — that is what the job actually consists of.

Include one member of the team they would manage in this session. Their read is frequently better than yours, and involving them makes the eventual onboarding materially easier.

Step 6 — Benchmark the offer against 2026 UAE bands

Current Dubai monthly base ranges from offers we have benchmarked this year:

These exclude housing allowance, typically AED 10,000 to 18,000 monthly at this level, annual family flight allowance, and end-of-service gratuity.

The line first-time employers forget is schooling contribution. At manager level most candidates relocate with children, Dubai international school fees are substantial, and its absence is frequently the reason a strong candidate declines an otherwise competitive offer. Decide your position on it before you make the offer, not during the negotiation.

Step 7 — Run visas in parallel and write the 90-day mandate

Plan 60 to 90 days from open requisition to first day. Sourcing takes four to eight weeks, interviewing two to three, and notice periods at this level are commonly two to three months in the UAE and rarely negotiable.

Standard employment visa processing through MOHRE runs three to five weeks; free zone entities in DIFC, Internet City and ADGM typically shave seven to ten days. Start visa paperwork at offer acceptance, not after notice ends — those two clocks run in parallel and most employers waste three weeks by running them in sequence.

Then write the 90-day mandate before the start date, agreed in writing with the candidate. Ours has three lines: what they are expected to have diagnosed by day 30, what they are expected to have changed by day 60, and what measurable outcome is expected by day 90. Keep the day-90 outcome modest. A manager who has stabilised one thing and understood the rest is ahead of one who reorganised everything.

Three mistakes I made, in order of cost

1. I promoted into repair jobs. Both failed promotions inherited teams with unaddressed performance problems. An internal promotion has to renegotiate every peer relationship simultaneously while learning a new role. Promote internally to scale a healthy team; hire externally to repair a broken one.

2. I interviewed on management frameworks. Our early loop asked about methodologies and feedback models. It graded vocabulary and passed two candidates who could not hold a difficult conversation. We dropped it entirely and quality went up.

3. I under-specified hands-on expectations. One hire was told twenty percent and found sixty. He was gone in seven months, and he was right to go. Write the real number, even when it is unflattering.

How this compares across the region

Manager hiring differs sharply by hub. Singapore's pool is deeper and the competition for the same profile pushes packages faster, which our colleagues at HireDeveloper.sg track in detail. Tokyo's constraint is demographic rather than competitive, and the expectations around a manager's hands-on involvement differ considerably — JapanDev covers what that means for scoping the role.

See also our role pages for engineering leadership and site reliability engineers in the UAE, our build guide for a marketplace app in the UAE for the delivery context most first manager hires inherit, and the Palo Alto and NTT DATA AI-security analysis for where senior security scope is heading.

Frequently Asked Questions