DK.PLATFORM ENGINEERING
CLOUD • PLATFORM • RELIABILITY

Building platforms
that ship with confidence.

I'm Dhileep Kumar, a Lead DevOps Engineer focused on cloud infrastructure, reliable delivery, and security built into the workflow.

AWS + Google Cloud Security by design
Dhileep Kumar
LEAD DEVOPS
9+ years

Building and operating cloud platforms across AWS and Google Cloud.

ops-console / live-demo INTERACTIVE
$kubectl get clusters --context=portfolio
verifiedplatform-prod Ready
verifiedplatform-staging Ready
$terraform plan -var-file=production.tfvars
→Plan: reviewed changes before apply.
$pipeline status --summary
verifiedquality gates · security scans · deploy
awaiting input

Illustrative demo only — no real infrastructure is accessed.

9+Years in DevOps
60Clusters supported
1000+CI/CD pipelines
40%Cloud spend reduction

Engineering for the real world.

A practical mix of platform thinking, automation, security, and operational ownership.

My work sits where infrastructure, delivery, and security meet. I build repeatable cloud foundations, automate the path from commit to production, and help teams operate services with clearer signals and fewer manual steps.

I have worked across AWS and Google Cloud, with Kubernetes, Terraform, CI/CD systems, observability stacks, and compliance-focused controls.

Secure by default. Observable by design. Automate the repeatable.

Platform thinking

Reusable patterns over one-off fixes.

Operational clarity

Useful alerts, clear ownership, better RCAs.

Security built in

Policy checks and evidence in the workflow.

Tools are useful. Outcomes matter.

A snapshot of the technologies and operating disciplines I use to build and support platforms.

1

Cloud & platform

AWSGoogle CloudGKECloud RunCloud SQLVPC
2

Delivery & automation

TerraformJenkinsCloud BuildCI/CDPythonBash
3

Reliability & observability

KubernetesDockerPrometheusGrafanaEFKIncident response
4

Security & governance

IAMOPAPolicy as CodeSOC 2 readinessHIPAA readinessHITRUST readiness

Case studies, not buzzwords.

Explore the thinking behind cloud foundations, delivery pipelines, and policy-driven operations.

Multi-cloud platform foundations

Reusable infrastructure patterns for secure cloud environments, with Terraform-managed resources and clear operational guardrails.

AWSGCPTerraformIAM

CI/CD delivery at scale

Pipeline standards, release automation, and practical feedback loops that help teams ship frequently without skipping quality gates.

JenkinsCloud BuildDockerSecurity scans

Policy-driven cloud governance

Infrastructure policy checks and automated evidence workflows designed to make security controls repeatable and auditable.

TerraformOPAAudit logsCloud IAM

How the work actually fits together.

Explore the problem, engineering approach, operational controls, and evidence behind each workstream. These are portfolio summaries of the experience described; add sanitized diagrams or public code where available.

Multi-cloud foundations and Kubernetes operations

Operate a platform spanning AWS and Google Cloud, with Kubernetes and managed cloud services at the core.

Context

Platform scope supplied for the portfolio: 60 clusters, 30 projects, 500 services, and 10 environments. Confirm that these figures describe the same platform and period before publishing them as a single scope statement.

Engineering approach
  • Provision and evolve infrastructure through Terraform rather than relying on one-off manual changes.
  • Use cloud IAM, VPC controls, Secret Manager, and platform-native security services to establish access and network guardrails.
  • Operate Kubernetes and supporting services with an emphasis on repeatable environments, clear ownership, and observable operations.
  • Treat changes as reviewable infrastructure changes, with configuration and policy checks built into the workflow.
Controls and practices
Terraform change reviewIAM and network boundariesSecret managementEnvironment consistency
Evidence to publish

Portfolio scale: 60 clusters, 30 projects, 500 services, 10 environments (user-provided; attribution and time period should be verified).

System flow

Click a node
SELECTED COMPONENT

AWS + Google Cloud

Separate cloud projects/accounts and network boundaries, with identity and secrets controls.

Conceptual flow for explanation, not a deployment diagram of a specific production environment.

From commit to verified release.

From commit to verified release.

Select a stage to see its purpose and controls.

STEP 01

Commit: Change record

Start from a reviewed change. Keep the source revision and build run traceable.

Generic reference workflow. The exact stages and gates should match the pipeline you can demonstrate in an interview.

Latest Writing

Field notes from the edge.

The latest published articles from the standalone engineering blog, plus the topics the work is circling around.

A good platform makes the safe path the easy path.

The operating loop I bring to infrastructure and delivery work.

1

Standardize

Reusable IaC modules, environments, and sensible defaults.

2

Automate

Build, test, scan, promote, and deploy through repeatable workflows.

3

Observe

Metrics, logs, actionable alerts, and service-level signals.

4

Improve

RCA follow-through, cost reviews, and continuous hardening.

05 / CONTACT

Have a platform challenge
worth solving?

Let's talk about cloud platforms, delivery engineering, reliability, or security automation.

RESUME

Experience,
on paper.

9+ years across AWS and Google Cloud, 60 clusters, 1000+ CI/CD pipelines, and 40% cloud spend reduction.