Skip to content
01

Turning ideas into reliable interfaces

I’m a frontend engineer working across the React ecosystem. In the last years, most of my work has been with Next.js, TypeScript, and teams that need reliable interfaces shaped from early ideas into production code.

My work usually starts before the final component: clarifying behavior, aligning frontend and backend contracts, translating design intent into reusable components, and keeping implementation decisions understandable for the people who maintain them.

02

Project experience

A compact view of the roles and scope behind the selected work.

  1. 01 / 03August 2019-Present

    LaneTalk

    Frontend since Aug 2019, lead frontend responsibility since 2023.

    LaneTalk connects bowling centers, score data, leagues, tournaments, ticketing, app-adjacent flows, and public live scoring.

  2. 02 / 032017-Present (maintainer)

    Revolico

    High-traffic classifieds marketplace.

    Revolico is a high-traffic classifieds marketplace with search, listing detail, publishing, contact paths, admin tools, and mobile web.

  3. 03 / 032019-2021

    OpsTalent

    Lead frontend engineer for B2B frontend delivery, backed with Strapi CMS.

    OpsTalent is a responsive B2B website for an outsourcing and technology company with content-led page sections.

03

From product questions to delivery

I stay close to the work from early product questions through release and the decisions that follow.

  1. Define the problem before the interface

    I clarify who the interface is for, what it needs to make possible, and which parts of the direction are still open. I gather what needs to be done, clarify the intent behind the work, set practical boundaries, and outline a realistic delivery sequence and timeframe.

  2. Make the behavior concrete

    I turn product decisions into behavior the whole team can reason about. I have helped shape payment flows end to end, translating product requirements into backend contracts, frontend states, and clear handoffs between them.

  3. Build quality into the behavior

    I treat accessibility and testing as part of the behavior, not a pass added at the end. Shared patterns have to hold up across real states, screen sizes, public websites, admin tools, and app-adjacent workflows.

  4. Stay with what ships

    I stay involved after release: maintaining the product, responding to what happens in production, and carrying those lessons into the next decision. Delivery is part of the work, not the finish line.

04 · Contact

Let's talk.

Send an email

A product can hide complexity everywhere else. In the interface, it has to make sense. That is why I keep coming back to frontend.