status: open to interesting Staff / Lead / Architect opportunities

Serhii
Zolotov

Staff DevOps Engineer / Specialization Lead

5+ years automating, securing, and scaling cloud infrastructure across AWS, Azure & GCP. I build resilient Kubernetes platforms, design CI/CD that teams trust, and lead the DevOps direction across Mobile, CORE & NOC.

serhii@grid-dynamics: ~/whoami
$whoami --full
Serhii Zolotov
Staff DevOps Engineer · Specialization Lead @ Grid Dynamics
Ukraine · 5+ yrs · AWS / Azure / GCP · Kubernetes · Security operations
$cat mission.txt
15+ platform projects · 22+ engineers led across NOC, CORE & Mobile · Spinnaker → ArgoCD · on-prem → GCP · SLOs by priority.
$status
open to interesting Staff / Lead / Architect opportunities
status: open to interesting Staff / Lead / Architect opportunities

Serhii
Zolotov

Staff DevOps Engineer / Specialization Lead

Resilient cloud platforms, CI/CD teams trust, and security operations baked in by default — across AWS, Azure & GCP.

~/system.statuslive
roleStaff DevOps · Team Lead
directionArchitecture · Standards
securitySecurity operations
clouds
locationUkraine 🇺🇦
kyiv time··:··:··
availabilityopen · flexible
engagementremote · hybrid · EU overlap
focusmulti-team platform leadership
domainsretail · regulated · enterprise
01 // method: How I work

I run the full DevOps lifecycle as one continuous loop — not a hand-off between silos. From planning and infrastructure-as-code through CI/CD, GitOps delivery, observability and security, I automate the toil and make the safe path the default so teams ship faster with fewer surprises.

// method: automate everything · shift left · standards scale · teach the why
[01]planRFCs · boring, reversible decisions · golden standards
[02]buildTerraform IaC · reproducible images & artifacts
[03]ci/cdshared GitLab CI templates · Jenkins pipelines
[04]deliverGitOps · ArgoCD · progressive rollouts on Kubernetes
[05]observemetrics · logs · traces · SLOs & fast feedback
[06]secureshift-left scanning · policy-as-code · least-privilege
02 // architecture: principles I engineer by
p.01

GitOps, or it didn't happen.

Declarative infrastructure is the single source of truth. Terraform, Helm and ArgoCD describe the system; the cluster reconciles to match. No snowflakes, no manual drift.

p.02

Automate the toil.

If a human does it twice, it becomes a pipeline. Python, Bash, Go and Java turn repetitive ops into reliable, reviewable automation — so engineers spend time on the hard problems.

p.03

Resilient by default.

Platforms should scale and self-heal before anyone is paged. Kubernetes, sane autoscaling, spot/standard tiering and migration strategies that keep production calm under load.

p.04

Observe everything.

You can't operate what you can't see. Metrics, logs and dashboards — ELK, CloudWatch, Zabbix, Azure Monitor — wired in from day one, not bolted on after the incident.

p.05

Standards scale teams.

The biggest leverage isn't a clever pipeline — it's a shared way of working. As Specialization Lead I define DevOps practices, mentor engineers, and align Mobile, CORE & NOC on consistent, repeatable standards. Good architecture is a team sport.

03 // stack: tools I reach for
cloudmulti-cloud
AWSAzureGCP
orchestrationcontainers
KubernetesOpenShiftDockerComposeHelm
ci / cddelivery
JenkinsGitLab CIArgoCDSpinnakerAzure DevOpsAWS Amplify
iac / configdeclarative
TerraformAnsibleChef
languagesscripting
PythonBashGoJava
observabilitysignals
ELKLogstashKibanaZabbixCloudWatchAzure Monitor
securitydevsecops
VaultKMSSnykX-Raycloud-custodianSSL
registries & qualityartifacts
ArtifactoryHarborNexusECSSonarQubeGerrit
04 // experience:
Grid Dynamics
Macy's · Cloud PlatformStaff · Team Lead

Staff DevOps Engineer · Specialization Lead

GCP · Kubernetes · ArgoCD · CI/CD

Hands-on Staff engineer on a major retail cloud platform — operating Kubernetes on GCP, driving GitOps delivery, and leading DevOps practice across Mobile, CORE & NOC. Built the NOC function from the ground up and led a group of 22+ engineers spanning NOC, CORE and Mobile.

  • Managed 15+ platform projects end-to-end; authored 3- and 6-month onboarding plans for newcomers across NOC and CORE.
  • Migrated deployments from Spinnaker to ArgoCD; introduced SLOs by metric priority — teams cut incident noise and responded faster to what mattered.
  • Optimized GCP infrastructure in code — right-sized workloads, introduced zero-downtime maintenance where the architecture allowed it.
  • Ran guilds, office hours, hiring loops, platform RFCs, runbooks, and a clear definition of done for platform changes.
GCPKubernetesArgoCDSLOsTeam LeadMentoring
Macy's · Cloud migrationSenior · Team Lead

Senior DevOps Engineer · Specialization Lead

GCP · Terraform · on-prem → cloud

Led migrations from on-prem into GCP with Terraform — Kubernetes, Artifactory, and delivery tooling — while standing up the standards that let three squads ship on one platform.

  • Participated in on-prem → cloud migration; later owned the Spinnaker → ArgoCD transition for production deployments.
  • On Jenkins, established the delivery flow and standards three squads followed; after migration to GitLab SaaS, introduced shared GitLab CI templates — deeper tool integration, stronger security, and higher reliability.
  • Created cross-team workflow standards so Mobile, CORE & NOC understood not just what to do, but why — faster issue resolution and more delivery per cycle.
TerraformSpinnakerArgoCDJenkinsGitLabHelm
Containers · CI/CD

DevOps Engineer

Kubernetes · Docker · CI/CD · Automation

Built and operated CI/CD and cloud infrastructure, deepening automation and platform reliability across containerized workloads.

KubernetesDockerCI/CDAutomation
Sigma Software Group
Monitoring · Pipelines · On-prem

Strong Junior Systems Engineer

Azure · AWS · Zabbix · Jenkins · ELK

Owned monitoring and incident response across US projects with Zabbix, CloudWatch/CloudTrail and Azure Monitor — including a custom status page for on-prem VMs and Stripe. Built Jenkins pipelines, tuned Dockerfiles and OpenVPN networking, and ran the ELK stack (Logstash/Kibana). On the on-prem Azure DevOps project: Build/Release pipelines, Harbor registry, Ansible roles, HashiCorp Vault and certificate management.

ZabbixELKJenkinsHarborAnsibleVaultKMSAmplify
Artjoker
Banking / security · NDA

Junior Systems Engineer

banking / security · Docker · GitLab CI

Worked on bank-operations and security-improvement projects under NDA. Managed containerization with Docker & Docker-Compose and ran delivery through GitLab CI as the primary tool.

DockerDocker-ComposeGitLab CI
EPAM Systems
EDP platform · GCP security

Junior Systems Engineer

OpenShift · GCP · Jenkins · Terraform

Configured CI/CD pipelines and the full delivery process on Jenkins, with templates and deployments in OpenShift (Sonar, Nexus, Gerrit). On a parallel security team, used Python and Google APIs with cloud-custodian and Terraform to provision and govern GCP infrastructure.

OpenShiftJenkinscloud-custodianTerraformPython
05 // selected work: platforms I've shipped
work.01Grid Dynamics · Macy's

Cloud Platform on GCP

problem Three squads, divergent delivery, migration risk on a retail-scale GCP estate.

approach Terraform platform, GitOps with ArgoCD, shared Helm patterns, SLOs by priority, GCP right-sizing.

outcome 15+ projects delivered, Spinnaker → ArgoCD migration, on-prem → cloud path, fewer priority incidents, zero-downtime maintenance where feasible — one platform for Mobile, CORE & NOC.

GCPKubernetesTerraformSpinnakerArgoCD
work.02Sigma Software

Monitoring & Incident Platform

Built end-to-end monitoring for US projects spanning Azure and AWS — Zabbix, CloudWatch/CloudTrail and Azure Monitor — plus a custom status page for on-prem VMs and Stripe. Investigated and resolved incidents across a hybrid estate.

AzureAWSZabbixELKCloudWatch
work.03Sigma Software

On-Prem Azure DevOps + Harbor

Stood up a fully on-prem delivery stack on a local Azure DevOps server: Build/Release pipelines, Harbor as the Docker registry, Ansible roles, HashiCorp Vault for credentials and access control, ELK for logs, and certificate management for domains.

Azure DevOpsHarborAnsibleVaultELK
work.04EPAM · security team

GCP Policy-as-Code

Governed GCP infrastructure with cloud-custodian, Python and Google APIs — automated guardrails and Terraform-provisioned infrastructure, building security policy directly into the cloud estate as code.

GCPcloud-custodianTerraformPython
06 // impact: philosophy · outcomes · leadership

I work at the intersection of platform, delivery, and team practice — not just clusters. I prefer boring, reversible decisions documented in RFCs over clever one-offs. I align squads by making the default path easy: shared CI templates, GitOps, and observability shipped with the platform — not after the first outage. Good architecture is a team sport; my job is to multiply the engineers around me.

// philosophy: automate toil · shift security left · standards scale · teach the why
15+
platform projects managed end-to-end
22+
engineers across NOC, CORE & Mobile — hired, mentored, promoted
3
squads on one delivery standard (Jenkins flow → GitLab CI templates · Spinnaker → ArgoCD)
SLOs
priority-based targets that cut incident noise across teams

scale & reliability

  • Migrated production deployments from Spinnaker to ArgoCD across the retail platform.
  • Participated in on-prem → GCP migration; optimized infrastructure in code and reduced unnecessary workloads.
  • Introduced zero-downtime maintenance patterns for services where the architecture supported it.
  • Defined SLOs by metric priority — teams focused on the right tickets and incident load dropped.

leadership & mentoring

  • Created the NOC team and led CORE & Mobile — 22+ engineers total, several promoted from intern to middle and senior.
  • Authored 3- and 6-month onboarding plans with detailed curricula for newcomers in NOC and CORE.
  • Ran guilds & office hours, review standards, hiring loops, platform RFCs, and internal runbooks.
  • Set definition of done for platform changes so shipping stayed safe and reviewable.

standards that stuck

Built a cross-team workflow so Mobile, CORE & NOC understood why the process exists — not just which button to press. On Jenkins we defined the flow and standard the teams followed; after moving to GitLab SaaS, we migrated to GitLab CI and introduced shared pipeline templates — integrated with our toolchain, blending industry best practices with our own security and reliability ideas. Result: faster issue resolution and more delivery in the same cycle.

engagement

  • Open to interesting Staff / Lead / Architect opportunities — remote, hybrid, or flexible arrangements.
  • Based in Ukraine 🇺🇦 with EU timezone overlap; C1 English.
  • Best fit: multi-team platform leadership — retail, regulated, or enterprise scale.
07 // credentials: certs · education · languages

certifications

● Google Cloud
Associate Cloud Engineer
Google Cloud Certified
GitOps with ArgoCD
Continuous delivery
Cloud Engineering
Foundations

education

M.Sc. — Metrology & Information-Measuring Technology
NTU KPI · 2019 — 2021
B.Sc. — Computer Science
NTU KPI · 2015 — 2019

languages

Ukrainian
native
English
C1
© 2026 Serhii Zolotov · built in the terminal · Ukraine 🇺🇦
>
help jump theme cv
anim