Should a frontend developer CV include a portfolio?

A link helps, but the CV must still explain each project: what it is, your role and one result. Many screeners read the CV before they click anything.

Is it worth mentioning accessibility on a frontend CV?

Yes, if you have done real work on it. Name the standard, what you fixed or built and how you tested it.

How do I show frontend performance work?

Use before-and-after measures you actually recorded, such as load time, Core Web Vitals, bundle size or conversion changes.

Engineering

Frontend Developer CV: what gets you shortlisted

Frontend roles are judged on what users experienced: speed, reliability, accessibility and how quickly the team could ship. Screeners look past framework names for proof that you built real interfaces, cared about quality and worked well with designers.

Get my free score

One-time analysis • $1.99 • No subscription

What employers look for in a Frontend Developer CV

Screeners check these first. Each one should be visible in your job entries, not only in a skills list.

Depth in the framework the posting names, usually React, Vue or Angular, backed by products you shipped with it.
TypeScript used in production, not just listed.
Performance work with results, such as Core Web Vitals, bundle size or load time improvements.
Accessibility practice: semantic HTML, keyboard support and testing with assistive technology.
Close work with design, including design systems or component libraries you built or maintained.

Skills Frontend Developer postings often ask for

Listing a skill is not the same as showing it. Resymetry counts a skill as matched only where your CV shows you used it.

React
TypeScript
JavaScript
HTML
CSS
Next.js
Accessibility (WCAG)
Testing Library
Playwright
Design systems
Web performance
REST and GraphQL

4 common Frontend Developer CV mistakes and how to fix them

Listing React, Vue, Angular and Svelte with equal weight.
Fix: Lead with the framework you know best and the posting asks for. Mention others briefly.
No mention of accessibility or performance.
Fix: If you have done either, add one concrete example. Many frontend postings list both.
A portfolio link with no context on the CV itself.
Fix: Name the product, your part in it and one result, so the CV stands on its own.
Describing pages you built instead of problems you solved.
Fix: Explain the user or business problem and how your interface changed it.

Weak and strong CV bullets

Illustrative examples, not real candidates. Use your own work and only numbers you can back up.

Weak: Built pages in React.
Stronger: Rebuilt the checkout in React and TypeScript, reducing JavaScript shipped by 40% and raising the Lighthouse performance score from 52 to 88.
Weak: Worked on accessibility.
Stronger: Fixed keyboard and screen-reader issues across 12 core components after an audit against WCAG 2.2 AA.
Weak: Maintained the component library.
Stronger: Maintained a shared component library used by five product teams, with Storybook docs and visual regression tests.

Know your chances for Frontend Developer roles

Your score and your biggest problems are free. The full report is a one-time $1.99.