SENIOR PLATFORM / INFRASTRUCTURE ENGINEER · BERLIN, GERMANY

I BUILD SYSTEMS
THAT HELP TEAMS SHIP.

14 years across infrastructure, cloud engineering, DevOps and platform engineering — from bare-metal systems and high-throughput networks to production Kubernetes and AWS.

SYSTEM STATUSONLINE
  • AWSOPERATIONAL
  • KUBERNETESOPERATIONAL
  • TERRAFORMOPERATIONAL
  • CI/CDOPERATIONAL
  • COFFEEREQUIRED

WHAT I BUILD

Three layers, one way of thinking.

Cloud Platforms

Standardized, automated cloud infrastructure that teams can build on without guesswork.

AWSKubernetesTerraformCloud Migration

Developer Experience

Tooling and workflows that make the correct engineering path the easiest one to take.

AutomationGitOpsSelf-Service InfrastructureInternal Tooling

Digital Products

Applying the same systems thinking used for infrastructure to building products end-to-end.

ArchitectureEngineeringProduct ThinkingIdea to Production

THINGS I'VE BUILT

Selected work

Cloud Migration

Moved legacy Linux-based services onto AWS EKS with infrastructure as code.

AWSEKSTerraformTerragruntHelm

CHALLENGEMigrating live services without standardized tooling or a shared deployment pattern.

OUTCOMEA standardized, automated Kubernetes platform replacing fragmented manual deployment.

High-Scale Streaming Infrastructure

Scaled a self-hosted streaming platform's throughput roughly eightfold.

HAProxyKubernetes on OpenStackLinux TuningTerraformAnsible

CHALLENGESustaining throughput growth from 5 Gbps to 40+ Gbps across ~100 servers without sacrificing availability.

OUTCOMEA tuned, highly available fleet capable of handling multiples of the original load.

Kubernetes Platforms

Operated both managed (EKS, GKE) and self-hosted Kubernetes clusters in production.

EKSGKEOpenStackHelm

CHALLENGEKeeping cluster operations consistent across managed and self-hosted environments.

OUTCOMEReliable, observable Kubernetes platforms serving as the standard runtime for services.

Infrastructure Automation

Automated infrastructure provisioning end-to-end with code-defined environments.

TerraformTerragruntAnsiblePythonShell

CHALLENGEReplacing manual, error-prone provisioning with a repeatable, reviewable process.

OUTCOMEEnvironments that can be recreated, audited and changed with confidence.

CI/CD & GitOps

Built automated delivery pipelines connecting code changes to running infrastructure.

GitLab CI/CDHelmGitOps workflows

CHALLENGEReducing the distance between a merged change and a safely deployed service.

OUTCOMEDeployment pipelines that made shipping routine rather than risky.

ReelzPro

A platform helping content providers accelerate video generation for Instagram and TikTok.

Cloud InfrastructureAutomation

CHALLENGEDesigning infrastructure for a content pipeline under early-stage budget constraints.

OUTCOMEA working platform that helps providers produce short-form video content faster.

ENGINEERING JOURNEY

Fourteen years, moving up the stack.

Not a resume — a system evolving. Each stage below is a checkpoint where the scope of the problem changed.

  1. 201110/2011 – 02/2017

    Network Engineer

    Takta

    Infrastructure projects spanning 250+ devices across Cisco, Huawei, IBM and HP needed reliable network design and rollout.

    IMPACTManaged IP planning, networking and hardware deployment across 250+ devices.

    This is where the foundation was built — understanding how packets move, how hardware fails, and why physical infrastructure decisions echo for years.

    Cisco IOSHuawei VRPIP PlanningVLANHardware Deployment
  2. 201702/2017 – 02/2019

    System Architect / DevOps Engineer

    Khallagh Borhan

    Systems needed to move from static, manually managed hardware toward virtualized, containerized infrastructure with reliable storage and messaging.

    IMPACTDesigned infrastructure using Docker, OpenStack and VMware, and implemented storage and messaging infrastructure using GlusterFS, SAN, NFS and RabbitMQ.

    The shift from network engineer to system architect — designing the layers that other systems would depend on, not just connecting them.

    DockerOpenStackVMwareGlusterFSSANNFSRabbitMQ
  3. 201902/2019 – 09/2021

    Head of Streaming & DevOps Engineer

    Aseman Company

    A streaming platform running on self-hosted Kubernetes needed to scale throughput dramatically while keeping ~100 servers highly available.

    IMPACTScaled streaming throughput from approximately 5 Gbps to 40+ Gbps while managing ~100 servers and self-hosted Kubernetes on OpenStack.

    Deep, hands-on performance engineering — kernel tuning, load balancer tuning, capacity planning — at a scale where every inefficiency multiplies.

    HAProxyLinux TuningKubernetes on OpenStackTerraformAnsible
  4. 202109/2021 – 12/2024

    DevOps Engineer

    Quandoo

    Legacy services running on Linux servers needed a path to a modern, standardized, cloud-native platform without disrupting delivery.

    IMPACTMigrated legacy services from Linux servers to Kubernetes (EKS) on AWS, automated provisioning with Terraform/Terragrunt, and built GitLab CI/CD pipelines with Datadog and Grafana/Prometheus observability.

    This is where infrastructure engineering became platform thinking — not just running Kubernetes, but making it a dependable, observable foundation for other engineers.

    AWSEKSGKETerraformTerragruntHelmGitLab CI/CDDatadogPostgreSQL
  5. 202501/2025 – Present

    Tech Consultant — Volunteering

    Experience Cafe

    Early-stage companies need pragmatic, cost-aware cloud and platform architecture without the overhead of enterprise-scale complexity.

    IMPACTAdvising startups on cloud cost minimization, Kubernetes adoption and CI/CD practices, and designing multi-cloud infrastructure blueprints for early-stage budgets.

    Applying platform thinking outside a single company — helping teams choose the right level of infrastructure for where they actually are.

    Cloud Cost OptimizationKubernetes AdoptionCI/CDMulti-Cloud Architecture
  6. 2026Ongoing

    Platform Engineering + Digital Products

    Independent

    Infrastructure teams often optimize for control at the expense of developer velocity — the two shouldn't be a trade-off.

    IMPACTFocused on platform engineering and developer experience: building the paved road that makes the correct path the easiest path, while applying that systems thinking to building digital products end-to-end.

    The current chapter — moving from operating infrastructure to designing it as a product, with engineers as the users.

    Developer ExperienceSelf-Service InfrastructureGitOpsProduct Engineering

CASE STUDY — QUANDOO

From Legacy Infrastructure to AWS EKS

Migrated legacy services from Linux-based infrastructure to AWS EKS, replacing fragmented manual deployment with a standardized, automated platform.

PROBLEM

Services ran directly on Linux servers with fragmented, manual deployment processes. Every service had its own quirks, its own runbook, and its own operational overhead — none of it standardized, all of it fragile under change.

APPROACH

Rebuilt the deployment path around Kubernetes on AWS EKS, with infrastructure defined as code and delivery automated end-to-end, so teams could ship without hand-holding infrastructure through every release.

BEFORE

Linux Servers
Manual / fragmented deployment
Operational overhead

AFTER

AWSEKS
TerraformTerragruntHelmGitLab CI/CDObservability

ARCHITECTURE

AWS EKS as the standard runtime, replacing bespoke per-service Linux hosts.

INFRASTRUCTURE

Terraform and Terragrunt for repeatable, environment-consistent provisioning.

DEPLOYMENT

Helm for packaging and release, GitLab CI/CD for automated delivery pipelines.

OBSERVABILITY

Datadog and Grafana/Prometheus for visibility into cluster and service health.

OPERATIONAL CONSIDERATIONS

PostgreSQL optimized for high availability, backups and query performance alongside the migration.

CASE STUDY — ASEMAN COMPANY

Scaling a Streaming Platform from 5 Gbps to 40+ Gbps

Scaled streaming throughput roughly eightfold across a self-hosted Kubernetes platform running on OpenStack, on a fleet of approximately 100 servers.

5 Gbps

Starting throughput

10 Gbps

First scaling pass

20 Gbps

Load balancing + tuning

40+ Gbps

Current scale

HAPROXY

Load balancing tuned for high-throughput, low-latency streaming traffic.

LINUX PERFORMANCE TUNING

Kernel and network stack tuning to remove throughput ceilings.

NETWORKING

Careful capacity and topology planning across the server fleet.

CAPACITY PLANNING

Scaling decisions grounded in observed load, not guesswork.

HIGH AVAILABILITY

Redundancy designed so scaling didn't come at the cost of reliability.

~100 SERVERS

Self-hosted Kubernetes on OpenStack across the fleet.

PLATFORM ENGINEERING

Building the Paved Road

The goal of a platform is not to hide infrastructure from engineers. It is to make the correct path the easiest path.
Developer
Developer Portal / CLI
Reusable Service Template
Infrastructure as Code
CI/CD
Cloud Infrastructure
Observability

ARCHITECTURE PLAYGROUND

Hover the system. See the trade-offs.

Conceptual architecture — illustrative, not a real production system.

Hover or tap a component to inspect it.

Infrastructure taught me how systems work.
Product building taught me why they matter.

Idea
Prototype
Architecture
Build
Ship
Learn

EXPERIENCE

Where I've worked

Tech Consultant — Volunteering

Experience Cafe

01/2025 – Present
  • Advising startups and companies on cloud cost minimization, Kubernetes adoption, and CI/CD practices.
  • Implemented the ReelzPro platform, helping content providers accelerate video generation for Instagram and TikTok.
  • Designed multi-cloud infrastructure blueprints for early-stage budgets.
  • Designed pragmatic cloud and platform architectures balancing developer experience, reliability, scalability and cost.

DevOps Engineer

Quandoo · Berlin, Germany

09/2021 – 12/2024
  • Migrated legacy services from Linux servers to Kubernetes (EKS) on AWS.
  • Maintained GKE clusters.
  • Automated infrastructure provisioning with Terraform / Terragrunt.
  • Managed deployments using Helm.
  • Designed GitLab CI/CD pipelines.
  • Maintained Datadog and Grafana/Prometheus observability.
  • Optimized PostgreSQL for high availability, backups and query performance.
  • Developed Python and Shell automation.

Head of Streaming & DevOps Engineer

Aseman Company · Tehran, Iran

02/2019 – 09/2021
  • Managed approximately 100 servers.
  • Operated self-hosted Kubernetes on OpenStack.
  • Scaled streaming throughput from approximately 5 Gbps to 40+ Gbps.
  • Performed Linux and infrastructure performance tuning.
  • Used Terraform and Ansible.

DevOps Engineer / System Architect

Khallagh Borhan

02/2017 – 02/2019
  • Designed infrastructure using Docker, OpenStack and VMware.
  • Implemented storage and messaging infrastructure using GlusterFS, SAN, NFS and RabbitMQ.

Network Engineer

Takta

10/2011 – 02/2017
  • Managed infrastructure projects involving 250+ devices.
  • Worked with Cisco, Huawei, IBM and HP infrastructure.
  • Managed IP planning, networking and hardware deployment.

CAPABILITIES

Skills, by area

PLATFORM ENGINEERING

  • Developer Experience
  • Platform Automation
  • Infrastructure Standardization
  • GitOps
  • Self-Service Infrastructure Concepts

CLOUD

  • AWS
  • EKS
  • EC2
  • S3
  • RDS
  • VPC
  • GCP
  • GKE
  • OpenStack
  • Bare Metal

INFRASTRUCTURE AS CODE

  • Terraform
  • Terragrunt
  • Ansible

CONTAINERS

  • Kubernetes
  • Docker
  • Helm

CI/CD

  • GitLab CI/CD
  • GitOps workflows

OBSERVABILITY

  • Datadog
  • Prometheus
  • Grafana
  • Alertmanager

NETWORKING

  • HAProxy
  • TCP/IP
  • VLAN
  • BGP basics
  • Cisco IOS
  • Huawei VRP

DEVELOPMENT

  • Python
  • Bash / Shell

EDUCATION

  • BSc — IT Engineering

    Qazvin University

  • Diploma — Mathematics & Physics

    Tehran

CERTIFICATIONS

  • CKA Certified Kubernetes Administrator

  • RHCE Red Hat Certified Engineer

    CERT UNAVAILABLE
  • LPIC-1 Linux Professional Institute Certification

    CERT UNAVAILABLE
  • LPIC-2 Linux Professional Institute Certification

    CERT UNAVAILABLE

ABOUT

A bit about how I think

I started close to the hardware and infrastructure layer and gradually moved upward — from networks and physical servers to distributed systems, cloud infrastructure, Kubernetes and platform engineering.

That background shaped how I think: understand the system deeply, automate what should be automated, and make the right path easier for the people using it.

Have a platform problem?

Let's build the path.