<aside> 🧠
Data Scientist at Optum. My background sits between engineering, data science, and product, so I usually end up working on problems that require both building the system and figuring out what should be built in the first place. I enjoy working on AI features that need to run in production, not just in notebooks.
</aside>
Currently
Data Scientist at Optum, working on healthcare AI systems, agents, and ML workflows.
Previously
Associate Product Manager at Unacademy and Assistant Product Manager at Scenes.
Builder side
I build AI agents, health-tech concepts, product prototypes, and dev-facing experiments.
<aside> ✉️
</aside>
<aside> 🔗
</aside>
<aside> 💻
</aside>
<aside> 🚀
Enterprise AI system that moved from POC toward a production-facing workflow.
</aside>
Healthcare contract processing is slow, document-heavy, and full of edge cases. I worked on a LangGraph + Google ADK multi-agent system that could process contracts, reason through steps, and reduce manual effort.
My role
Product thinking, architecture, AI workflow design, implementation, and infra migration support.
What I worked on
Impact
The system grew from POC into a workflow strong enough to replace a 40+ member manual process, with expansion planned across business units.
<aside> 🏆
Hackathon-winning claims assistant headed toward production consideration.
</aside>
Built a conversational claims agent to help users and teams navigate claim-related questions and reduce manual resolution effort.
My role
Prototype owner, AI workflow designer, product builder.
What I worked on
Impact
Won an internal hackathon and moved toward production exploration.
What this proves
I can quickly turn an ambiguous business problem into a usable AI prototype.
<aside> 🌐
Multilingual healthcare chatbot using retrieval augmented generation.
</aside>
This project focused on answering prescription and healthcare-related queries with grounded context instead of generic LLM replies.
What I worked on
Impact
Won an internal hackathon around claims and healthcare AI.
What this proves
I understand that healthcare AI is not just chat. It needs context, caution, and reliability.
<aside> 📉
Agentic automation that reduced insurance claims ticket turnaround by 33%.
</aside>
Built an automation layer using CrewAI and ServiceNow MCP to reduce repetitive manual work in claims ticket workflows.
What I worked on
What this proves
I can connect agents to real enterprise tools and make them useful beyond chat.
These are older product pieces. They are not the main thing anymore, but they show the foundation: market research, product thinking, monetization, UX, and strategy.