Public source
Doximity Dialer launched as a physician calling product.
Public launch evidence for the product context.
About
I make sure that when a system is wrong, someone can trace why, challenge it, and fix it.
Seeking VP Product / CPO / Founding Product Lead roles in high-stakes healthtech and AI infrastructure.
Quick version · 30 seconds
Clinical workflow Verified identity Care navigation Accountable routing Expert review AI decision infrastructure
At Georgia Tech, I studied RNA folding dynamics and sRNA-mRNA interactions in Roger Wartell's lab, modeling free energy barriers that determine whether reactions proceed or stall. I co-authored an ACS Symposium Series book chapter on sRNA-mRNA interactions at 19, and spent a summer on thoracic surgery outcomes at Memorial Sloan Kettering. Both taught the same habit: find the barrier that decides whether a process completes or stalls.
At Epic, I configured EHR workflows where a single misrouted alert could bury a critical lab result. As an Implementation Engineer, I configured workflows and rollout quality metrics to reduce alert fatigue without compromising safety. The workflow around the clinician was usually the constraint, not the clinician. That left an obvious next question: when a system tells a clinician something, why would they believe it?
Patients don't answer calls from unknown numbers. That single observation drove Doximity Dialer. As product lead, I built a HIPAA-conscious calling tool that masked personal numbers, preserved carrier identity rules, and routed missed calls through verified fallback paths. iOS app reviews climbed from 3.7 to 4.8 stars during mobile product work. Doximity later reported that Dialer enabled 110M+ video and audio visits from 300K+ active clinicians. Trust turned out to be a product decision: what a system can prove about itself determines whether anyone acts on it.
At CancerCompass / CTCA Marketplace, I led digital products for an oncology navigation platform serving 30MM annual visitors (CTCA was later acquired by City of Hope). Internal analytics showed product changes cut bounce rate by 25% and lifted chat conversions 267%. Translating clinical protocol into steps a frightened family can act on, at that scale, makes the guidance itself the risk surface — and guidance is only as good as whoever owns the next step.
At Transcarent, I directed product across value-based specialty-care and navigation programs (Surgery, Urgent Care, Behavioral Health, Oncology Care), building a unified member record, clinician-led routing rules, escalation paths, and care-plan completion dashboards. Routing output without a workflow owner is just a suggestion; making ownership visible is what reduced exceptions. Which surfaced the harder case — what to do when the recommendation is genuinely contestable.
As co-founder and CEO of Andwise, I raised $240K in initial funding, grew to 1,200+ physician users and a 700-member community, and convened a physician medical advisory board that grew to 50+ physicians. Sensitive recommendations needed accountable sign-off and inspectable provenance, not a confidence score. Encoding expert authority into a workflow is the same problem as governing an automated decision, one layer down.
Across molecular biology, EHR configuration, clinician tools, oncology navigation, and financial support, one pattern held: high-stakes decisions become opaque once embedded in software. The higher the stakes, the harder it got to trace, question, or undo them. As U.S. healthcare shifts clinical judgment to algorithms, responsibility must move alongside it. That is what I build now — traceability, challenge, and correction as explicit infrastructure rather than institutional goodwill. I write about AI governance at The Crumple Zone and publish open standards at Ethotechnics to ensure automated decisions remain auditable in production.
Every claim on this page is classified by evidence level. Public sources, self-reported metrics, and anonymized outcomes are separated. This is the same traceability discipline I apply to AI decisions in production.
Public source
Public launch evidence for the product context.
Public source
Company-reported scale after my early product work on Dialer.
Public source
Public interoperability trail for the Dialer ecosystem.
Mixed
Acquisition is public; traffic and conversion deltas are self-reported internal analytics.
Public source + anonymized outcomes
Public link establishes program context; routing and completion outcomes are anonymized.
Public source
Public founder and company context.
Public source + self-reported count
The public board page confirms the board and names its members; it states no total. The 50+ figure is founder-reported and is labelled separately from the board's existence.
Self-reported
Kept separate from public founder and advisory-board proof.
Public source
Publication-context evidence for early systems research background.
Current public practice
Methodology and research positioning, distinct from shipped-product proof.
Method described, results pending
The scoring method is specified and in use. A resolved forecast register will be published once scores are inspectable.
Co-authored a book chapter in the ACS Symposium Series on sRNA-mRNA interactions and Hfq.
Care as default
If a workflow requires someone to remember a step at 3AM, the step is the problem, not the person.
Evidence over lore
Watch how operators actually work. Instrument what matters, even when it's hard to measure.
Trustworthy automation
Every automated decision needs a visible override path. People can see who can pause it, what changed, and what to do if it is wrong.
Georgia Institute of Technology
Human-centered clinical systems, pairing biomechanics and design research.
NYU Stern School of Business
Finance and technology focus, paired with product leadership in regulated markets.