I'm a recent computer science graduate, but most of my practical programming experience has been self-taught. I understand the fundamentals and can follow professional code reasonably well, yet I struggle to design and write larger applications myself.
I've spent more than eight years making games with GameMaker Studio and have a portfolio of personal projects, but I'm having trouble applying for jobs outside game development. Many listings mention technologies such as Node.js, .NET, Linux, databases, cloud platforms, Kubernetes, Terraform, and Ansible. I've touched some of these through school or experimentation, but I don't have professional experience and often get stuck after introductory tutorials.
I also feel discouraged by job postings that require experience, security clearances, certifications, or industry-specific tools that seem impossible to obtain without already having a job. Even though I have a bachelor's degree and experience teaching programming, I'm unsure how competitive that makes me.
What would be the most practical way to build the missing experience and move beyond beginner-level programming, especially when transitioning from game development to web or enterprise software?
4 Answers
That listing looks more like a mid-level or specialized position than a realistic new-graduate target. Look specifically for junior and new-grad roles where a degree, internships, or a project portfolio are the main requirements. You can also consider adjacent technical roles, such as support or operations, and move internally later. Keep using university career services, but broaden the companies and job titles you’re targeting.
Your main gap may not be programming fundamentals; it’s that nearly all of your shipped work is game-related. Build one deliberately boring application from end to end: authentication, a CRUD interface, an API, a relational database, tests, deployment, and basic documentation. It doesn’t need to be original. Completing the whole lifecycle will teach you more about professional software than repeatedly watching beginner tutorials.
Your game-development background is still valuable, but employers for enterprise roles need evidence that you can work with their common patterns. Build a full-stack CRUD project using Node.js or .NET and a relational database, then deploy it. Learn the basics of Git workflows, testing, logging, configuration, and Linux administration along the way. You don’t need to learn every item in a long ‘nice to have’ list; focus on one coherent stack and be able to discuss the decisions you made.
Don’t learn tools just because they appear in a job listing. Pick a concrete problem and build something that requires the tools you want to learn. For example, you could add player statistics to one of your games by creating a .NET or Node.js API, storing the data in a relational database, and deploying it on Linux. That gives you a reason to learn the technology and a project you can explain in interviews.
That makes sense. I’ve applied to some adjacent positions and used my university’s job resources, but I haven’t had much luck so far. I’ll try narrowing my search toward genuinely junior postings instead of trying to meet mid-level requirements.