For about two years I treated the intake meeting as an administrative step. The manager sent a draft job description, I read it, we had a fifteen minute call that was mostly pleasantries, and I started sourcing. Three Dubai roles in a row went badly in the same way: good candidates, consistent rejections, no pattern anyone could name. Eleven weeks of sourcing produced one offer, and that one was declined. The roles were not hard. The brief was empty, and nobody had noticed because the job description looked full.
What follows is the structure I use now. It is one meeting, forty-five minutes, before the role is posted. The output is a two page brief, not a job description. The questions are ordered deliberately, because the later ones only produce honest answers once the earlier ones have been said out loud.
Step 1: Bring One Artefact, Not a Job Description
Open the meeting with a real piece of work the hire will own. A ticket from the backlog. A pull request that sat for three weeks. An incident write-up. A roadmap line item with a date attached. Put it on the screen and ask the manager to walk you through it.
The reason is mechanical. A job description is a document written to be approved, so it is written in language that nobody can object to: strong communication skills, proven track record, passion for clean code. You cannot search for any of that. A ticket forces concrete nouns, and concrete nouns are what sourcing runs on. Within four minutes of looking at a real ticket you will hear the name of a framework, a system boundary, a person who is currently overloaded and a constraint that was never in the draft.
If the manager cannot produce an artefact, that is the finding. A role with no identifiable work attached to it is a headcount request, and headcount requests get cancelled. Our note on engineering headcount planning in Dubai covers what to do when that is genuinely what you are dealing with.
Step 2: Ask What Breaks if This Role Stays Open for 6 Months
Ask it plainly, and then stay quiet long enough to be uncomfortable. You are looking for a specific consequence with a name attached: a launch that slips, a system only one person understands, an on-call rotation that is two people deep, a client commitment that will be missed.
Three answers tell you the role is in trouble. The first is a shrug. The second is a generic efficiency claim, which usually means the role was approved in a planning cycle and nobody has revisited it since. The third, and the most dangerous, is the answer where the manager describes something that is already broken and has been for a year. That one is not a hiring problem, it is a retention or architecture problem wearing a hiring problem as a costume, and filling the seat will not touch it.
Write down the answer in the manager’s own words. You will reuse that sentence in outreach, and it will outperform anything you write yourself, because it is the only part of the pitch that is specific to this company.
Step 3: Ask Who This Person Replaces, Copies or Relieves
Every developer role is modelled on a human being, even when the organisation chart says it is new. Somebody left, or somebody is drowning, or somebody is so good at one thing that the manager wants a second one of them. Get the name.
Then ask the two follow-ups that matter: what would you keep about how that person works, and what would you change. The second question is where the real requirements live. Managers who would never write difficult to work with in a job description will happily tell you that the previous person shipped quickly but nobody could read the code afterwards. That single sentence tells you to screen for readability and documentation habits, which is a completely different interview from the one the draft job description implies.
Step 4: Force One Trade-off Out Loud
This is the step most intake meetings skip, and it is the one that determines whether your shortlist gets accepted. Put two realistic profiles side by side, both of which exist in the Dubai market at the approved band, and make the manager choose.
Useful pairs, depending on the role:
- Depth or breadth. One engineer who has spent six years in your exact stack, or one who has shipped in four stacks and will need a month to get productive in yours.
- One senior or two mid-level. Same budget, very different team dynamics, and a different answer depending on whether the work is one hard problem or twenty ordinary ones.
- In the UAE or remote into your timezone. This one has to be settled before sourcing starts, not after a candidate the manager likes turns out to be in another country.
- Available in three weeks or available in three months. Notice periods in this market will quietly decide your shortlist if you do not decide first.
Write the choice down and read it back. A manager who will not pick is telling you, early and cheaply, that they will reject every candidate for being the wrong half of a trade-off they never made. That is worth discovering in minute twenty of an intake meeting rather than in week seven of sourcing.
💡 Our Expert Take
The trade-off question is the one that makes people uncomfortable, and that discomfort is the entire value. A hiring manager who says both is not being demanding, they are deferring a decision onto you, and you will pay for it with rejected shortlists you cannot explain to candidates. I have started saying the quiet part aloud in the meeting: if we do not choose now, we will choose in six weeks, except the choice will be made by whoever happens to apply. Nobody has ever argued with that sentence.
Step 5: Pin the First 90 Days to 3 Deliverables
Ask the manager to name three things this person will have shipped by day ninety. Not learned, not understood, not contributed to. Shipped.
Three is the right number. One is a formality, five is a fantasy, three forces prioritisation. The answers do two jobs at once. They give you concrete material for outreach, which is what makes a Dubai developer reply to a message from a company they have never heard of. And they give the eventual probation conversation an objective spine, instead of the vague impressions that make probation reviews in this market so unpleasant for everyone.
If the manager cannot name three, the role is not ready to post. Say so. It is a short, awkward conversation that saves a long, awkward quarter.
Want the intake run for you, with the brief written up?
HireDeveloper.ae runs the intake conversation as the first step of every engagement, and the two page brief goes back to you before any sourcing starts. If the answers say the role is not ready, we tell you that instead of starting a search we both know will stall. It is a faster conversation than most employers expect.
Start with an intake callStep 6: Agree the Evidence, Not the Qualifications
Take each must-have the manager has named and ask a single question: what would a candidate have to say or show in an interview for you to believe they have this?
This converts a requirements list into an interview plan. Five years of Node experience becomes a described production incident and what they changed afterwards. Experience with microservices becomes a service boundary they argued for and the argument they lost. Comfortable with ambiguity, which is the single most common unfalsifiable requirement in Dubai job postings, becomes a project where the requirements changed mid-build and what they did about it.
Run the same exercise on the nice-to-haves and you will usually find two of them are secretly must-haves and the rest can be deleted. A shorter, sharper requirement list widens the pool and narrows the interview, which is the correct direction for both. If you want the downstream artefact, our walkthrough on building a technical interview scorecard picks up exactly where this step ends.
Step 7: Close With the Decision Chain and the Clock
Last question, and never skip it: who can say no to this hire, in what order, and when are they unavailable in the next three weeks?
In practice this is where Dubai processes break. The technical interviewer travels. The department head is at a conference. The final approval needs a signature from someone who is out of the country for ten days. None of this is unusual and all of it is knowable in advance. A candidate who waits eleven days between a strong technical interview and any further contact is a candidate who accepts a different offer, and the loss gets recorded as a compensation problem because that is the reason people give when they are being polite.
Write the chain down as a list of names with dates beside them. Then ask one more thing: if the manager is unreachable for a week during the process, who decides. Getting a named deputy on paper costs thirty seconds and saves the whole timeline once per quarter.
The Two Page Brief, and Why the Confirmation Reply Matters
Write the brief within twenty-four hours, while the manager’s phrasing is still fresh. Page one holds the work, the trade-off that was chosen and the three ninety day deliverables. Page two holds each must-have with its evidence, the decision chain in order, and the dates each decision maker is away.
Then send it and ask for one line of confirmation. Not a meeting, not a review cycle, one line.
That reply is the whole point of the exercise. Six weeks later, when a shortlist gets rejected for a reason that contradicts the brief, the conversation is thirty seconds instead of thirty minutes, and it is about the role rather than about whose fault it is. Nothing else in a hiring process converts future conflict into present clarity that cheaply. A quarterly hiring retrospective is the natural place to check whether the briefs are holding up or quietly drifting.
💡 Our Expert Take
If you only adopt one thing from this, adopt the artefact. Walking into an intake with a ticket on screen instead of a draft job description changes the register of the entire conversation, and it does it in the first four minutes. Managers stop performing a requirements document and start explaining their actual problem. Everything else in this list works better once that has happened, and the questions are almost unnecessary once it has.
FAQ: Developer Role Intake Meetings in Dubai
What is a developer role intake meeting?
A short structured conversation between the person who will source the role and the person who will manage the hire, held before the job is posted. Its output is a brief rather than a job description: what the hire will own, what breaks without them, which trade-off the manager accepted, what they will have shipped by day ninety, what evidence satisfies each requirement, and who can say no. Forty-five minutes is enough with an artefact and a question list.
How long should an intake meeting take for a Dubai developer role?
Forty-five minutes, once, with the hiring manager present rather than a delegate. Two shorter meetings work worse than one that overruns, because the second restarts the context. If the manager cannot find forty-five minutes before the role is posted, that tells you how much attention the shortlist will get later.
What should the output of an intake meeting be?
A two page brief written within twenty-four hours and sent back for a one line confirmation. Page one: the work, the chosen trade-off, three ninety day deliverables. Page two: each must-have with the evidence that satisfies it, the decision chain in order, and the dates each decision maker is unavailable. The confirmation reply is what makes later disagreements cheap.
Who should attend a developer hiring intake meeting?
The hiring manager and whoever owns sourcing, and by default nobody else. Add the closest future teammate only for a direct peer replacement, and add finance only if the band is genuinely unsettled. Large intake meetings produce consensus job descriptions, and those attract the widest and least useful candidate pool.
Run the first one with us and keep the template
Whether you are scoping an engineering team for a fintech build in the UAE or backfilling a single TypeScript developer, the intake is the same forty-five minutes and it decides the next three months. HireDeveloper.ae will run it with your hiring manager, write the brief, and hand you the question list to reuse on every role after that.
Book the intake