jeff@bilder — zsh — 96×24
$
name: Jeff Bilder
role: DevOps Manager · Cloud & Infrastructure Leader
focus: multi-region AWS / GovCloud / Azure, automation, secure delivery
status: operational ✓

I design, automate, and secure
cloud infrastructure at scale.

DevOps and infrastructure leader helping organizations ship faster and sleep better — turning sprawling, fragile systems into automated, observable, and secure platforms, and leading the teams that run them.

cloud_architectdevops_managerinfrastructure_managersecurity_operations
$ ls ~/capabilities

What I bring to a team

Four disciplines, one operating principle: make infrastructure boring. Predictable, reproducible, and secure by default — so engineers can focus on the product, not the plumbing.

01 — cloud_architecture/

Cloud Architecture

Multi-region, multi-account estates across AWS commercial, GovCloud, and Azure — designed for scale, compliance, and clean networking.

  • Transit Gateway hub-and-spoke design
  • 26 accounts: US · EU · GovCloud
  • Terraform-baselined VPC / IAM / observability
02 — devops/

DevOps Leadership

Leading a team of 7 — and the pipelines, IaC, and Agile process that let them ship consistently. Everything peer-reviewed in Git.

  • team of 7 · Scrum on Azure DevOps Boards
  • reusable ADO YAML pipeline templates
  • IaC: Terraform, Ansible, SaltStack
03 — infrastructure/

Infrastructure & Platform

Operating business-critical SaaS at 24×7×365, on containers and auto-scaling build infrastructure, with cost kept honest.

  • ECS / Fargate / EKS container platforms
  • EC2 ASG build agents (Playwright, 1-hr SLA)
  • CloudZero multi-account cost telemetry
04 — security_ops/

Security Operations

Security and compliance built into the platform — from least-privilege IAM to STIG-hardened images, audit-ready by design.

  • IAM least-privilege audits & remediation
  • DISA STIG CAT II compliant imaging
  • SOC 1 audits · gMSA / Kerberos
$ cat stack.yaml

Tools I reach for

Opinionated, but never dogmatic — the right tool for the blast radius.

cloud: AWScloud: GovCloudcloud: Azurecloud: GCP iac: Terraformiac: Terraform Cloudiac: Ansibleiac: SaltStack ci/cd: Azure DevOpsci/cd: GitHub Actionsci/cd: OIDC federation containers: ECS / Fargatecontainers: EKScontainers: Podman net: Transit Gatewaynet: Fortinetnet: Cisco · BGP/OSPF obs: Datadogobs: Sumo Logicobs: CloudZeroobs: Grafana / ELK sec: IAM least-privilegesec: DISA STIGsec: gMSA / Kerberos data: Aurora PostgreSQLdata: Elasticsearch / Redis agile: Scrum · ADO Boards lang: Pythonlang: Bashlang: PowerShell

# swap any of these for what your org already runs — the principles travel.

$ ls -lt ~/writing

From the blog

Notes on building and simplifying the systems I work on. If I can't explain it, I don't understand it yet.

2026-05-28 Designing a GitOps Pipeline That Survives 3am gitops

$ ls ~/writing --all →

$ ./connect.sh --with jeff

Let's build something resilient.

Whether you're scaling a platform, untangling cloud spend, or hardening your security posture — I'd love to hear what you're working on.