Principal Engineer · Hyderabad, India
Dasari Yashwanth Kumar
I build full-stack systems and the architecture behind them — Node.js and React end to end, event-driven pipelines, and the AWS/GCP infrastructure they run on.

At a glance
12+
Years in the field
Full software development lifecycle — greenfield architecture through production.
15
Platforms shipped
Across 2 employers and independent work — satellite IoT, compliance SaaS, equity research, and e-commerce platforms among them.
4
Industries
Healthcare, fintech, e-commerce, and enterprise SaaS.
2
Clouds, one architecture
AWS and GCP, often in the same system — event-driven, serverless where it earns it.
About
I build products end to end — architecture, backend, and the UI on top.
Twelve-plus years across the full software development lifecycle: greenfield architecture, production ownership, and the migrations in between. That work has spanned the full stack — Node.js services, React and Angular front ends, relational and NoSQL data stores, and cloud infrastructure on AWS and GCP — for products in healthcare, fintech, e-commerce, and enterprise SaaS.
I care about clean APIs, maintainable codebases, and systems that are legible to the next engineer. Alongside the hands-on work, I spend time on technical leadership — design reviews, mentoring, and keeping a team aligned on architecture and delivery standards.
More recently, that curiosity has extended into applied AI — integrating Google's Gemini API at Emtrain to power text-to-image generation directly inside the platform. I treat a new model API the same way I treat a new cloud service: understand its constraints, ship something real with it, then decide if it earns a permanent place in the stack.
Snapshot
- Based in
- Hyderabad, India
- Timezone
- IST · UTC+5:30
- Experience
- 12+ years
- Status
- Open to a good conversation
What I argue for in design review
If we end up working together, these are the arguments I’ll make in the room.
Systems-thinking first
Every design decision is made with the whole system in view — scalable design, clean APIs, and outcomes I can measure, not just ship.
Own the architecture, mentor the team
Technical ownership of system design and code quality goes hand in hand with design reviews and mentoring — the architecture only holds if the team understands why it looks the way it does.
Cloud-first, event-driven
AWS and GCP are tools for decoupling, not defaults. Queues, scheduled functions, and event buses go in where they remove a bottleneck, not everywhere.
Clean APIs, maintainable code
Node.js, TypeScript, React, and SQL are the daily stack, but the bar is the same regardless of language: an API and a codebase the next engineer can actually read.
Education
B.Tech — Computer Science
Abhinav Hi-Tech College of Engineering & Technology
72% aggregate
Experience
Where I have worked, and what changed because of it
Skills
What I can be dropped into on day one
Backend & languages
8 toolsWhere I spend most of my time
- Node.js
- NestJS
- Express.js
- TypeScript
- PHP
- Laravel
Frontend
5 toolsEnough to own the whole feature
- React.js
- Electron.js
- jQuery
- HTML5
- CSS3
Cloud — AWS
15 toolsHands-on, not diagram-only
- Lambda
- S3
- RDS
- DynamoDB
- SQS (incl. FIFO)
- SNS
Cloud — GCP
3 toolsMulti-cloud alongside AWS
- Cloud Functions
- Cloud Scheduler
- Cloud Storage
Databases
3 toolsRelational and document, by the problem
- PostgreSQL
- MySQL
- MongoDB
Tooling & DevOps
5 toolsShip small, ship often
- Docker
- Git (GitHub, GitLab, Bitbucket)
- Serverless Framework
- Azure DevOps
- Gemini API (text-to-image)
Independent work
What I build outside client work
Client and employer engagements live under Experience — this is the one I’ve taken from idea to production entirely on my own.
Contact
Tell me what you are building
Availability
Open to a good conversation
Based in Hyderabad, India (IST · UTC+5:30). Comfortable with US and EU overlap hours.