Frontend engineer
for product teams that need shipping power.

I build React and Next.js frontends that can grow without turning into one-off screens. Venlyn, gym operations, trainer SaaS, and CRM dashboards all needed reusable components, predictable state boundaries, and layouts that stay clear as features multiply.

• →Reusable component libraries and design systems
• →Modular architecture for complex UIs
• →Clear state boundaries and data flow

My frontend work is product design in code. Forms, filters, empty states, transitions, and mobile layouts should make the next action obvious, especially in dashboards, scheduling flows, CRM screens, and operational tools used during busy workdays.

• →Mobile-first, conversion-focused layouts
• →Purposeful micro-interactions and transitions
• →Clear visual hierarchy and spacing systems

I structure frontend applications so the data path is readable. My experience includes REST API integration, Supabase-backed real-time data, scheduling logic, dashboard filters, and a clear split between UI state and server state.

• →API-driven UI architecture
• →Async state handling and caching strategies
• →Separation of UI state and server state

I pay attention to the parts users feel immediately: load speed, layout stability, responsive behavior, and smooth interaction. I also care about the parts teams feel later: readable code, debuggable state, and components that survive changing requirements.

• →Optimized LCP, CLS, and interaction latency
• →Code splitting and lazy loading strategies
• →Render optimization and memoization

I implement AI when it has a specific job: answer repetitive support, qualify calls, route messages, draft structured outputs, or update a CRM. My work connects LLMs, Vapi voice agents, n8n, webhooks, and product UI so automation is visible, controlled, and useful.

• →LLM integration for support, intake, and decision support
• →AI voice agents for calls, scheduling, and CRM updates
• →Structured outputs and model routing for reliable workflows

Automation is the layer behind the product work. I use n8n, webhooks, Git, and practical developer tooling to connect systems, reduce manual coordination, and make common workflows easier to repeat and maintain.

• →n8n workflows for onboarding, messaging, and scheduling
• →Webhook-based integrations between SaaS tools and CRMs
• →Version-controlled development workflows with Git

I am frontend-first, but I understand the systems behind the interface. My experience spans relational data, REST APIs, Supabase, webhooks, and server-side business logic, which helps me build UI that matches the real shape of the data.

• →API design and integration
• →Relational data modeling
• →Server-side business logic

I work with the platforms that support frontend delivery: Vercel, Supabase, Docker, CI/CD, and database-backed product workflows. The goal is simple: ship reliably from local development to production.

• →Containerization and environment parity
• →Automated deployments
• →Cloud-based backend services

I combine technical execution with business and product awareness. My operations background helps me ask better questions, understand workflow pressure, and communicate clearly with stakeholders from the first brief through production fixes.

• →Cross-functional collaboration
• →Product and business alignment
• →Leadership and coordination