Senior full-stack engineer: rebuild a live debate platform's front end (Firebase, Daily video)

Rebuild Debatable's front end from zero on top of an existing backend, without losing a single user, rating, round, or subscription. Fixed-scope, milestone-paid, 8 to 10 weeks. Possible ongoing role after. WHAT DEBATABLE IS Live debates with a leaderboard. Two people get matched, argue one motion on video, an AI judge writes the ballot, the result moves a rating. You can debate or you can watch. Live at itsdebatable.com with real users, real subscriptions, real money in tournaments. THE PROBLEM, STATED PLAINLY The site was built solo, fast, with AI coding agents, over about five months. It works. It is also 20x the code it should be. - 128 public pages, 266 serverless functions, ~370,000 lines of HTML, JS and functions - The homepage alone is 1.27 MB and 22,900 lines. About 1,200 of those are needed - Three multi-thousand-line single-file React-via-CDN pages with no build step - Features layered on features. Nobody has been deleting The backend is in better shape and stays: Firebase auth and Firestore with real security rules, Daily.co video rooms, OpenAI Realtime voice, Stripe billing, a three-model AI judge panel with a published rubric and 80+ guard scripts. THE JOB, IN FOUR PHASES Phase 1 (weeks 1-2): audit and kill list. Read the site, read the data on what people actually use, and hand me a list: keep, delete, fold in. I expect you to argue for deleting most of it. You get my sign-off inside 48 hours. Phase 2 (weeks 3-6): the core loop. Homepage, matchmaking, the live room, the ballot, the leaderboard, watching a replay. One codebase, one component system, line budgets per page. Same URLs. Same analytics events. Phase 3 (weeks 7-9): everything that survived the kill list. Pricing, profile, settings, legal, the SEO pages that rank. Phase 4 (week 10): cutover. Redirects for every retired URL, service worker migration, zero downtime, rollback plan. You own the switch. HARD CONSTRAINTS - Every account, rating, round, transcript and subscription carries over untouched. No data migration that cannot be reversed. - Existing Firestore rules, auth, judge, billing and video functions are reused, not rewritten. Trim them if you want; replace them only with a written case. - Public URLs keep working. Google traffic is real and we are not throwing it away. - The result has to be smaller than what it replaces. I will measure it. YOU - You have shipped a consumer product rebuild before and it went live. Show me. - Strong on the browser: real CSS taste, performance instincts, you know what a 1.27 MB HTML file costs on a phone. - Comfortable with Firebase/Firestore, a video SDK (Daily, LiveKit, Twilio) and serverless functions (Netlify or similar). - You say no to features. You delete code and feel good about it. - Bonus: you have debated, or built something with a live audience. HOW TO APPLY No cover letter. Your proposal must contain exactly two things: 1. One product you built that replaced something bloated, with a sentence on what you cut. 2. Five lines on what is wrong with itsdebatable.com's homepage. Be blunt. Proposals without both are not read. I reply to everyone who sends both.