I like working at the intersection of engineering, product, and design.

My favorite problems usually involve:

• turning messy workflows into simple products
• designing systems that can grow without becoming fragile
• building polished web and mobile experiences
• creating reusable component and design systems
• using AI as part of the product and the development workflow
• shipping quickly without treating the first version as the final version

Operating system for coaches and fitness studios.

Sessions, clients, packages, subscriptions, payments, trainer operations, analytics, and business workflows in one connected product.

React TypeScript Node.js PostgreSQL React Native Expo Stripe

A social fitness product built around progress, motivation, and community.

Working across product strategy, mobile architecture, social mechanics, achievements, journeys, and the systems behind a polished consumer experience.

React Native Expo TypeScript PostgreSQL

A product for discovering, organizing, and exploring movies and television.

Understand the problem
        ↓
Model the system
        ↓
Design the smallest useful version
        ↓
Build the foundations carefully
        ↓
Ship
        ↓
Observe real usage
        ↓
Iterate

I care a lot about the part between "it works" and "this feels good to use."

Frontend

React · Next.js · TypeScript · Vite · TanStack Query · Tailwind CSS

Mobile

React Native · Expo

Backend

Node.js · NestJS · Express · PostgreSQL · Firebase

Product infrastructure

Stripe · PostHog · Google Cloud · Vercel · Sanity

Quality

Vitest · Jest · Cypress · Storybook

AI-assisted development

ChatGPT · Codex · Claude · Gemini · MCP

Build systems, not piles of features.

A few things I try to optimize for:

• Clarity over cleverness
• Strong foundations over premature abstraction
• Product thinking inside engineering decisions
• Small feedback loops
• Interfaces that explain themselves
• Learning from shipped software instead of chasing perfect first versions

My background started in mechanical engineering and research before moving fully into software.

That still shapes how I think: understand the system, identify constraints, model the interactions, test assumptions, and then build.

These days I spend most of my time somewhere between:

engineering × product × design × startups