I grew up in Sangli, Maharashtra, studied computer applications there, and moved to Bengaluru for work. I started out as a web developer — shipping school and retail products at AppiVa, then learning platforms and an e-commerce PWA at DigVerve — and grew into full-stack work at Edulyx, where I built an ed-tech platform and its React Native app.

In 2019 I joined Styldod, the chapter that's shaped me most. I came in as a software engineer and grew, step by step, through lead and architect roles into Head of Engineering — living every stage of startup growth from the inside. Along the way I helped scale the company from zero revenue to roughly $2.5M ARR, serving 2.1M+ users across 185+ countries.

I didn't get there by specializing narrowly. I kept widening my scope — building products from scratch, designing scalable architectures, hiring, and working directly with founders. Today I lead engineering across AI, web, mobile, backend, infrastructure, and operations, with a lot of recent work in AI: large-scale image pipelines and generative-AI products like ReimagineHome.

The throughline hasn't changed — turn an ambitious idea into a production-grade system that serves real customers. I care about the unglamorous parts that make products last: reliability, cost, clear ownership, and systems someone can actually operate at 2 a.m. And I still like being close to the work, because that's where the real learning lives.

Principles

How I lead and build

A few convictions that show up in how I work and how I run a team.

Ownership and accountability

I take responsibility for outcomes, not just tasks. The teams I build do the same — owning their work end to end, including the parts that are hard.

Lead by example, not authority

Titles don't earn trust; doing the work does. I'd rather show what good looks like than mandate it from a distance.

Stay hands-on

I lead while staying close to the technology. Being near the real problems keeps my judgment sharp and my decisions grounded.

Build for scale and clarity

Systems should be understandable as they grow. I care about where boundaries are drawn and how things behave under real load.

Calm in the chaos

Steady beats frantic. When things break — and at a growing startup they do — calm, clear thinking is what brings order back and keeps the team moving.

Keep learning

I taught myself Flutter to ship mobile apps and moved into AI as the work demanded it. Curiosity is how I've grown across the whole stack.

Technologies

What I work with

The stack I've used to build and ship across web, mobile, cloud, and AI. I pick tools to fit the problem and go deep where it counts.

Languages

  • JavaScript
  • TypeScript
  • Python
  • Dart

Frontend

  • React
  • Next.js
  • Redux
  • React Query
  • Material UI
  • Tailwind CSS

Mobile

  • Flutter (iOS & Android)

Backend & APIs

  • Node.js
  • Express
  • REST
  • GraphQL (Apollo)
  • WebSockets

Databases

  • MongoDB Atlas
  • PostgreSQL
  • DynamoDB

Cloud & Infrastructure

  • AWS Lambda
  • SQS / SNS
  • S3 / CloudFront
  • API Gateway (REST + WS)
  • SageMaker
  • Docker / ECR

Payments & Identity

  • Stripe
  • Paddle
  • PayPal
  • AWS Cognito
  • Firebase Auth

AI & Computer Vision

  • OpenAI
  • Gemini
  • Claude
  • Stability AI
  • Replicate
  • Vertex AI
  • ResNet / ViT / YOLOv7

Architecture & Practice

  • System Design
  • Distributed Systems
  • Event-driven Architecture
  • Multi-tenant SaaS
  • Technical Leadership
What I'm looking for

Where I do my best work

I'm drawn to problems where technology, product, and business impact meet — especially in AI and at the scaling stage.

  • AI products
  • Scalable & distributed systems
  • Platform engineering
  • Product engineering
  • Team building & leadership
  • Early-stage growth
Working style

How I work with teams

  • Highly hands-on — I stay close to the code and the architecture while helping the team execute.
  • Lead by example and give engineers real ownership of meaningful problems.
  • Hire deliberately and build teams that can operate without me in the room.
  • Work directly with founders and product to keep engineering tied to business impact.
  • Bias toward shipping — learn what's needed, build it, and improve from real usage.
Outside work

Away from the keyboard

When I'm not building, I'm usually still curious about something — exploring a new place, a new cuisine, or a new idea.

  • Traveling
  • Food & cooking
  • Music
  • TV series
  • Formula 1
  • Reading
  • Side projects

Languages English · Hindi · Marathi · Sanskrit

Want the condensed version, or want to talk?