Aadarsh Srivastava
I build clear product systems around how people actually work.
Across enterprise software, startup operations, and consumer travel, I turn messy workflows into useful interfaces and durable systems.
What breaks
Software fragments when features become the plan and the work around them disappears from view.
Enterprise coordination, startup operations, and consumer travel at scale.
Advisor360 is a private production system built around a working advisory business.
Start with the workflow, keep useful complexity, then choose the system shape.
What shaped me
Three environments.One evolving judgment.
Context over chronology
Different scales changed what I notice: shared systems must survive coordination, operational products must respect the work around the screen, and consumer journeys must stay clear under scale.
MakeMyTrip
1 yr 7 mo- Senior Software Engineer IIJan 2025 to Present
Consumer scale across web, mobile, and discovery journeys.
Zolo
2 yr 6 mo- Senior Software Engineer IIApr 2024 to Dec 2024
- Senior Software Engineer IApr 2023 to Mar 2024
- Software Development Engineer IIJul 2022 to Mar 2023
Customer proximity, operations, and commercial consequences.
PwC India
1 yr 10 mo- Associate (Full Stack Developer)Sep 2020 to Jun 2022
Enterprise coordination and durable shared systems.
Those environments changed what I build on my own: products that begin with a specific person and the work already happening around them.
Selected work / 03
Work shaped by real constraints
Products that began with a person, a workflow, or a system I wanted to understand properly.
Built for Independent financial advisors
Advisor360
Before
Commission data, client context, goals, and research were split across spreadsheets and manual reconciliation.
Now
Commissions, clients, goals, research, and business signals in one operating view.
System decision
Separate the advisor experience from a reusable domain-first platform, FinHQ.
Private, in production
Inspect the case note
For Import-export operators and customers
Syntara / TradeFlow
Before
Product data, enquiries, supplier context, and trade documents moved through scattered files, messages, and memory.
Bring catalogues, enquiries, relationships, and trade documents into one system.
Decision
Separate the public catalogue from the operational trade data model.
For Frontend and backend teams
Specimen
Before
Teams could share example payloads, but the payload alone did not explain required, nullable, unstable, or meaningful fields.
Turn example payloads into shared, annotated contracts.
Decision
Keep contract inference separate from editing and persistence.
Working notes
Notes from building
Usually a product hunch, engineering discomfort, or mental model I wanted to make clearer.
Optimizing React Re-renders
A practical look at when re-renders actually matter, and when we reach for memoization before understanding the real bottleneck.
From Junior to Senior Engineer
What actually changed in my thinking, ownership, and judgment as I moved from execution to product-aware engineering.
Server-Driven UI Done Right
Why most server-driven UI conversations miss the real problem, and what it takes to keep the frontend opinionated and scalable.
React to React Native: A Mental Model Shift
The mindset shift that matters more than APIs when you move from web habits to native constraints.
Materials
Tools, grouped by purpose
A compact view of the tools behind the work shown here.
Interfaces
TypeScript
React
TanStack Start
React NativeProduct systems
Node.js
FastAPI
Express
Convex
SupabaseData and AI
Python
ChatGPT
ClaudeShipping and operations
Vite
Bun
Vercel
Git