I'm a Technical Product Manager with 5+ years bridging business and technology teams to ship AI-first, data-driven platforms. My work spans LLM integration, RAG pipelines, agentic workflows, and API-driven integrations — always with a prototype-and-iterate mindset. I'm currently filing a patent with my CTO for a 5-layer multi-agent AI platform, and I hold a Masters in Engineering Management from Cornell (3.88 GPA, full merit scholarship) and am pursuing a Doctor of Business Administration at Westcliff University.
Where I'm strongest as an AI product leader — self-assessed and backed by shipped outcomes.
From multi-agent AI platforms at Likewize to product strategy and 0→1 healthcare. Click any to explore the trade-offs and outcomes.
A framework I use before shipping AI features. Try it.
The same five-step process I run from 0→1 — designed for regulated, high-stakes domains where being wrong is expensive. Every step produces a concrete artifact.
Before a single prompt, I define what success looks like and — more importantly — what a wrong answer costs. In insurance and healthcare, a hallucination is a compliance event, not a UX bug. The risk surface defines the spec.
I build a working slice fast with Lovable, v0, and Claude tooling, then put it in front of real users and execs within days. A live demo surfaces the real requirements that no discovery doc ever will.
I write the evaluation rubric — accuracy, safety, latency, explainability, recovery — before choosing an approach. Weighted scorecards turn 'feels good' into a defensible ship/no-ship decision.
Agents do the heavy lifting; people make the call with a visible audit trail. This is what flips adoption from 'interesting' to 'can't work without it' in regulated environments.
Every AI feature ships with telemetry: confidence distributions, deflection, escalation, drift. The roadmap is driven by what production tells me, not what the backlog assumes.
Inbound HubSpot form submissions trigger an n8n workflow: MCP enriches company data via LinkedIn + Clearbit, Claude scores lead quality (1-100) with reasoning, auto-routes hot leads to a Slack channel, and logs to Airtable.
Legal uploads PDFs to Google Drive. n8n detects new files, MCP extracts text via Document AI, Claude identifies key clauses (termination, liability, auto-renewal), compares against standard terms, and pushes a risk-scored summary to Notion.
Pulls NPS from Delighted, tickets from Zendesk, reviews from App Store Connect via MCP. Claude runs sentiment analysis, clusters themes via embeddings, and autopublishes a weekly product insight report to Confluence.
Monitors 8 competitor sites + Product Hunt + Crunchbase via MCP scraping. A diff engine detects pricing changes and new features. Claude writes a daily brief against our roadmap positioning, delivered 7am to Slack.
Most PMs ask 'what should the AI do?' I ask 'what happens when it's wrong?' In regulated domains like insurance and healthcare, wrong answers are compliance violations, not bad UX. Designing guardrails IS the product work.
In regulated environments, adoption flips the moment a human stays in control. My Traceability agent only took off once I added the sign-off loop. Agents do the heavy lifting; people make the call with a visible audit trail.
A working demo beats any deck. I use Lovable and Claude tooling to turn abstract LLM orchestration into interactive prototypes — which is how I've secured executive sponsorship for AI-first initiatives.

Open to AI Product Manager roles at ambitious companies.
nj222@cornell.edu · +1 (607) 595-8222 · Irving, TX