A complete example below. The person is invented; the writing is not. The notes on the right point at what's worth copying — swap in your own names, companies and numbers.
Sam Zhou
Frontend Engineer
(555) 010-0000sam.zhou@example.comNew York, NY
Summary
Five years in frontend on React and TypeScript, across two internal-tools platforms at 100+ person companies. Alongside feature work I've owned build tooling, the component library and frontend standards. I measure before I optimise, so every improvement here has a named metric.
Education
2016 - 2020State University
B.S. Computer Science
Coursework in data structures, operating systems, networks and web development. GPA 3.6/4.0.
Experience
Apr 2022 - PresentConsumer Internet Company
Senior Frontend Engineer
Own the frontend architecture for trading back-office tools; split 12 modules into independent build units, taking local startup from 96s to 21s
Led the component library — 46 components with docs and visual specs — cutting average new-page build time about 35%
Drove first-paint work against LCP specifically: route-level code splitting and image lazy loading took LCP from 3.4s to 1.5s
Introduced frontend error monitoring; blank-screen incidents went from 4-6 per week to effectively zero
Jul 2020 - Mar 2022Enterprise Software Company
Frontend Engineer
Built modules of a B2B admin platform in Vue.js, owning permissions and workflow end to end
Ran code review and helped set standards; module defect rate fell about 20%
Delivered mobile web support across 10+ common device profiles
Projects
Jun 2023 - PresentLow-code Page Builder
Frontend lead
Lets the marketing team assemble campaign pages by drag and drop instead of filing frontend tickets.
Designed the schema-driven rendering core and material protocol; time to publish a campaign page dropped from 3 days to 2 hours
Held 55fps+ in edit mode on 800-node canvases using virtual scrolling and incremental rendering
Skills
Deep React and TypeScript; practical understanding of Fiber scheduling and concurrent rendering
Build tooling: Webpack and Vite configuration, bundle analysis, dependency hygiene
Performance work driven by LCP and INP rather than guesswork
Component libraries end to end — docs, tests and release process
Node.js for BFF layers and API integration
Three mistakes this example avoids
✕A skills wall of frameworks with no evidence of depth in any
✕'Optimized performance' with no metric, no number, no method
✕Describing pages built instead of problems solved