I’m a University of Washington Bothell Business Administration graduate working across product, operations, finance, data, and technical systems. My strongest work connects the layers: how information is captured, how assumptions become decisions, how products behave over time, and how the result is validated.
Each case study shows the problem, my role, the system or model I built, the tradeoffs I made, and how I validated the result.
A 15-year international-expansion decision framework connecting country screening, empirical distributions, dependence, financing capacity, rollout strategy, and valuation across 120,000 simulated paths.
A private Android/Desktop application where I define product requirements, analytics behavior, local-first history/sync semantics, testing rules, and AI-assisted development workflows.
Read the full case study →At United Indians, I digitized a recurring reporting process, added validation/correction controls, handled grant operations, and managed an eight-person intern program.
Read the experience case study →I’m most useful when a problem crosses boundaries: operations + data, finance + modeling, product + testing, or customer research + execution.
Start with who does what, where information breaks, what decisions are delayed, and which constraints actually matter.
I try not to become attached to “my side.” Bring the evidence, listen to the competing explanation, and update when better evidence wins.
When information is incomplete, I prefer a solution that remains acceptable across plausible scenarios rather than one optimized for a fragile point forecast.
If something looks wrong, determine whether the cause is data, an assumption, documentation, implementation, or architecture before “fixing” it.
Essays on model governance, product semantics, operations, valuation, strategy, and decision-making—grounded in the projects and experiences that produced them.
Why I built a GitHub-backed multi-worker AI relay, what it actually automates, and where I deliberately kept human review.
Read →The difference between moving a paper form online and designing error controls, correction paths, and a usable reporting process.
Read →How empirical marginals, rank dependence, PSD repair, and validation changed the model from “random inputs” into a coherent joint system.
Read →