// about
A complete software engineer
I turn code into reliable systems.
I build backend systems and the infrastructure they run on. Most of what I know came from the gap between those two things — a service that looks correct in review behaves differently at 3am with a dependency degraded and a queue backing up.
That's the thread through my work: designing systems that fail narrowly instead of all at once, and building the observability to see it happening. Timeouts, circuit breakers, error budgets and reproducible infrastructure aren't separate specialities to me — they're the difference between software that works and software that keeps working.
I'm currently doing an M.Tech in CSE at NIT Warangal, deepening the systems foundations underneath all of it.
How I work
Build it, then run it
Writing the service is half the job. The half that teaches you something is carrying the pager for it — operability, failure modes and observability are design inputs, not a follow-up ticket.
Boring where it counts
Novelty is a cost paid at 3am by whoever is on call. I spend the complexity budget on the part of the system that's genuinely hard, and pick the dull, well-understood option everywhere else.
Make the tradeoff explicit
Every decision costs something. Writing down what it cost — and what would make me revisit it — is what separates a design from a preference.
Automate the thing you did twice
Manual steps rot silently: the runbook is correct the day it's written and quietly wrong a month later. Encoding it in CI makes drift visible instead of surprising.
Where I've been
- Education
NIT Warangal
currentM.Tech, Computer Science & Engineering
Aug 2026 – present · Warangal, IN
Applying my skills, building new ones, and keeping the coffee-to-code ratio healthy.
- Work experience
Nasdaq Inc
Software Engineer
Jan 2024 – Jul 2025 · Pune, IN
Worked on Regulatory Reporting Solutions, supporting the development and maintenance of automated regulatory reporting workflows.
- Education
Symbiosis Institute Of Technology
B.Tech, Computer Science & Engineering
Jun 2020 – Jan 2024 · Pune, IN
4 years of coding, coffee, and convincing myself that one more cup would fix the bug.
Toolkit
// Languages
- Java
- Python
- Go
- Bash
- SQL
// Backend & Systems
- Spring Boot
- REST APIs
- Microservices
- Distributed Systems
- System Design
- Databases
// Cloud & Infra
- AWS
- Kubernetes
- Docker
- OpenShift
- Terraform
- Linux
// DevOps & CI/CD
- Jenkins
- GitLab CI
- GitHub Actions
- Helm
- IaC
// Observability & SRE
- Prometheus
- Grafana
- ELK / Kibana
- Alertmanager
- CloudWatch
- SLIs / SLOs