React Developer (Part-Time, Long-Term)

Summary We're looking for an experienced React developer to join our growing team on a part-time basis with the potential for a long-term engagement. This is not a short gig — we want someone who wants to grow with the project, contribute meaningfully, and operate like a real team member. We're building a spatial productivity platform. The front-end is React/TypeScript with significant business logic — state management, API layers, Supabase integration, and real-time data flows. The 3D environment runs in Unity WebGL and React communicates with it through a JavaScript bridge. You don't need to be a Unity developer, but you need to be comfortable building the React side of that communication. If you're looking for something to pick up and drop whenever it suits you, this isn't for you. We're looking for someone consistent, communicative, and genuinely invested in what we're building. MUST HAVE NO AGENCIES - do not apply if you are an agency. Individual talent only. Can work within 9am–5pm EST, Monday–Friday (hard requirement — do not apply if you cannot commit to this) 10–15 hours/week availability, consistent week over week Extensive hands-on React experience — hooks, Context API, custom hook architecture, component design patterns Strong API integration experience — RESTful APIs, async patterns, error handling at scale Real Supabase experience — auth, RLS policies, real-time subscriptions, edge functions Experience building React apps with heavy business logic (not just UI rendering) Experience with an app where React communicated with Unity (via a JS bridge or similar) — you don't need to have built the Unity side, but you need to have built the React side of that conversation NICE TO HAVE TypeScript (our codebase is React/TypeScript) Netlify deployments Familiarity with AWS Claude/Anthropic API or other LLM API integration Familiarity with react-unity-webgl or Unity WebGL embedding STACK React, TypeScript, JavaScript ES6 Supabase (auth, database, edge functions, RLS) Claude API, Netlify, AWS Unity WebGL (you'll be on the React side, not the Unity side) HOW WE WORK Individuals only. No agencies. No delegation to a team member. We're building a team culture — you'll collaborate daily with our Unity developer, work closely with our Technical PM, and have visibility into product direction. You'll be expected to attend planning sessions, ask questions before starting work, and flag blockers early. Hourly contract. We don't do manual time tracking. We ask for a ballpark estimate before any Jira ticket starts — we know things change, we just need a starting point. Fast response expected during your overlap hours. If something is blocked, we need to know immediately — not at the end of the day. WHAT THE WORK LOOKS LIKE Building and maintaining React components with complex state and business logic Integrating and maintaining Supabase data flows (real-time, auth, RLS-aware queries) Working on the React-side of the Unity bridge — passing messages, handling events, managing load state Collaborating with our Unity developer to design clean communication contracts between the two layers Helping improve code architecture as the product scales LONG-TERM POTENTIAL We're not looking for someone for 4 weeks. If you integrate well with the team and the work quality is there, we want this to grow into a sustained engagement. We invest in the people we work with. TO APPLY Keep it short. We don't read long proposals. Your availability in EST clock hours (e.g. "I'm online 10am–3pm EST weekdays") — not "I'm flexible" or "I can overlap." Specific hours. One example of a React project with heavy business logic — link or description. What was complex about it beyond the UI? Explain the System Design. Your Supabase experience — briefly, what have you built with it? (auth, RLS, edge functions, real-time — which of these have you actually shipped?) Answer this in your proposal: Have you built the React side of a Unity-communicating app? If yes, how did the two layers exchange data — what was the mechanism, and what was the trickiest part? Your hourly rate. Applications that skip question 4 or give a vague answer will not move forward.