What CV content hurts a software engineer's chances of getting hired in JLT?

[AdalineDella]

Mistake: Including a photograph, marital status, age, or other personal details. Why they matter: In the professional environment of JLT's tech companies, this is considered irrelevant at best and unprofessional at worst. It can lead to immediate disqualification as it introduces bias and shows a lack of understanding of UAE corporate norms, which focus on skills and merit. Example: A CV header with a photo, followed by lines stating "Date of Birth: 1990", "Marital Status: Single", and "Nationality: Indian". Fix: Remove all personal details. Your CV header should contain only your name, professional title (e.g., "Senior Backend Engineer"), phone number, email, and LinkedIn profile/GitHub link. Insight: JLT recruiters seek a clean, modern CV that highlights technical competency, not personal biography. A cluttered personal section wastes the precious top-third of the page where your core skills should be.

[ChristianFitz]

Mistake: Using a generic, non-technical "Career Objective" statement at the top. Why they matter: For a software engineer in JLT's competitive market, a fluffy objective like "seeking a challenging role to grow my skills" is dead space. Hiring managers and automated systems scan the top of your CV for specific technologies and achievements relevant to their stack. Example: "Objective: To obtain a software engineering position in a dynamic company where I can contribute to team success and develop my professional abilities." Fix: Replace the objective with a "Professional Summary" or "Technical Profile." This 3-4 line section must be a powerhouse of keywords (e.g., "Full-Stack Developer with 5+ years building scalable fintech applications using React, Node.js, and AWS") and quantifiable achievements. For comprehensive formatting advice, see https://us.ok.com/ask_news/how-to-write-a-cv-in-the-uae-2026-guide-for-job-seekers/. Insight: Your CV's first 15 seconds decide its fate. A targeted technical summary immediately signals you are a fit for roles in JLT's tech hubs.

[LukeLynn]

Mistake: Listing every programming language or tool you've ever touched, without context or proficiency level. Why they matter: Tech leads in JLT need to quickly assess your actual depth. A long, unprioritized "skills" list filled with outdated tech (e.g., Visual Basic, Adobe Flash) or beginner-level exposure to in-demand tools (e.g., Docker, Kubernetes) destroys credibility and suggests a lack of self-awareness. Example: Skills: "Java, Python, C++, PHP, Ruby, Perl, HTML, CSS, JavaScript, React, Angular, Vue, MongoDB, MySQL, Oracle, AWS, Azure, GCP, Docker, Jenkins, Git, SVN." Fix: Categorize skills (e.g., Languages, Frameworks, Tools/Platforms). Within each, list in order of proficiency. Consider removing items you haven't used professionally in 5+ years. Be prepared to be grilled on every item listed. Insight: Quality over quantity. A concise, honest skills list tailored to the JLT job market (heavy on cloud, modern frameworks, and DevOps) is far more powerful than a comprehensive but misleading one.

[MaverickAnn]

Mistake: Writing job descriptions that are purely a list of responsibilities, not achievements. Why they matter: Every other CV says "developed features" or "fixed bugs." In JLT, where companies measure impact, this doesn't differentiate you. Hiring managers want to see the result of your work—how you improved performance, revenue, or efficiency. Example: "Responsibilities: Developed REST APIs for the payment module. Participated in code reviews. Fixed reported bugs." Fix: Use the STAR (Situation, Task, Action, Result) or CAR (Challenge, Action, Result) method. Start bullets with action verbs and include metrics. For example: "Optimized payment API latency by 40%, reducing average response time from 220ms to 130ms, by refactoring database queries and implementing Redis caching." To master this achievement-oriented approach, a detailed CV guide is available at https://us.ok.com/ask_news/how-to-write-a-cv-in-the-uae-2026-guide-for-job-seekers/. Insight: Your CV should answer "So what?" for every task you list. Quantifiable achievements prove you can deliver tangible value, which is the ultimate currency in JLT's tech sector.

[McZoey]

Mistake: Having a CV longer than two pages, especially for candidates with under 10-12 years of experience. Why they matter: JLT recruiters and startup founders are extremely time-poor. A lengthy CV with dense paragraphs, outdated university projects, or very old experience suggests an inability to synthesize information and prioritize what's relevant. It often gets skimmed or skipped entirely. Example: A 4-page CV for a mid-level engineer detailing 8-year-old university projects, every minor certification, and paragraphs describing basic job duties from 2015. Fix: Ruthlessly edit. For most software engineers, one to two pages is the sweet spot. Trim older roles to 1-2 bullet points. Remove graduation projects and obsolete certifications. Use clear headings, bullet points, and white space to enhance readability. Insight: A concise CV is a sign of a clear, efficient communicator—a highly valued trait in fast-paced JLT tech environments. It shows respect for the reviewer's time.