How to write it
"React" is table stakes — the differentiator is what you fixed
Every frontend resume in the pile says React, TypeScript, and responsive design. Those words get you parsed; they don't get you picked. What gets you picked is the sentence a weaker candidate can't write, and in frontend that's almost always performance, accessibility, or systems adoption.
So instead of "developed responsive UIs using React", write the one that has a number in it: "cut the initial bundle from 6MB to 900KB and LCP from 4.1s to 1.3s". The stack is implied. The judgement isn't, and that's what's being assessed.
Performance work is the easiest place to find real metrics
Frontend is unusually well instrumented, which is a gift for anyone writing a resume. Lighthouse scores, Core Web Vitals, bundle sizes, time to interactive, render counts — these are all numbers you can honestly quote, and most developers never think to.
Pair the technical number with the business one where you have it. "34-point Lighthouse gain" is good; "22% lift in organic conversion on a 34-point Lighthouse gain" is the version that survives the conversation with the hiring manager's manager.
- Bundle size before and after
- LCP, CLS, INP, or the Lighthouse score
- Number of components, and how many teams adopted them
- Accessibility violations closed, or the audit you passed
- Test coverage added, and the regressions it caught
Accessibility, stated specifically
"Passionate about accessibility" is a phrase that appears on resumes belonging to people who have never opened a screen reader. Naming the standard, the tool, or the outcome is what makes the claim land: WCAG 2.2 AA, axe, VoiceOver, keyboard-only navigation, focus management in a modal.
This matters more than it used to. Public-sector and enterprise buyers increasingly require accessibility conformance, so a developer who has actually been through an audit is solving a procurement problem, not just a moral one. Say that you've done it.
A portfolio link that loads is worth a paragraph of prose
Frontend is the one specialism where the work can be inspected in a browser in five seconds, and reviewers do exactly that. One live, fast, accessible site under your own name will do more than any bullet on the page — and a portfolio that's slow or broken does proportionate damage, since the medium is the message here.
Keep the link short and put it in the header next to your email. If your best work is under NDA, ship something small of your own instead; a single well-built page beats a list of client names nobody can click.