Tailor your CV for Frontend Engineers roles
Frontend roles attract hundreds of applicants, and most CVs die in the ATS because they list 'JavaScript' while the job description says 'React 18, TypeScript, Next.js'. Recruiters then spend under 10 seconds scanning survivors for framework depth, not framework count. A generic CV that names every library you have ever touched signals breadth without ownership.
Tailor each application to the stack in the posting: mirror exact terms like 'server components' or 'design tokens', and back them with outcomes — Lighthouse scores raised from 62 to 95, bundle size cut 40%, INP under 200ms. Lead with shipped product work, link a live portfolio or GitHub, and show accessibility (WCAG 2.2) as a skill, not an afterthought.
Key skills recruiters look for
CV tips that actually move the needle
Quantify performance wins with Core Web Vitals
Replace 'improved site speed' with measurable results: 'Cut LCP from 4.1s to 1.8s by code-splitting and lazy-loading images, lifting conversion 12%'. Hiring managers trust Lighthouse, Web Vitals, and bundle-size numbers far more than adjectives.
Match the posting's exact framework vocabulary
If the job says Next.js, App Router, and Tailwind, those exact strings must appear in your skills and experience bullets — ATS keyword matching is literal. Listing 'React ecosystem' alone can filter you out before a human reads anything.
Link work recruiters can actually open
Put a portfolio URL, GitHub profile, or two live project links directly under your name. For each, add one line of context: stack used, your role, and a metric. Broken or private links are a common silent rejection.
Show accessibility and testing as core skills
Mention WCAG 2.2 audits, axe or Lighthouse a11y scores, and testing tools like Jest, React Testing Library, or Playwright. Teams increasingly screen for engineers who ship inclusive, tested UI — it separates seniors from tutorial-level candidates.
Frequently asked questions
What keywords do ATS scan for in frontend engineer CVs?
The exact technologies in the job posting: React, TypeScript, Next.js, CSS, JavaScript, plus context terms like 'accessibility', 'responsive design', 'web performance', and testing tools (Jest, Cypress, Playwright). Use the same spelling and casing the posting uses — 'Node.js', not 'NodeJS' — because many parsers match literally.
How long should a frontend engineer CV be?
One page for under eight years of experience, two pages maximum for senior or staff roles. Recruiters scan the top third first, so put your strongest stack and one quantified achievement — like a Core Web Vitals improvement — in the summary, not buried under older jobs.
Should I include personal projects on a frontend CV?
Yes, if they are deployed and demonstrate skills the role needs — a Next.js app with real users beats a todo-list tutorial. Give each project one bullet with the stack, a link, and a number: traffic, Lighthouse score, or GitHub stars. Drop them once work experience fills the page.