- Reading time: 3 minutes
- Price: Free download
- Published: 17th September 2026
- Word count: 770 words
- File format: Text
Why do you want to study this course or subject?
The part of my A level Computer Science course that stayed with me was pathfinding. We were given a grid with obstacles and asked to get from one square to another, and I was surprised how quickly a breadth-first search became unusable as the grid grew. Adding a simple straight-line estimate of the remaining distance, as A* does, cut the number of squares examined dramatically without giving up the shortest route. What interested me was not the code but the idea that a good guess, used carefully, can be more valuable than more computing power. That is roughly the question I want to spend three or four years on: how a system can act sensibly when it cannot check every possibility. Reading parts of Russell and Norvig's Artificial Intelligence: A Modern Approach in my school library showed me how much of the field sits on that foundation, and how much of it is mathematics rather than clever programming. Constraint satisfaction, probability and optimisation all appeared long before anything resembling the neural networks that get the attention online. That made the subject more appealing, not less. I want a degree that treats intelligent systems as engineering with proper theory underneath, covering search, machine learning, robotics and the awkward questions about what happens when a system's confident output is wrong. I am also drawn to the practical side: intelligent systems only matter once something physical or useful depends on them.
How have your qualifications and studies helped you to prepare?
Mathematics is the subject I work hardest at and enjoy most. Matrices, vectors and sequences have already turned up in my computing work, and learning to differentiate made gradient descent make sense when I met it later: the method is just following the slope downhill in small steps. Statistics has been unexpectedly useful for thinking about data rather than code, particularly the difference between a pattern and a coincidence. Physics has trained me to estimate, to keep track of units and to accept that a model is an approximation with a range of validity, which I think is the right attitude to bring to any predictive system. In Computer Science I have worked in Python and a little C#, and my coursework project is a timetable-clash checker for sixth form option blocks. I began with a brute-force approach that compared every pair of subject combinations, then reduced the work by grouping subjects by block first. Writing up why the second version was faster taught me more than building it did. Alongside lessons I have been working through free online material on linear algebra and have started a short course on machine learning, where I built a k-nearest neighbours classifier on a small dataset of handwritten digits. Seeing it fail on badly centred images was a useful lesson in how much of this work is preparing data rather than choosing algorithms.
What else have you done to prepare outside of education, and why are these experiences useful?
For the past eighteen months I have helped run a Saturday robotics club at my old school, working with ten and eleven year olds building line-following robots from kits. Explaining why a robot oversteers when the light sensor reading is checked too rarely forced me to understand feedback properly myself, and I learned to break instructions into steps small enough to follow without me. Last spring our club entered a friendly schools challenge and one of my groups finished second in the line-following event, which mattered more to them than to me but was a genuinely good afternoon. My Saturday job at a garden centre covers the tills and the click-and-collect desk. Customer-facing work has made me calmer and clearer under pressure, especially during bank holiday weekends, and I have become the person colleagues ask when the stock system shows an item as available that is not on the shelf. I now keep a written note of the mismatches I find, which the supervisor uses when reordering. It is a small thing, but it showed me that a system's output is only as trustworthy as the process feeding it. Badminton for a local league team keeps my weekday evenings structured and has taught me to lose a match without losing the next one. Between shifts, club sessions, training and A levels I have had to plan my week deliberately, which I expect to be useful at university.
This example has 4,205 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 thoughtful, well-evidenced statement whose A* and timetable examples show genuine curiosity and reflection appropriate to a sixth-former. Its main problem is length: at the stated 4,205 characters it exceeds the 4,000 limit, so you need targeted cuts. Some outside-education material reads as general character evidence rather than preparation for intelligent systems.
Subject motivation
a good guess, used carefully, can be more valuable than more computing power
You turn a classroom pathfinding exercise into a clear intellectual question about acting without checking every possibility. That is specific and personal. The closing line about practical systems is vaguer than the rest, and the course wish-list risks sounding like a module catalogue rather than your own reasoning.
Academic preparation
learning to differentiate made gradient descent make sense when I met it later
You link Mathematics, Statistics and Physics to concrete computing ideas instead of just listing subjects. The gradient descent and pattern-versus-coincidence points show understanding at a plausible school level. The linear algebra material is mentioned without saying what you took from it, so it adds little.
Evidence and reflection
Writing up why the second version was faster taught me more than building it did
Your best evidence is selective and reflective: the brute-force coursework, the k-nearest neighbours failure on badly centred images, and the stock mismatches all end in a real lesson. This is reflection rather than skill-claiming, and it repeatedly returns to how reliable a system's output is.
Relevant experience
forced me to understand feedback properly myself
The robotics club gives credible, subject-relevant evidence about feedback and control. The garden centre stock note links well to data quality. The competition result, customer calmness and badminton are fine, but they are less connected to your subject and are the obvious places to trim.
Credibility and voice
which mattered more to them than to me but was a genuinely good afternoon
Your tone is modest, precise and believable. You never overstate your authority, and phrases like 'a little C#' keep your claims in proportion. This aside is warm, but it is a sentence you can spare under the character limit. Generic claims such as 'calmer and clearer under pressure' are weaker than your concrete examples.
Structure and format
This example has 4,205 characters across the three answers
Each answer is well over 350 characters and keeps its evidence distinct, with no duplication across sections. However, the total exceeds the 4,000-character UCAS limit by about 205. The final time-management sentence is a familiar, low-value conclusion that could be cut.
What you’ve done well
- The A* pathfinding opening establishes a genuine question that carries through the whole statement.
- Your coursework and k-nearest neighbours examples show learning from limitations, not just completion.
- The stock-mismatch example turns an ordinary job into thoughtful evidence about trusting system output.
How this draft could improve
- Cut roughly 250 characters, prioritising the competition result, badminton and the closing time-management sentence.
- Either say what the linear algebra study taught you or remove it.
- Replace the general course wish-list with one sentence on which open question you most want to explore.