Player-Coach Technical Range

Most technical portfolios list features shipped. This one is organized around judgment calls instead — the moments where a nontrivial trade-off got made, and why.

It covers two healthcare products I built and largely launched solo (anonymized here as Project A, a claims-appeals SaaS platform, and Project B, a payer-rate data platform), indexed across eight categories: product management, software architecture, development craft, DevOps/AWS, AI/LLM engineering, data engineering at scale, security, and incident response. Each category maps onto a capability chart — from hands-on execution to strategic judgment, and from build-time work to running a live system — and every claim traces back to a specific decision, not a generality.

It also adapts to who’s reading it: an employer, a consulting client, or an investor each get a different framing on the same underlying evidence.