- Reading time: 4 minutes
- Price: Free download
- Published: 17th September 2026
- Word count: 965 words
- File format: Text
Why do you want to study this course or subject?
What draws me to electrical and computer engineering is the point where a physical measurement becomes a number a program can act on. I noticed this properly while building a soil moisture sensor for my college's allotment project. Reading a voltage across two probes was straightforward; making that voltage mean something useful was not. The readings drifted as the probes corroded, and the same soil gave different values in the morning and afternoon because temperature affected the circuit as much as the water did. Solving that needed both sides: better hardware choices, and code that averaged, compensated and flagged nonsense values. I want a degree that treats those as one problem rather than two.
My Physics course gave me the groundwork in circuits, fields and waves, and I have enjoyed seeing how much of it is genuinely load-bearing rather than illustrative. Further Maths has mattered just as much. Complex numbers felt arbitrary until I used phasors to understand why a capacitor shifts phase, and matrices stopped being bookkeeping once I saw them used to describe systems with several inputs and outputs. I read Charles Platt's Make: Electronics early on, which taught me to expect components to behave imperfectly, and more recently I have been working through the parts of Horowitz and Hill's The Art of Electronics that I can follow, particularly the sections on operational amplifiers and noise, which are harder but more rewarding.
I am interested in embedded systems and power electronics in particular, because both involve accepting real constraints: a fixed energy budget, heat that has to go somewhere, a microcontroller with limited memory. I would like to work eventually on control and measurement systems for energy infrastructure, and a degree covering signals, electronics, digital design and programming is the honest route into that.
How have your qualifications and studies helped you to prepare?
I am studying Mathematics, Further Mathematics and Physics at sixth form college, having chosen that combination deliberately after my GCSEs because it keeps both engineering and physics open. In Maths, differential equations and the mechanics work on damped motion have been the most directly relevant topics, since the same second-order equations turn up describing an RLC circuit. Further Maths has stretched me most: complex numbers, matrix transformations and polar coordinates were the first mathematics I had met that did not have an obvious everyday picture attached, and getting comfortable with them has changed how I approach unfamiliar material. I now expect to work with a structure for a while before it makes intuitive sense.
Physics practical work has been useful in a less obvious way. Writing up experiments on internal resistance and on the characteristics of diodes and filament lamps forced me to take uncertainty seriously, and I have become careful about how many figures a measurement actually justifies. My teacher's comments on my error analysis pushed me to stop treating it as an appendix to the write-up.
Alongside my A levels I completed an extended college project on low-cost environmental monitoring, which required me to read beyond the syllabus about sensor calibration and data logging, and to present my findings to staff and other students. I also took GCSE Computer Science, where I learned Python, and I have kept programming since, mainly in Python and a little C for microcontrollers. I taught myself enough about version control to keep my project code organised after losing an afternoon's work to an overwritten file. Independent study has become the part of my week I plan around rather than fit in.
What else have you done to prepare outside of education, and why are these experiences useful?
For the past two years I have worked most Saturdays and some holidays on the shop floor of an independent hardware store. I serve customers, restock, cut timber to length and help people work out what they actually need, which is often not what they came in asking for. A customer describing a light fitting that trips the breaker is giving me symptoms, not a diagnosis, and I have got better at asking useful questions and admitting when something should go to a qualified electrician. The job has also taught me to be accurate while busy: mis-measuring a cable length costs the shop money and the customer their afternoon.
I attend a community repair club that meets monthly in a library hall. Volunteers there help people fix lamps, toasters, radios and occasionally something more interesting, and as a younger member I mostly assist: dismantling casings, identifying obvious dry joints, learning to solder more neatly than I used to, and fetching the right tool. One of the experienced volunteers showed me how to trace a fault systematically rather than replacing parts hopefully, which is the single most useful thing anyone has taught me about electronics. I have also taken responsibility for the club's tool inventory and logging what comes in and whether it leaves working, and the honest answer is that a fair proportion does not.
The soil moisture project was entered into a regional college engineering showcase, where it was commended for practicality. Four of us built it: I handled the sensing circuit and the logging code, and a teammate built the enclosure. It still runs on the allotment, though it needs the probes cleaning more often than I predicted.
Outside this I play badminton in a local league, which gets me away from screens, and I help my younger brother with his maths homework, which has taught me that explaining something clearly is a good test of whether I understand it.
This example has 5,529 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 specific, credible engineering statement built on genuine projects and honest reflection, especially the soil sensor and repair club. Its central problem is length: at 5,529 characters it exceeds the 4,000 limit, and some evidence repeats across answers, notably Further Maths and the soil project. Cutting duplication and minor extras would leave a strong, focused statement.
Subject motivation
the point where a physical measurement becomes a number a program can act on
Your opening defines a precise interest that fits electrical and computer engineering, then proves it through drift, corrosion and temperature effects. Ending on treating hardware and code as one problem gives a genuine reason for this combined subject rather than a generic passion claim.
Academic preparation
the same second-order equations turn up describing an RLC circuit
You link A level content to engineering convincingly, and the phasor example shows real understanding. However, Further Maths appears in both the first and second answers with overlapping detail; consolidating it in the second answer would save space and sharpen each section's role.
Evidence and reflection
stop treating it as an appendix to the write-up
Reflection is a strength: you explain what changed in your practice, not just what you did. The version-control anecdote and uncertainty work do similar work. The line about independent study being planned around is weaker, as it asserts commitment without new evidence.
Relevant experience
trace a fault systematically rather than replacing parts hopefully
The repair club and hardware shop are ordinary experiences used well, showing diagnosis, accuracy and knowing limits. The badminton and tutoring paragraph adds little engineering relevance, and the soil project paragraph partly repeats material from your first answer, so these are natural places to trim.
Credibility and voice
the parts of Horowitz and Hill's The Art of Electronics that I can follow
Your voice is modest and stage-appropriate: assisting at the club, deferring to qualified electricians, admitting many repairs fail. This honesty makes the reading claims believable. Keep the clear division of team roles, which avoids overclaiming the showcase result.
Structure and format
This example has 5,529 characters across the three answers.
Each answer exceeds 350 characters, but the total is roughly 1,500 over the 4,000 limit, so substantial cuts are essential rather than optional. Removing duplicated maths, the repeated soil project and lower-value extras should bring you within range while staying above 3,500 without padding.
What you’ve done well
- The soil moisture sensor gives a concrete, technically accurate origin for interest in both hardware and software.
- Ordinary experiences like the hardware store and repair club are reflected on precisely, showing diagnostic thinking and honest limits.
How this draft could improve
- Cut to under 4,000 characters by moving all Further Maths detail into the qualifications answer and removing the reused soil project paragraph from the third answer.
- Drop or compress the badminton and tutoring lines and the generic independent study claim, keeping space for reflective evidence.