Senior Software Engineer, Stream

• 5+ years in infrastructure, platform, DevOps or SRE engineering, with clear depth in infrastructure over application development
• A 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
• Kubernetes at meaningful production scale, past operations: you have driven cluster strategy, designed workloads, or led a migration, and you have tuned what came out the other side for cost and efficiency
• Cloud cost or efficiency optimisation you personally led on AWS or GCP, with an outcome you can put a number on. FinOps practice is a plus
• Direct experience running high-scale, high-load production systems
• Strong cloud fundamentals across networking, compute, storage and IAM, and the habit of asking why a system behaves the way it does instead of accepting the default
• Comfortable in a small team: leading a project and reviewing a PR in the same week
• AI tooling already in your engineering workflow. Applied use, not familiarity

Desirable

• We are hiring a Senior Software Engineer to help rebuild the platform underneath Stream
• Over the next year the infrastructure team is moving from AWS to GCP, moving onto Kubernetes, and relocating 35 to 40 Postgres shards off managed RDS to self-hosted, while the platform keeps serving billions of API requests a month
• You will own parts of that outright
• This is a small, senior team without the support structures of a large organisation
• You will write code most of the time and make infrastructure calls on your own
• Success looks like systems that scale predictably under load, cloud spend that falls per unit of traffic, and migrations that land without incident
• Design, build and operate infrastructure for real-time systems carrying millions of concurrent connections and billions of monthly API requests
• Drive Kubernetes end to end: cluster architecture, workload design and the migration of existing services. You will be designing clusters, not operating someone else's
• Re-architect workloads as part of the AWS to GCP migration, for cost and performance rather than a lift and shift
• Own cloud cost and efficiency work: find the levers, measure them against real spend and utilisation data, and show what moved
• Write production Go and Python: internal services, platform tooling and automation that change how product and SDK engineers deploy, observe and debug
• Lead post-migration tuning and capacity planning, closing the loop between the architecture you chose and what production actually does
• Work with backend, video and moderation engineers on system design, reliability targets and tradeoffs that cross service boundaries
• Take part in on-call, incident response and root cause analysis, and turn what you find into durable fixes
• ---Our stack---
• Go, gRPC, RocksDB, Python
• PostgreSQL, RabbitMQ
• GCP
• Grafana, Prometheus, ELK (Elasticsearch and Kibana)
• Jaeger and Tempo for distributed tracing, Datadog
• Redis, Memcached
• Claude Code, Cursor