
Mistake: Submitting a CV that is excessively long (e.g., 4-5 pages for a mid-level role), often including every single project, technology touched, and responsibility since graduation. Why it matters: Recruiters and hiring managers in JLT's fast-paced tech scene spend seconds on an initial scan. A lengthy CV obscures your key achievements and relevant skills, making you seem unfocused or unable to synthesize information. Example: A software engineer with 8 years of experience lists 15 detailed projects, including university assignments and minor bug fixes from 6 years ago, pushing the CV to 5 pages. Fix: Strictly limit to 2 pages for most roles. For senior/lead positions, 3 pages is the absolute maximum. Prioritize recent (last 5-7 years), relevant experience and quantifiable achievements that match the job description. Insight: In JLT, where roles often demand specific tech stacks (like .NET for fintech or React for startups), conciseness demonstrates you understand the market's need for clarity and impact.

Mistake: Making the CV too short and vague (e.g., 1 page with only job titles and basic duties), failing to demonstrate depth of experience or technical competency. Why it matters: A sparse CV leaves the recruiter guessing. It fails to prove you have the hands-on expertise in the specific languages, frameworks, or architectures mentioned in the JLT job ad. For a comprehensive guide on structuring your experience, visit https://us.ok.com/ask_news/how-to-write-a-cv-in-the-uae-2026-guide-for-job-seekers/. Example: "Senior Developer at XYZ Tech (2020-2024): Responsible for coding and team ." This reveals nothing about the tech stack, scale of projects, or outcomes. Fix: Expand each role with 3-5 bullet points. Use action verbs and metrics: "Led a team of 4 to migrate a monolithic payment system to microservices using Java and Spring Boot, reducing deployment time by 40%." Insight: JLT employers value demonstrable results. A detailed, yet concise, account of your projects shows you can deliver tangible value.

Mistake: Using inconsistent formatting to cram more information onto a page, leading to a cluttered, unprofessional, and difficult-to-read document. Why it matters: Poor formatting directly impacts scannability. If a recruiter struggles to find your key skills or career progression, they will move on. It also suggests a lack of attention to detail—a critical soft skill for engineers. Example: Mixing multiple font sizes and styles, using tiny margins, and having inconsistent spacing between sections to fit an extra half-page of text. Fix: Use a clean, single-column template with consistent headings, bullet points, and generous white space. Stick to one professional font (e.g., Calibri, Arial) and use bold/italic sparingly for emphasis only. Insight: In the competitive JLT market, a polished, easy-to-navigate CV acts as the UI/UX of your professional profile. It must be intuitively designed for the "user" (the hiring manager).

Mistake: Including large sections for irrelevant personal information, hobbies, or outdated certifications, which waste precious space without adding professional value. Why it matters: Every line on your CV is prime real estate. Wasting it on non-essential details dilutes your technical narrative and can make you appear less serious about your core discipline. Example: Dedicating 5-6 lines to listing "Reading, Travel, Football" or including a driver's license number and marital status, which are not required or recommended in the UAE. Fix: Remove all non-relevant personal details. Only include certifications directly related to the job (e.g., AWS Solutions Architect, PMP for tech leads). For mastering what to include and exclude, see https://us.ok.com/ask_news/how-to-write-a-cv-in-the-uae-2026-guide-for-job-seekers/. Insight: UAE CV norms are professional and skills-focused. Tailoring content to highlight only job-relevant technical and leadership skills aligns with local hiring expectations.

Mistake: Artificially inflating the CV length with "keyword stuffing" or overly verbose descriptions of basic tasks, without adding new substantive information. Why it matters: This is easily spotted by experienced recruiters and ATS systems. It comes across as deceptive padding and shows a lack of genuine, impactful experience to discuss. Example: Writing "Leveraged synergistic coding paradigms to facilitate robust implementation of front-end user interface components utilizing HTML, CSS, and JavaScript" instead of "Built responsive UI components with React.js." Fix: Be direct and use standard industry terminology. Focus on what you built, how (tech stack), and the business result (e.g., improved performance by X%, increased user engagement by Y%). Insight: JLT tech hiring managers are technically savvy. They respect clear, honest communication about your skills and see through fluff immediately. Authenticity and precision win.


