edward@platform ~ % whoami

Software Engineer · Platform & Infrastructure

I build cloud platforms and the automation that keeps them reliable.

Terraform, Python, and AWS by day; OpenTelemetry pipelines and SLO-backed alerting to make sure it all stays up. Currently at Cisco, building a greenfield procurement & ITSM platform on AWS. Previously automated a 10,000+ device fleet at Splunk. After hours: Copywarden.

Greater Boston · e_vartanessian@live.com

Get in touch Résumé GitHub LinkedIn
10,000+
devices automated
<15 min
security enforcement (was hours)
97%+
macOS patch compliance, fleet-wide
OTel
custom Collector fleet-wide · upstream proposal #33393

~/work

Proof, not adjectives.

Three builds, written up properly — architecture, trade-offs, what broke, and the numbers.

~/work/fleet-automation

Automating a 10,000-device fleet

SLO-backed alerting, Python auto-remediation, and zero-downtime enforcement across macOS, Windows, and Linux at Splunk — with the compliance auditors watching.

<15 min enforcement · was hoursread the case study →

~/work/otel-collector

A custom OpenTelemetry Collector, fleet-wide

Built and shipped a purpose-built OTel Collector distribution to 10,000+ endpoints — and drove upstream macOS host-metrics support (proposal #33393, since shipped).

10,000+ endpointsread the case study →

~/work/copywarden

Copywarden: an encrypted clipboard manager

A security-first macOS product designed and built solo — AES-256-GCM, Secure Enclave key wrapping, screen-share-aware redaction. In development at copywarden.com.

signed · notarized · in developmentread the case study →

~/experience

Where I’ve shipped.

Cisco

Sept 2025 — Present

via Splunk acquisition

Software Engineer

  • Building a greenfield internal procurement & ITSM platform on AWS, built to replace two enterprise SaaS products — Lambda, Aurora PostgreSQL, S3, CloudFront, Route 53, IAM and VPC networking — infrastructure in Terraform, delivered by GitHub Actions CI/CD.
  • Own the platform's data layer — Aurora Serverless v2 in Terraform across dev, staging and production — and one of two required approvers for infrastructure and security changes platform-wide.
  • Designed the platform’s passwordless database access model — no stored password anywhere in the path: an in-VPC Lambda migrator authenticating through IAM, with schema-migration and application roles separated so the application cannot alter schema. Version-controlled, peer-reviewed Drizzle migrations, validated end to end against dev Aurora including a tested forward-only rollback.
  • Designed and built the self-service machine-ordering site end to end — the platform's primary user-facing workflow.
  • Developing ServiceNow automations and integrations: scripted workflows, catalog automation, and API-driven tooling that remove manual steps from request fulfillment.
  • Own incident management for device automation across the fleet — automated triage, cleaner runbooks, fewer repeat incidents.

Splunk

Apr 2022 — Sept 2025

Client Platform Engineer (DevOps/SRE)

  • Automated a 10,000+ device fleet (macOS, ~1,200 Windows, ~1,000 Linux) for reliability and compliance — SOC 2, ISO 27001, UK Cyber Essentials — with zero-downtime updates.
  • Built fleet-wide observability on OpenTelemetry and Splunk: defined health and compliance SLIs, shipped a custom OTel Collector, and drove upstream macOS host-metrics support (authored proposal #33393, since shipped).
  • Cut security state-change enforcement from hours to under 15 minutes using SLO-backed alerting, Python/Bash auto-remediation, and runbooks.
  • Built Docker-based GitLab CI/CD pipelines; automated with AWS (Lambda, EC2, S3, CloudFront, Secrets Manager) and Terraform.
  • Owned Puppet as the configuration-as-code layer across a heterogeneous fleet — ~1,200 Windows and ~1,000 Linux devices under version-controlled state enforcement and drift reduction.
  • Led vulnerability remediation across the fleet with Splunk, Tenable, and SonarQube; modernized legacy Perl/Shell automation into Python services in CI/CD.
  • Carried the team’s weekly on-call rotation (VictorOps, later Splunk On-Call) — including through the 2024 CrowdStrike outage that took Windows endpoints down fleet-wide.
  • Selected by the Director to set the technical bar for the team’s hiring — technical interviewer for senior and junior engineers and for the team’s incoming manager.

Starburst Data

Dec 2020 — Jan 2022

IT / Cloud Engineer

  • Owned Okta as the company IDP and the Harbor container registry — the company’s only IT engineer, running multi-cloud infrastructure in Terraform as headcount grew from ~100 to 300.
  • Codified Okta IAM in Terraform (groups, app assignments, SCIM): least-privilege access by default and same-day onboarding/offboarding through the growth.
  • Automated container-registry access end to end — replaced hand-provisioning with a Jira → Harbor API workflow issuing scoped credentials with an audit trail, cutting turnaround from hours to minutes; scoped the design and brought in a software engineer for the Jira API integration.

before that A decade across systems administration and IT engineering (Arent Fox, McDermott Will & Emery, LiveCare) — the operational instincts behind my reliability work.

~/toolkit

The toolkit.

Languages

  • Python
  • Bash
  • PowerShell
  • Swift
  • TypeScript
  • JavaScript
  • HCL

Infrastructure

  • AWS
  • Terraform
  • Docker
  • Kubernetes
  • Puppet

CI/CD & Tooling

  • GitLab CI
  • GitHub Actions
  • ServiceNow development
  • Okta / IAM-as-code

Observability & SRE

  • OpenTelemetry
  • Splunk
  • Prometheus
  • Grafana
  • SLOs / SLIs
  • Incident management

Security & Compliance

  • Zero-trust design
  • AES-256-GCM / Secure Enclave
  • Vulnerability management
  • SOC 2 / ISO 27001

~/colophon

How this site ships.

This page is its own demo: a static site served from a private S3 bucket behind CloudFront — TLS, security headers, and the keyless CI deploy pipeline all defined in Terraform, all in the public repo. And it’s observed: live SLOs with a visible error budget →

Deployment architecture git push triggers GitHub Actions, which assumes an AWS role via OIDC with no stored keys and syncs the site to a private S3 bucket. CloudFront serves the bucket over HTTPS with security headers, using an auto-renewing ACM certificate. Terraform defines all of the AWS infrastructure. git push main branch GitHub Actions OIDC · keyless S3 private · OAC you browser · HTTPS Terraform main.tf ACM TLS · auto-renew CloudFront sec headers · HTTP/3 everything after the push is defined in Terraform — one apply, zero stored keys 
$ terraform apply
aws_cloudfront_distribution.site: deployed ✓
response_headers_policy: HSTS · CSP ✓
Apply complete! Resources: 12 added.
$ git push origin main
→ Actions: OIDC ✓ sync ✓ invalidate ✓  (38s)
$

~/about

The long way here.

I got into engineering the long way — years of hands-on systems and IT work before moving into platform engineering — and it shows in how I build: automation with an operator’s paranoia, observability before things break, and a strong bias for deleting manual work.

I care about infrastructure as code, measurable reliability, and leaving every system easier to run than I found it. This site practices what it preaches ↑

// open to senior platform & SRE roles

Let’s build something reliable.

e_vartanessian@live.com Résumé (PDF) LinkedIn GitHub

reply SLO: < 24h · Greater Boston · remote-friendly