At Twitch, we transfer more petabytes every month than you can count on both hands and a foot. That means tackling a complex distributed systems problem: how do you get the right video streams to the right servers in the right datacenters quickly and efficiently? What happens when a stream that has been getting around 50 viewers gets embedded on a huge website and suddenly has 50,000 viewers? If a viewer asks for a stream available at many different servers, how do you decide which server is best to send them to?
If you eat thundering-herd problems for breakfast, if you think handling data by the terabit per second sounds kind of neat, if you've ever asked yourself "but what if we lose one of the backbone links?" then we need you to come scale our system up the next order of magnitude.
Qualifications:
- You know a lot of languages and you’re comfortable learning new ones quickly.
- You have strong opinions o! n what makes a language good, but at the end of the day you’re a pragmatist and you’ll use whatever it takes to get the job done.
- You're constantly thinking, "That would be a great feature to add to..."
- You know Linux. You wouldn’t be uncomfortable if someone suggested you spend a few hours digging around /proc to see if you can squeeze a bit more performance out of the tcp stack.
- You know how the web works, at least from HTTP to HTML. You probably need to look up the details, but you know if you needed to, you could figure out everything from cache-control headers to why something isn’t rendering properly. You don't just use open source, you've contributed bug fixes or features back. Or even better, you have your own project.
Benefits: Competitive salary (including equity), full medical & dental, catered lunch & dinner, biweekly massages, gym mem! bership, onsite haircuts, fun team events, whatever design too! ls you desire, as many monitors as you can fit on your desk.
Twitch is a Y-Combinator company. We're based out of San Francisco, CA.
Apply for this job vacancy
No comments:
Post a Comment