---
name: Tanay Kishore Shinde
role: Product-minded Frontend Engineer
updated: 2026-06-09
canonical: https://tanayshinde.me/llms/about
---

# About - Tanay Kishore Shinde

## Biography
Product-focused engineer who enjoys turning ambiguous ideas into shipped software.Experienced in building and owning products end-to-end across mobile and web in early-stage startup environments. Interested in product systems, AI tooling, fast iteration, and high-agency engineering.

How something is built determines how it feels. That's the part I'm interested in.

I'm a product-minded frontend engineer who's probably a little too obsessed with how products should feel. I don't build websites or apps. I build experiences - obsessing over how something feels to the person on the other end. Every interaction, every transition, every moment where trust is either built or broken.

Engineering and design aren't separate worlds to me. I like taking rough ideas, messy constraints, and disconnected systems and slowly refining them into something that feels simple, cohesive, and calm.

Products are remembered less for what they do and more for how they feel to use. Most of my work lives somewhere in that space, thinking about rhythm, hierarchy, motion, clarity, and the countless small decisions that shape an experience over time.

Beneath that is a different kind of work. How pieces fit together, where complexity belongs, and how a product grows without becoming harder to work on or harder to use. Building features is one part of the job; designing the structure that supports them is the part I enjoy most.

Most recently: sole frontend engineer at Nirovia - a health-tech startup. Before that, Tech Core at ITSA VIT. Always building something.

### Personal Story
It started in COVID. Stuck at home, I picked up HTML and immediately got obsessed with making things look good. Not in any informed way. Just different fonts, random colors, whatever felt exciting. No contrast theory, no composition, no system. Just a kid who needed things to feel right and didn't yet know why.

That was five years ago. The obsession never went away, it just got sharper. Slowly, I developed the eye. Composition started making sense. I began noticing why certain interfaces felt effortless while others felt frustrating. Spacing, hierarchy, typography, motion, the small details that shape an experience without drawing attention to themselves.

Eventually, code and design stopped feeling like separate things. I became interested in the space between them, where architecture affects experience and technical decisions shape how people interact with a product. The gap closed, and I realized that's exactly where I wanted to be: in the overlap, where both sides of the problem are visible at once.

### Core Qualities
- **the system**: Architecture isn't just structure. It shapes experience.
- **the details**: 2px matters. Easing matters. Rhythm matters.
- **the product**: Every technical decision becomes a user experience decision.
- **the motion**: Transitions should guide, not perform.
- **the restraint**: Complexity should stay behind the interface.