Senior DevOps Engineer

Manage cloud operations across Google Cloud, Alibaba Cloud and AWS: provisioning, upgrades, capacity and the full resource lifecycle, including rightsizing and releasing unused resources.

Run, upgrade and scale Kubernetes clusters, keeping them on supported versions and designing node pools, autoscaling and Spot capacity.

Operate the blockchain node fleet — validator, sentry, seed, RPC and archive nodes — including peering topology, snapshots, sync and client upgrades.

Handle networking and edge infrastructure: VPC design, load balancers, DNS, Cloudflare Workers, Tunnels and WAF, keeping internet egress deliberate and cheap.

Define every environment as infrastructure as code using Terraform or Pulumi, and design and run CI/CD on Jenkins or an equivalent (GitHub Actions, GitLab CI), covering builds, tests, security scans and releases from commit to production with no manual steps.

Maintain observability and on-call practices: metrics, logs, alerts, dashboards and control of metric cardinality, plus incident response and postmortems.

Enforce security and access controls: least-privilege IAM across every provider, secrets management, and no databases or admin ports exposed to the internet.

Manage cost: billing exports, budgets and alerts, tagging, monthly cost reviews and commitment planning.

Support developer enablement through templates, preview environments, documentation and help for engineers shipping on the platform.

5+ years in DevOps, SRE or platform roles, including 3+ years running production Kubernetes and owning CI/CD pipelines.

Deep Kubernetes experience: zero-downtime control plane and node pool upgrades; scheduling (requests/limits, affinity, taints and tolerations, priority, eviction); autoscaling via HPA, cluster autoscaler or Karpenter, plus Spot/preemptible pools; in-cluster networking (CNI, Services, Ingress or Gateway API, network policies, DNS); security practices (RBAC, Pod Security, workload identity, proper secrets handling); stateful workloads (StatefulSets, persistent volumes, CSI drivers, backup/restore); packaging via Helm or Kustomize, ideally with GitOps (Argo CD or Flux); and debugging failing pods, nodes or rollouts.

Strong CI/CD experience: building and running production pipelines on Jenkins or equivalents (GitHub Actions, GitLab CI, CircleCI, Tekton) defined as code with shared libraries and templates; operating CI platforms (Jenkins controllers with ephemeral agents on Kubernetes, or self-hosted runners), including upgrades, credentials and scaling; building multi-service/monorepo pipelines with caching, parallel stages and versioned artifacts; building container images with Docker, BuildKit or Kaniko, including multi-arch builds, scanning, SBOMs and signing; managing deployment pipelines with promotion stages, approvals, gates, blue-green/canary releases and rollback, GitOps, and database migrations as part of release; running infrastructure pipelines (Terraform/Pulumi plan and apply from CI) with policy checks and drift detection; securing pipelines with short-lived credentials (OIDC or a secrets vault), least-privilege deploy roles and protected branches; handling release engineering for the chain, including building and publishing node binaries/images and coordinating rolling upgrades across validator and RPC fleets; and tracking delivery health metrics (build time, cost, flaky tests, DORA metrics) while reducing wasted builds.

Solid networking fundamentals: TCP/IP, subnetting and CIDR, routing, NAT, L4 vs L7 load balancing, DNS, TLS and certificates, firewalls and security groups, VPC design and peering, private endpoints, and troubleshooting with dig, curl, mtr and tcpdump, along with an understanding of egress costs.

Production experience with at least two of Google Cloud, AWS and Alibaba Cloud, with willingness to quickly learn the third.

Production experience with Terraform or Pulumi, plus scripting in Bash and in Python or Go.

A track record of reducing cloud costs through data-driven rightsizing, cleanup or commitment planning.

A security-first approach to handling production credentials, and clear written communication.