Personal statement examples

I built my first real program because I was annoyed. Our family chore rota kept vanishing under the post on the kitchen table, so I wrote a clumsy Python script that texted everyone their jobs each morning. It barely worked; it once messaged my grandmother forty times before breakfast. But watching a few lines of code reach out and change something in the physical world hooked me completely. Six years later that feeling has not worn off, it has only become more disciplined.

Since then I have taught myself enough to be dangerous, and then, more slowly, enough to be careful. Studying Further Maths has been the turning point: it handed me the language of proof, induction and complexity that separates a program which happens to work from one I can actually reason about. A project to scrape and visualise my city's bus-delay data taught me a lesson no tutorial had: the hard part is almost never the algorithm, it is the missing, contradictory, badly formatted data underneath it. I spent three evenings on the model and three weeks on the cleaning, and I have never trusted a tidy dataset since.

I wanted problems with no obvious way in, so I entered the British Informatics Olympiad and worked through a university-level algorithms course in my own time. Reading Brian Christian and Tom Griffiths' 'Algorithms to Live By' then did something I did not expect: it convinced me that computer science is less a branch of engineering than a way of thinking about decisions, trade-offs and limited time. That idea, that the same logic can govern a sorting routine and a sensible life, is roughly what I want to spend three years taking apart. I am drawn to the theoretical side not despite its difficulty but because of it. I have also begun contributing tiny fixes to an open-source library I rely on, and the first time a maintainer accepted a change of mine, three lines correcting an off-by-one error, I understood that real software is a slow conversation between strangers who will never meet.

Code is rarely written alone, and I learned that the hard way. I co-led a small team building a revision-flashcard app for my year group, and the technical problems turned out to be the easy ones. Merging three people's work without overwriting each other, disagreeing about a feature without sulking, deciding what to leave out, those were the real tests. We shipped something forty of my classmates actually used, and the bug reports they sent taught me more about software than any green tick from an automated marker. Above all I learned to write code other people could read, which I now think is most of the job.

Away from a screen I play the cello, which is where I first understood that fluency comes from boring, repeated, unglamorous practice rather than talent, a truth that transfers neatly to debugging at midnight. I also volunteer teaching basic coding to younger students, and explaining a loop to an eleven-year-old has forced a clarity on my own understanding that I did not have before. If you cannot explain it simply, I have decided, you do not really understand it yet.

I do not just want to use these tools; I want to understand why they work and, more interestingly, why they sometimes do not. The systems running modern life were built by people who once wrote clumsy scripts and kept going, ideally learning to test properly along the way, and I intend to be one of them. This course, with its insistence on theory alongside building real things, is exactly the kind of difficulty I have been looking for. I am ready for it.

I reread the books I love until their spines give up. What changed me was noticing that the second reading was never the same as the first: the words held perfectly still while I moved beneath them. A novel I had thought was about ambition at fifteen was plainly about grief at seventeen. That gap, between a fixed text and a changing reader, is the thing I find most alive in literature, and it is what I want to spend three years learning to think about properly.

Studying 'Mrs Dalloway' alongside the war poetry of the same period showed me how form carries meaning that plot alone never could; Woolf's sentences enact the very consciousness they describe, and once I had seen it I could not unsee it. I became fascinated by how writers make time bend, and chose to read 'Beloved' across a summer to follow that question into a tradition I knew far less well. Toni Morrison taught me that a haunting can be a structural device as much as a ghost, and that the gaps a writer leaves are doing as much work as the words on the page. I began annotating for silence as carefully as for image, and now read with a pencil permanently in hand, distrustful of any response I cannot point to a line for.

Wanting to argue about this with other people, I started a small reading group at school where we fought, politely, about endings. I learned more from being persuasively wrong in those conversations than from any essay grade, and I learned to change my mind in public, which is far harder than it sounds. Beyond the syllabus I have been working through Achebe and Atwood, partly to unsettle the quiet assumptions my own reading had built without my noticing, and partly because a literature that only flatters its reader is not worth much. I keep a commonplace book of sentences I wish I had written; it is now embarrassingly full. I have also begun teaching myself enough literary theory to know what I am arguing against, reading a little Barthes and finding his 'death of the author' equal parts liberating and infuriating, which is probably the point.

Literature is not a private hobby, though it is easy to treat it as one. Volunteering at a primary-school reading club reminded me that stories are how people first learn to imagine a life other than their own. Watching a reluctant seven-year-old finally care what happened to a character was a small but genuine lesson in why any of this matters. I also write reviews for the school magazine, which has taught me the discipline of defending a judgement with evidence rather than enthusiasm, and the humility of cutting my own clever sentences when they are only clever.

I am not always the fastest to land on the 'right' interpretation, and I have made an uneasy peace with that, because the point, for me, was never to arrive first. It was to keep looking. I act, too, mostly in small parts, and standing inside a text rather than over it has changed how I read dialogue entirely; a line means something different once you have had to say it aloud and mean it in front of an audience.

I want to read more widely than is comfortable, argue more precisely than is easy, and write about all of it with more care than I currently can. I am applying to study English because the questions it asks, about meaning, memory and how language shapes thought, are the ones I return to whether or not anyone is grading me. Three years of taking them seriously, in good company, is the closest thing to a plan I have ever genuinely wanted.

A broken washing machine taught me more than any open day. My dad and I spread its parts across the kitchen floor one Saturday, and the moment the seized drum bearing finally made sense, the why of it and not just the what, I understood that engineering is really curiosity with a spanner in its hand. I put the machine back together, it worked, and I have been taking things apart ever since, though I have learned, eventually, to photograph each step before I do.

Physics and Maths are the obvious groundwork, and I have come to love the moment an abstract equation suddenly describes something I can hold. A weekend course in CAD made that concrete: the formulas I had treated as homework became shapes, tolerances and forces I could watch failing on screen. For my EPQ I designed and 3D-printed a low-cost prosthetic hand mechanism, actuated by tendons of fishing line and elastic. The three prototypes that failed taught me far more than the one that finally closed around a pencil. I learned to treat each failure as data rather than defeat, and to distrust a first design that works, because it usually means I have not tested it hard enough.

I wanted to understand the discipline beyond my own workbench, so I read Henry Petroski's 'To Engineer Is Human', which argues that engineering advances chiefly by studying its failures, the collapsed bridges and split fuselages, rather than its triumphs. It changed how I think about design entirely: robustness is not the absence of failure but the management of it. I now sketch the failure modes of an idea before I sketch the idea itself. Following the same thread, I have been teaching myself the basics of finite-element analysis, mostly so I can stop guessing where a part will break and start predicting it. I have since entered a local Formula-style design challenge, where a rule book, a tiny budget and a fixed deadline impose exactly the constraints that make real engineering interesting rather than merely clever.

I help run the engineering section of a local youth club, where explaining gear ratios to ten-year-olds forces a clarity I did not know I lacked, and where a marble-run competition taught me more about iterating under a deadline than any lesson. I also spent two weeks shadowing technicians at a small manufacturing firm, and watching a machinist hold a tolerance of a few microns by feel reset my sense of what precision actually costs. Theory and the shop floor, I realised, are not rivals; the engineers I admired moved easily between them, and that is the kind of engineer I want to become.

I cycle competitively, and maintaining my own bike has become a quiet laboratory: every creak is a hypothesis, every fix a small experiment with a clear result the next time I ride. I am not a natural at the pure-maths corners of the syllabus, and I have had to work harder there than I would like to admit, but that struggle has made me a more careful and less arrogant problem-solver than I was two years ago.

I am applying for mechanical engineering because I want to keep getting my hands dirty while I learn the theory that turns tinkering into something rigorous and genuinely useful. The design-and-make thread running through the early years of this course is exactly what I have been doing in my bedroom and the youth-club workshop for years, only with proper tools, better mathematics, and people far cleverer than me to learn from. I cannot think of anything I would rather spend my time on.

I started paying attention to economics from behind the till of a corner shop. Working Saturdays, I watched a ten-pence rise in the price of own-brand bread quietly redraw what an entire street chose to buy, and I was doing supply and demand with my hands long before I had the words for it. The questions that job raised, why people choose what they choose, and who is left worse off when prices move, are the ones that pulled me towards this subject and have not let go since.

I chose Maths and Geography alongside Economics deliberately, because I am as interested in why a place is poor as in the equations that try to model its poverty. Maths gave me the confidence to read a model rather than be intimidated by it; Geography keeps reminding me that those models describe real, uneven ground. Reading Banerjee and Duflo's 'Poor Economics' reshaped how I think about policy, replacing grand slogans with small, testable questions: not 'does aid work?' but 'does this bed net, at this price, in this village, actually get used?' That shift, from ideology to evidence, is roughly what I find most exciting about economics as a way of thinking.

I tested that mindset in a national economics essay competition, arguing that behavioural 'nudges' are often a cheap substitute for fixing the incentives underneath a problem rather than a real solution to it. Building the argument forced me to read beyond the syllabus, into Thaler and into his critics, and to hold two persuasive opposing views in my head long enough to judge fairly between them. I have since followed central-bank decisions with the slightly obsessive attention other people give to football, and I keep a notebook of predictions I have got wrong, which is, so far, most of them. I now read the Financial Times most mornings, not because I follow all of it, but because I have learned that the gaps in my understanding are the most useful map I have of what to study next.

As treasurer of two school societies I learned that a budget is really just a set of choices made visible, and that the hardest part of any spending decision is the thing you quietly choose not to fund. Running the accounts for our charity week, I had to weigh fairness against efficiency in a way no textbook had quite prepared me for, and I finally understood why economists argue about that trade-off endlessly. I also tutor younger students in maths, where explaining compound interest to a fourteen-year-old taught me that the ideas only matter once someone can see themselves inside them. That, more than any grade, is what convinced me I want to study economics rather than simply read about it: I like the difficult work of making an abstract idea land.

I will not pretend every model comes easily; econometrics humbles me on a regular basis, and I have had to learn to sit with confusion rather than flee it. Outside economics I play chess at county level, and the game has quietly trained the habit the subject most rewards: thinking several moves ahead, and being willing to give something up now for a position that is stronger later.

I am drawn to economics precisely because it refuses easy answers and insists you show your working. This course's blend of rigorous theory and real-world application is exactly the kind of productive difficulty I have been looking for, somewhere between the corner-shop street and the models that try to explain it. I want to spend three years learning to ask sharper questions about how people and societies make their choices, and to be wrong more usefully than I am now.