Technology · Mid-career

Frontend Developer Resume Example

This example is for a frontend developer with several years of experience in React or a similar framework. It shows how to write about the parts of the job that a list of frameworks cannot convey: accessibility to a named standard, measured page performance, a shared component library and day-to-day collaboration with designers.

The example resume

Laid out in the Masthead template. The person, employers, schools and figures in this example are invented for illustration. Any resemblance to real people or organisations is unintended.

Freya Lindholm

Frontend Developer

  • freya.lindholm@example.com
  • +1 555 0152
  • Copenhagen, Denmark
  • freya-lindholm.example.com
  • github.example.com/freya-lindholm

Professional summary

Frontend developer with seven years of experience building accessible, fast interfaces for online retail in React and TypeScript. Maintains a component library used by four product teams and works with designers from the first Figma sketch to release. Brought a storefront to WCAG 2.2 AA and to good Core Web Vitals on mobile.

Work experience

Frontend Developer

Hearth & Alder (online homeware retailer), Copenhagen

May 2022 – Present

  • Rebuilt the product listing and checkout pages in React and TypeScript with Next.js, improving mobile Largest Contentful Paint from 4.1 s to 2.2 s at the 75th percentile
  • Maintained a library of 46 components in Storybook, with design tokens shared with Figma, used by 4 product teams
  • Led an accessibility programme with an external audit, fixing 130 issues to reach WCAG 2.2 AA; checkout now works fully by keyboard and screen reader
  • Cut the JavaScript sent on first load by 38% through route-based code splitting and replacing 2 heavy date and carousel libraries
  • Ran A/B tests on checkout with the product designer and analyst; the redesigned address form raised completed mobile orders by 6%

Web Developer

Nyhavn Lane Digital (agency), Copenhagen

Aug 2019 – Apr 2022

  • Built responsive sites and shop front ends for 14 clients using Vue, Sass and semantic HTML, working from designers' Figma files
  • Introduced visual regression tests with Playwright, so layout breakages were caught before client review instead of after it
  • Reduced Cumulative Layout Shift on a client's home page from 0.31 to 0.04 by reserving image space and loading fonts with fallbacks
  • Wrote the agency's front-end checklist covering focus order, colour contrast, alt text and form error handling

Skills

Languages: TypeScript, JavaScript, HTML, CSS

Frameworks: React, Next.js, Vue

Accessibility: WCAG 2.2, ARIA, screen reader testing (NVDA, VoiceOver), axe

Performance: Core Web Vitals, Lighthouse, code splitting, image optimisation

Tooling: Storybook, Vite, Jest, Testing Library, Playwright, Figma

Volunteer experience

Accessibility Reviewer

Harbourside Web Meetup

2023 – Present

  • Reviewed 12 charity and community websites for keyboard and screen reader access and wrote a prioritised list of fixes for each

Education

BSc Web Development

Kastrup Harbour University College, Copenhagen

2016 – 2019

Open this example in the resume builder Start empty with this template

Why this resume works

  • Performance is reported in the metrics frontend teams actually track (Largest Contentful Paint, Cumulative Layout Shift, JavaScript size), each with a before and after value.
  • Accessibility is treated as engineering work with a standard (WCAG 2.2 AA), a method (external audit, 130 issues fixed) and an outcome, instead of a single word in the skills list.
  • The component library bullet gives its size and reach (46 components, 4 teams) and mentions design tokens shared with Figma, which shows the collaboration with designers that the role depends on.
  • One bullet links interface work to a commercial result, a 6% rise in completed mobile orders, without claiming sole credit: the designer and analyst are named as part of it.
  • Skills are grouped under accessibility and performance as well as languages and frameworks, and the volunteer entry repeats the accessibility theme with different evidence.

What employers look for in this role

  • Build responsive, accessible user interfaces from design files
  • Develop and maintain reusable components and a design system
  • Measure and improve page performance, including Core Web Vitals
  • Write unit, component and end-to-end tests for interface code
  • Agree states, edge cases and feasibility with designers before build
  • Integrate with REST or GraphQL APIs and handle loading and error states
  • Check behaviour across browsers, devices and input methods

Skills to consider

List only the skills you can back up with an example. These are the ones that come up most for this kind of role.

Core web
Semantic HTML, Modern CSS (grid, flexbox, custom properties, container queries), JavaScript and TypeScript, Browser APIs, Responsive design
Frameworks and tooling
React, Vue, Angular or Svelte, Next.js or Nuxt, State management, Vite or webpack, Storybook, Jest, Vitest and Testing Library, Playwright or Cypress
Quality and collaboration
WCAG and ARIA, Screen reader and keyboard testing, Core Web Vitals and Lighthouse, Design tokens, Figma handoff, A/B testing

More bullet points to adapt

Each of these follows the same pattern as the example: an action, what it was applied to, and what changed. Swap in your own facts and figures. The bullet builder assembles the pattern for you.

  • Improved Interaction to Next Paint on the search page from 420 ms to 160 ms by virtualising a long results list and deferring filter updates
  • Migrated 120 components from JavaScript to strict TypeScript over two quarters, removing a class of undefined-property errors from production logs
  • Replaced a custom modal with the native dialog element and correct focus handling, closing 9 open accessibility tickets
  • Introduced responsive images in modern formats with correct sizes attributes, reducing image weight on product pages by 55%
  • Wrote usage guidelines with do and do not examples for 20 design system components, cutting repeated questions in the design channel
  • Added a dark theme through CSS custom properties and design tokens without rewriting any component

Words that recur in adverts

These terms appear often in adverts for this kind of role. Use the ones that are true of you, in sentences that show the skill in use, and check a specific advert with the keyword checker.

  • React
  • TypeScript
  • responsive design
  • accessibility (WCAG)
  • Core Web Vitals
  • design system
  • component library
  • HTML and CSS
  • cross-browser
  • Figma
  • Jest or Vitest
  • REST or GraphQL
  • server-side rendering

Which sections to include

Lead with a summary that names your framework and the two things many frontend adverts ask for beyond it: accessibility and performance. Experience comes next. Because frontend work is visible, put a link to a portfolio or code profile in the header if it shows current, working examples. Group skills so that HTML, CSS and accessibility are not buried under framework names. Volunteer or community work fits well when it shows the same craft. Keep the resume itself clean and well structured, since a frontend developer's own document is judged on that too.

Mistakes to avoid

  • Listing a framework and leaving out HTML, CSS and accessibility, which suggests you can assemble components but may not understand what the browser renders.
  • Writing "improved performance" with no metric; name the measure (LCP, INP, CLS, bundle size), the before and after values and whether they come from lab or field data.
  • Offering "pixel-perfect" as a selling point, when teams care more about how a layout behaves across screen sizes, zoom levels and content lengths.
  • Sending a heavily designed resume with columns, icons and skill bars to show visual flair; many application systems extract text poorly from such layouts, and a portfolio link shows design sense better.
  • Linking to a portfolio that is slow, broken on mobile or fails basic keyboard navigation, which undermines every accessibility and performance claim on the page.

Questions and answers

Do I need a portfolio as a frontend developer?

It helps more in this role than in most, because the work can be seen and inspected. Two or three real pieces with a sentence on your part in each are enough. If your work is behind a login or under a confidentiality agreement, describe it in the bullets and offer to walk through it at interview.

How do I write about accessibility if I am not a specialist?

Say exactly what you did: added labels and error messages to forms, fixed focus order, tested with a screen reader, met a contrast ratio. Name the standard you worked to, usually WCAG at level AA. Honest, specific claims are more convincing than "passionate about accessibility".

Which performance numbers should I include?

Use the metrics your team tracked, most often the Core Web Vitals (LCP, INP and CLS) or bundle size, with before and after values. Say whether the figure is from real users or a lab test if you know. The guide to quantifying achievements covers what to do when you have no exact figure.

Should I list both React and Vue?

Yes, if you have shipped work in both, with the one in the advert first. A second framework suggests you understand the underlying ideas (components, state, rendering) and can adapt. Do not add frameworks you have only followed a tutorial for.