Claude Code Front End Engineer Next.js + Web Performance Optimization + Performance + Tech SEO

**FULL TIME 40+ HOURS A WEEK, NEW YORK TIME ZONE, USA HOURS, 830 AM TO 5 PM EST** CLAUDE CODE MAX REQUIRED: We are hiring a full-time Frontend Performance & Reliability Engineer to take ownership of the speed, reliability, and technical quality of AutoBuffy ⚠️ TWO NON-NEGOTIABLE REQUIREMENTS 1. WORKING HOURS: 8:30 AM–5:00 PM NEW YORK TIME You must be online, available, and actively working during 8:30 AM–5:00 PM New York time (Eastern Time), Monday–Friday. There are no exceptions to this schedule. Please do not apply if you cannot consistently work these hours. 2. CLAUDE CODE MUST BE YOUR PRIMARY DEVELOPMENT TOOL We are specifically looking for an engineer who uses Claude Code extensively every day. We are NOT looking for someone who occasionally uses Claude, ChatGPT, Cursor, or AI autocomplete. You should already know how to use Claude Code deeply for: Understanding large codebases Planning implementations Debugging and root-cause analysis Writing and refactoring code Creating and managing CLAUDE.md Skills, commands, hooks, and sub-agents MCP integrations Automated testing Playwright/browser testing Code review Git/GitHub workflows QA and verification loops Documentation and maintaining project context If Claude Code is not already central to how you engineer software, please do not apply. Your Mission Your job is straightforward: Make AutoBuffy extremely fast, reliable, observable, and technically clean — every day. This is not a general feature-development position. You will be the engineer responsible for continuously finding and fixing performance problems, frontend errors, regressions, technical SEO issues, browser problems, and customer-facing bugs. We want you finding problems before our customers or CEO finds them. What You Will Own Next.js / React frontend performance Core Web Vitals — LCP, INP, CLS PageSpeed Insights / Lighthouse Chrome DevTools profiling JavaScript and browser errors Sentry monitoring and investigation Mobile and cross-browser reliability PDP, search, category, cart and checkout performance API/network waterfall analysis Next.js App Router performance SSR / ISR / caching behavior JavaScript bundle optimization Image and asset optimization Cloudflare / CloudFront performance Performance regression detection Automated browser testing Critical customer-journey monitoring Breadcrumbs, structured data and technical SEO Proactively identifying technical problems Our Stack Frontend: Next.js 14, React, TypeScript, Tailwind CSS, SSR/ISR, PM2 Backend: Python, FastAPI, Celery Data: MySQL 8 / AWS RDS + read replica, Redis, Typesense Infrastructure: AWS EC2, S3, CloudFront, Cloudflare Engineering: GitHub, GitHub Actions Monitoring: Sentry, GA4, Microsoft Clarity, Cloudflare RUM Payments: Stripe, PayPal, Apple Pay ---- How We Work We move quickly, but evidence matters more than assumptions. If you say something is fixed, we expect you to prove it. A strong update looks like: “I reproduced the issue, traced the root cause, implemented the fix, ran automated tests and browser QA, and here are the before/after production results.” Not: “Claude says it's fixed.” Claude Code should dramatically increase your output, but you remain responsible for understanding, testing, and verifying everything you ship.