- Reading time: 4 minutes
- Price: Free download
- Published: 17th September 2026
- Word count: 1005 words
- File format: Text
Why do you want to study this course or subject?
My Design and Technology coursework this year is a watering system for the raised beds at my college's allotment plot. The pump was the easy part. What took months was everything around it: where the sensor sits, what happens when the water butt runs dry, how a volunteer who has never seen the thing can tell whether it is working. I kept solving one problem and creating another somewhere else, and eventually I started drawing the whole thing as boxes and arrows rather than as a circuit. That shift in how I was looking at the problem is why I want to study systems engineering rather than only electrical or mechanical engineering.
What appeals to me is that the discipline takes interfaces seriously. In Physics I am comfortable analysing a component in isolation, and I enjoy that, but the failures I have actually caused have almost never been component failures. They have been mismatched assumptions between two parts I built at different times, or a case I never considered because I was thinking about the sensor and not about the person refilling the butt. Reading about requirements, verification and trade-off analysis gave me vocabulary for something I had been fumbling towards on my own.
I am also drawn to the breadth. I like that a systems engineer might work on water infrastructure, rail signalling or satellite ground segments, and that the transferable skill is disciplined thinking about how parts combine, degrade and are maintained. I would like to work eventually on infrastructure that has to keep running for decades, where the interesting constraints are reliability, maintainability and cost over a whole life rather than peak performance. Studying systems engineering at degree level would let me build the mathematics and modelling underneath that instinct, instead of relying on trial and error in a shed.
How have your qualifications and studies helped you to prepare?
My A levels give me the foundations the course needs. Maths is the subject I work hardest at and enjoy most; mechanics has been useful for my coursework, but I have found the statistics content unexpectedly relevant, because thinking about reliability means thinking about probability rather than certainty. Differential equations and modelling change over time feel directly connected to how systems behave when disturbed.
Physics has taught me to be honest about assumptions. Writing up practicals, I have learned to state the conditions under which a result holds and to quantify uncertainty rather than quietly rounding it away. My electricity and circuits work underpins the sensing side of my project, and my teacher's insistence on drawing a clear system boundary before writing any equations has stuck with me.
Design and Technology is where I have practised the full cycle: identifying a real user need, writing a specification, iterating prototypes and testing against the criteria I set myself. Being marked on whether my product meets my own stated requirements has been a good discipline, because it exposes vague requirements immediately. I have also learned to keep a design log, which has made my reasoning traceable when something stops working.
My AS in Computer Science introduced me to structured problem decomposition and to thinking about what happens at the edges of expected input. I write in Python and have taught myself enough C to program a microcontroller.
Outside the syllabus I have read Donella Meadows' Thinking in Systems, which changed how I think about feedback and delay, and I follow engineering failure case studies because they show how organisational and technical causes intertwine. I have found that reading about failures teaches me more than reading about successes.
What else have you done to prepare outside of education, and why are these experiences useful?
I built a small monitoring rig for the greenhouse at home using a microcontroller, a soil moisture probe and a temperature sensor, logging readings to an SD card. The first version gave readings that drifted badly in the heat, and rather than replacing the sensor I spent a fortnight comparing its output against a cheap thermometer at different times of day so I could describe the error properly. I ended up averaging readings and recording the raw values as well, so I could see later whether I trusted them. It is a modest piece of work, but it taught me that measuring your measurement is part of the job.
On Saturdays I work at a garden centre, mostly on tills and restocking. It is ordinary work, but it has shown me how a physical system runs under pressure: the queue length depends on how stock is laid out, how quickly the card terminals respond and whether the person on the second till has been trained. I suggested moving the compost pallets closer to the trolley bay after noticing how many customers walked the length of the shop twice, and my supervisor tried it for a weekend. Watching a small change ripple through the whole flow of the shop was genuinely interesting.
I volunteer with a junior football club where I help organise fixtures and kit. Coordinating pitch availability, referees, parent drivers and cancelled games has made me better at building in slack and at communicating changes clearly, since a plan nobody understands is no plan at all. I keep a shared spreadsheet that the coaches actually use, which took a few attempts to get simple enough.
I play trombone in a community brass band, where rehearsing a part that only makes sense alongside everyone else's is its own lesson in integration. I also mentor two Year 11 students in maths through a college scheme, which has sharpened how I explain method rather than answers. Together these commitments have taught me to manage my time across competing deadlines and to work steadily on long projects, which is what I expect degree-level study to demand.
This example has 5,701 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.