I build practical systems and small tools that reduce friction.

About

Calm systems, clear rules, steady progress

I’ve spent most of my career working on the kinds of systems where reliability matters, the work sits behind the scenes, and small mistakes can become big problems. That shaped how I think, I prefer clear inputs, predictable outputs, and tooling that makes work feel calmer.

What I’m optimizing for now

At this point, I’m most interested in roles that feel focused and sustainable. Smaller teams, clearer priorities, and a pace that leaves room for deep work. I’m remote-first, but flexible when the role fits.

I’m not trying to “escape” any industry. I’m choosing the kind of environment and cadence that helps me do my best work. If the right opportunity shows up in finance or another high-compliance space, I’m open to it.

What I’m doing right now

I’m working on Site Engine, a foundation for running multiple sites from one engine. It lets me ship without rebuilding basics each time, and it gives me a place to explore practical AI-assisted workflows, in a way that stays grounded in real constraints.

How I like to work

• Clear rules and clean data shapes

• Small slices, shipped and verified

• Observability and failure modes considered early

• Simple UI, strong backend discipline

If you’re hiring

I’m a strong fit for backend engineering, data-heavy work (SQL, ETL, pipelines), automation, and internal tools. I can’t share past employer code, but I can talk clearly about architecture, tradeoffs, and how to make systems more reliable over time.

If you’re a builder

I keep notes on decisions, mistakes, and what actually worked while building Site Engine and other experiments. No hype, just the process.