How Can I Move From Game Development to Professional Software Engineering?

Your main gap probably isn’t basic programming—it’s that your experience is concentrated in games. You’ve already shipped projects, which is valuable, but employers hiring for web or enterprise roles may not see evidence of APIs, databases, testing, deployment, or maintainable application structure. Build one deliberately boring CRUD application end to end. A polished, documented project is more useful than ten unfinished experiments with different frameworks.

That job posting looks aimed at someone with several years of specialized industry experience, not a typical new graduate. Many postings list an enormous collection of preferred qualifications, so don’t treat every line as a requirement for your first role. Focus on graduate and junior positions that ask primarily for a degree, basic programming ability, and perhaps internship or project experience. Your university’s career resources can still help, but you may need to apply broadly and expect a slow market.

The best way to learn these tools is to use them to solve a problem instead of completing disconnected tutorials. For example, build a small service related to one of your games: a Node.js or .NET API that records player statistics, stores them in a relational database, and runs on Linux. Add authentication, tests, documentation, and a simple deployment. That gives you a concrete reason to learn each piece and creates a project that demonstrates more than another tutorial clone.

You can also consider adjacent roles at technology companies, such as technical support, QA automation, tools development, or build and release support. These can provide exposure to Linux, scripting, databases, and team workflows, making a later move into development easier. Keep applying to junior programming roles too, and present your game work in terms of transferable skills: debugging, version control, project ownership, iterative development, and shipping software.