[Your Name] · [Email] · [Phone] · [City, ST]
April 21, 2026
Dear Hiring Manager,
I'm applying for the Senior Frontend Engineer role on your Growth team. Your engineering blog post on shipping React Server Components in Next.js 15 without breaking your legacy Pages Router pages matched almost exactly the migration I led at Linear last year, and I'd love to bring that playbook to your checkout funnel.
At Linear I led the frontend rebuild of our onboarding flow in Next.js App Router, replacing a 4-year-old CRA codebase that was blocking our move to React 19. I shipped the migration incrementally behind a middleware-based routing split, cut our Largest Contentful Paint from 3.1s to 780ms on mid-tier Android, and dropped the initial JS bundle from 412KB to 168KB through Server Components and route-level code splitting. Mobile activation moved from 41% to 52% in the eight weeks after launch — a number I only got because I pushed for the experiment design before we started, not after.
Before Linear I spent two years at a design-tooling startup (Paper) as the third frontend hire, where I built our component library from scratch in Radix + Tailwind and wrote the accessibility test harness that got us to WCAG 2.2 AA across 180 screens. I enjoy that kind of foundational work — design tokens, Storybook docs, a11y audits — as much as I enjoy shipping product. What drew me to your team specifically is that the growth charter sits inside the design system org; most companies treat those as opposing forces, and I think you're right that they aren't.
I'd love to walk you through the Core Web Vitals instrumentation we built at Linear and hear where your current performance budgets are landing. I can share a 15-minute Loom of the onboarding rebuild or jump on a call whenever suits your schedule.
Sincerely,
[Your Name]