Software Engineer — systems, interfaces, the occasional 3AM incident
I build products where engineering, interaction and visual design meet.
I build products that hold up under real traffic — from the database up to the pixel. Ten years turning ambitious roadmaps into software that ships, and occasionally into technical debt I fully intend to pay off.
SCROLL TO EXPLOREInterfaces and products designed to scale beyond the prototype.
APIs, databases, authentication, synchronization and reliable infrastructure.
Thoughtful UX, motion and realtime interfaces that make complex systems feel simple.
Turning ideas into production-ready software from architecture to deployment.
Rebuilt the collaboration layer for a 40-person design tool from a polling API to a CRDT-backed WebSocket engine. Cut sync latency from ~800ms to under 60ms and made concurrent editing actually pleasant.
Led the migration of a legacy reporting stack to a streaming pipeline, replacing 6-hour nightly batch jobs with sub-minute dashboards, without a single day of downtime for finance.
Designed and shipped an internal component library adopted across 12 product teams, cutting new-feature build time by roughly a third and finally killing four competing button styles.
Less about frameworks, more about how a system of people and code stays sane as it grows. A rough version of the loop I run on most projects:
Usually it isn't the one in the ticket. I dig until I find the thing actually limiting the system.
A working, unstyled thing beats a polished mockup for deciding if an idea survives contact with data.
No performance work starts without a number to move. Otherwise it's just vibes with extra steps.
The next person touching this code is probably me, in six months, having forgotten everything.
Currently open to new roles & select contract work
Have a project in mind, a difficult systems problem to solve, or an engineering role open? Send a message or email directly.
Leave a note here and I'll get back to you within a couple of days.