A chemist choosing a synthesis route, a researcher working through a hundred papers, a care coordinator documenting a visit: none of them can be handed a simpler version of their job. What they can be handed is an interface that shows the right thing at the right moment, and is honest about what the system is doing underneath.
Some days that means…
reading reaction schemes with chemists
sitting in on client calls
co-writing PRDs with the CEO
building working front-ends in Cursor
prototyping the design system in code
untangling legacy healthcare software
testing whether researchers trust a citation
reading reaction schemes with chemists
sitting in on client calls
co-writing PRDs with the CEO
building working front-ends in Cursor
prototyping the design system in code
untangling legacy healthcare software
testing whether researchers trust a citation
pull me up ↑
Harshini
untangle the mess
sort what matters
design for it
How I work
Figure out what's actually going on, find the distinctions that matter, and design around those rather than around the org chart or the database. It usually means writing the spec before drawing anything.
Background
I started as a software engineer at Amazon and studied CS at Cornell Tech, so I design with the data model in view. Since then I've been the founding or lead designer at three companies: DigiChem (agentic chemistry), Aristto (AI research), and eVero (healthcare software for disability service providers).
Best fit
Engineers who want to show the machinery
Founders who need a technical product to make sense to buyers
Domains I start out knowing nothing about
Looking for: founding or early product design roles at AI, deeptech, and technical B2B teams.
