$ cat /etc/aditya.conf
NAME = "Aditya Konda"
ROLE = "Junior SRE | DevOps Engineer"
COMPANY = "Dorian Mode Technologies"
LOCATION = "Mumbai, India 🇮🇳"
EDUCATION = "B.E. Information Technology — 2025"
PORTFOLIO = "adityakonda04.vercel.app"
FOCUS = "Reliability. Automation. Scale."
STATUS = "Building systems that wake me up — not page me."I'm not a software developer.
I'm the person who makes sure what developers build actually survives production.
I obsess over systems that heal themselves, pipelines that deploy while you sleep, and infrastructure that doesn't fail at 3am — or when it does, recovers before anyone notices.
"If it can be automated, it will be.
If it can break, I've already thought about it."
First role. Full ownership. No hand-holding.
Dropped into a production environment and immediately started building things that matter — real pipelines, real infrastructure, real consequences if something breaks. Here's what that looks like day-to-day:
- ☸️ Deploying and managing containerized workloads on Kubernetes with zero-downtime release strategies
- 🔁 Building and owning end-to-end CI/CD pipelines — code hits production fast, clean, and safely
- 🏗️ Provisioning cloud infrastructure using Terraform — everything version-controlled, nothing clicked by hand
- 🔐 Embedding DevSecOps gates into pipelines: static analysis, image scanning, secrets detection before merge
- 📊 Standing up observability stacks — metrics, logs, traces, dashboards, alerts — so teams see problems before users do
- ⚡ Driving SRE culture: SLOs, error budgets, blameless postmortems, and reducing toil relentlessly
The goal isn't uptime. The goal is confidence — that any engineer on the team can deploy on a Friday at 5pm.
☁️ Cloud
📦 Containers & Orchestration
🏗️ Infrastructure as Code
🚀 CI/CD & GitOps
📊 Observability & SRE
🔐 DevSecOps
💻 Languages
🗄️ Databases
🐧 OS & Systems
Two projects worth your attention. Both are production-minded, not tutorial-cloned.
A zero-trust CI/CD pipeline that treats security as a first-class citizen — not an afterthought bolted on after deployment.
Git Push
│
▼
GitHub Actions
│
├──► Bandit (SAST) ──────────── Python code vulnerability scan
│
├──► Docker Build + Trivy ────── Container image CVE scanning
│
└──► ECR Push → EC2 Deploy ───── Only clean images reach production
Every commit goes through automated security gates. Bad code doesn't ship — the pipeline rejects it before a human even sees it. That's shift-left security in practice, not in slides.
A full React + Node.js + MongoDB application deployed on Amazon EKS — with Helm charts, AWS Load Balancer Controller, ECR-managed images, and persistent EBS volumes.
React (Frontend) Node.js (API) MongoDB (DB)
│ │ │
ECR Image ECR Image EBS Volume
└──────────┬────────┘ │
▼ │
AWS EKS Cluster ◄─────────────────┘
Helm • Manifests • ALB Controller
Not just "it runs on Kubernetes." Proper Helm-versioned releases, proper load balancing, proper persistent storage — the way you'd actually do it at a company.
More in the lab 🔬 — Blockchain dApp for donation transparency, Android SOS safety app with paired IoT hardware, Selenium automation framework, MERN e-commerce clone. Browse all 46 repos →
╔══════════════════════════════════════════════════════════════════════╗
║ ║
║ AUTOMATE EVERYTHING Manual process = future incident ║
║ SHIFT SECURITY LEFT Catch it in the pipeline, not prod ║
║ OBSERVE OR FLY BLIND Metrics. Logs. Traces. No exceptions. ║
║ INFRA IS CODE If it's not in Git, it doesn't exist ║
║ MTTR > MTBF Fast recovery beats perfect uptime ║
║ TOIL IS THE ENEMY If you do it twice, automate it ║
║ ║
╚══════════════════════════════════════════════════════════════════════╝
| 🏋️ Gym | 🏍️ Bikes | 🎥 Motovlogging | 🗺️ Solo Rides |
|---|---|---|---|
| Discipline isn't motivation — it's a system | A mountain road at 6am resets everything | Motion is expression | 500km of silence beats a weekend of noise |
The same mindset that runs a blameless postmortem at 2am is the one that finishes a solo ride in the rain.
Consistency. Composure. Keep moving.
Junior SRE | DevOps Engineer | Open to the right opportunity
Mumbai, India · Remote / Hybrid / Relocation welcomed
Always open to collabs, infra war stories, and brutal architecture debates.
If you're building something serious — let's talk.




