- Reading time: 3 minutes
- Price: Free download
- Published: 17th September 2026
- Word count: 888 words
- File format: Text
Why do you want to study this course or subject?
The first game I made was a top-down maze game where the walls moved. It played badly, but taking it apart taught me more than finishing it would have: my collision checks were running against every wall in the level on every frame, and once I split the map into a grid and only tested nearby tiles, the frame rate stopped stuttering. That moment, when a bit of structure turned something sluggish into something responsive, is why I want to study games programming rather than art or design. I am interested in the machinery underneath play, and in the fact that a player feels a decision about data layout as smoothness or lag.
What draws me to a degree specifically is the parts I cannot teach myself well from tutorials. I can follow instructions to make a character jump; I am much shakier on the mathematics of rotation, on physics solvers, or on why one approach to memory use beats another on a console with a fixed budget. I want to work in C++ alongside the C# I already know, understand graphics pipelines properly instead of treating shaders as recipes, and learn to write code that other people can read and extend. I am also interested in how gameplay code is tested, since bugs in my own projects usually appear in the parts I was most confident about.
Longer term I would like to work on gameplay or engine programming in a studio, or in simulation and interactive software where similar skills apply. Studying in an environment with deadlines, code reviews and other people's projects to compare against feels like the right way to get from hobbyist to someone employable.
How have your qualifications and studies helped you to prepare?
My A-levels in Maths, Computer Science and Physics support this course closely. Maths has been the most directly useful: vectors and trigonometry appear constantly once I started moving objects in two and three dimensions, and I only really understood the dot product when I used it to work out whether an enemy could see the player. Calculus has changed how I think about movement, because acceleration and velocity stopped being formulas to recall and became variables I was tuning.
Computer Science gave me the vocabulary for things I had been doing badly by instinct. Learning about data structures explained why my inventory system, built on a long list I searched from the start each time, slowed down as it filled up. The course also involves a programming project, and mine is a small 2D platformer with a tile-based level editor, which has forced me to think about file formats and saving data rather than just gameplay. Writing the documentation was harder than writing the code.
Physics has been useful for intuition about forces, friction and energy, and for the discipline of estimating whether an answer is sensible. It has also made me more careful about units and sign conventions, which is a surprisingly common source of bugs in game code.
Outside the syllabus I have worked through online material on C++ and read parts of Jason Gregory's Game Engine Architecture, which gave me a clearer picture of how the pieces of an engine fit together and how much of a game is tooling rather than gameplay. I am aware I have only scratched the surface of it.
What else have you done to prepare outside of education, and why are these experiences useful?
Most of my practical experience comes from my own projects. My current one is a small puzzle game about redirecting light beams through mirrors, which I have rebuilt twice: the first version tracked each beam as a physics object and became impossible to debug, so the second traces the path mathematically each time something moves. It is not finished, but the level loading, the mirror rotation and the win condition all work, and a friend played it for twenty minutes and found two bugs I had missed.
I took part in a weekend game jam run online, working with two people I had not met before. I was responsible for player movement and the camera, which sounds small but took the whole first day to feel right. We submitted something playable, and the clearest lesson was about agreeing early on how our code would talk to each other, since we wasted an hour reconciling two different ideas of where the player's state should live.
At college I help run a lunchtime coding club for younger students, mainly setting up small tasks in Python and helping when things break. Explaining why an error message is actually helpful has improved my own debugging habits considerably.
On Saturdays I work in a garden centre, serving customers and handling stock checks. It has taught me to stay organised when several things need attention at once and to keep a civil tone when a query takes longer than expected. I also play in a local badminton league, which gets me away from a screen and is a useful reminder that improvement comes from regular practice rather than occasional bursts of enthusiasm.
This example has 4,756 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.
Why this example works — strengths and ways to improve
This is a well-grounded games programming statement. Its best evidence comes from small technical problems you solved and explained clearly, and the tone stays honest about your current level. The main task is cutting about 760 characters to meet the 4,000 limit. Trim the weaker general material rather than the precise technical reflection that makes the draft convincing.
Subject motivation
once I split the map into a grid and only tested nearby tiles
Your motivation rests on a real technical moment rather than a claim of passion. You show that performance problems are what interest you, then explain why this points to programming rather than art or design. The list of things you cannot teach yourself turns curiosity into a clear reason for studying a degree.
Academic preparation
I only really understood the dot product when I used it
Each A-level is linked to a concrete use: vectors for line of sight, data structures for the slow inventory, and physics for units and sign conventions. The Gregory reading is the thinnest part. Naming one idea from it that changed how you approached a project would make it as strong as your coursework evidence.
Evidence and reflection
the first version tracked each beam as a physics object and became impossible to debug
This is genuine reflection. You explain the failed design, why it failed and what replaced it. The friend finding two bugs supports your earlier point about testing without overclaiming. The project is unfinished, but you are explicit about what works, which keeps the evidence credible.
Relevant experience
we wasted an hour reconciling two different ideas of where the player's state should live
The game jam lesson is specific and useful because it shows you learning about code interfaces in a team. The coding club point is also well reflected. The garden centre and badminton paragraph relies on generic skills such as staying organised and practising regularly, so it adds little for this course.
Credibility and voice
I am aware I have only scratched the surface of it.
The voice sounds like a capable school student, not a professional. You admit gaps in your knowledge of rotation maths, physics solvers and memory use, and this modesty makes your stronger claims more believable. The prose is plain and economical, so you can cut without needing to change the style.
Structure and format
This example has 4,756 characters across the three answers.
Each answer clears 350 characters easily and covers distinct ground, apart from slight overlap between the platformer and puzzle projects. However, the total is roughly 760 characters over the 4,000 limit, so this version cannot be submitted. Cutting to about 3,900 characters would meet both the UCAS limit and the library's 3,500 minimum.
What you’ve done well
- The technical examples, such as grid-based collision, the linear inventory search and mathematical beam tracing, show real problem-solving with clear cause and effect.
- You candidly identify what you cannot yet do. This gives a credible reason for wanting a degree and avoids sounding like a professional.
How this draft could improve
- Cut most of the garden centre and badminton paragraph, or reduce it to one sentence, to recover much of the 760 characters you need to lose.
- Trim the career paragraph in answer one and the general opening sentence about your A-levels, both of which repeat points made elsewhere.
- Replace the general comment about Game Engine Architecture with one specific idea from it that you applied or questioned in your own work.