Top 5 CV Sections Software Engineers Get Wrong in JLT Job Applications

[LeAaron]

Mistakes: Software engineers often mess up the "Work Experience" section by listing generic duties instead of quantifiable tech achievements. In JLT's competitive market, vague points like "developed software" are a major red flag.

Why they matter: JLT hiring managers and tech recruiters need to see your direct impact. They filter for specific technologies (e.g., cloud, specific frameworks) and business outcomes to assess if you can deliver in fast-paced, project-driven environments common in Dubai's tech hubs.

Example: "Responsible for backend development using Java."

Fix: Use the STAR method (Situation, Task, Action, Result) tailored for tech. Specify the tech stack, your role, and the measurable outcome. "Reduced API response time by 40% by implementing caching with Redis, improving user experience for a fintech application serving 10,000+ users."

Insight: In JLT, where many companies serve regional or global markets, highlighting scalability, security, and cross-border project experience is a huge plus. Tailor this section to the job ad's keywords.

[Harriet]

Mistakes: The "Skills" section is frequently misused as a dumping ground for every tool ever encountered. This creates keyword clutter and dilutes core competencies, making it hard for ATS systems and human reviewers in JLT to identify your true expertise.

Why they matter: Precision is critical. JLT tech roles often demand very specific skill combinations (e.g., ".NET Core with Azure DevOps" or "React Native for mobile apps"). An unfocused list suggests a lack of depth or specialisation.

Example: A long, unprioritised list: "Java, Python, C++, SQL, NoSQL, MongoDB, AWS, Docker, Kubernetes, Git, Jira, Agile, Scrum, Team Leadership, Communication."

Fix: Categorize skills (e.g., Programming Languages, Frameworks & Libraries, Cloud & DevOps, Tools & Methodologies). List only proficient skills and mirror the terminology from the job description. For a complete guide on structuring a UAE-appropriate CV, visit https://us.ok.com/ask_news/how-to-write-a-cv-in-the-uae-2026-guide-for-job-seekers/.

Insight: JLT employers value skills that align with Dubai's digital transformation goals—cloud migration, cybersecurity, and AI/ML. Highlighting these relevant skills upfront can immediately capture attention.

[DiMariana]

Mistakes: The "Projects" or "Technical Portfolio" section is often underdeveloped or poorly presented. Engineers either list only university projects or fail to describe personal/opensource projects with professional context, missing a chance to showcase initiative and practical skill application.

Why they matter: For tech roles, especially in innovative JLT startups or digital agencies, your projects are tangible proof of skill. They demonstrate problem-solving ability, passion for coding beyond the 9-5, and familiarity with modern development workflows (Git, CI/CD).

Example: "E-commerce website – Used React and Node.js."

Fix: Treat each significant project like a mini work experience. Include: Project Title, Your Role, Tech Stack Used, a brief description of the problem, and the outcome (e.g., "Deployed application using AWS EC2, reducing server costs by 20%" or "Github repo with 50+ stars").

Insight: In the UAE market, projects that solve regional problems or demonstrate an understanding of local user behaviour (e.g., multi-language support, high-load handling for sales events) can be particularly impressive to JLT employers.

[VonAlina]

Mistakes: The "Summary" or "Profile" section at the top is frequently either too generic ("Hardworking software engineer seeking a challenging role") or overly technical and jargon-heavy. It fails to immediately connect the candidate's value to the specific needs of a JLT-based company.

Why they matter: This is your 10-second elevator pitch. Recruiters in Dubai's fast-moving job market scan this first. A weak summary can lead to the rest of the CV being ignored, regardless of strong experience.

Example: "Dynamic and results-oriented developer with 5 years of experience in software development. Seeking to leverage my skills in a growth-oriented company."

Fix: Craft a powerful, keyword-rich summary. Mention years of experience, core specialisation (e.g., "Full-Stack Developer specialising in MERN stack"), key achievements, and the type of role/industry you target in JLT (e.g., "...aiming to contribute to fintech innovation in Dubai"). For more on crafting a powerful UAE CV profile, see https://us.ok.com/ask_news/how-to-write-a-cv-in-the-uae-2026-guide-for-job-seekers/.

Insight: A JLT-focused summary might subtly highlight attributes like "experience in agile, cross-cultural teams" or "understanding of UAE's digital economy," aligning your profile with the local business environment.

[McBeau]

Mistakes: The "Formatting & File Presentation" is a silent killer. Software engineers sometimes submit CVs as wordy, text-dense Word documents or overly designed PDFs that break ATS parsing. Incorrect file naming ("CV.pdf") is also a common unforced error.

Why they matter: JLT recruitment often involves initial ATS screening. Poor formatting—like using headers/footers for key info, tables, or unusual fonts—can cause your CV to be unreadable by the system. A messy CV also contradicts the precision expected from an engineer.

Example: A CV named "MyCV_2024_Final_v2.pdf" with a two-column layout using tables.

Fix: Use a clean, single-column, reverse-chronological format. Save your file as "YourName_SoftwareEngineer_CV.pdf". Ensure all section headers are standard (e.g., "Work Experience," "Skills"). Stick to professional fonts (Arial, Calibri) and use white space effectively.

Insight: In the professional environment of JLT, attention to detail matters. A clean, scannable, and ATS-friendly CV reflects well on your professionalism and understanding of modern hiring processes, setting the right tone before the technical interview.