Diagnosis → redesign → automation. 15+ years at the intersection of product management, service design, and data — across healthtech, proptech, and public sector digital transformation.
Manual tenant evaluation was the bottleneck killing contract velocity. I redesigned the process around government data APIs and automated scoring — eliminating fraud and friction simultaneously.
The emergency department was drowning in overcrowding. I mapped patient flows from security camera footage, identified systemic coordination failures, and redesigned the service — down to the architectural floor plan.
Healthcare clinics lose revenue to invisible process failures — but can't quantify it. I applied full product discipline: JTBD, PRD, architecture spec, data strategy, and shipped a live product in 4 days using AI as the development lever.
High-ticket dental clinics lose patients mid-treatment to anxiety, not clinical failure. Kira tracks patient emotional state between visits and alerts clinics before someone disappears — built with full PRD, design system, and technical architecture before the first line of code.
I identify what's worth solving, build the case to get it resourced, and design systems that hold up after I leave. That's been true working inside a Fortune 500 proptech platform, redesigning a public hospital emergency department, and advising Chile's Ministry of Health on national surgical patient flows.
My core loop: diagnose what's broken → redesign how it works → automate so it doesn't break again.
Based in Santiago, Chile (GMT−4). Available for remote and hybrid roles globally. Fluent in English and Spanish.
I lead with the desired outcome, not a feature list. Weekly user contact — interviews, observation, assumption tests — feeds directly into prioritization before a spec is written.
I structure what I learn from users into a hierarchy of opportunities before exploring solutions. This prevents solution bias and ensures I'm solving the right problem at the right level.
I define the metric and its guardrail before writing any spec. If I can't name a counter-metric, I haven't thought hard enough. Shipping is when the real signal starts — not when it ends.
I use AI across the full PM workflow — not just for writing. Discovery synthesis, assumption pressure-testing, rapid prototyping with Claude Code, spec drafting. The Revenue Leak Calculator went from problem to deployed product in 4 days using this stack.
The key distinction: AI is the development lever. JTBD, strategic framing, architecture decisions, data quality design — those are product judgment calls. Claude executes them.
Particularly in healthtech, enterprise SaaS, and AI-native product development. Remote-first, global.