Hi, I'm Shrikar

Platform / Cloud / DevOps Engineer

I design, build, and operate production-inspired cloud platforms that improve reliability, reduce deployment risk, and enable developer self-service at scale.

My work focuses on platform engineering and DevOps systems, combining infrastructure automation, Kubernetes orchestration, CI/CD pipelines, and observability to create systems that are resilient by design. I emphasize failure handling, rollback safety, and guardrails, because real-world systems are defined by how they break, not how they work on a happy path.

This portfolio showcases a hands-on Internal Developer Platform built with enterprise-style constraints: infrastructure as code, automated validation, drift detection, and operational visibility, reflecting the same reliability and ownership mindset used by senior DevOps and SRE teams.

Featured Project: Internal Developer Platform

A self-service platform that automates infrastructure and deployment workflows, allowing development teams to ship faster with confidence.

  • Self-service deployments
  • Kubernetes (AKS) orchestration
  • Terraform-managed infrastructure
  • CI/CD with GitHub Actions
  • Real failure handling and rollbacks

How It Works

A simple, automated deployment flow

1

Developer submits app details

Simple form or API call with app configuration

2

Platform API validates request

Check resources, naming, and permissions

3

CI/CD pipeline is triggered

GitHub Actions workflow starts automatically

4

Infrastructure is verified

Terraform ensures cloud resources are ready

5

Application is deployed to Kubernetes

Containers are rolled out with health checks

6

Deployment status is returned

Developer receives confirmation and app URL

What Breaks in Real Systems

Learning from production failures

Deployment Failure

Pod crash loop due to missing environment variable

Root cause: Configuration was not validated before deployment

Fix: Added pre-deployment validation step in pipeline

Infrastructure Drift

Manual changes made outside Terraform caused conflicts

Root cause: No enforcement of infrastructure-as-code policy

Fix: Implemented drift detection and automated reconciliation

Failed Rollback

Database migration prevented automatic rollback

Root cause: Migration ran before deployment health check

Fix: Separated migrations from deployments, added rollback-safe patterns

Key takeaway: Real platforms aren't about perfect codeโ€”they're about graceful failure handling, observability, and continuous improvement.