One team across two cities, one repo, three hours between the desks. We ship every week to three quarters of a million players, and the boring parts are held by agents so the hours go on the parts that are not.
Every one of them ships to players who are already here. This is the week that comes with it.
Mobile, real time, backend, LiveOps. People who ship to production weekly and treat the release history as the résumé.
A week in this seat
- MonPick up the week's branch. The agents have already walked the last build and filed what broke.
- TueShip something a player can see. Small, whole, behind a flag if it needs one.
- WedSit in the console with an operator and watch your feature get used by someone who did not read the spec.
- ThuCut the release, walk it yourself, hand it to the QA that never sleeps.
- FriRead what your change moved, and write down the one thing you would do differently.
What we look for
- Production code in a live product, not a portfolio of prototypes
- Comfort with real-time and with other people's players
- An opinion about latency, and one about Arabic layout
Every engineer here works with agents that hold the keys to our systems. Ops, QA, catalogue and economy review run without us, so the team spends its hours on judgement.
agentsthe repetitive passes, the watching, the first draft
peoplewhat to build, what to charge, what to cut
youwhichever of those you are better at than we are