Ivan

IVAN PAVLENKO
DevOps Engineer - AWS, Kubernetes and CI/CD
[open contact info](look above in the "contact info" section) | [open contact info](look above in the "contact info" section) | [open contact info](look above in the "contact info" section) | github.com/filooww | [open contact info](look above in the "contact info" section)
English B2 | Ukrainian native | Russian native | Bulgarian basic

SUMMARY
DevOps engineer with two years of hands-on work on AWS infrastructure, Linux and delivery pipelines. I describe
environments in Terraform and configure them with Ansible, run containerised workloads on Kubernetes - both EKS and
clusters I built from scratch on plain virtual machines - and deliver them through Argo CD and GitHub Actions with image
scanning as a blocking gate.
About half of what I do is operations rather than building: alerts from Prometheus and CloudWatch, incidents across Linux,
NGINX, DNS, TLS, containers and databases, and the write-up afterwards so the same fault is not diagnosed twice. I am
comfortable owning a problem end to end - reproducing it, finding the real cause, fixing it with a rollback path prepared, and
documenting it. Everything I build outside work is public on GitHub.

TECHNICAL SKILLS
• Cloud: AWS - EC2, EKS, ECS, VPC, IAM, RDS, S3, CloudWatch, ALB/NLB, Route 53, ECR, Auto Scaling
• Infrastructure as Code: Terraform, Ansible
• Containers and orchestration: Docker, Kubernetes, Helm
• GitOps and CI/CD: Argo CD - app-of-apps GitOps delivery, and Argo Workflows for pipeline jobs inside the cluster. GitHub
Actions, GitLab CI, Trivy
• Monitoring: Prometheus, Grafana, Alertmanager, CloudWatch
• Linux and networking: Ubuntu, Debian, RHEL, systemd, NGINX, TCP/IP, DNS, TLS, firewalls
• Security: least-privilege IAM, OIDC in pipelines, External Secrets Operator with IRSA, SOPS, image scanning
• Scripting and data: Bash, Python, JavaScript/Node.js, PostgreSQL, MySQL, Redis
• Ways of working: Git and pull request review, Jira, Confluence, runbooks

EXPERIENCE
WOW Corporation - DevOps Engineer
May 2024 - Present | Remote
• Maintain and extend AWS infrastructure - EC2, VPC, security groups, IAM, S3, RDS, CloudWatch - described in
Terraform and configured with Ansible, with plan review before every apply.
• Run the delivery pipelines in GitHub Actions: build, Docker image creation, Trivy scanning as a blocking gate,
deployment across environments with manual approval before production.
• Administer Linux servers (Ubuntu, Debian, RHEL) and NGINX: systemd units, patching, permissions, TLS certificate
issuance and renewal, reverse proxy and load balancing.
• Monitor production with Prometheus, Grafana and CloudWatch - dashboards and alert rules that fire on conditions users
would notice; triage incidents across Linux, DNS, TLS, containers and PostgreSQL/MySQL, and write the resolution into
Confluence.
• Shipped two browser extensions (JavaScript, WebExtensions API) through the Chrome Web Store, used daily by two
internal teams of 20 and 10 people; one cut a routine lookup from 30 seconds to 2. Wrote a Python desktop utility that
replaced a manual process for the same teams.
Independent DevOps work - freelance contracts and self-built infrastructure
2024 - 2026 | Remote | code public on github.com/filooww
• Built a Kubernetes cluster from scratch on virtual machines, without a managed control plane, and delivered everything
onto it with Argo CD app-of-apps, Helm and External Secrets - cluster state in Git, rollback by revert. Verified autoscaling
under k6 load (2 to 6 pods and cleanly back), and alerted on cluster and application health with Prometheus and Grafana.
• Ran deliberate failure exercises against that cluster - broken images, failing probes, exhausted resources - and worked
each one back to root cause.
• Wrote a full AWS environment in Terraform with Ansible configuration (VPC, subnets, EC2, security groups,
least-privilege IAM), destroyable and rebuildable entirely from code, delivered through GitHub Actions with Trivy. Traced
a cross-architecture build fault where ARM-built images failed silently on AMD64 targets.
• Built and still operate a live Node.js service: automatic failover across providers, API key rotation, Redis-backed state with
an in-memory fallback and an admin dashboard - containerised and deployed end to end.
• On an Upwork contract, fixed a production TLS failure where a mobile app could not connect while browsers worked. Two
separate causes: an incomplete certificate chain in NGINX, and an expired certificate in the application server keystore on
the port the app actually used. Fixed both, with backups taken and a rollback path prepared first.

EDUCATION AND CERTIFICATION
• Associate Degree in Computer Engineering - Paton College of Welding and Electronics, 2022 - 2026
• AWS Certified Solutions Architect - Associate (SAA-C03): in preparation