CV Information Mistakes Software Engineers Make for JLT Tech Roles

[MilesLee]

Mistake: Including irrelevant personal details (like marital status, nationality, photo) or an overly generic "Objective" statement. Why they matter: JLT tech recruiters and hiring managers prioritize skills and cultural fit within fast-paced, diverse teams. Outdated personal information wastes space and can introduce unconscious bias, while a generic objective fails to show specific interest in the role or company. Example: A CV starting with "Career Objective: To secure a challenging position in a growth-oriented company" followed by personal particulars. Fix: Replace with a sharp "Professional Summary" of 2-3 lines tailored to the JLT role, highlighting key tech expertise and the value you bring. Omit photo, age, and marital status. Insight: The UAE's private sector focuses on merit and relevance. A modern, professional summary immediately aligns you with international tech standards expected in JLT.

[Mario]

Mistake: Listing every technology ever encountered instead of curating for the specific JLT role. Why they matter: JLT companies often use Applicant Tracking Systems (ATS) and human screeners who look for precise keyword matches. A bloated "Skills" section dilutes your core competencies and can make you seem like a generalist rather than a specialist fit for their stack. Example: A backend engineer's CV listing "Python, Java, C++, PHP, Ruby, React, Angular, AWS, Azure, GCP, Docker, Kubernetes, Jenkins, Photoshop, MS Office." Fix: Prioritize and group skills. Match the primary languages/frameworks from the job description, then list relevant proficiencies. Move outdated or irrelevant tools lower or omit them. 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: In JLT's competitive tech scene, specificity wins. Tailoring your tech stack demonstrates genuine interest and saves the recruiter's time.

[MayaMarie]

Mistake: Using only generic job duties under experience (e.g., "wrote code," "fixed bugs," "attended meetings"). Why they matter: Tech leaders in JLT need to see impact and problem-solving ability. Duties tell what you did; achievements show how well you did it and the business value delivered. Example: "Responsible for developing new features for the payment module." Fix: Quantify achievements using the STAR method (Situation, Task, Action, Result). Rewrite as: "Developed and optimized the payment gateway integration, reducing transaction processing time by 40% and improving system reliability." Insight: Your CV is a marketing document for your problem-solving skills. Metrics and outcomes translate your experience into tangible value for a potential JLT employer.

[StBrayden]

Mistake: Ignoring UAE-specific CV conventions, such as not highlighting UAE experience or visa status. Why they matter: For roles in JLT, local experience is a significant advantage as it implies familiarity with the market and business culture. Clearly stating your current location and visa status (e.g., "UAE Residence Visa with transferable sponsorship") addresses immediate logistical questions for employers. Example: A CV from an expat already in Dubai that doesn't mention their current location or visa, making the employer assume they are abroad. Fix: Include a header with "Location: Dubai, UAE" and mention visa status if advantageous. Prominently feature any prior UAE/GCC work experience. For more on local best practices, a great resource is https://us.ok.com/ask_news/how-to-write-a-cv-in-the-uae-2026-guide-for-job-seekers/. Insight: Making it easy for a JLT company to hire you by pre-answering key administrative questions can give you a decisive edge over equally skilled candidates.

[OCaden]

Mistake: Submitting a CV in a non-ATS-friendly format (e.g., over-designed templates with columns, graphics, icons, or unusual fonts). Why they matter: Many JLT firms use ATS software to parse CVs initially. Complex formatting can corrupt, scramble text, or cause the ATS to reject the file entirely, meaning a human never sees your application. Example: A visually impressive CV with a two-column layout, progress-bar icons for skills, and custom fonts saved as a JPEG image. Fix: Use a clean, single-column, reverse-chronological format. Stick to standard fonts (Arial, Calibri). Save as a PDF unless specified otherwise. Ensure clear section headings (Experience, Education, Skills). Insight: The first "reader" of your CV is often a machine. Prioritize scannability and compatibility to ensure your content—not your design—gets through.