Getting a job
Software engineer CV for Dubai: what to show and what to cut
What a software engineer's CV (or resume) needs for Dubai: the stack, projects and results, seniority, what Dubai ads ask for, and what to leave out.
11 min readUpdated 14 October 2026
Short answer
Who reads a software engineer resume in Dubai, and how fast
A recruiter reads your CV first, not an engineer, and quickly. Gergely Orosz, who writes The Pragmatic Engineer and a book on tech CVs, says recruiters do the first screen in most companies and take 5 to 20 seconds to decide whether you might be a match (his chapter on the hiring pipeline (opens in a new window)). A Michael Page recruiter in the Gulf: “We have 10 seconds.” and “We match words on the CV and those on the client’s job description.” (Michael Page Middle East (opens in a new window)). So your role, stack, level and location have to be findable in that time.
Two claims you may have read don't hold up. The “6 seconds” figure comes from a 2012 study of 30 recruiters by the job site TheLadders, and it timed the first “fit/no fit” decision, not the whole reading (the study (opens in a new window)). And we found no study showing that software rejects most CVs before a person sees them: Orosz reports, from recruiters who use them, that as of 2020 none of the major tracking systems rejected CVs automatically; the exception he gives is a knockout question on the application form (his chapter on ATS myths (opens in a new window)). What the software does do is in ATS-friendly CV: what it means and how to make one.
Your stack: where it goes and how much of it
Put a grouped skills list near the top, then name the tools again in the lines of the role where you used them: the list is what a recruiter's search finds, and the role lines show what you use now. The founder of ARC Talent told Gulf News that software engineers from big companies often “talk more about what the company does rather than what programming languages they can work with” (Gulf News (opens in a new window)). Michael Page's advice for the Gulf: “Group your skills clearly, for example technical, languages or systems.” (Michael Page Middle East (opens in a new window)).
Our CV review marks three things here. Each title links to the rule's reasons and sources.
Should fixA grouped skills list, not a keyword dump
Group skills (languages, cloud, data, tools) and keep the list under 40 items you can discuss in an interview.
Should fixThe technologies of each recent role
Name the languages, frameworks, cloud and tools you used in each recent role, especially the current one.
Must fixCovers the key terms of the job ad
Use the ad's own words for the skills and tools you really have, in your summary and in the role where you used them. Never add a skill you don't have.
Leave out star ratings and skill bars: “This self-rating can only backfire.” (Orosz, on common mistakes (opens in a new window)). A plain word of proficiency after a tool is a matter of taste.
A hiring manager on Hacker News, not a Dubai one, asks for the same list:
“Technology under each bullet point makes me as a reviewer do extra work. Some kind of summary of technology you're proficient in will be a good addition.”
So name the tools inside a role's lines, not as a tag under every bullet.
Above the list goes the summary: 2 to 4 lines on your role, years, main stack and domain. The summary at the top of your CV shows how to write it, with tech examples.
Projects and results: the formula Google gives
Write each project bullet as a result: what changed, by how much, and what you did to cause it. Google's careers page: “Be specific about projects you’ve worked on or managed. What was the outcome? How did you measure success? When in doubt, lean on the formula, ‘accomplished [X] as measured by [Y], by doing [Z].’” (Google Careers (opens in a new window)). The formula is Laszlo Bock's, who ran hiring at Google, and he added: “Providing data helps. Making it meaningful with a comparison helps even more.” (his post from 2014 (opens in a new window)). Recruiters in the Gulf say it in fewer words: “Use a simple structure for each role, action plus result.” (Michael Page Middle East (opens in a new window)).
Weak: Responsible for backend services in the payments team.
Better: Cut checkout API response time from [before] to [after] ms by moving session lookups to Redis, on a payments platform with [number] daily users.
Weak: Worked on Project Falcon.
Better: Led the move of [number] services from on-premise servers to Kubernetes on AWS for a UK retail bank; releases went from monthly to weekly.
Both pairs are invented examples. The brackets are deliberate: fill them with your own figures, and only ones you could explain in an interview. The second pair drops the internal project name, which means nothing to a reader outside your company (Orosz, interviewed by Coding Sans (opens in a new window)).
Should fixResults, not duties
At least 50% of the bullets in your recent roles should show a result: what changed, by how much, for whom. Use only numbers you can back up; leave a gap to fill in rather than guessing.
Should fixFew "responsible for" lines
Start bullets with what you did (built, cut, migrated, led) instead of "responsible for", "worked on" or "involved in".
You don't need a number in every bullet. Our review looks for a result in at least 50% of the bullets of your recent roles, and Google's own words are “When in doubt”.
Seniority: title, scale, team and scope
A reader works out your level from four things: your title, the size of what you built or ran, your team, and how far your decisions reached. Google asks for exactly that: “If you’ve had a leadership role, tell us about it. How big was the team? What was the scope of your work?” (Google Careers (opens in a new window)).
Nice to haveA specific title that fits your level
Use a specific title ("Senior Backend Engineer, payments") that matches your years and the levels employers use; avoid vague ones.
Should fixThe scale you worked at
Show the size of what you built or ran: users, requests, data volume, team size, uptime. Only figures you can stand behind.
Nice to haveUncommon acronyms and titles explained
Spell out an internal acronym or an unusual job title the first time you use it.
Titles travel badly, and Michael Page warns applicants from outside the Middle East to explain any that aren't universally recognised (Michael Page Middle East (opens in a new window)). If yours is “Module Lead” or “Member of Technical Staff”, keep it, because it has to match LinkedIn and your references, and add the common equivalent in brackets. Keep team sizes and titles to what you could defend in an interview (the rule and its sources).
Open source, GitHub and side projects
Link to GitHub or a portfolio only if it is current and shows something. Orosz: “Link only if they are up to date. Otherwise, save the space and remove it.” (common mistakes (opens in a new window)).
What a hiring manager looks for on opening it, again from Hacker News:
“When I go to a GitHub as a hiring manager, I try to get as much signal as I can. You are scared that I'll solely judge you on the code, but I'm looking for metadata.”
For a projects section, the Tech Interview Handbook asks for at least 2 projects you contributed to, with your own part spelled out and each name linked to the code (its guide (opens in a new window)). An open-source contribution works the same way: name the project and say what you changed.
Nice to haveProof beyond the CV
Link to your GitHub, portfolio or open-source contributions, and name any recognisable cloud certification.
Nice to haveCertifications with issuer and year
List each certification with the issuer and the year you got it (and the expiry, if it has one).
What Dubai ads ask for
These are our own counts from the Dubai tech job ads we track (how we get our numbers). Use them to decide what goes first in your skills list, never to add a tool you haven't used.
| Item | Share of ads |
|---|---|
| CI/CD | 10% |
| C++ | 6% |
| machine learning | 6% |
| Python | 6% |
| AWS | 5% |
| LLM | 5% |
| TypeScript | 5% |
| Elasticsearch | 4% |
| Item | Share of ads |
|---|---|
| machine learning | 14% |
| Python | 10% |
| CI/CD | 9% |
| SQL | 7% |
| AWS | 6% |
| Kubernetes | 6% |
| LLM | 6% |
| TypeScript | 5% |
| Item | Share of ads |
|---|---|
| A degree | 8% |
| A certification | 3% |
| Gulf experience | 1% |
| Arabic | 3% |
Of those 78 ads, 8% mention a degree, 3% a certification, 3% Arabic and 1% UAE or Gulf experience. An ad that mentions one may still treat it as a plus and not a must: read the ad, and claim none of them unless it's true. The 72 Dubai tech ads that state the experience they want ask for a median of 4 years: a guide, not a cut-off.
The rules in this guide hold for every engineering role. What changes is which measures show your level:
Backend and full-stack. Lead with the language and framework the ad names, then requests, users and data volume. For a full-stack role, say in each role's lines which side you owned; our data has no separate full-stack role.
DevOps and platform. Show uptime, the size of what you ran and how releases changed. List each certification with its issuer and year: the family ads name most is Cloud (AWS, Azure, GCP), in 0% of all tech ads.
Data roles. Show data volume, what ran in production and who used the result. A link to code counts as proof here too. In the 59 data scientist ads we tracked, the tools named most are machine learning (32%), Python (17%) and SQL (10%).
We show a role's own figures from 30 ads, and don't have that many yet for backend engineer and DevOps engineer roles: for those, read the all-roles chart above.
Applying from India or the UK
Add one line near the top saying where you are, your visa status and your notice period. Whether you are local, need relocation or need a visa changes how a recruiter ranks you (Orosz (opens in a new window)), and Michael Page's advice for the Gulf is to keep it short: “A simple line stating availability to move is enough.” (Michael Page Middle East (opens in a new window)). Our review checks all three, with its own advice for CVs from India and from the UK:
Must fixWhere you are and when you can start in Dubai
State your current city and country, and a line such as "Relocating to Dubai, available from the month you can start". Never give a Dubai address you don't have.
From the UK: Keep your UK town and add "Relocating to Dubai, available from the month you can start". Never give a Dubai address you don't have.
Must fixVisa or right-to-work status
Say where you stand: "Requires UAE employment visa", "UAE residence visa (transferable)", or "Golden visa holder".
From the UK: Replace a UK right-to-work line with your UAE status: "Requires UAE employment visa".
Must fixYour notice period, and whether it can be shortened
Say how long your notice is and whether it can be shortened or bought out ("Notice: two months, negotiable").
From the UK: UK CVs often leave it out: add your notice period and whether it can be shortened.
From India: Say how long your notice is and whether it can be bought out or shortened ("Notice: three months, can be bought out"). If it can't, say when you could start.
Give your real notice period. UAE law sets notice between 30 and 90 days (Decree-Law 33 of 2021, Art. 43 (opens in a new window)), so employers in Dubai are used to waiting that long, and a longer Indian notice period needs the buy-out line. In the UK the legal minimum is 1 week once you have been in the job for more than 1 month (GOV.UK (opens in a new window)), and contracts usually ask for more: state what yours says.
From India, also name the client behind a services firm (the rule). From the UK, add your nationality: UK guidance tells applicants to leave it out (National Careers Service (opens in a new window)), and Gulf recruiters expect it. Personal details, the photo, the layout and a free template are in our Dubai CV format guide; the search itself is in getting a tech job in Dubai from India.
What to cut, and how long to keep it
Cut whatever doesn't help a recruiter decide in that first scan. Our review marks these:
- No clichés or personal traits. Drop phrases like "hard-working", "team player" or "results-driven"; show it with a result instead.
- References on request, or left out. Don't list referees' names and numbers; "References available on request" or nothing at all.
- Older roles cut to a line or two. Roles that ended more than 10 years ago get a line or two each, so the space goes to recent work.
- No CTC or LPA figures (CVs from India). Take your current CTC and expected LPA off the CV. Talk pay on the application form or the first call, in AED a month, after checking the Dubai range for your role.
- No "I hereby declare" line or signature block (CVs from India). Delete the declaration ("I hereby declare that the information above is true…"), the place, date and signature at the end.
A photo is your choice: Tiger Recruitment in Dubai lists one among its don'ts (Tiger Recruitment (opens in a new window)), Bayt, the Gulf job site, calls a headshot “expected rather than optional” (Bayt (opens in a new window)), and our review never counts either as a fault. See photo or no photo.
On length, keep to 2 pages: Michael Page Middle East says ideally no more than 2 and never more than 3 (its CV guide (opens in a new window)), and Tiger Recruitment (opens in a new window) agrees. A 1-page CV is a US big-tech convention (Tech Interview Handbook (opens in a new window)), and Google sets no limit: “We don’t have a length requirement, but being clear and succinct are key.” (Google Careers (opens in a new window)). Our review allows 3 pages only past 15 years of experience. Which file to send is in CV as PDF or Word.
When the content is done, test the file. The free ATS check shows what tracking software reads from it; it looks at the file, not at how good your bullets are. The CV review reads the content: it marks each weak line against the rules linked in this guide and suggests a fix, leaving a gap where a number is missing. It can't know whether a claim is true.
Sources
The quotes and figures in this guide come from the pages below. Each rule of the CV review lists its own sources in the Dubai CV format guide, and the figures on job ads are our own counts.
- Federal Decree-Law No. 33 of 2021 on employment relationships, with its amendments (opens in a new window), MOHRE, 10 October 2026
- How to write a CV: CV sections (opens in a new window), National Careers Service (UK government), 10 October 2026
- Practical guide to writing FAANG-ready software engineer resumes (opens in a new window), Tech Interview Handbook (Yangshun Tay), 7 August 2026
- CV format for UAE jobs: the complete 2026 guide (opens in a new window), Bayt.com, 1 June 2026
- My personal formula for a winning resume (copy hosted by California State University, Los Angeles) (opens in a new window), Laszlo Bock, then head of People Operations at Google, 29 September 2014
- Handing in your notice: giving notice (opens in a new window), GOV.UK, 10 October 2026
- How to write a great CV (opens in a new window), Michael Page Middle East, 10 October 2026
- CV tips (opens in a new window), Tiger Recruitment (UAE), 29 July 2026
- How we hire: your resume (opens in a new window), Google Careers, 10 October 2026
- What do recruiters look for in a CV? (opens in a new window), Michael Page Middle East, 18 July 2026
- Recruiter's tips: how I read a CV (opens in a new window), Michael Page Middle East, 10 October 2026
- Seven CV traps to avoid (opens in a new window), Michael Page Middle East, 10 October 2026
- Keeping an eye on recruiter behavior (eye-tracking study, 2012; copy hosted by Boston University) (opens in a new window), TheLadders, 10 October 2026
- Applicant tracking systems and ATS myths busted (sample chapter of The Tech Resume Inside Out) (opens in a new window), Gergely Orosz, 10 October 2026
- Software engineer resume: tips to get in the door at hot tech companies (interview with Gergely Orosz) (opens in a new window), Coding Sans, 9 November 2020
- 5 mistakes to avoid when hunting for a job in the UAE (ARC Talent) (opens in a new window), Gulf News, 10 August 2022
- Common resume and CV mistakes (sample chapter of The Tech Resume Inside Out) (opens in a new window), Gergely Orosz, 10 October 2026
- The hiring pipeline (sample chapter of The Tech Resume Inside Out) (opens in a new window), Gergely Orosz, 10 October 2026
This is guidance, not legal or tax advice. Rules change; check the official source and your employer before you act.