Senior DevOps Engineer
Scalable.
Boring.
Senior DevOps Engineer with 5+ years of experience elevating platform efficiency. I drive TCO reduction and developer velocity by building boring, predictable systems—whether on bare-metal, hybrid, or pure cloud (AWS, EKS, Serverless).
In plain English: I keep systems fast, cheap, and always online.
📍 Bangalore, India • Full-time • Remote-friendly
Bare Metal
K3s optimization on physical hardware.
Hybrid Cloud
Seamlessly bridging AWS & On-prem.
Disaster Recovery
RTO < 10min for 200+ services.
Cost Ops
Reduced cloud spend by ~25%.
01. PLATFORM IMPACT
Force Multiplier
My work doesn't just improve one server; it lifts the baseline for the entire engineering organization.
How I Work
Leadership without Authority
Driving consensus and technical excellence across distributed teams.
Design Reviews
I lead infra design reviews to catch scalability issues before a single line of code is written.
Mentorship
I mentor engineers on reliability patterns, cost optimization, and incident management.
Escalation Point
I act as the final escalation point for complex production incidents that stump the on-call team.
Boring Systems
I bias heavily toward boring, proven technology over the latest hype to ensure long-term maintainability.
02. EXPERIENCE LOG
The Bare-Metal Orchestration
Key Impact
The Challenge
Managing high-throughput ad-tech traffic on rigid bare-metal infrastructure lacked the elasticity of the cloud, risking latency spikes during traffic surges.
The Goal
Architect a Kubernetes layer on top of bare metal to bring cloud-native flexibility to physical hardware without the virtualization overhead.
The Solution
- Drove a 60% TCO reduction vs. public cloud by deciding to pivot to a bare-metal K3s architecture (trading operational convenience for massive financial gain).
- Led resolution of critical production incidents (DNS, HAProxy) and optimized ingress for zero-downtime reloads under high burst traffic.
- Built a complete observability ecosystem with 100+ Grafana dashboards covering infrastructure health and business KPIs.
Trade-offs & Decisions
- Chose K3s over full Upstream K8s for lighter footprint on bare metal, accepting reduced ecosystem compatibility.
- Accepted higher maintenance complexity of bare-metal to ensure massive long-term financial stability.
- Prioritized predictable performance over maximum theoretical density by using dedicated CPU pinning.
The Outcome
Achieved cloud-like orchestration on owned hardware, maintaining low-latency ad delivery while owning the full stack and reducing potential cloud costs by 60%.
03. DEPENDENCIES
Tech Stack
Cloud & Infrastructure
- AWS
- Azure
- Terraform
- Ansible
Orchestration
- Kubernetes
- EKS
- K3s
- Helm
- Bare-Metal
- Docker
CI/CD
- Jenkins
- Spinnaker
- GitHub Actions
- Rancher Fleet
- CircleCI
Monitoring
- Prometheus
- Grafana
- CloudWatch
- ELK Stack
- OpenTelemetry
Security & Networking
- Checkmarx
- IAM
- HAProxy
- Nginx
- Ingress
Data & Processing
- Aerospike
- Airflow
- Superset
- Druid
Automation & Scripting
- Python
- Go
- Shell
- Groovy
- PowerShell
Tools
- Linux
- GitHub
- JIRA
04. HANDSHAKE
Let's Connect
Currently open to new opportunities. Whether you have a question about my bare-metal clusters or just want to say hi, I'll try my best to get back to you!