Frontend Developer

Front End DeveloperPeterMD | Remote (U.S.) | Full-time About PeterMDPeterMD is a PE-backed direct-to-consumer telehealth company in the men's health and wellness space — TRT, weight management, peptides, labs, sexual health, and supplements, sold as subscription care plans with pharmacy fulfillment. We're a growing business serving tens of thousands of patients, and we run the whole operation on one platform: a public marketing site, care funnels, and patient, provider, and admin portals.Here's the part worth knowing: we're bringing product engineering in-house. Until now the customer-facing web has been built largely by outside contractors and agencies. That's changing, and you'd be the first dedicated front-end engineer we hire.The RoleYou own the surface every acquisition dollar lands on.Our legacy WordPress marketing site is at the end of its life — peak load times north of twenty seconds, caching problems, and a page-build process measured in days. Its replacement is a React and Vite front end on Vercel, and it's close to ready. You'd own the everything that comes after.The bar we're setting: marketing should be able to launch a new package or landing page in hours, not days. You'll build the component and page architecture that makes that true. Data models and APIs are handled elsewhere; you build on top of them.This is a build role with real ownership, not a ticket queue. You'll also work across the patient, provider, and admin portals, and on the mobile builds that ship from the same codebase.What You'll DoOwn the customer-facing web — the React 18 + TypeScript + Vite front end on Vercel that replaces our WordPress site, plus the Start-TRT, GLP-1, and peptide care funnelsBuild pages the marketing team can reuse — composable section and package components with a self-serve authoring path and independent deploys, so new offers ship without an engineering ticketTranslate Figma to production at 1:1 fidelity — Figma is the source of truth for marketing pages, and we verify against itWork in a real design system — Tailwind CSS, Radix primitives with shadcn patterns, Framer Motion, Lottie for motion graphics, Lucide icons, and documented typography and surface guidelinesOwn page performance — performance budgets, code splitting, image and asset pipelines, motion-graphic weight on mobile, measured before-and-after. Load time is a revenue metric here, and today it's a bad oneBuild product UI across roles — patient portal, provider review surfaces, and admin operations screens using React Router, TanStack Query, React Hook Form with Zod validation, Recharts, TipTap, FullCalendar, dnd-kit, and rrweb-backed session replay and heatmap viewsShip conversion-critical flows — checkout, onboarding, one-click upsell, and product-aware intake, including our migration to StripeSupport the SEO migration — roughly 500 legacy routes remapped, structured data, and analytics and consent instrumentation. Our current attribution setup is tied to the root domain and needs rebuilding as landing pages move to a subdomainSupport the mobile app — the same React codebase ships to iOS and Android through Capacitor. App Store submission is on the roadmap and you'd be central to itWrite the tests that protect your work — Gherkin scenarios and Playwright coverage for auth-visible and conversion-critical flows, and meet our documented Definition of Done before handoff. Note there is no CI yet; verification is deliberate and manual todayCare about accessibility and cross-browser behavior — real patients on real devices, including a meaningful share of older usersWhat We're Looking ForMust-haves4+ years building production React with TypeScript — you've owned significant surface area, not just contributed componentsModern build tooling (Vite, ideally with SWC) and genuinely component-driven architectureTailwind CSS and headless component primitives (Radix, shadcn, Headless UI, or similar)You can take a Figma file and ship it pixel-accurate without a designer chasing youDemonstrated performance work — you've measured page load and Core Web Vitals, found the problem, and can tell us what the numbers were before and afterExperience on conversion-critical surfaces: checkout, funnels, multi-step forms, experimentsComfort with serverless and preview-deploy workflows (Vercel, Netlify, or similar)Solid Git hygiene — feature branches, small commits, PRs you'd be happy to have reviewedStrong plusDTC ecommerce or subscription commerce, especially Stripe Elements or CheckoutCapacitor, React Native, or any mobile app store submission experienceLarge SEO migrations and redirect mappingFront-end work in PCI or otherwise regulated environments where what you log and expose is governedHeavy AI-assisted development — Cursor, Claude Code, Codex. We're an AI-forward engineering team and we interview for how well you use these tools, not whether you doAnalytics, attribution, and consent tooling: Freshpaint, GA4, Triple Whale, server-side trackingLottie and motion work, PDF generation in the browser (jsPDF, pdf-lib), or session-replay toolingDesign instinct. If you can improve a layout rather than only implement it, say soFamiliarity with Supabase or a similar BaaS client on the front endCompensation & DetailsLevel: Mid to Senior (4–8 years)Location: Remote — U.S. basedEmployment type: Full-time employeeStack notes: Node 24, TypeScript, npm workspaces monorepo, Vercel, SupabaseCompensation: Competitive base commensurate with experienceBenefits: Health, dental, visionWhy This Role, Why NowThree things make this unusual.First, you're first. There is no legacy front-end team whose decisions you inherit. The component architecture, the performance standards, the way marketing ships pages — you set those.Second, the work is visible immediately. This isn't an internal tool nobody sees. Every paid acquisition dollar the company spends lands on pages you own, and the conversion effect of your work shows up in a scorecard the CEO reads weekly.Third, we're rebuilding in the open. We're migrating off a failing WordPress stack, cutting over payment processors, launching new product lines, and preparing a mobile app for the App Store. If you want to arrive after the interesting decisions are made, this isn't it.We move fast, we document what we build, and we're honest about the state of things. The site is slow. The quality process is being built as we speak. That's why we're hiring.PeterMD is an equal opportunity employer. We celebrate diverse backgrounds and are committed to building an inclusive team.