CV Spelling Mistakes That Get a Software Engineer's Application Rejected in JLT

[MakaylaRose]

Mistakes: Misspelling core technical terms, frameworks, or programming languages listed in the job description (e.g., "Jave" instead of "Java," "ReactJS" as "ReactJs," "Kubernetes" as "Kubernete"). Why they matter: In JLT's competitive tech market, such errors immediately signal a lack of technical familiarity and attention to detail. Recruiters and hiring managers scan for keywords; misspelling them means your CV may not even pass the initial Applicant Tracking System (ATS) filter. Example: Writing "Mongo DB" inconsistently as "MongoDB," "Mongo Db," and "mongo db" within the same CV. Fix: Use the official capitalization and spelling from the technology's documentation. Be meticulously consistent throughout the entire document. Insight: Your CV is your first code review. Typos in tech stacks are like syntax errors—they prevent the program (your application) from running.

[JaceMarie]

Mistakes: Incorrect spelling of company names, especially the prospective employer's name or major tech firms in your work history (e.g., "Careem" as "Caream," "Emirates NBD" as "Emirates NDB"). Why they matter: This shows a lack of research and care. For a JLT hiring manager, it suggests you might not be genuinely interested in their specific company or role. It undermines professionalism before you even get an interview. For a comprehensive guide on professional presentation, review https://us.ok.com/ask_news/how-to-write-a-cv-in-the-uae-2026-guide-for-job-seekers/. Example: Listing a past employer as "Noon.com" but spelling it "Nooon" or "Noon" in the summary. Fix: Triple-check the exact spelling of every company name on your CV against their official LinkedIn page or website. Insight: Getting a company's name wrong is a basic but fatal social error. It tells the reader you are broadcasting your CV without customization.

[LaMarley]

Mistakes: Spelling errors in the names of recognized certifications, methodologies, or protocols (e.g., "AWS Certified Solutions Architect" as "AWS Certified Solution Architect," "Scrum Master" as "ScrumMaster," "REST API" as "Rest API"). Why they matter: These credentials are key differentiators. Misspelling them devalues your achievement and raises doubts about its authenticity. In a precise field like software engineering, accuracy in terminology is non-negotiable. Example: Abbreviating "Information Technology Infrastructure Library" as "ITIL" is correct, but writing it as "I.T.I.L." or "Itil" is not. Fix: Copy the exact title from your certificate or the awarding body's official website. Use the standard abbreviation if applicable. Insight: A certification's value lies in its recognized, standard name. Altering the spelling unintentionally turns an asset into a red flag.

[MacDaisy]

Mistakes: Misspelling location-specific terms like "JLT" (Jumeirah Lakes Towers), "UAE," "Dubai," or visa types (e.g., "Employment Visa" vs. "Work Permit"). Why they matter: For a role based in JLT, this indicates a lack of local market awareness and can imply inexperience working in the UAE context. Recruiters look for candidates who understand the environment. Ensuring every detail is correct is crucial, as outlined in resources like https://us.ok.com/ask_news/how-to-write-a-cv-in-the-uae-2026-guide-for-job-seekers/. Example: Writing "Jumeirah Lake Towers" instead of the universally used acronym "JLT" in the target job location field. Fix: Use standard local abbreviations (UAE, not U.A.E.). If mentioning "JLT," spell out "Jumeirah Lakes Towers" once in parentheses if space allows, then use the acronym. Insight: Adapting your CV to the local market's conventions is a subtle test of your cultural and professional adaptability.

[LeMiles]

Mistakes: Inconsistent use of American vs. British English spelling within the same CV (e.g., "center" and "centre," "optimize" and "optimise"). Why they matter: While not always a direct rejection reason in isolation, inconsistency portrays a lack of meticulousness and final review. For a software engineer, it mirrors sloppy code formatting, which degrades readability and professionalism. Example: Using "color" in one section (American) and "colour" in the project descriptions (British). Fix: Choose one variant (American English is widely used in tech) and use your word processor's spell check set to that language to enforce it consistently. Insight: Consistency in language is a form of code quality for your document. It subconsciously assures the reader of your systematic approach.