A complete application in a minute
Tailored resume and cover letter, ready to send.
Stream is seeking a Staff Backend Engineer to own the technical direction of Stream Video's media plane and its infrastructure. This hybrid role can be Amsterdam-based or EU remote, focusing on architecture, scalability, and cost-aware reliability of live video systems.
You will lead design, drive a roadmap for the backend, and collaborate with the Video SDK teams, infrastructure, and enterprise customers to deliver robust real-time streaming at scale.
Stream powers real-time Chat , Video , Activity Feeds , and AI Moderation for more than 1 billion end users across 4,000+ apps, from Strava and Bumble to eBay and Patreon. Our platform processes billions of API requests per month and supports applications with millions of concurrent users, while delivering highly reliable, low-latency services and a great developer experience.
We're looking for a Staff Backend Engineer to join Stream on our mission of elevating the quality of apps for billions of users globally. You'll own the technical direction of Stream Video's media plane and the infrastructure it runs on.
This is a full-time role, hybrid with 3 days a week in our Amsterdam office, or remote from anywhere in the EU.
Stream Video runs on an SFU we built in Go on top of Pion, plus ingest and recording fleets, all on a global edge network we own across more than one cloud. Nobody at Stream has owned this media plane end to end before. Our central infrastructure team is tuned for request-based services, and video breaks in different ways: live sessions can't be dropped, bandwidth is the biggest cost, and placement is the main lever. That's why this is a Staff role. You'll set the direction for the video backend and its infrastructure with your own roadmap, reporting to our Director of Engineering with a direct line to our CTO. The Video SDK teams own the client side, and you'll work closely with them and with infrastructure. Part of the fleet is mid-move to Kubernetes.
You've owned systems where a dropped session or a bad rollout is visible to users within seconds, and you think about cost and reliability as much as features. You'd rather write the hard design doc than wait for one. A founder background is an asset here. The team is small, so you'll still write and review plenty of code. If you're looking for a large organisation with a platform team to hand problems to, or a management track, this role won't suit you.
We're a Series B company with offices in Boulder, Amsterda