Work on Arian Svirsky | DevOps Engineering

A Multi-Cloud Identity Platform

Mon, 01 Jan 0001 00:00:00 +0000

Descope — identity and authentication infrastructure

Part of the platform team behind an auth product that processes millions of requests per day across 4 global regions. My remit is the boring but load-bearing part: the infra stays up, the deploys stay boring, and production never surprises us.

Scale & surface area

25+ microservices in one platform, running simultaneously on AWS (primary) and GCP
4 regions, each a fully independent production environment
Millions of auth requests/day across customer workloads
TypeScript + Pulumi as the IaC substrate — every cluster, every service, every env

What I own and drive

Reliability & observability — Full Datadog footprint (APM, structured logs, dashboards, SLOs) across every region. I build and maintain the dashboards on-call actually uses, set the SLO targets for services I own, and drive the runbook standard for infra-level incidents. When latency creeps in Singapore, we see it before customers do.

Migrating a Security Product to Kubernetes

Mon, 01 Jan 0001 00:00:00 +0000

Palo Alto Networks (Cortex XSOAR, formerly Demisto) — 6 years

Joined Demisto as a DevOps Engineer, stayed through the Palo Alto Networks acquisition, left as Principal DevOps Engineer. Led infrastructure architecture and mentored a growing DevOps team through a startup-to-enterprise transition.

The hard problem: Docker-in-Docker on Kubernetes

Cortex XSOAR is a SOAR product — it runs customer automation playbooks inside Docker containers. When we moved from EC2 to Kubernetes, I led the design of how to securely run Docker-in-Docker inside Kubernetes pods.

The Linux Foundation

Mon, 01 Jan 0001 00:00:00 +0000

2014–2018 — inManage, Interhost Networks, Calanit

Before Kubernetes existed in my vocabulary, I was managing Linux servers, configuring DNS zones, hardening firewalls, and writing Bash scripts that are probably still running somewhere.

Interhost Networks was web hosting infrastructure — hundreds of customer sites, shared servers, the kind of environment where you learn DNS, SSL, and Apache configuration by necessity. When something broke at 2am, there was no Kubernetes self-healing. You SSH’d in and fixed it.