GAME DEVELOPER CAREER PATH: FROM HOBBY TO STUDIO

The game developer career path doesn't look like other career paths. There's no clean ladder. There's no obvious next rung. There's a confusing tangle of options that all claim to be the right one, and most of the people giving advice are pointing toward the path they happen to be on.

I've been making games long enough to watch friends take every route. Some went AAA and never looked back. Some went indie and ate ramen for three years. Some did the day job hybrid and shipped nights and weekends until they could afford to quit. None of them are wrong. All of them made trade-offs that the others wouldn't accept.

This is the honest version of the game developer career path, written by someone who has actually thought about which direction to go and why.

The traditional studio path

The classic path starts as a junior at a studio. AAA if you can get in, AA or mid-size if you can't, mobile or work-for-hire if those doors are also closed. You take what's offered because the goal at this stage isn't your dream job. The goal is shipping credits.

Junior roles are usually narrow. You're a junior gameplay programmer working on one system. A junior environment artist making props for one biome. A junior QA tester running through the same level for the eighth time today. The work is constrained and often tedious, but you're learning how a real production works. Source control discipline. Code review. Asset pipelines. The thousand small processes that separate a hobbyist project from a shipped game.

After two or three years, if you're competent and you don't burn out, you become a regular dev. Mid-level. The training wheels come off. You own systems instead of tasks. You mentor the next juniors coming in. Your salary jumps because the market values shipped credits more than potential.

Five to seven years in, senior. Now you're owning entire features. You're in design discussions. You're influencing direction instead of just executing it. The salary jumps again. This is where a lot of devs stop and stay forever, because senior pays well and the responsibility is bounded.

Past senior, the path forks. Lead is a management track. You're running a team of five to ten devs. You're in meetings most of the day. You're doing less hands-on work and more unblocking other people. Some devs love this. Some hate it and bounce back to senior individual contributor roles.

The other fork is principal or staff. This is the technical IC track. You stay in the code. You solve the hardest problems. You set technical direction across multiple teams. The pay is comparable to lead but the day-to-day is completely different. Studios that have this track are great. Studios that don't force everyone into management whether they want it or not.

Beyond that, you're looking at director, studio head, or starting your own studio. By this point you've been in the industry fifteen years and you know what you actually want.

What AAA actually looks like

AAA gets sold as the prestige path. You work on big games. Your name is in the credits of titles that millions of people play. Your salary is solid and your benefits are real. There's a reason people aim for it.

The trade-off is creative compromise. You don't pick the games you work on. You don't pick the features. You execute someone else's vision, and that vision is shaped by marketing, executive priorities, and franchise constraints. If you're a gameplay programmer at a studio making the next yearly sports release, you're tweaking systems that have existed for fifteen years. The creative ceiling is low because the brand can't risk too much innovation.

The other AAA reality is crunch. Some studios have genuinely cleaned up. Some still grind their teams into the floor for the final six months of every project. You don't always know which one you're joining until you're inside, and by then you've signed the lease on the apartment near the office.

Then there's the layoff cycle. The 2023-25 stretch was brutal. Tens of thousands of devs got cut, including from studios that had just shipped successful games. Embracer, Microsoft, Unity, Sony, EA, every name in the industry. Profitable projects didn't protect anyone. Veteran devs with twenty years of credits got walked out the door. The lesson nobody wants to internalize is that AAA stability is a story the industry tells itself, not a reality.

The indie path

Indie is the other end of the spectrum. You make your own games. You set your own scope. You pick the engine, the art style, the tone, the marketing strategy. Everything is your call.

The starting point isn't building a studio. It's building a portfolio. Game jams. Itch.io releases. Small finished projects that prove you can ship. Nobody funds an unproven indie. Nobody publishes one. You get into the indie world by demonstrating that you can take an idea from prototype to released game without falling apart in the middle.

If you want a real picture of how rough the early days are, my solo game development lessons post is the most honest writeup I have on what the first few years looked like for me. It's not the version that gets posted on Twitter.

After the portfolio comes contract work for a lot of indies. You take freelance gigs to pay rent while building your own thing. Asset packs, plugins, port work, contract programming for other indies who got funded but need extra hands. The contract money keeps the lights on while your real project incubates.

Eventually, if things go well, you ship something commercial. Steam release. Maybe a publisher. Maybe self-published with savings. The first commercial release is rarely the breakout. Most indies don't have a breakout at all. They have a steady catalog of small games that collectively make a livable income.

Going full indie usually means surviving on a mix of revenue from older games, contract work, Patreon, YouTube, and whatever new project you're shipping. It's not one income stream. It's five small ones stacked together.

What indie actually looks like

The freedom is real. Nobody tells you what to make. Nobody tells you when to stop. You wake up and work on the project that excites you, in the engine you prefer, with the art style you love. The creative ceiling is whatever you can imagine.

The financial uncertainty is also real. Most indie games don't make back their development time at minimum wage rates. The median Steam release earns under a thousand dollars in its first year. The successful indies you've heard of are statistical outliers, and even they often had a previous failed game or two that nobody talks about.

Health insurance in the US is a separate nightmare. You're paying for it yourself. Retirement savings is on you. Sick days don't exist. Vacation means your income stops. The studio benefits package that AAA devs grumble about looks pretty different when you're staring at a marketplace plan that costs more than your rent.

Burnout hits indies harder because there's no boundary between work and life. The studio at least sends you home at some point. When you're indie, the studio is your apartment, and there's no one to tell you that twelve hours of debugging a save system isn't actually a healthy workday.

The cost reality is brutal once you actually add it up. Engine subscriptions, asset purchases, marketing, the year of lost income while you build, the Steam fee, the legal stuff if you incorporate. The numbers stack faster than people expect.

The hybrid path

The hybrid is the most honest path for most people, and the one almost nobody recommends because it's not glamorous.

You keep a day job. Ideally one that's adjacent to game dev so the skills transfer, but any stable income works. Software engineering jobs outside of games are the most common. Web dev, backend, mobile apps, embedded systems. The pay is comparable to or better than AAA games, the layoff risk is lower, and the work-life boundary is usually saner.

Then you make games on the side. Nights, weekends, the precious slivers of time you can carve out. You ship small projects. You build a portfolio. You release on itch and Steam. The pace is slower than full indie, but the financial pressure is zero. You're not making this game to pay rent. You're making it because you want to make it.

Some people do this for their entire career. They build a back catalog over a decade, make a steady side income from it, and never once worry about whether their next game has to hit. Other people do it for five years until their side income matches their day job, then jump to full indie with a real safety net.

The downside is exhaustion. You're doing two jobs. Your weekends are work. Your relationships need to tolerate it or they don't survive it. Not everyone has the personality or the support system for it.

The upside is option preservation. You can ship without panic. You can take a year off from game dev if you need to. You can quit and go full indie when the moment is right, instead of when desperation forces it.

The skills that matter at every stage

Programming is the floor. You don't have to be a senior systems engineer, but you need to write code that works. Even artists and designers benefit from being able to script behaviors and understand how their assets get used.

Pick one specialty beyond programming. Pure generalists struggle to stand out in a market full of generalists. Pick gameplay programming, or technical art, or shader work, or audio implementation, or level design, or narrative design. Become known for that thing. Generalists who are also specialists in something get hired faster than pure generalists.

Networking is the skill that programmers especially underestimate. Every job I've seen filled, AAA or indie contract, came through someone knowing someone. Discord servers for your engine of choice. Local IGDA chapters. GDC if you can afford it, even if just for the off-site bar conversations. The IGF and Indie MEGABOOTH alumni network. Twitter while it still functions for game dev. The people you know are the pipeline through which work flows.

Shipping over polishing is the trait that separates working game developers from people who would like to be working game developers. The portfolio of someone who finished six rough projects beats the portfolio of someone who has been refining one masterpiece for three years. Done is the skill. Done is the deliverable. Done is what proves you're a developer instead of someone who started a project.

How the layoff cycles change the math

The 2023-25 layoff cycle changed how I think about the AAA path. Not because AAA is dead, but because the assumption that AAA equals stability has been thoroughly disproven. A senior dev with twelve years at a studio can get cut on a Tuesday. The institutional loyalty doesn't run both directions.

What this means for career planning is that you need a personal moat. A side project that could become commercial. A network that could find you contract work in a week. A specialty that's hard to replace. Savings that buy you six months of runway. Something that's yours, not the studio's, so that when the studio decides you're not theirs anymore, you have something to land on.

The hybrid path looks much better in this light. So does the indie path with multiple income streams. The pure AAA dependency, where your entire financial life rests on one studio's continued employment, is the riskiest position the industry currently offers, even though it looks the safest from the outside.

If you're at the very start and trying to figure out what direction to even point in, the actual first steps come before any of this career math becomes relevant. You can't strategize a career you haven't begun yet.

The version of advice I wish I'd gotten

Pick the path that matches your risk tolerance and your life situation, not the one that looks coolest in interviews. AAA isn't more legitimate than indie. Indie isn't more authentic than AAA. The hybrid isn't a compromise. They're different paths with different trade-offs, and the right one for you depends on what you actually want from your work.

Don't quit your day job to go indie until you have at least a year of expenses saved and a portfolio that's already earning something. Romance about ramen years usually comes from people who survived them. Plenty didn't.

Don't take an AAA job assuming it'll be stable. Treat every employer as temporary. Build the moat in parallel.

Don't underestimate the hybrid path because it's not the dream. The dream is making games for a living. The hybrid lets you do that with less existential dread, and existential dread is genuinely bad for the games you make.

The career path isn't a ladder. It's a map with three roads, and you can switch roads more than once. The people who do this for thirty years usually have. Pick a direction, start moving, and adjust when you learn something new about yourself or the industry.

That's the whole secret. The map looks complicated because it is. But you only have to walk one step at a time.