Engineering & Data

Front-End Developer resume example & template

A mid-level front-end developer resume that moved from agency work to a product team. Performance claims use Core Web Vitals at p75, and accessibility work names the WCAG level and what was fixed.

  • Performance bullets name the metric (INP, LCP) and the before and after, not a Lighthouse score.
  • Accessibility is shown as work done against WCAG 2.2 AA, not a skill-list keyword.
  • Portfolio and GitHub links sit in the header where a hiring manager will click them.
100%
Samir Aziz
Front-End Developer · React, TypeScript & Accessibility
Pittsburgh, PA(412) 555-0154samir.aziz@email.comsamiraziz.devgithub.com/samiraziz

Summary

Front-end developer with 7 years building customer-facing web apps, the last 4 on a ticketing checkout used during high-traffic on-sales. Works in React, TypeScript and Next.js, and owns Core Web Vitals and WCAG 2.2 AA compliance for the purchase flow.

Experience

Front-End Developer · Keystone TicketingFeb 2022 – Present
Pittsburgh, PA
  • Rebuilt the seat-map checkout in React and TypeScript, cutting mobile p75 INP from 420ms to 160ms during on-sale traffic spikes.
  • Moved event and venue pages from jQuery to Next.js with server rendering, dropping p75 LCP from 3.9s to 1.8s.
  • Built a Storybook component library of 46 components used by 3 product teams, with visual regression checks in Chromatic.
  • Led WCAG 2.2 AA remediation of checkout after a venue client's audit: fixed 71 issues and added keyboard seat selection.
  • Trimmed the main bundle from 1.4 MB to 620 KB by splitting routes and replacing Moment.js with date-fns.
Web Developer · Three Rivers InteractiveJun 2019 – Jan 2022
Pittsburgh, PA
  • Shipped 24 client sites for hospitals, universities and local retailers, from Figma handoff to launch, in HTML, Sass and JavaScript.
  • Wrote Cypress end-to-end tests for the agency's 5 largest e-commerce builds, catching checkout regressions before client review.
  • Converted 9 legacy WordPress themes to responsive, mobile-first layouts with no change to the client editing experience.

Education

B.S. Information Science · University of PittsburghApr 2019

Skills

Languages: TypeScript, JavaScript, HTML, CSS and Sass
Frameworks: React, Next.js, TanStack Query, Redux Toolkit, Tailwind CSS
Testing and tooling: Jest, React Testing Library, Cypress, Storybook, Chromatic, Vite
Accessibility and performance: WCAG 2.2 AA, ARIA, axe DevTools, NVDA and VoiceOver testing, Core Web Vitals (LCP, INP, CLS)

Projects

shift-board
Volunteer shift scheduler for a Pittsburgh food pantry, built in Next.js; used by about 150 volunteers a month.

How to write a front-end developer resume

What hiring teams in this field actually screen for, and the terms that get matched.

What front-end hiring managers screen for

On the first pass, screeners look for three things: a stack match (React, TypeScript, and whatever framework they run), a title that fits the opening, and a number that proves you ship. The strongest numbers are the ones users feel: Core Web Vitals at p75, bundle size, conversion or completion rates on a flow you built. Hiring managers then look for the size of the product surface you owned and whether you worked from designs with a design team. Accessibility work carries real weight when it names a standard and a result.

Terms and tools that get matched

List TypeScript, JavaScript, HTML and CSS explicitly even though they seem obvious; filters check for them. Add the framework and data layer by name (React, Next.js, Vue, TanStack Query, Redux), the styling approach (Tailwind, Sass, CSS modules), and testing tools (Jest, React Testing Library, Cypress or Playwright). For performance, use the current Core Web Vitals: LCP, CLS and INP, which replaced FID in 2024. For accessibility, cite the WCAG version and level (2.1 AA or 2.2 AA), ARIA, and the screen readers you test with.

Common mistakes on front-end developer resumes

The most common is a row of framework logos and a Lighthouse score with no number a manager could repeat to their team. Another is a portfolio link that is broken, slow, or three years stale; a bad link hurts more than no link. Avoid listing accessibility as a skill with nothing behind it, since interviewers will ask how you tested. Keep design tools in proportion if you are applying as a developer, and cut tutorial clones (todo apps, weather apps) once you have production work to show.

Front-End Developer resume FAQ

Quick answers before you start writing.

What should a front-end developer resume include?

A strong front-end developer resume opens with a concise professional summary, then work experience written as quantified, results-first bullets, followed by education, a skills section, and any certifications. The example above shows each section in order.

What skills should a front-end developer resume highlight?

Lead with the skills the job posting asks for. For a front-end developer, recruiters and ATS filters commonly look for TypeScript, JavaScript, HTML, CSS and Sass, React, and Next.js. Group them so they are easy to scan.

Is this front-end developer resume template ATS-friendly?

Yes. It uses a single-column structure, standard section headings, real text (no text trapped in images), and no tables or graphics that confuse applicant-tracking systems, so it parses cleanly while still looking polished.

How long should a front-end developer resume be?

One page is ideal for most front-end developers. Use two pages only if you have ten or more years of directly relevant experience, then tune the text size and margins so it stays clean.

Make this resume yours

Edit the wording, switch styles and colours, and tailor it to each job. All free.

Edit this template for free

Free · your data stays yours · no credit card