Front-End Developer resume example

This example resume shows how a front-end developer can present component work, performance fixes, and accessibility improvements with modest, believable results. Noah Fischer is a fictional candidate based in Edinburgh.

Start with this template

Noah Fischer

Front-End Developer

Edinburgh

Professional summary

Front-end developer with six years of experience building React and TypeScript interfaces for web applications. Focused on accessible components, measurable page performance gains, and clear collaboration with designers and back-end engineers.

Experience

Front-End Developer · Harbourline Software
2021 – Present
- Built a shared React and TypeScript component library of 40 components, cutting duplicated UI code across three product teams
- Reduced Largest Contentful Paint on the dashboard from 3.8s to 2.4s by splitting bundles, lazy-loading charts, and optimizing images
- Integrated REST and GraphQL APIs with consistent loading, error, and empty states, lowering UI-related support tickets by about 20%
Junior Web Developer · Pentland Digital Studio
2018 – 2021
- Converted design mockups into responsive, semantic HTML and Sass, delivering 15 client sites that passed internal accessibility checklists
- Wrote Jest unit tests and Cypress checks for checkout flows, catching regressions before release and reducing hotfixes during the final year
- Applied feedback from senior engineers in code reviews, improving code style and shortening average pull request review time

Skills

React · TypeScript · JavaScript (ES6+) · HTML5 · CSS3 / Sass · Web Accessibility (WCAG) · Core Web Vitals Optimization · Jest · Cypress · Git

Education

BSc, Computer Science — University of Edinburgh (2018)

This example is fictional and written for illustration. Replace every name, company, date and number with your own facts.

Name the frameworks and versions you used in each role, such as React with TypeScript, so keyword scans and engineers see your actual stack.
Quantify performance work with a metric and before-and-after values, such as LCP, bundle size, or Lighthouse score.
Mention accessibility work specifically, naming WCAG level, screen reader testing, or automated checks, instead of listing 'accessibility' as a skill.
Describe collaboration with designers and back-end engineers through a concrete handoff, like a shared component library or API contract.
Add a portfolio, GitHub, or live project link near your contact details so reviewers can inspect your code and rendered work.

Should a front-end resume list every framework I know?

No. List the ones you can discuss in depth and have used in real projects. A focused stack with evidence in your bullets reads as stronger than a long list of tools you touched once.

How do I show design sense without being a designer?

Mention work like turning mockups into responsive layouts, building design-system components, or fixing visual inconsistencies with designers. A portfolio link with live examples supports these claims.

What if I lack exact performance numbers?

Use approximate figures you can defend, such as a Lighthouse score change or bundle size reduction from your own tooling. If you have no numbers, describe the specific fix and its observable effect honestly.