SENIOR DEVOPS & PLATFORM ENGINEER

Systems that ship.
Platforms that stay.

I’m Venu Gopal Reddy. I modernise delivery at scale and operate cloud and Kubernetes platforms with production in mind.

Based in India Open to relocate to the Netherlands

venu@platform · workflowILLUSTRATIVE

➜ ~/delivery inspect --scope enterprise

13,000+ Bamboo plans in migration scope

➜ ~/delivery validate --mode parallel

✓ Reusable workflows · phased cutover · rollback controls

➜ ~/ops improve --signal alerts

✓ Approximately 60% less recurring alert noise

➜ ~/next

EXPERIENCE SNAPSHOT03 / 03
13,000+

Bamboo plans in migration scope

~60%

Less recurring alert noise

10

Engineers in the team I led

7+

Years across systems and cloud

01 / SELECTED WORK

Built in production.
Explained with clarity.

Three areas of professional experience that connect large-scale delivery, cloud platforms, and operational reliability.

CAPGEMINI · CI/CD MODERNISATION

A migration measured in thousands of pipelines.

Led the assessment and phased migration of approximately 13,000 Bamboo plans to GitHub Actions. Reusable workflows, composite actions, parallel validation, self-hosted runners, and rollback controls supported a cutover without release disruption.

↗~20%lower pipeline maintenance effort, as reported in my CV
See the delivery approach
DELIVERY MIGRATIONEXPERIENCE MODEL
EXISTING ESTATEBamboo13,000+ plans
MODERNISED DELIVERYGitHub ActionsReusable workflows
Map the estate

Identify build-plan patterns, dependencies, and migration candidates before changing delivery paths.

ILLUSTRATIVE · REUSABLE WORKFLOW

One workflow, every stage gated.

How a change moves through the kind of reusable GitHub Actions workflow the migration introduced: build, quality gate, versioned artifact, approval, and a GitOps deploy. Timings are illustrative.

reusable-deploy.yml · main · a3f9c2e● passed · illustrative
  1. Commitpull request · reviewpassed
  2. BuildMaven · Docker imagepassed
  3. Quality gateSonarQubepassed
  4. ArtifactJFrog Artifactorypassed
  5. Approvalproduction gatepassed
  6. DeployHelm · Argo CDpassed

[deploy] Helm values updated, Argo CD sync healthy

02 / PLATFORM ENGINEERING

Cloud fluency.
Operational consistency.

Repeatable infrastructure and delivery practices across development, test, and production environments.

PLATFORM TOPOLOGYAZURE · AWS · GCP
AZUREAKS
AWSEKS
GOOGLE CLOUDGKE
TERRAFORMHELMGITOPS

A shared operating approach across multiple cloud environments.

From infrastructure to release.

At Capgemini, I worked on Kubernetes and cloud workloads across AKS, EKS, and GKE, supporting 2 to 7 deployments daily through controlled CI/CD and GitOps practices.

  • Terraform provisioning and repeatable patterns
  • Helm, Argo CD, and Flux CD delivery
  • Quality checks, secrets controls, and approval gates
  • Linux, networking, and production troubleshooting

Earlier work at Persistent Systems covered AWS and Azure provisioning, Docker and Kubernetes deployments, and Ansible/Puppet automation.

KUBERNETES · SELF-HEALINGSIMULATION
replicas6/6
cpu (avg)48%
self-healed1
nodes ready3/3

kubectl get events -w

  • Scheduledapi-7f9c2-x2k4p → node-1
  • Scheduledapi-7f9c2-m81qz → node-2
  • HPAscaled api 4 → 6 (cpu 71%)
  • BackOffapi-7f9c2-d03lk OOMKilled, restarting
  • Healedapi-7f9c2-q7w2e → node-3

Illustrative simulation of autoscaling and self-healing on a cluster like the AKS, EKS, and GKE platforms above. Not live cluster data.

k8scontrol-planenode-1node-2node-3

03 / INFRASTRUCTURE AS CODE

Every resource
starts as a pull request.

I provision Azure platforms with Terraform so every change is reviewable in git and repeatable across development, test, and production. The configuration below is an illustrative example, not a client environment.

main.tfILLUSTRATIVE
provider "azurerm" {
  features {}
}

resource "azurerm_virtual_network" "hub" {
  location      = "westeurope"
  address_space = ["10.0.0.0/16"]
}

resource "azurerm_kubernetes_cluster" "aks" {
  location           = "westeurope"
  kubernetes_version = "1.31"
  default_node_pool {
    min_count = 3
    max_count = 20
  }
}

resource "azurerm_container_registry" "acr" {
  sku = "Premium"
}

resource "azurerm_postgresql_flexible_server" "db" {
  version = "16"
  zone    = "1"
}

resource "azurerm_key_vault" "kv" {
  sku_name                 = "standard"
  purge_protection_enabled = true
}

resource "azurerm_monitor_metric_alert" "p95" {
  severity = 2
}
AZURE · WESTEUROPE6 / 6 CREATED
  • azurerm_virtual_networkVNet10.0.0.0/16 · westeurope✓ created
  • azurerm_kubernetes_clusterAKS clusterv1.31 · 3–20 nodes✓ created
  • azurerm_container_registryContainer RegistryPremium tier✓ created
  • azurerm_postgresql_flexible_serverPostgreSQL Flexiblev16 · zone 1✓ created
  • azurerm_key_vaultKey Vaultpurge protection on✓ created
  • azurerm_monitor_metric_alertp95 alertAzure Monitor · sev 2✓ created

Apply complete! Resources: 6 added, 0 changed, 0 destroyed.

04 / RELIABILITY ENGINEERING

Make the signal
worth responding to.

Monitoring is useful when it helps a team notice, understand, and resolve an actual production problem.

ALERT QUALITYREPORTED OUTCOME
~60%

reduction in recurring alert noise

Illustrative trend, not a live telemetry feed

Operate. Learn. Improve.

At Capgemini, I improved production visibility with Prometheus, Grafana, Datadog, Splunk, AppDynamics, CloudWatch, and Azure Monitor. As shift lead, I coordinated major incident bridges, stakeholder communication, root-cause analysis, and mentoring.

21+engineers trained
10 / 10CSAT for Bravo Team recognition

My foundation includes Linux operations across an approximately 8,000-server estate at Nielsen.

api-gateway · p95 latencyILLUSTRATIVE112 ms
  • deploy
  • alert: above threshold
  • automatic rollback
  • alert threshold 250 ms

Illustrative: a regression after a deploy crosses the threshold, fires one actionable alert, triggers a rollback, and recovers. The goal behind the alert-noise work above is fewer alerts like this that each mean something.

status page · last 90 daysILLUSTRATIVE
90 days agooperationaldegradedtoday

Illustrative status-page view of the kind stakeholders read during and after an incident. Not a record of a specific service.

05 / EXPERIENCE

The path to
platform ownership.

Progression from Linux systems administration to multi-cloud platform delivery and operational leadership. Roles sit on main; the work inside each role branches off and merges into the next.

  1. HEAD
    chore Open to DevOps and Platform roles in the Netherlands HEAD → main
    2026
  2. e3b58c1
    cert AWS Certified Solutions Architect – Associate
    2026
  3. 4c7d0fa
    perf Cut recurring alert noise by ~60%; led a 10-person team and trained 21+ engineers
    2025
  4. 9a1e6b2
    perf Migrated ~13,000 Bamboo plans to GitHub Actions without release disruption
    2024
  5. d0c4e71
    merge

    Capgemini

    Consultant · Senior DevOps & Multi-Cloud Engineer · Shift Lead

    Kubernetes platform delivery, CI/CD modernisation, incident ownership, and team leadership.

    2024 - PRESENT
  6. 58ac0e3
    feat Monitoring with Prometheus, Grafana, Splunk and AppDynamics
    2023
  7. b27e5d9
    feat Terraform for AWS and Azure: EKS, AKS, VPC, RDS, Entra ID
    2022
  8. 3f6a7c0
    feat Jenkins CI/CD with Maven, SonarQube, Nexus and Artifactory
    2021
  9. e90b1f2
    merge

    Persistent Systems

    DevOps Engineer

    Cloud provisioning, Jenkins pipelines, container deployments, monitoring, and configuration automation.

    2021 - 2024
  10. c4d81aa
    feat BigFix patching plus Bash and Python health-check automation
    2020
  11. 7be20d4
    feat Operated ~8,000 RHEL, CentOS and Ubuntu servers
    2019
  12. a1f3c9e
    init

    Nielsen

    Linux Engineer & Administrator

    Server operations, security patching, troubleshooting, and Bash and Python automation.

    2019 - 2021

06 / TOOLKIT

Tools selected
for the problem.

Practical experience across delivery, cloud infrastructure, operations, and automation.

Cloud & orchestration

Azure · AWS · GCP · AKS · EKS · GKE · Kubernetes · Docker · Helm · Terraform · Entra ID

Delivery & GitOps

GitHub Actions · Jenkins · GitLab CI/CD · Bamboo · Harness · Argo CD · Flux CD · SonarQube · JFrog Artifactory

Observability & systems

Prometheus · Grafana · Datadog · Splunk · Linux · RHEL · Ansible · Vault · Python · Bash

07 / PUBLIC PROJECTS

Evidence you can
open and inspect.

Three original, public labs that make my engineering approach reviewable. Each uses synthetic data and is separate from employer systems.

01 / FEATURED CASE STUDYPUBLIC REPO

Pipeline Modernization Lab

Dependency-aware migration waves, explainable risk scoring, a source-to-target parity gate, reusable GitHub Actions, and a cutover runbook.

PYTHON · JSON · GITHUB ACTIONS
02 / KUBERNETESPUBLIC REPO

AKS Reliability Lab

A reproducible Go service and Kubernetes workload design with probes, scaling, disruption controls, network policy, metrics, and a Helm chart. The repository does not provision an AKS cluster.

GO · KUBERNETES · HELM · PROMETHEUS
03 / OPERATIONSPUBLIC REPO

Daily Automation Toolkit

Python and Bash tools for health checks, log triage, rollout validation, and operational snapshots, with redaction, bounded timeouts, and dry-run safeguards.

PYTHON · BASH · LINUX · KUBERNETES

LET’S CONNECT

Ready for the
next challenge.

Exploring Senior DevOps and Platform Engineering opportunities in the Netherlands.

Based in India · Employer-sponsored work authorisation required
90-day notice period, negotiable