- Reading time: 3 minutes
- Price: Free download
- Published: 17th September 2026
- Word count: 810 words
- File format: Text
Why do you want to study this course or subject?
The robot I am most proud of is a line-following buggy that took me four attempts to get right. The first version veered off the tape whenever the light in the room changed, and fixing that taught me more than the version that worked. I had to think about what the sensors could actually measure, how much noise to expect, and how to write control code that responded smoothly rather than jerking between full speed and stopping. That gap between a system that works on paper and one that works on a slightly dusty kitchen floor is what pulls me towards robotics rather than electronics or mechanics alone. A robot is only as good as the connections between its parts. Sensors give imperfect information, motors do not respond instantly, and code has to cope with both. I find that layered problem genuinely interesting to sit with, because improving one part often exposes a weakness somewhere else. Reading about sensor fusion and simple feedback control has shown me how much established theory there is behind decisions I have been making by trial and error, and I would like to learn to do it properly. I am also drawn to how widely robotics is applied, from warehouse handling to inspecting pipework that people cannot easily reach. A degree that teaches control, embedded systems and mechanical design together, with laboratory work and a substantial project, is what I want next, and I hope to work in automation design afterwards.
How have your qualifications and studies helped you to prepare?
My A levels in Maths, Physics and Design and Technology have each contributed something I use in my own building. Mechanics in Maths and Physics gave me the language for torque, friction and moments, which changed how I chose motors and gear ratios rather than guessing from datasheets. Differentiation and vectors made more sense to me once I saw them describing how a wheel's position changes over time, and I now find the algebra of rearranging equations to solve for an unknown quite satisfying. Physics practicals have been useful in a different way: writing up uncertainty, repeating measurements and thinking about what a result actually shows has made me more careful about claiming my robots work when they have only worked once. In Design and Technology I designed and made a folding stand for a tablet, which involved sketching options, prototyping in card, then producing technical drawings and cutting parts accurately. That project taught me to work to tolerances and to accept that a part which is two millimetres out will not assemble. I have also taught myself Python outside lessons, working through online exercises, and I use it for small scripts that plot sensor readings from my microcontroller so I can see what is happening instead of relying on a flashing LED. I read New Scientist regularly and have been following coverage of warehouse and agricultural automation, which is partly why the systems side of engineering appeals to me more than any single component.
What else have you done to prepare outside of education, and why are these experiences useful?
Most of my practical experience comes from making things at home with a limited budget. I take apart broken printers and toys from house clearances for stepper motors, gears and switches, and I keep a notebook of what each part does and where it came from. Working with salvaged components means I cannot simply order the ideal part, so I have become reasonably good at adapting a design around what I have, including 3D printing brackets at college when I can book time on the printer. At college I helped a friend build a small robotic arm for his coursework. He led the design and I took responsibility for the wiring and the servo control code, and we agreed early which of us was deciding what. Keeping to that split, and testing each servo individually before connecting everything, saved us a lot of confusion when a joint would not move and the cause turned out to be a loose connector rather than the code. For two terms I helped a teacher run a lunchtime robotics club for Year 9 pupils, setting up kits and helping groups debug their programs. Explaining a loop to someone who has never coded forced me to understand it better myself. My Saturday job at a garden centre involves serving customers, moving stock and covering the till at busy times, which has taught me to stay organised and polite when several people need help at once. I also play in a local badminton league, which is where most of my patience comes from.
This example has 4,362 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.
Review this personal statement
Latest reviews
There are no reviews yet. Be the first one to write one.