Building this portfolio like a product.

A résumé can show what shipped. It doesn't show how I think nearly as well: what I noticed, which trade-offs mattered, how I worked with technical constraints, and why one path was chosen over another.

I wanted a portfolio that could do both jobs: let a recruiter understand the signal quickly, while giving a product leader or engineer enough depth to see the reasoning underneath the outcome.

The constraint was that the site also had to stay coherent as the content grew. Seven case studies could not become seven unrelated microsites.

The primary audience was hiring teams: recruiters, product leaders and engineers evaluating whether the work was credible and whether I could operate at senior scope.

That led to a simple design rule: every case needed a fast path through problem → decision → trade-off → outcome, with enough evidence underneath for someone who wanted to keep reading.

The biggest risk with fast generation is accepting something because it looks finished. I treated every output as a draft until it survived the same questions I would ask of a product artifact.

The useful shift for me was not “I can generate a website.” It was realizing how much closer a product person can now stay to the thing being built. That still means respecting the expertise of designers and engineers and being clear about where the tool ends and accountability begins.