Front-End Engineer | Project Experience Resume

Prompt

Create an editable two-page A4 resume for a fictional front-end engineer: use three projects (a React component library, mobile performance optimization and an accessibility overhaul) to show technical decisions, validation methods, deliverables and impact still to be validated; page two expands on the testing checklist for the accessibility overhaul. Dark gray, cyan-blue and white; mark all experience and metrics "Sample content". Write all content, headings, labels, sheet names and file names in English.

Result

docx
Alex Morgan — Front-End Engineer (Sample Content)

PROFILE

Front-end engineer working where product design, performance and accessibility meet. Each sample engagement below was owned end to end: framing the problem, choosing the approach, defining how it would be measured, and stating plainly what is proven and what is not.

CORE COMPETENCIES

SELECTED PROJECTS

Accessibility overhaul — testing checklist

Expanded working checklist for the accessibility project summarised on page one. Each row names the check, the method used to run it, and the acceptance criterion that has to hold before a flow can ship.

Sample content — a reusable template, not a record of a completed audit. Status values describe the sample project and are illustrative.

SCOPE AND ENVIRONMENTS

TESTING CHECKLIST

SIGN-OFF

Two-page A4 resume, editable in Word and print-ready as PDF. Both files are exactly two A4 pages, built from the same content so they stay identical.

Page one — dark-gray header band with name, role line and contact details; a cyan-bordered "Sample content" notice; profile; four core-competency rows; then three project cards, each with Context, Technical decisions, Validation method, Deliverables and an "Impact — to be validated" list:

  • React component library (Northwind UI) — headless core with CSS-custom-property theming, typed API with a codemod-backed change policy, one token source; validated with Testing Library, Playwright visual regression and consuming-team API review.
  • Mobile performance optimisation — route budgets enforced in CI before caching work, JavaScript reduction first, field data from mid-tier Android; validated with Lighthouse CI, 75th-percentile field Web Vitals and a 10% staged release.
  • Accessibility overhaul — fix the primitives rather than the pages, automated checks as a floor not a verdict, one owner per flow with a public scorecard; validated with manual NVDA/VoiceOver passes and a re-audit against the same baseline.

Page two expands the accessibility work into a 20-check testing checklist across six groups (automated gates, keyboard and focus, screen reader and semantics, visual/motion/responsive, content/forms/errors, release gate and regression), each row giving check, method and tool, acceptance criterion and status, followed by a gate rule, a status legend and a sign-off block.

On "Sample content": it is marked four ways — a banner under the header, a badge on every project title, a "sample content" tag on every metric line, and a footer on both pages. No figure is presented as a verified result; the third project's impact bullets explicitly say "pending re-audit" and "not yet significant", and the performance project states that no conversion claim is made.

Colour and type: dark gray #24292E for the header band and headings, cyan-blue #0E7C9B for rules, labels and badges, white for the page and reversed text, with a pale cyan tint for callouts. Arial throughout, 8 pt body with exact leading.

The DOCX is fully editable — native text, real tables and styled runs, no images of text, with page-number fields and a running header on page two only. The PDF is the print/share copy.

How it was made

Mode
Document
Try this prompt

Related document prompts