Games development personal statement example

Why do you want to study this course or subject?

The game I am proudest of is about carrying a full mug of tea up a staircase. It began as a joke between me and a friend at college, but building it taught me more than any of my finished projects: how a single physics constraint can create tension, how players interpret wobble as risk, and how quickly a funny idea collapses if the controls feel unfair. I rebuilt the staircase layout six times before the difficulty curve stopped frustrating testers in the first thirty seconds.

That experience is why I want to study games development rather than teach myself indefinitely. I can follow tutorials and get something moving on screen, but I keep hitting the edges of what I understand. When my inventory system grew past about a dozen items it became a tangle of special cases, and I could tell the problem was my structure rather than my syntax. Reading about component-based design helped, though I want to be taught properly why certain architectures survive being changed halfway through a project.

I am drawn to the overlap between maths and feel. Working through vectors and trigonometry in A level Maths changed how I read my own code, particularly when I was trying to make a camera follow a character without making players queasy. Damping a value over time is arithmetic on paper and something oddly emotional in play. A degree that covers graphics programming, engine internals and production practice would let me work on that seriously, and the group projects matter to me as much as the technical modules, because the games I admire are clearly the result of people arguing productively about small details.

How have your qualifications and studies helped you to prepare?

My BTEC Extended Diploma in Games Development has given me a broad base and, usefully, made me work to briefs I did not choose. Units on games engines, asset production and narrative design meant I could not stay in the comfortable part of the process. For a level design unit I produced a blockout of a small warehouse map with annotated sightlines, and the written justification was harder than the building; I had to explain why I placed cover where I did rather than say it looked right.

A level Maths runs alongside, and I chose it deliberately after realising how much of my early code was guesswork. Sequences, calculus and vectors have all turned up in practice: interpolation in animation, rates of change in movement curves, dot products when I wanted an enemy to notice the player only within a cone of vision. I also take an extra qualification in programming through the college's enrichment timetable, mainly in C#, which has made moving between scripting in an engine and writing plain console programs feel less like two separate skills.

Outside the course I read around the subject steadily. Jesse Schell's The Art of Game Design was recommended by a tutor and I found its emphasis on asking questions about your own design more useful than any checklist; the idea that the game exists only in the player's experience has stuck with me. I also follow technical postmortems and developer talks, and I keep a notebook of mechanics I want to try to rebuild, which is how I ended up attempting a simple pathfinding grid from scratch before learning the library version.

What else have you done to prepare outside of education, and why are these experiences useful?

Through a college partnership I spent four supervised half-days with a two-person indie studio working on a puzzle game. I was an observer and helper: I took notes during their playtest sessions, tidied bug reports into their tracker under instruction, and tested the same level repeatedly to check a fix had held. What surprised me was how much of their week was decision-making rather than building. They cut a mechanic I liked because it needed art they could not afford, and they explained the reasoning without any drama. Seeing a small team accept constraints so calmly made the industry feel reachable rather than mythical.

At college I organise the games club's fortnightly playtesting sessions. I book the room, gather the builds students want tested, and write up the feedback into something the maker can actually use, which usually means separating what players said from what they did. Watching someone ignore a door I thought was obvious has taught me more about signposting than any article.

I work Saturdays in a bakery, on the counter and packing orders. It is busy and repetitive, and it has made me better at staying steady when several things need doing at once. I have also learned to explain things quickly to people who are in a hurry, which turned out to be good practice for presenting my work in class.

I play in a five-a-side team most weeks, which keeps me out of my room, and I have begun helping my younger cousin with her GCSE computing coursework. Explaining loops to someone else exposed the gaps in my own explanations, and I now sketch diagrams before I start talking. I would bring to a degree course a habit of finishing small things, a willingness to be tested on my assumptions, and a genuine interest in the parts of development that are not glamorous.

This example has 5,004 characters across the three answers. Use it for ideas and structure. Your own UCAS answers must fit within 4,000 characters in total, including spaces.