Full-Stack Developer for Restoration Platform

ABOUT THE PROJECT We're a multi-branch disaster restoration company (fire, water, storm, mold, reconstruction) replacing whiteboards, paper checklists, and scattered spreadsheets with a custom digital platform. Initial discovery and architecture planning is done — we have schemas, wireframes, and a roadmap to work from — but we're open to your input on approach, timeline, and tooling. ———————————————————————————— WHAT WE NEED BUILT ▸ Core Backend ("Shared Brain") A central database powering everything: jobs, tasks, leads, photos, messages, and user profiles. Must support multiple regional branches with strict data isolation (subcontractors in one region can't see another region's jobs), role-based access control, and passwordless SMS-code login. ▸ Field Technician Mobile App (iOS + Android) • Digital daily job board with simple Green / Yellow / Red status indicators • Job detail screens with interactive task checklists that update progress in real time • Photo capture with automatic compression and OFFLINE SUPPORT — crews often work in disaster zones with no signal, so everything must cache locally and sync when connectivity returns • In-app team chat per job • GPS-verified check-in (confirm the tech is actually on site before allowing task logs) ▸ Homeowner Web Portal + Marketing Site • Simple passwordless login for clients to see their project's live progress timeline and photos — with internal data (margins, subcontractor info, lockbox codes) completely walled off • Automated weekly progress email digests • Fast public marketing site with an automated review-request flow when jobs complete ▸ Sales CRM + Automations • Lead pipeline (New → Contacted → Estimating → Won) with incident alert ingestion and proximity-based rep routing • Mobile contract e-signing • Automatic lead-to-job conversion — no double data entry anywhere in the system ———————————————————————————— OUR PRIORITIES 1. SECURITY — row-level access control everywhere; homeowners and subs only ever see what their role allows 2. OFFLINE-FIRST — the field app must work in dead zones 3. SIMPLICITY — many users are non-technical field subs; big tap targets, no passwords, no walls of text 4. OWNERSHIP — all code and assets live in our repository; we retain full ownership ———————————————————————————— SUGGESTED STACK (Open to Your Recommendations) We've scoped this around React Native/Expo, Next.js, and Supabase/PostgreSQL, with Twilio for SMS login and workflow automation tooling for scheduled jobs. If you have strong reasons to use different tools, we're happy to hear them. ———————————————————————————— IDEAL CANDIDATE • Has shipped production mobile apps to both app stores • Solid backend/database experience, especially with role-based security • Experience with offline-first mobile architecture • Communicates well — we want weekly progress updates and working demos, not surprises at the end