About
Sagar Panwar
Software engineer and builder.
I've spent the last 8+ years working across software development, cloud infrastructure, architecture, and delivery. I'm based in Dehradun, Uttarakhand, India.
I started with web development. The work gradually moved toward the systems underneath those applications — cloud platforms, distributed services, serverless architecture, and infrastructure as code. I now work as a senior software engineer and team lead: I still write code, but a large part of the job is understanding the requirement, shaping the technical approach, and getting the result into production.
That shift wasn't a change of identity. It was the same problem getting larger. Once software is running for a real business, architecture, cost, reliability, and delivery stop being separate concerns.
Building for real businesses
Working directly with businesses has changed the way I think about software.
A technically elegant solution is not useful if it doesn't solve the actual business problem, arrives too late, or costs more to operate than it should.
I care about understanding the requirement first, choosing an architecture that fits the problem, and delivering something that works reliably in production.
Alongside my engineering career, I'm building Zeron Technologies, where I'm exploring that relationship between software, business requirements, and delivery more directly.
How I think about engineering
AI is changing how quickly software can be built. I think that makes engineering judgment more important, not less.
I use modern tools to move faster, but I still care about the fundamentals: understanding requirements, system design, security, observability, infrastructure cost, failure modes, and the trade-offs behind technical decisions.
For me, good engineering is not about producing the most code. It is about understanding the problem, making the right decisions, and delivering something that works.
Experience
Reducing cloud infrastructure cost
On an event-ticketing system, we replaced Kafka with a Lambda and SQS architecture for expected traffic of around 55 requests per second. That change cut AWS infrastructure cost by about 50% and made the system simpler to operate.
Building cloud platforms
I've built serverless middleware on AWS with Lambda, API Gateway, DynamoDB, WAF, and CDK — platform work where the architecture has to hold up for other teams, not just a single application.
Automating infrastructure
A lot of reliability in this work comes from treating infrastructure as code. I've built Terraform modules and CI/CD pipelines with GitHub Actions and AWS OIDC, including cross-account monitoring with EventBridge, CloudWatch, and SNS.
Working across teams
The technical work sits next to the delivery work: gathering client requirements, defining the solution, reviewing code, mentoring, and shipping in an Agile cadence.
What I work on
- Cloud architecture
- AWS
- Serverless systems
- Event-driven architecture
- Infrastructure as code
- CI/CD
- Backend systems
- System design
- Production reliability
- Cloud cost optimization
Writing
I write about the things I learn while building software — architecture decisions, AWS, infrastructure, production problems, and the trade-offs that are easy to miss when you're focused only on writing code.