Perla › Manifest › a job in gaming
Manifesting a Job in Gaming the build, then the playtest
You picture your name in the credits at launch. The actual day is a new build downloaded, a bug that's been quietly annoying the playtest group, and the small satisfaction of watching it disappear.
- A full script for a job in gaming, written in the present tense and ready to read tonight.
- Shorter versions — one for falling asleep, one for the morning, and one line to carry with you.
- How to use it: No script builds the portfolio, ships the project or gets an offer sent — that is real technical or design skill, a body of work and applications, and this page is honest about that.
- The common mistake: Picturing the finished, celebrated launch while skipping the daily grind of builds, playtests and unglamorous bug fixes that actually make a game misunderstands where almost all the real work happens in this industry.
The script
Read it slowly, in the present tense, as though it has already happened. It is written to be spoken aloud, but silently is fine.
I pull the latest build first thing and it's different from yesterday's in small, specific ways, a level tweak, a sound effect swapped, a bug someone else fixed overnight. I run through the section I'm responsible for and find the thing that's been bothering me for two days, a collision issue that only shows up in one specific corner of one specific level, and tracing it back to its actual cause feels disproportionately good for how small the fix ends up being. In the playtest session, I watch someone hit that exact corner and, this time, nothing breaks, and I don't say anything, I just quietly note it as fixed and move to the next thing on the list. A designer wants my opinion on whether a mechanic feels fair or just frustrating, and I give an honest answer based on actually playing it repeatedly, not on what I think they want to hear. There's a long conversation about whether a feature is worth the time it would take to build properly, and I argue my side plainly and accept the call that goes the other way. By the end of the day the build is a little more solid than it was this morning, because of specific, unglamorous work, not inspiration. I still love this the way I did before I worked in it, just differently now.
Shorter versions
Two for the ends of the day, and one line to carry through the middle of it.
The collision bug in that one corner is actually fixed, confirmed in today's playtest, not just hoped-fixed. The build is a little more solid than it was this morning, and the designer's mechanic got its honest answer, no softer than it needed to be. Nothing about tonight needs troubleshooting. I let the list of tomorrow's small fixes wait until tomorrow. Today's specific, unglamorous work is done, and it held.
I pull the latest build before I've properly woken up, an old habit now, curious what changed overnight. Whatever the playtest surfaces today, I'll trace it back to its actual cause rather than guessing at a fix. I am not chasing my name in a launch-day credits reel. I am doing careful, specific work that makes a game a little more solid, one bug at a time.
Someone hits the corner that used to break everything. This time, nothing breaks.
How to use it
No script builds the portfolio, ships the project or gets an offer sent — that is real technical or design skill, a body of work and applications, and this page is honest about that. Read this before a portfolio review or a technical interview, to settle into the ordinary craft of the work, the build, the playtest, the fix, rather than the fantasy of a launch, and let the actual portfolio carry its own real weight.
The mistake to avoid
Picturing the finished, celebrated launch while skipping the daily grind of builds, playtests and unglamorous bug fixes that actually make a game misunderstands where almost all the real work happens in this industry. The other failure is rehearsing a studio's approval instead of your own honest judgement about whether a mechanic actually plays well. Keep the scene in the build and the playtest, and let the portfolio carry the rest.
Questions
Do I need a specialised games degree to work in the industry?
Not always — plenty of people move in through general programming, art or design backgrounds plus a strong personal portfolio of playable work.
Is crunch really as common as its reputation suggests?
It varies significantly by studio and has been actively pushed back on in recent years, so it's worth researching a specific employer's culture directly.
What matters most in a games portfolio, quantity or quality?
Most hiring teams say a small number of polished, finished, playable pieces demonstrates more than many unfinished or rough ones.
Have this written about you
The script above is written for anyone. Perla asks about your actual situation, writes it as a present-tense narrative and reads it back to you — in a calm voice or your own, recorded once. One ritual instead of ten apps.