About

I help teams make complex technical systems easier to understand and safer to ship.

I am an AI systems and commerce engineer with a background in enterprise e-commerce, technical discovery, and delivery leadership. My work is strongest where ambiguous business goals need a clear technical route.

Profile

Practical engineering, direct communication, and a bias toward working systems.

I have spent more than fifteen years building and supporting digital commerce systems across agencies, product teams, and enterprise clients.

AI is now a major part of that work, but I treat it as part of a system rather than a magic layer: inputs, outputs, people, risks, review points, and operational reality all matter.

15+
Years Experience
100+
Projects Delivered
6+
Commerce Platforms
20+
Industries Served

Interests

What shapes the work.

The useful thread is systems thinking: how things are framed, how feedback appears, and how people make decisions with imperfect information.

I01 AI Systems

I am interested in how agents, retrieval, evaluation, and human review can make knowledge work more reliable.

I02 Photography

Photography keeps me attentive to framing, constraint, and the way small details change how something is understood.

I03 Games

Good games are systems with feedback, trade-offs, and visible rules. That way of thinking shows up in my engineering work.

I04 Reading

I read across technology, business, and speculative fiction to keep my thinking broad without losing practical judgement.

Values

V01

Clarity

Complexity is acceptable. Confusion is not. I prefer diagrams, plain language, and named assumptions.

V02

Delivery

Architecture needs a route to production, a way to be tested, and an owner after launch.

V03

Judgement

AI work needs restraint. The useful question is where the system should help, where it should stop, and how people verify it.

Notes

  • Built my first website young enough that table layouts still felt normal
  • I enjoy explaining technical trade-offs to non-technical teams
  • I care about the boring work: naming, interfaces, logs, handovers, and supportability
  • I prefer useful prototypes over speculative slideware