React roles are usually filled by a hiring manager who reads the CV for about a minute, then decides whether to open your GitHub profile or your portfolio. That first minute is spent looking for two things: which parts of the React ecosystem you have used in production, and whether you have owned a feature end to end rather than picking up tickets from someone else.
The mistake most React CVs make is listing the framework and stopping there. "React, Redux, TypeScript" tells a reviewer nothing, because every applicant writes it. What separates a strong CV is the sentence after the stack: which screens you built, how many users saw them, what the load time was before and after your work, and what broke when you got it wrong.
This example is written for a mid-level developer with roughly four years of experience. If you are earlier in your career, move Projects above Professional Experience and let two or three well-documented builds carry the CV.
Opens in the editor with this content already filled in, so you can replace it with your own.
Arjun Mehta
Front-End Developer · React & TypeScript
arjun.mehta@example.com+44 7700 900112Manchester, United Kingdomlinkedin.com/in/example-arjun-mehtagithub.com/example-arjunmehta
Profile
Front-end developer with four years building customer-facing React applications in TypeScript. Most recent work covers a shared component library used by three product teams and a performance programme that halved Largest Contentful Paint on the highest-traffic page. Comfortable owning a feature from design review through to production rollout.
Tailwind CSSCSS ModulesRadix UIStorybookWCAG 2.2 AA
Testing
JestReact Testing LibraryPlaywrightMSW
Build & Delivery
ViteWebpackGitGitHub ActionsVercelLighthouse CI
Professional Experience
Front-End DeveloperFebruary 2023 – Present
Northgate Property Group · Manchester, United Kingdom
–Rebuilt the property search interface in Next.js and TanStack Query, replacing a jQuery page that had grown to 4,000 lines and was the source of most front-end bug reports.
–Cut Largest Contentful Paint on the listing page from 4.1s to 1.8s by code-splitting the map bundle, deferring third-party scripts and moving hero images to next/image.
–Designed and shipped a shared component library in Storybook, now used by the search, agent portal and marketing teams; new landing pages went from roughly two days to half a day.
–Introduced Playwright coverage for booking, enquiry and sign-in, which caught three regressions before release in the first quarter.
–Ran the accessibility pass that took the enquiry journey to WCAG 2.2 AA, including keyboard traps in the date picker and missing form labels flagged by an external audit.
Junior Front-End DeveloperJuly 2021 – January 2023
Brightloom Digital · Leeds, United Kingdom
–Built customer-facing screens for four client projects in React and Redux Toolkit, working directly with designers on component specs.
–Migrated a 60-component codebase from JavaScript to TypeScript over two quarters, agreeing a strict-mode rollout order with the team rather than converting everything at once.
–Reduced the main bundle by 310 KB by replacing moment.js with date-fns and removing three unused chart libraries.
–Took over front-end code review for the team after six months and wrote the review checklist still in use.
ReactRedux ToolkitTypeScriptJestWebpack
Web Development InternJanuary 2021 – June 2021
Civic Loop CIC · Leeds, United Kingdom
–Built a volunteer sign-up flow in React used by around 600 people during a city-wide recruitment drive.
–Wrote the first set of component tests for the codebase and set up the GitHub Actions workflow that ran them.
ReactJavaScriptJest
Selected Projects
Fieldnote
Creator and maintainer
–An offline-first note-taking app for site surveyors, built with React, IndexedDB and a service worker for full offline use.
–Handles conflict resolution when two devices edit the same survey, using a last-writer-wins strategy with a visible change log.
–Around 900 monthly active users; roughly 40 issues triaged and closed since launch.
ReactTypeScriptViteIndexedDBWorkbox
github.com/example-arjunmehta/fieldnote
a11y-forms
Contributor
–Merged three pull requests into an open-source accessible form library, covering error announcement, fieldset labelling and focus return after validation.
–Wrote the documentation page on validation timing that the maintainers now link from the readme.
ReactTypeScriptTesting Library
Education
BSc (Hons) Computer ScienceSeptember 2017 – July 2020
University of Leeds · Leeds, United Kingdom
–Final-year project: a browser-based visualiser for sorting algorithms, marked at 78%.
Upper Second Class (2:1)
Certifications
Meta Front-End Developer Professional CertificateApril 2022
Coursera
Web Accessibility (W3Cx)September 2023
edX
Languages
EnglishNative
HindiC1
GujaratiB2
React Developer example on the Developer layout. All details are fictional and shown for demonstration only.
What recruiters expect
Before writing anything, it helps to know what the person reading is checking for. In this field that is usually a short, specific list:
Production React, not tutorial React: routing, data fetching, caching, error boundaries and forms in a codebase other people also work in.
A clear position on TypeScript. Teams increasingly treat untyped React as a liability, and will ask how you type component props and API responses.
Evidence of performance work. Bundle size, Core Web Vitals, list virtualisation and render profiling come up in almost every interview loop.
Testing that goes beyond snapshots. Naming a testing library is weak; describing what you test and why is strong.
Some sense of how your work reached users: build pipeline, preview deploys, feature flags, release cadence.
Recommended CV structure
This is the running order the example uses. It is a starting point rather than a rule, but the order reflects what tends to be read first in this profession.
Profile — Three or four lines positioning you for the role.
Technical Skills — Grouped skills, for example "Languages" and "Tooling".
Professional Experience — Paid roles, in reverse chronological order.
Selected Projects — Work you built, with outcomes and the stack used.
Education — Degrees, diplomas and school-leaving qualifications.
Certifications — Completed certifications with the issuing body.
Languages — Spoken languages with CEFR levels.
Sections worth adding
Open Source — Worth adding if you have merged pull requests into a library a reviewer would recognise. Link to the PRs, not the profile.
Awards — Only if the award is technical - hackathon wins age quickly after your second job.
Community — Meetup talks and mentoring read well for senior roles where you will be expected to raise the team.
Skills worth including
Grouped rather than listed in one block. Grouping makes a long list readable and shows that you can tell the difference between the things you use daily and the things you have touched.
Vite · Webpack · Git · GitHub Actions · Docker · Vercel · Lighthouse CI
Beyond the technical list: Code review, Pairing with designers, Writing technical specs, Mentoring junior developers, Estimating and scoping. These belong inside your experience bullets, demonstrated, rather than in a list of adjectives.
Example professional summary
Three or four lines, positioned for the role rather than describing your personality. Two versions you can adapt:
Front-end developer with four years building customer-facing React applications in TypeScript. Most recent work covers a component library used by three product teams and a performance programme that halved LCP on the highest-traffic page. Comfortable owning a feature from design review to production rollout.
React developer focused on accessible, well-tested interfaces. Experience across Next.js, TanStack Query and Tailwind CSS in a codebase of around 90,000 lines, with a habit of leaving the parts I touch better documented than I found them.
Writing your experience
The difference between a CV that gets a call and one that does not is almost always in the bullet points. Each pair below shows a real rewrite of the kind of line that appears on most CVs in this field.
Weak
Responsible for building new features in React.
Stronger
Built the saved-search and alerting features used by roughly 40,000 monthly users, from component design through to rollout behind a feature flag.
Names the feature, gives a sense of scale, and shows you owned the release rather than just the code.
Weak
Improved website performance.
Stronger
Cut Largest Contentful Paint on the property listing page from 4.1s to 1.8s by code-splitting the map bundle and deferring third-party scripts.
A measured before and after, plus the specific technique. This is the bullet that gets asked about in interviews.
Weak
Wrote unit tests for components.
Stronger
Raised coverage of the booking flow from 34% to 81% with React Testing Library and added Playwright checks for the three journeys that generated most support tickets.
Ties testing effort to the parts of the product that were actually causing problems.
Taken from the example
The sample CV for this profession is fully written. A few sections from it, so you can see the level of specificity that works:
Experience
Front-End Developer, Northgate Property Group
Rebuilt the property search interface in Next.js and TanStack Query, replacing a jQuery page that had grown to 4,000 lines and was the source of most front-end bug reports.
Cut Largest Contentful Paint on the listing page from 4.1s to 1.8s by code-splitting the map bundle, deferring third-party scripts and moving hero images to next/image.
Designed and shipped a shared component library in Storybook, now used by the search, agent portal and marketing teams; new landing pages went from roughly two days to half a day.
Introduced Playwright coverage for booking, enquiry and sign-in, which caught three regressions before release in the first quarter.
Projects
Fieldnote — An offline-first note-taking app for site surveyors, built with React, IndexedDB and a service worker for full offline use.
a11y-forms — Merged three pull requests into an open-source accessible form library, covering error announcement, fieldset labelling and focus return after validation.
Education
BSc (Hons) Computer Science, University of Leeds — Upper Second Class (2:1)
Certifications and registration
Meta Front-End Developer Professional Certificate — Coursera
Web Accessibility (W3Cx) — edX
Common mistakes
A skills list that is really a syllabus
Thirty technologies with no grouping suggests exposure, not competence. Group them, and drop anything you would not want to be interviewed on for ten minutes.
Bullets that describe the ticket, not the outcome
"Worked on the checkout page" is a task. "Rebuilt the checkout form, cutting validation errors by a third" is a result a reviewer can ask about.
Claiming full-stack because you once touched an endpoint
If the role is front-end, depth beats breadth. Mention back-end work under the relevant job rather than restyling yourself as a full-stack engineer.
Portfolio links that 404
Side projects go stale. Before you send the CV, open every link. A dead demo is worse than no demo, because it suggests you did not check.
Burying the stack in prose
A reviewer scanning for "TypeScript" should find it in under three seconds. Keep a scannable technical skills block near the top.
ATS considerations
Applicant tracking systems behave differently by sector, and generic advice is often wrong for a given field. These points are specific to react developer applications:
Write "React" as a standalone word somewhere in the skills section. Filters frequently search for the exact token and will not expand "ReactJS" or "React.js" for you.
Keep the framework names out of image-only logos or skill bars. A rating out of five is unreadable to a parser and unconvincing to a human.
Spell out both forms once where they differ in the wild: "CI/CD (continuous integration and delivery)", "UI/UX".
If the advert names a specific state library, mirror its exact wording in your CV where it is true - "Redux Toolkit" and "Redux" are indexed differently.
Put your GitHub as plain text as well as a link. Some parsers keep the anchor text and drop the href.
The Minimal ATS layout is built for this, and the ATS guide covers what parsers do to a file in more detail.
Questions about react developer CVs
How long should a React developer CV be?
One page up to about five years of experience, two pages after that. If you are trimming, cut older roles down to a single line each rather than shrinking the font.
Should I include a GitHub link if my repositories are quiet?
Include it if there is something to see: a project with a readme, a few merged pull requests, or a repository that shows how you structure code. An empty profile invites a conclusion you would rather avoid.
Do I need a portfolio site as well as a CV?
Not for most React roles. A deployed project with a clear readme does the same job. If you do build a portfolio, make sure it loads quickly on a phone - reviewers notice when a front-end developer ships a slow site.
Where do side projects belong?
Below professional experience once you have two or more jobs. Before it if you are junior or changing career, in which case treat them like real work: problem, approach, outcome.
Is a photo expected?
Not in the UK, Ireland or the United States. It is normal in much of continental Europe. Match the convention where you are applying.