CV example
Frontend developer CV example
Frontend roles are judged on what users see and feel: speed, polish and accessibility. This example shows a React developer who backs up every claim with a number or a link you can click.
Below you'll find a full example CV (also called a résumé), summaries for different experience levels, the skills and keywords employers search for, stronger bullet points, and the interview questions to prepare for.
Frontend developer CV summary examples
Your summary is the first thing a recruiter reads. Two or three sentences: who you are, your strongest evidence, and what you want next. Here is the example CV's summary, plus versions for other levels.
Example CV
Frontend developer with 4 years of experience building fast, accessible React and Next.js interfaces for e-commerce and SaaS. I care about the details users notice: load time, keyboard support and clear error states.
Career changer or bootcamp graduate
Frontend developer who moved from graphic design after a 6-month bootcamp. Built 5 responsive React projects, including a booking app used by a local salon, and brings a designer’s eye to UI detail.
Senior
Senior frontend engineer with 8 years building design systems and complex web apps. Set up the performance budget and accessibility standards for a 40-person engineering team.
Skills to put on a frontend developer CV
Hard skills
- React (or Vue, Angular or Svelte, matching the job)
- TypeScript and modern JavaScript
- Semantic HTML and CSS layout
- State management and data fetching
- Web performance (Core Web Vitals)
- Accessibility (WCAG, screen readers, keyboard)
- Testing (Jest, Testing Library, Playwright or Cypress)
- Design systems and component libraries
Soft skills
- Working closely with designers
- Attention to detail
- Explaining technical trade-offs
- Owning features end to end
Show soft skills through your bullet points rather than listing them on the CV itself.
Keywords recruiters and ATS look for
Many employers screen CVs with an applicant tracking system (ATS) that matches words from the job ad. These come up often in frontend developer postings. Use the ones that are true for you, in the same wording as the job you're applying for. To compare your CV with a specific job ad, use the free CV keyword checker, or have Litjob tailor your CV to the job description for you.
- frontend developer
- React
- TypeScript
- JavaScript
- Next.js
- responsive design
- accessibility
- web performance
- component library
- REST API
- unit testing
- UI
For live figures, see the skills most requested in Software engineering job ads, updated weekly from thousands of postings.
Bullet points: before and after
Strong bullet points say what you did, how big it was and what changed. Compare:
WeakBuilt pages using React.
StrongerBuilt the product catalogue in React and TypeScript, serving 300,000 monthly visitors.
WeakMade the website faster.
StrongerHalved JavaScript bundle size with code splitting, improving mobile load time by 2 seconds.
WeakWorked with designers.
StrongerTurned Figma designs into a 40-component library, cutting new-page build time from days to hours.
WeakFixed accessibility issues.
StrongerMade sign-up fully keyboard and screen-reader accessible, meeting WCAG 2.1 AA.
Only use numbers you can explain in an interview. An honest estimate (“about 30%”) is better than a made-up exact figure.
Tips for writing a frontend developer CV
Put a live link at the top
Frontend is visual. A portfolio or a live project in your header lets a hiring manager judge your work in 30 seconds.
Quantify speed and usage
Load times, Lighthouse scores, users and conversion rates turn "built a page" into proof that it mattered.
Name the framework the job uses
If the posting says Vue and you have Vue experience, say Vue. Applicant tracking systems match exact framework names.
Show accessibility and testing
Many candidates skip these. A single bullet on WCAG or end-to-end tests sets you apart from the crowd.
Common frontend developer interview questions
Your CV gets you the interview, and interviewers will ask about what's on it. Prepare for these:
- How would you make a slow page faster?
- Talk about measuring first (Lighthouse, real-user metrics), then images, bundle size, caching and rendering strategy.
- How do you manage state in a large React app?
- Compare local state, context and a store, and say when you would use each, with an example.
- What makes a component accessible?
- Mention semantic elements, labels, focus management, keyboard support and colour contrast.
- Walk me through a project in your portfolio.
- Explain the problem, your decisions and one thing you would change. Have it open and working.