About
Engineer first. Designer by necessity.
I build digital
products end to end.
- Experience
- 14+ years
- Platforms
- Web · Mobile · Desktop
- Scope
- Idea → Production
- Based in
- New York
For fourteen years I’ve worked across the full surface of software: the interfaces people use every day, the applications behind them, the APIs and data models underneath, and the infrastructure the whole thing runs on. Websites, web applications, SaaS platforms, mobile apps, desktop software, CMS platforms, internal business systems, AI integrations and automation.
The work I’m best at sits where engineering meets product design — building things that are technically sound and still feel obvious to use. Staying close to both sides, instead of specialising into one, is a deliberate choice; it’s where I think the interesting problems are.
I’m equally comfortable past the codebase. Provisioning a Linux server, configuring Nginx, moving DNS, issuing certificates, getting email to actually deliver — that’s part of shipping, and I’d rather own it than hand it off and hope.
I also pay attention to what happens after launch: conversion, analytics, marketing, the operational reality of a product that has to earn its keep. Software isn’t finished when it works. It’s finished when it does the job someone needed done.
14+ years building
digital products.
01 — Web
Marketing sites, editorial experiences and conversion-driven frontends.
Fourteen years of production websites, from single-page brand statements to multi-service architectures sitting under paid search.
Responsive systems, technical SEO, Core Web Vitals, analytics and the conversion structure underneath.
Five things I’m
fairly certain about.
01
Build for humans
Good software feels obvious. If the interface needs explaining, the problem is upstream of the documentation.
02
Performance is UX
Speed is not an optimization pass at the end. How fast something responds is part of how it feels to use, and users judge it long before they judge the design.
03
Design and engineering are one job
Intent gets lost at handoffs. Carrying a product from concept through implementation keeps the finished thing recognizable as the thing that was designed.
04
Ship it
A product on localhost is worth nothing. Getting to production — servers, domains, certificates, all of it — is part of the work, not a step someone else handles.
05
Solve the business problem
Technology is a means. The interesting question is never which framework, it's what outcome the thing is supposed to produce.
Think we'd work well together?
I take on a small number of projects at a time, which means I can be genuinely involved in each one. Tell me what you're building.