What Not to Include on a CV as a Software Engineer Applying for Roles in Dafza

[LeAnastasia]

Mistake: Including personal details like age, marital status, nationality, or a photograph. Why they matter: UAE anti-discrimination laws and professional norms emphasize skills over personal attributes. Including these details is outdated, can introduce unconscious bias, and may immediately mark your CV as non-compliant with local standards. Example: A header stating "Date of Birth: 1985", "Nationality: Indian", or including a headshot. Fix: Only include your name, professional phone number (with UAE country code), email, and links to your LinkedIn/GitHub profiles. Omit all other personal information. Insight: DAFZA hosts international companies that expect modern, professional CVs focused solely on your capabilities as a software engineer. A clean, minimalist personal details section signals your awareness of international hiring practices.

[VanEllie]

Mistake: Listing every programming language or tool you've ever encountered in a dense, unprioritized "skills dump." Why they matter: In a competitive hub like Dafza, recruiters scan CVs quickly. A cluttered skills section makes it hard to identify your core competencies and suggests a lack of focus or self-awareness regarding the job's requirements. Example: "Skills: Java, C++, Python, HTML, CSS, JavaScript, React, Angular, Vue, Node.js, SQL, MongoDB, AWS, Docker, Kubernetes, Jenkins, Git, MS Office, Photoshop." Fix: Create a "Core Competencies" section tailored to the specific role. Group skills (e.g., "Languages," "Frameworks," "Cloud & DevOps") and list them in order of proficiency. Remove outdated or irrelevant tools. Insight: A targeted skills matrix is more effective. For comprehensive formatting advice suited to the UAE market, review a resource like https://us.ok.com/ask_news/how-to-write-a-cv-in-the-uae-2026-guide-for-job-seekers/.

[VanJayce]

Mistake: Including hobby projects or freelance work without clear context, metrics, or verifiable links. Why they matter: DAFZA companies value tangible impact and professional delivery. Vague mentions of personal projects come across as filler content and do not demonstrate the professional rigor or collaborative skills needed in a corporate free zone environment. Example: "Built a mobile app for fun" or "Did some freelance web development." Fix: For relevant projects, create a concise "Projects" section. For each, state your role, the technologies used, and a quantifiable outcome or link to a live deployment/GitHub repository with clean, documented code. Insight: Quality over quantity. One well-documented, complex project relevant to the target role (e.g., a fintech API integration for a DAFZA trade company) is infinitely more valuable than five vague hobby mentions.

[KiaraMarie]

Mistake: Using excessive technical jargon, acronyms, or internal company terminology without explanation. Why they matter: The first screener of your CV in Dafza might be an HR professional or a recruitment AI, not a technical lead. Overly niche language can obscure your achievements and cause your CV to be incorrectly filtered out. Example: "Refactored the GC to reduce STW in the JVM" or "Managed the CR for the QMS using SOPs." Fix: Write for a semi-technical audience. Spell out acronyms on first use and explain the business impact of technical tasks. Instead of "Optimized queries," write "Optimized SQL queries, reducing API response time by 40%." Insight: Clarity is key. Your CV must bridge the gap between technical depth and broad comprehensibility. For more on structuring achievements for UAE roles, see https://us.ok.com/ask_news/how-to-write-a-cv-in-the-uae-2026-guide-for-job-seekers/.

[StWillow]

Mistake: A generic "Objective" statement at the top that focuses on what you want, rather than a "Professional Summary" highlighting what you offer. Why they matter: DAFZA employers need to solve business problems with specific technical skills. A self-centered objective wastes precious top-of-CV real estate and misses the chance to immediately align your experience with their needs. Example: "A passionate software engineer seeking a challenging role in a growth-oriented company to utilize my skills." Fix: Replace it with a 3-4 line "Professional Summary." State your years of experience, core expertise (e.g., "backend systems," "cloud migration"), one key achievement, and your target domain (e.g., "seeking to contribute to scalable logistics solutions in a DAFZA-based firm"). Insight: Frame your introduction from the employer’s perspective. This shows commercial awareness and positions you as a solutions-provider from the first second.