For founders & engineering teams
I'm Dhruv Bajaj, a founder and AI engineer based in India. First hire at SimCare and Artisan, previously Stack AI, and co-founder of UpgradeLLM. I connect language models, backend systems, and the product experiences people use.
Building an AI product in the US or Europe? Explore my work, then let's talk about what you're building.
Talk through your ideaDifferent products, with a shared engineering challenge: making models, data, and integrations work together reliably.
SimCare AI · YC S24
A conversation is a whole system: transcription, streaming language-model inference, speech generation, and the interface on the other side. At SimCare, I work across the FastAPI backend, infrastructure, and product surfaces behind AI client conversations for healthcare training.
How I build real-time AI at SimCareStack AI · YC W23
A visual AI builder needs dependable execution underneath. At Stack AI, I worked on a clearer input-output contract for the node engine, Gmail and Outlook integrations, email-triggered automations, and notifications for workflow events.
Inside the workflow engine at Stack AIArtisan · YC W24
Useful automation starts before the prompt and ends inside someone's workflow. As Artisan's first hire, I built prospect research, enrichment, and personalized outreach pipelines, with batching, parallel execution, and integrations into communication tools.
The outbound systems I built at ArtisanMy own venture / Dec 2024 – Apr 2025
Co-Founder · Enterprise legacy modernization
Co-founded UpgradeLLM and built an application to help enterprise clients migrate legacy systems from older technology stacks to modern ones.
That work is part of why I care about the product behind the technology: who needs it, what problem it solves, and how to make it useful.
Explore my founder and engineering experienceThe way I think about building is practical. Understand the constraints, make trade-offs explicit, and test the assumptions.
Start with the workflow and a useful outcome. A model is one part of a product someone has to understand and trust.
Look at the boundaries: latency between services, data moving through a workflow, and the integrations the product depends on.
Make assumptions visible, test the behavior, and refine the design. Clear interfaces and measurable outcomes make decisions easier.