Get a reply from this employer
Your resume and cover letter, tailored to exactly what they’re hiring for.
Stream is seeking Staff Software Engineers to join the Chat or Activity Feeds team in Amsterdam. You will own backend systems used by thousands of developers, shaping how they’re structured and scaled.
This is an individual contributor role where you’ll write code and touch databases yourself, with leads also hands-on about 80% of the time. You’ll work with a stack including Go, Python, PostgreSQL, Redis, Kubernetes, and more, delivering production-ready features and influencing cost, latency,
We’re also hiring Senior Engineers on these teams. If your experience fits Senior better than Staff, we’ll say so openly and talk it through with youYou’ve built backend systems at high scale and stayed long enough to live with your own decisions, good and bad. You care about how a system is structured, not only the next feature, and you can explain your trade-offs to the people who’ll live with them. Maybe you led a team for a few years and chose to go back to hands-on workExtensive backend engineering experience, including technical leadership on systems in productionProficiency in Go, Python, or in another backend language plus the willingness to switch to GoExperience building features used by a large number of users, and scaling them as usage growsExperience building public APIs or SDKs that other developers useHands-on experience with Redis or a similar in-memory data storeStrong experience with a relational database. We use PostgreSQL, but any relational database countsGood written and spoken English. It’s our working languageComfort with infrastructure and database work as part of your normal week, including KubernetesDon’t worry if you haven’t used every tool we run. You’ll get exposure to most of them, and you’re welcome to convince us to add your favoritesPostgreSQL in production at scale, including sharding, partitioning or large migrationsExperience improving or redesigning legacy parts of a system that’s serving live trafficGo and gRPC in production at high request ratesMessaging, feeds or other real-time systems, or message queues such as RabbitMQ or KafkaDistributed storage internals, such as Raft or RocksDBYou’ve cut infrastructure cost at a company where margins matteredExperience running workloads on GCP or AWS