| > Do you mind me asking how you got into server software engineering for a video game? Honestly, it was just chance. My first job out of university was at a smaller studio, and they needed a junior to help out on the backend. That being said..."be lucky" isn't very useful. Some more useful info: there are a few different things one can do on the backend of a multiplayer game. There's the core game replication logic, there's web server/matchmaking/database work, or just infrastructure management type of work. I think core game server work is the most specialized. For an authoritative server, it's the kind of work where you write the game server's simulation of the game and replicate it to all the clients. Games can also be peer-to-peer, but I don't have any experience in that area. The people I know who excel in this area have strong math and computer network skills. A book like "Multiplayer Game Programming: Architecting Networked Games" is an example of problems in this space. Web server application work is what I do. Includes work like writing matchmaking services, authn & authz, robust purchasing flows (both in game and real money transactions), retrieving/storing database state. I think someone could break into video games if they have previous experience doing web server development, even if they haven't necessarily solved the same types of problems. I've worked with people who had web server experience outside of games. Infrastructure work is exactly that. Involves the usual sort of work like IaC, CI/CD, cloud providers like AWS, Azure, GCP. Sometimes they're called dev ops engineers. > how is the work-life balance. It really depends on the company & the team. The places I've worked highly value work life balance and reject crunch culture. There have been some late nights to solve an outage or hit a deadline, but those have been far and few between. I think probing about it at the interview stage and reading reviews about the company on sites like glassdoor are the best way to avoid the hellscapes. |