What are we actually trying to achieve? What are the essential parts? What can be simplified, reused or automated? I like finding the structure underneath a problem and understanding the tradeoffs before deciding how to build it.

That thinking continues once the work starts. Building often reveals things that plans and conversations don’t. So I like to get ideas into working form, learn from them, and adjust as the problem becomes clearer.

finding the shape of an unfamiliar system quickly

building is how we discover what the product should become

. And as a product grows, the problem becomes 

I start by understanding the problem, not by reaching for a solution.

Depending on the problem, I might be writing code, designing an architecture, prototyping an interaction, mentoring an engineer, or helping a team find its direction. I’m comfortable leading technically, working independently, or moving between the two.

AI has expanded that practice. I increasingly work with agents as part of the engineering process, giving them context, breaking work into the right problems, reviewing what they produce, and deciding where human judgment matters.

The tools have changed quickly, but the responsibility for understanding the system and making good decisions has not.

I like being close to the work, but being hands-on no longer means doing everything myself.

My background reaches beyond engineering into design, product, teaching and leadership. That experience helps me understand how differently people can describe the same problem, and turn those perspectives into a shared understanding of what we’re trying to build.

My background in art direction and interaction design is particularly present in how I engineer. I care about visual craft, motion and how an interface feels to use, but also about who gets to use it and how. Accessibility isn’t separate from that. It is part of making the thing well.

Some of my best work happens in the space between disciplines.

I’ve worked on products with very different purposes, but I’m most drawn to work where good engineering can have a tangible impact. That might mean reducing the amount of disturbing content people have to review, making workplace training something people actually engage with, or simply building a product that respects the people using it.

That was especially clear to me while working on 

, where engineering, interaction, accessibility and a subject that I cared deeply about all came together.

I care about what happens beyond the screen.

Experience

I’m a Staff Software Engineer with nearly two decades of experience building and shipping products.

Name

Please enter your name.

cy.wtf

Taking products from idea to production, working alongside design and product teams.

Product engineering

Building across frontend and backend, from interfaces to infrastructure.

Full stack development

Designing systems that scale, with tradeoffs made on purpose.

Technical architecture

Building with and around AI: agents, prompts, models and the systems that support them.

AI engineering

Leading teams, working independently, or directing agents, depending on what the work needs.

Technical leadership

Visual craft, interaction, motion and WebGL, with accessibility built in, not bolted on.

Design engineering

Analytics are on for this device. Opting out stops all future measurement immediately and remembers the choice in this browser. Anything already recorded before you object stays as it is.

Client Work

Product engineering

Full stack development

Technical architecture

AI engineering

Technical leadership

Design engineering

Let’s work
together.

cy.wtf

Client Work

Product engineering

Full stack development

Technical architecture

AI engineering

Technical leadership

Design engineering

Let’s worktogether.

Let’s work
together.