Frontend developer with six years' experience building fast, accessible React interfaces for travel and subscription products. Turns design files into reusable components, fixes slow pages with measurement rather than guesswork, and treats WCAG as part of done. Recently brought a booking flow's Largest Contentful Paint under two seconds and lifted mobile conversion by 9%.
Experience
Frontend Developer · Wayfarer Trips, London
2022 – Present
Cut Largest Contentful Paint on the booking page from 3.8 s to 1.9 s with image preloading, code splitting and a leaner font stack.
Rebuilt the checkout in React and TypeScript; mobile conversion rose 9% in the first quarter after launch.
Led an accessibility audit against WCAG 2.2 AA and closed 112 of 126 issues, including full keyboard support for the date picker.
Created a shared component library in Storybook now used by four product teams, removing about 30% of duplicated UI code.
Junior Web Developer · Peachtree Subscriptions, London
2020 – 2022
Moved the account area from jQuery to React over eight releases without a single rollback.
Wrote Cypress end-to-end tests for sign-up and billing, cutting regression bugs reported by support by roughly half.
Worked with two designers to turn a Figma style guide into design tokens shared by web and email templates.
Education
BA (Hons) Graphic Design · University of the Arts London
2016 – 2019
Self-taught JavaScript alongside the degree; final project was an interactive exhibition guide.
Skills
Core
React, TypeScript, JavaScript (ES2023), HTML, CSS
Tooling
Next.js, Vite, Storybook, Jest, Cypress
Quality
WCAG 2.2, screen-reader testing, Lighthouse, Core Web Vitals
Collaboration
Figma handoff, design tokens, pull-request review
Certificates
Certified Professional in Accessibility Core Competencies (CPACC) · IAAP2023
Projects
Contrast checker extension
2023
A browser extension that flags low-contrast text on any page; around 2,000 weekly users.
Languages
English — Native
Gujarati — Fluent
Three summary options
Start from the one closest to where you are now.
Bootcamp graduate
Frontend developer fresh from a 14-week bootcamp, with three shipped React projects including a recipe planner used by 300 people. Writes semantic HTML first, tests with a keyboard and screen reader, and is looking for a junior role with real code review.
Senior frontend
Senior frontend developer with eight years across e-commerce and media. Owns performance budgets, design systems and frontend architecture for a team of nine, and moved a 400-page site to Next.js while keeping organic traffic steady. Mentors juniors through their first production releases.
Designer turned developer
Former UI designer who now writes the code as well. Five years in Figma and three in React mean fewer handoff gaps: components match the design, spacing follows tokens and edge cases are caught before review. Built a 60-component library adopted by three squads.
Keywords to include
Use the ones that are true for you, inside real sentences.
React
TypeScript
JavaScript
Next.js
HTML5 and CSS3
Web accessibility (WCAG)
Core Web Vitals
Responsive design
Component library
Jest
What recruiters look for
Tips for this role, with the kind of numbers that count.
Turn performance into before-and-after numbers
"Improved page speed" tells nobody anything. Quote the metric, the page and both values: "LCP on the booking page from 3.8 s to 1.9 s". Add the business effect if you have it, such as conversion or bounce rate.
Treat accessibility as a skill
Many teams now screen for it. Name the standard (WCAG 2.2 AA), what you tested with (VoiceOver, NVDA, keyboard only) and what you fixed. "Closed 112 of 126 audit issues" reads as ownership, not a checkbox.
Show components, not just pages
Hiring managers want people who build reusable parts. Mention a design system, a Storybook library or shared hooks, and how many teams or screens use them. Reuse is one of the clearest signs of frontend seniority.
Link a live demo you're proud of
For frontend roles a working interface often beats a list of skills. Pick one or two projects that load fast, work on a phone and pass a basic accessibility check, because reviewers will open them.
Mention how you test
Unit tests with Jest or Vitest, component tests and end-to-end flows in Cypress or Playwright show you protect the user journey. Pair it with an outcome, such as fewer regressions reported by support.
Keep framework lists honest
Listing React, Vue, Angular and Svelte together invites tough interview questions. Lead with the stack you used daily in the last two years, and mention the rest only if you could still build something with them this week.
Make this CV yours
Answer one question at a time; the assistant fills each section and never invents numbers.
Should a frontend developer CV include a portfolio?
Yes, when it shows the kind of work the job needs. One or two live projects with clean code, a mobile layout and sensible loading behaviour are enough. Describe each in a single line with the stack and one result, so the CV still works if nobody clicks.
How do I list design skills as a developer?
Put them where they help you deliver: Figma handoff, design tokens, spacing systems or prototyping. Avoid presenting yourself as a full designer unless that is the role. A bullet about closing the gap between design and build is usually more convincing than a list of design tools.
Is it worth mentioning older tools like jQuery?
Only as part of a story. "Migrated the account area from jQuery to React without a rollback" shows you can modernise a legacy codebase safely, which many employers need. Listing jQuery on its own in your skills section adds little for a modern frontend role.
