React Developer Based in California.

React rewards developers who understand both how it works and why it works that way. I've been writing React professionally since the class-component era — through the hooks rewrite, the rise of server components, and the Next.js App Router. That history matters because most React performance problems aren't bugs; they're misunderstandings of the render model.

At Skywest, where I'm CTO, I architect React applications that handle real production traffic: data-heavy admin dashboards, multi-role SaaS interfaces, and AI-powered tools with streaming responses. I work in React with TypeScript, Next.js (App Router and Pages), and the surrounding ecosystem — TanStack Query, Zustand, React Hook Form, Radix, Tailwind. I also integrate React frontends with Django, Node.js, and FastAPI backends.

What I bring as a React developer

• Component architecture that scales. Composition over inheritance, sensible boundaries, predictable APIs.
• State management that fits the problem. Local state by default, server state via TanStack Query, global state only when it's actually global.
• Performance you can measure. Profiling with React DevTools, fixing real re-render problems, code-splitting, lazy loading, and avoiding the easy traps.
• Accessibility built in. Semantic HTML, keyboard support, focus management, ARIA only when it's actually needed.
• Forms that don't suck. React Hook Form + Zod, server-side validation, optimistic updates, error UX.
• Type-safe end to end. TypeScript across the boundary — schema, API, client — so refactors are safe.

The kind of React projects I'm strongest at

Data-dense SaaS dashboards, internal tools, B2B admin panels, AI-powered apps with streaming UIs, and Next.js marketing sites that need to be fast and SEO-friendly. If you've got a React app that feels slow, looks dated, or has component spaghetti — that's exactly the kind of work I'm good at fixing.