What CV skills mistakes do software engineers make when applying for tech roles in JLT?

[LaPaul]

Mistake: Listing a generic, unprioritized skills section without tailoring it to JLT's specific tech ecosystem. Why they matter: JLT companies often look for candidates with skills that match their immediate project needs, which can be niche (e.g., specific fintech APIs, payment gateways, or compliance-related tech). A generic list forces recruiters to guess your relevance. Example: Writing "Python, Java, SQL, React, AWS" without context or priority for a role that specifically requires deep expertise in Python and AWS for a backend position. Fix: Research the dominant industries in JLT (fintech, logistics, SaaS). Reorder your skills to highlight the most relevant ones first. Create a "Core Competencies" section at the top of your CV. Insight: The purpose of a skills section is to pass the 7-second scan. Tailoring it acts as a direct signal that you understand the local market's demands, moving you past the initial filter.

[EmmanuelDella]

Mistake: Failing to quantify achievements and instead listing only responsibilities under each role. Why they matter: JLT employers, especially in competitive tech roles, need proof of impact. Responsibilities tell them what you were supposed to do; quantifiable achievements show what you actually delivered, which is crucial for standing out. Example: Writing "Responsible for backend development" vs. "Optimized API response times by 40%, reducing server costs by 15% for a key client product." Fix: Use the STAR method (Situation, Task, Action, Result) to frame each bullet point, always focusing on the measurable Result. For comprehensive guidance on structuring achievements for the UAE market, see https://us.ok.com/ask_news/how-to-write-a-cv-in-the-uae-2026-guide-for-job-seekers/. Insight: This addresses a common misunderstanding that a CV is just a job description ledger. Its true importance lies in being a marketing document for your proven value.

[Hylla]

Mistake: Overlooking the inclusion of key "soft" or "power" skills like cross-cultural communication, agile teamwork, and client-facing experience. Why they matter: JLT's corporate environment is intensely collaborative and international. Tech roles often require liaising with global teams, non-technical stakeholders, and clients. Showing only hard skills paints an incomplete picture. Example: A CV filled with technical jargon but no mention of "Collaborated with UX team in Dubai and QA team in Asia to deliver a unified product feature." Fix: Integrate power skills into your role descriptions. Use phrases like "Translated complex technical requirements for business stakeholders" or "Mentored 2 junior engineers from diverse backgrounds." Insight: In a multicultural hub like JLT, the definition of a strong software engineer expands beyond code to include effective collaboration and communication within diverse teams.

[DelJonathan]

Mistake: Using outdated or overly broad technology keywords that don't match current job descriptions (e.g., "HTML" instead of "HTML5, Semantic HTML"; "Photoshop" for a UX role instead of "Figma, Adobe XD"). Why they matter: Many JLT firms use Applicant Tracking Systems (ATS) to filter CVs based on specific keywords from the job ad. Outdated terms can cause your CV to be rejected before human review. Example: Applying for a "DevOps Engineer" role and listing "VMware" when the ad emphasizes "Kubernetes, Docker, Terraform, and AWS ECS." Fix: Meticulously mirror the language from the job description. If they ask for "React.js," don't just put "JavaScript." For a masterclass on keyword optimization for UAE job searches, visit https://us.ok.com/ask_news/how-to-write-a-cv-in-the-uae-2026-guide-for-job-seekers/. Insight: This mistake stems from not understanding the purpose of keywords in the modern digital recruitment process, which is fundamentally different from even five years ago.

[AubreeAnn]

Mistake: Using complex formatting, graphics, charts, or multi-column layouts that corrupt in an ATS or distract from content. Why they matter: A visually "creative" CV might look good to a human, but if an ATS cannot parse it accurately, your information gets jumbled and you are auto-rejected. JLT recruiters often process hundreds of applications quickly. Example: A CV with an infographic-style skills chart, icons for contact info, or text boxes inside headers/footers. Fix: Use a clean, single-column, reverse-chronological format with standard section headings (e.g., "Experience," "Skills," "Education"). Save and send your CV as a PDF (unless specified otherwise) to preserve formatting. Insight: The core definition of a CV's design is not artistic expression but clear, machine-and-human-readable information architecture. Simplicity ensures both the ATS and the recruiter can easily find what they need.