Backend & APIs
CoreWhere most of my work lives.
- Node.js
- Python
- Express
- NestJS
- FastAPI
- REST
- MongoDB
- MySQL
Software Engineer
Vishal Pundhir · India
I turn business problems into working systems.
And then I make sure they keep working.
Event-driven backends, queues and pipelines — the parts that decide whether a product survives its own traffic.
I move fast. I also care about getting it right.
2.3 yrs
building and running systems in production
1000+
videos a month through the pipeline I own
Writing code was never the job.
I use AI to multiply what I can do.
Engineering was always about solving the problem with the best tools your domain hands you. One of those tools now writes code. So I use it every day — to read more logs than I could, to draft three designs instead of defending my first idea, to try every path through a piece of test data. What it doesn't do is decide which number matters, or notice that the number everyone quotes has no source, or own it at 2am. That part is still the job.
Education
BITS Pilani
Bachelor of EngineeringClass of 2024
Pilani campus. Years of being surrounded by people who were better than me at something, which turned out to be the useful part.
About
I build AI products end to end — pipeline, backend, frontend, and keeping them running once they are live. Outside work I build tech for the everyday problems I notice around me. Learning by doing is what keeps making me better at the part that matters: working out what the real problem is.
Off the clock
Guitar and singing. Filmmaking. Football — playing, not watching.
Skills
What I work with.
Grouped by what I actually reach for. The two marked core are where most of my time goes.
Queues & event-driven
CoreKafka, SQS, FIFO ordering, idempotency, retries, dead-letter queues.
- Kafka
- SQS / FIFO
- SNS
- CDC events
- Round-robin dispatch
- Idempotent consumers
Cloud & infra
Deploying it, running it, and being the one paged for it.
- AWS
- Lambda
- Step Functions
- ECS
- EC2
- S3
- CloudFront
- Nginx
- PM2
AI in production
Real workflows, not demos.
- Structured outputs
- LangGraph
- RAG
- Tool calling
- MCP
- LLM-as-judge
- Speech in / out
- Prompt versioning
Frontend
Enough to own a product end to end.
- React
- Next.js
- TypeScript
- Tailwind
- Three.js / WebGL
- React Native
Monitoring
The one I care about most. A system you can't see into is a system you're guessing about — and every number on this page came from having built the thing that reports it.
- Grafana
- CloudWatch
- ClickHouse
- Metabase
- Loki
- Structured logging
- Alerting
Design
The creative side I never dropped.
- After Effects
- AE scripting
- Premiere Pro
- Illustrator
- Figma
The list is the easy part. Picking one, and knowing why not the other, is the hard part — which is what the next section is actually about.
How I work
Same four steps, every time.
In this order. The tools change constantly; the sequence hasn't.
- 01
The problem, and what the customer actually needs
A ticket tells you what someone typed. I go find out what they were trying to do — which is often a different problem with a different answer.
- 02
Break it into parts that can each be wrong
If a failure can only be described as “it broke”, it was never broken down. Each piece should be able to fail on its own, visibly.
- 03
Find the edge cases before a customer does
The empty field. The message that arrives twice. The one dealer who uploads a hundred cars at once. These decide whether it survives.
- 04
Design the system — then prove the number moved
Pick the architecture, write down what it was chosen over, ship it, and measure it. Every number I claim comes with how I measured it.
Recent work
Problems I worked on.
Four from work, one from my own time. Open any to see what was asked, what it turned out to be, how I built it, and what changed.
Contact
Say hello.
Happy to talk about engineering, business problems, music, or football. If you're hiring: I want to own something real, with users and a number attached to it.
I'll happily argue the other side of anything on this page. Most of what I know came from being wrong out loud.