Staff Software Engineer, Infrastructure

Stream

Where
Hybrid in Amsterdam office

Posted 45 days ago· Checked live at Stream 59 minutes ago

Stale: open 45 daysUp for more than two weeks. It may already be filled.

See how you score for this job

One sentence and your resume. We score it against what Stream asks for, line by line.

See my score
Is this job still open?
Yes. We checked it live on Stream's own hiring page 59 minutes ago.
What is the job?
We are hiring a Staff Software Engineer for our Infrastructure team. Stream runs behind apps that more than a billion people use: billions of API requests a month, a 99.999% uptime promise, and a small team keeping it all running. Infrastructure here decides how fast our products feel, how well they scale, and how quickly we can launch new ones.
What does it pay?
The posting doesn't say.
Our verdict
Stale. Up for more than two weeks. It may already be filled.

What the job is

We are hiring a Staff Software Engineer for our Infrastructure team.

Stream runs behind apps that more than a billion people use: billions of API requests a month, a 99.999% uptime promise, and a small team keeping it all running. Infrastructure here decides how fast our products feel, how well they scale, and how quickly we can launch new ones.

What you will do

  • Define what "good" looks like for the platform. Set latency and uptime SLOs for every product team, and decide what we measure, from error rates and delivery times to how healthy our customers' apps really are.
  • Make the big infrastructure calls. Lead the design reviews and decisions on where and how we run, working with backend, video and moderation engineers on tradeoffs that cross service boundaries.
  • Build the platform tooling. Write the internal tools and services that help engineers ship, deploy and debug faster, plus the docs and AI skills that make launching a new product repeatable.
  • Turn incidents into fixes that stick. Take part in on-call, and make sure every root cause ends in a durable fix, not a workaround.
  • Make cost part of every design. Weigh cost alongside reliability in every decision, and give teams the numbers to do the same.

What we are looking for

  • A software engineer who has built systems, not only configured them. You write production code in Go, Python or a similar language. Scripting-only backgrounds are not a fit.
  • Strong system design. You can reason about failure modes, capacity and cost in distributed systems, and explain why you chose what you chose.
  • Solid fundamentals in networking, storage and concurrency, and the habit of asking why a system behaves the way it does instead of accepting the default.
  • You have owned high-scale production systems and set technical direction beyond your own work, through design reviews, RFCs and decisions other engineers build on.
  • You experiment. When you hit Kubernetes, a database or a cloud service you have not run before, you dig in, use AI to close the gap, and ship.
  • You already use AI tools every day in your engineering work.
  • You treat cost and reliability as engineering problems, and you can put a number on an outcome you drove.
  • You write clearly. Much of this role is docs and standards that other teams will follow.
  • You are comfortable in a small team, setting direction and reviewing a PR in the same week.

Nice to have experience

  • Kubernetes in production: cluster architecture, workload design or a migration you led.
  • PostgreSQL at scale, ideally self-hosted or with CloudNativePG: sharding, replication, partitioning tradeoffs.
  • Valkey or Redis at scale, ideally on Kubernetes.
  • Hands-on AWS and GCP, including multi-cloud setups or migrations between providers.
  • Cloud commitment and reservation strategy (committed use discounts, savings plans), or formal FinOps practice.
  • SLO design, alert hygiene and a Prometheus and Grafana based observability stack.
  • Real-time systems: WebSockets, WebRTC, streaming or other persistent-connection workloads.
  • Open source contributions, or writing and talks on cloud, platform or distributed systems.

Why join stream?

We're a Series B company with global presence and a team of around 145 people from more than 35 countries.

We're backed by Felicis Ventures, GGV Capital, 01 Advisors, Techstars, and Arthur Ventures, with angels including Dick Costolo (ex-CEO of Twitter), Olivier Pomel (CEO of Datadog), Tom Preston-Werner (co-founder of GitHub), and Nicolas Dessaigne (co-founder of Algolia).

We'll be straight with you: a startup is more demanding than a large company. There's no fixed playbook, you'll own things end to end, and you'll sometimes pick up work outside your title. That's also what makes it a fast place to grow. If you want real ownership and high scale more than structure and a set career ladder, you'll feel at home here.

Hybrid office policy: applicants based (or relocating to) one of our office locations are expected to work according to the applicable local office attendance policy.

Equal opportunity employer statement: Stream provides equal employment opportunities to all employees and applicants for employment and prohibits discrimination and harassment of any type without regard to race, color, religion, age, sex, national origin, disability status, genetics, protected veteran status, sexual orientation, gender identity or expression, or any other characteristic protected by federal, state or local laws.

This policy applies to all terms and conditions of employment, including recruiting, hiring, placement, promotion, termination, layoff, recall, transfer, leaves of absence, compensation and training.

Note for external recruiters: We currently have this role covered and do not accept unsolicited agency resumes. We are not responsible for any fees related to unsolicited resumes.

Similar open jobs

Software engineer jobs in Toronto (191)Software engineer jobs in Amsterdam (15)Jobs in Toronto (825)Jobs in Amsterdam (92)