Senior React/Vite Developer Needed for 2-Week MVP Sprint — Branching Diagnostic App, Individual Only

We need a senior React/Vite developer who can help us stabilize and complete a working diagnostic app quickly. This is a time-sensitive MVP sprint. We need to be able to show a credible working version in about 2 weeks. This is not a basic website and not a simple quiz app. It is a branching diagnostic app with report generation, routing logic, early Playwright testing, and a large resource-library layer. We are open to developers worldwide, but you must be able to start this week and have meaningful overlap with Eastern Time or work Eastern Tim Zone hours when needed. Individual freelancers only. No agencies. Current Status We already have a working React/Vite app deployed on Vercel. The app includes: * multi-step diagnostic flow * branching logic * section routing * personalized report generation * early Playwright tests * registry-based documentation of app logic * AI-assisted/Cursor-built code * no backend currently * no database currently * state currently handled in React The current app is React/Vite. TypeScript experience is strongly preferred even if the existing code is not fully TypeScript. We have an existing junior builder with important context. You would not be starting from zero. We need a senior developer who can quickly review what exists, preserve what works, stabilize what is fragile, and help us get to a credible MVP demo. We are not looking for an automatic rebuild. If your first instinct is to rebuild from scratch before reviewing the code, this is probably not the right project. What We Need in the Next 2 Weeks The goal is a beta-showcase version that can be demonstrated to partners, testers, and internal reviewers. The user should be able to: * start the diagnostic * move through the flow * see appropriate sections based on answers * complete the diagnostic * receive a personalized report * see clear report status labels * click into relevant resource-library pages or resources * ideally leave and return later using the lightest reliable save-and-resume approach for MVP The goal is not to finish every feature. The goal is a stable, showable MVP path that demonstrates the diagnostic, report, and resource connection clearly. We do not need a perfect enterprise platform in 2 weeks. We do need a stable, credible MVP path. Immediate Technical Priorities We need help with: 1. Reviewing the current React/Vite structure quickly. 2. Stabilizing diagnostic state and routing. 3. Protecting working conditional logic. 4. Improving report generation where needed. 5. Adding or improving Playwright tests for core user journeys. 6. Recommending the lightest reliable save-and-resume approach for v1. 7. Recommending how to connect the app to a large resource library without storing hundreds or thousands of files inside the Vercel repo. 8. Working with our current builder during a fast handoff. 9. Providing full-stack judgment on whether MVP needs local storage, lightweight backend storage, Supabase/Firebase, Cloudflare, or another simple architecture. Resource Library Scale We will have 200+ resources very quickly and may grow to 1,000+ PDFs, templates, workbooks, and short videos over time. We need practical recommendations on: * file storage, such as object storage or a comparable approach * CDN delivery, including Cloudflare or comparable options * video hosting or streaming approach for larger video libraries * access control * resource versioning * resource manifest or registry * how the React app should link to resources without hardcoding hundreds of URLs For the 2-week sprint, we need the simplest architecture that avoids creating a migration mess later. Product Boundaries The product is educational only. It does not provide legal advice. The app has strict user-facing language boundaries. The developer should not rewrite legal/product language or create legal conclusions. For example, the app should not tell users they are: * compliant * protected * safe * approved * high risk * low risk * in violation * legally sufficient The developer does not need to be a lawyer. But the developer must respect product rules and avoid changing routing, report status logic, or user-facing product language without approval. First Milestone The first milestone should move fast. Within the first 24–48 hours, we need: 1. Quick architecture review What is working, what is fragile, and what should not be touched yet. 2. Short stabilization plan The safest path to a demo-ready MVP within 2 weeks. 3. Build recommendation Preserve, targeted refactor, or rebuild only if truly necessary. Any rebuild recommendation must be supported by specific evidence. 4. Testing recommendation Which Playwright checks are needed before showing the product. 5. Immediate sprint plan What you will do first, what our current builder should continue doing, and what should wait. After that, we expect implementation work to begin quickly if we are aligned. Ideal Candidate You are a strong fit if you have experience with: * React/Vite * TypeScript * JavaScript * Node.js * complex state management * branching forms, diagnostics, intake tools, quizzes, or decision-tree apps * report generation from user answers * Playwright or similar end-to-end testing * Vercel deployment * Git/GitHub * RESTful APIs or lightweight backend integrations * database architecture or lightweight storage decisions * Cloudflare, object storage, CDN delivery, or comparable asset-delivery architecture * working with existing codebases * reviewing AI-assisted code carefully * explaining technical tradeoffs in plain English * working with a nontechnical founder and an existing builder * moving quickly without creating a mess Must Have Please apply only if you can: * start this week * work during at least 3–4 hours of Eastern Time overlap * join a live handoff call with the current builder * communicate well in writing * explain technical tradeoffs without jargon and in plain English * work from existing code instead of defaulting to a rebuild * deliver practical fixes, not just advice Please do not apply if: * you are an agency * you are applying on behalf of an unnamed developer * the person interviewing would not be the person doing the work * you default to rebuilding before seeing the code * you treat this like a simple landing page or quiz * you do not work with tests * you are uncomfortable inheriting an existing codebase * you cannot explain technical decisions clearly to a nontechnical founder * you rely on AI-generated code without reviewing it carefully * you want to rewrite product/legal language yourself * you cannot work within strict product language boundaries Engagement and Budget We are open to hourly or fixed-price milestone work. We are also open to a capped first milestone for the first 24–48 hour technical review and sprint plan. If the first milestone is strong, we may continue immediately into a 2-week MVP completion sprint. To Apply Please answer these questions directly. Generic responses will be ignored. 1. Can you start this week and work with at least 3–4 hours of Eastern Time overlap? 2. Have you built or stabilized a branching diagnostic, intake flow, quiz, decision-tree app, or report-generating app before? Please describe two examples. 3. If you inherited a React/Vite app with diagnostic routing and report generation, what would you review in the first 24 hours? 4. We may have 1,000+ PDFs, workbooks, and videos over time. In plain English, how would you start thinking about where those assets should live? 5. In one sentence, explain the difference between storing 1,000 PDFs in the Vercel app repo versus using external storage with CDN delivery. Use no technical jargon. 6. How would you decide whether to preserve, refactor, or rebuild the current app? 7. What is your experience with Playwright or similar testing tools? 8. How do you use AI coding tools, if at all? How do you review and test AI-generated code before merging? 9. Are you an individual freelancer who would personally perform the work? 10. What is your hourly rate, and what fixed price would you propose for the first 24–48 hour technical review and sprint plan? We are reviewing applications immediately and expect to interview qualified candidates this week.