Senior DevOps / Platform Engineer (10 years) building secure, scalable cloud & Kubernetes platforms with strong operational rigor—CI/CD, observability, IAM, compliance, and incident-driven runbooks.

• 🔧 Core: AWS, Kubernetes/EKS, Terraform, Docker, Helm, ArgoCD/Argo Workflows
• 📈 Ops: Prometheus + Grafana, logging/triage, cost optimization, scaling (Karpenter)
• 🔐 Security & Compliance: SOC 2 awareness + controls mindset, compliance automation (AWS Config), security tooling (Vanta), least-privilege access
• 🧰 Delivery: GitHub Actions, GitOps-style deployments, preview environments, automation via scripts/Rundeck

I document real-world engineering scenarios (anonymized) as repeatable tasks: outages, latency regressions, rollout failures, scaling issues, and secure deployment patterns.

Example scenarios I like to capture

• K8s rollout triggers elevated errors → diagnosis + rollback + guardrails
• Latency spike (DB pool exhaustion / downstream dependency) → signal-based mitigation
• Certificate / ingress misconfig → restore service + prevention checks
• Node pressure / evictions → capacity plan + requests/limits + autoscaling

• Kubernetes platform engineering: EKS, secure-by-default workloads, GitOps deployments (ArgoCD)
• Scaling & reliability: autoscaling with Karpenter, graceful termination patterns
• Observability: Prometheus/Grafana monitoring & alerting across microservices
• Compliance automation: AWS Config checks + evidence-ready workflows; SOC 2 controls mindset
• CI/CD & release engineering: GitHub Actions, automated delivery pipelines (incl. mobile delivery via App Center)
• IAM & access control: granular policies aligned to least privilege

• CKAD
• AWS Solutions Architect – Associate (exp Dec 2026)
• AWS DevOps Engineer – Professional (in progress)

• LinkedIn: https://www.linkedin.com/in/ivneetsinghwahi3/
• GitHub: @ivneetsinghwahi03