Case studies

Real problems. Documented decisions.

Every case follows the same spine: challenge, constraints, architecture, trade-offs, and lessons. The reasoning is the work.

On a platform handling sensitive healthcare data, protecting it wasn't a feature — it was the architecture.

Calling an AI API is easy. Making it a reliable feature of a product at scale is the actual engineering.

The slow screen usually isn't a frontend problem. Being full-stack is what lets you fix it where it actually lives.

A full loan-lifecycle dashboard for a bank, built from zero — and what regulated software taught me about 'production-ready'.

Five and a half years at one company, from writing features to making sure projects succeed technically — while staying hands-on.