We posted this a while ago on the site - but when we got a new site, it got lost in the move. Never mind, we found it in a box and have unpacked it again. So, if you missed it the first time, here it is again :)
Here at Mm, we make the server software that lets the LittleBigPlanet community play, create and share. We provide scoreboards, ratings, favourites, tags, publishing services and search indices to millions of players (tens of thousands concurrent) and millions of levels. We often serve tens of millions of HTTP requests and over a terabyte of traffic in a day.
We need someone who knows what it takes to make big services like this go fast - reliably.
You will be using the following tools and techniques to help get our server technology ready for life as a high-volume production system:
- Continuous integration – including acceptance testing and performance testing
- Automated deployment
- Automated virtual server provisioning
- Automated everything else!
- Grown-up monitoring systems
- Helping design processes that interface with various teams in Mm and Sony
You will understand the value of (and hopefully be excited by) working on internal tech like this:
- A fast HTTP server with an embedded Ruby interpreter
- An in-memory, hierarchical key-value store with on-demand indices, eventually-consistent replication and sharding
- A Ruby web framework with a NeverBlock-style calling convention to the outside world, which makes adding features easy
- A simple RPC protocol that helps us write non-blocking, distributed systems
- Telemetry processing of lots of data using MapReduce
If you think this is what you’re looking for, we’d love to hear from you!
- We have server tech written in C/C++, Ruby and Perl. If you know a few different languages and are comfortable with learning and getting productive in other languages, that’s fine.
- We’d like you to be comfortable developing in, deploying to, getting stats from and tweaking Linux.
- The server team is very small (1.5 people right now), so you’ll be making a valuable contribution to both code and culture.
- We’ll be operating an on-call rota, but our engineering practices (hopefully) keep calls to a minimum!