Senior Infrastructure Engineer

Join Stream, a leading real-time API platform, as a Senior Infrastructure Engineer. In this hands-on role, you will be responsible for designing, building, and operating infrastructure for high-scale real-time systems. You will drive Kubernetes work end-to-end, contribute to the AWS-to-GCP migration, and own cost and efficiency optimization across cloud infrastructure. You will also write production code in Go and Python, lead post-migration tuning and capacity planning, and partner with backend, video, and moderation engineers on system design and reliability targets.

• Design, build, and operate infrastructure for high-scale real-time systems handling millions of concurrent connections and billions of monthly API requests.
• Drive Kubernetes work end-to-end: cluster architecture, workload design, and migration of existing services, rather than operating clusters someone else designed.
• Contribute to the AWS-to-GCP migration, including re-architecting workloads for cost and performance rather than lifting and shifting.

• 5+ years in infrastructure, platform, DevOps, or SRE engineering, with clear depth in infrastructure over application development
• Kubernetes experience at a meaningful production scale that goes beyond operations: you have driven cluster strategy, designed workloads, or led a migration
• Hands-on in a small team: comfortable leading a project and reviewing a PR in the same week, without large-org support structures
• Active use of AI tooling in your engineering workflow: applied adoption, not familiarity
• Software engineering background: you have built systems, not only configured them. Production coding experience in Go or Python; scripting-only backgrounds are not a fit
• Demonstrated cloud cost or efficiency optimisation at scale, on AWS or GCP
• Direct experience running high-scale, high-load production systems
• Strong cloud fundamentals of networking, compute, storage, IAM and the habit of asking why a system behaves as it does rather than accepting defaults
• Experience across both AWS and GCP; cloud migration experience between providers is a strong plus
• Large-scale PostgreSQL knowledge: sharding, replication strategy, or partitioning tradeoffs, ideally self-hosted
• Familiarity with the wider stack: CockroachDB, Redis, Terraform, and a Prometheus-based observability stack
• Background with real-time systems — WebSockets, WebRTC, streaming, or persistent-connection workloads
• Prior experience at an API-first or infrastructure-enabling scaleup