Engineering Personal Statementfor Oxford & Cambridge

The Grenfell Tower fire was the point at which engineering stopped looking like a set of school problems and started looking like a public duty. Reading about the Inquiry drew me past the headlines and into the chain of material choices, testing failures and assumptions that turned one fire into a disaster. What unsettled me was that a building failed through decisions which may each have seemed acceptable on their own. That is what first drew me towards engineering: the need to calculate carefully, but also to ask what a calculation leaves out when real people depend on it. I want to study engineering because I am most engaged by problems that sit between mathematics and material reality. Structures and materials interest me because they force engineers to combine analysis with judgement because the consequences of getting that judgement wrong are public. At university I want to study that balance deeply: not only how to design something that works on paper, but how engineers decide what can be trusted when calculation, testing and reality do not quite agree.

That question changed the way I approached Physics and Mathematics. Mechanics and materials interested me most because stress, strain and moments began to feel less like quantities to substitute into an equation and more like ways of locating where a design is vulnerable. In class, I started paying more attention to assumptions behind equilibrium and deformation. I found myself wondering what would happen if a load were uneven, if a connection introduced rotation, or if a compression member buckled before the structure reached its predicted limit. I wanted to test that gap between theory and behaviour, so for my EPQ I compared the efficiency and failure behaviour of Warren and Pratt truss bridges. I modelled each design in Autodesk Fusion, estimated member forces by resolving joints, and built small balsa-wood prototypes to test under increasing loads. I expected the design with the lower predicted deflection to perform better. Instead, one prototype failed earlier than I had calculated because the glued joints twisted and separated before the members themselves reached the forces my model suggested. That result mattered more than a clean match between theory and experiment. It made boundary conditions feel real and showed me that load paths depend not only on the members on a diagram but on the quality of the connections between them. Writing up the project also forced me to be more honest about evidence. My sample was small, the material quality varied, and the prototypes were far simpler than real bridges, so I could not claim that the test proved one design universally better. What I could defend was this: modelling is useful only if you understand the assumptions it rests on, and some engineering judgement begins where a neat model stops fitting messy physical behaviour.

Outside formal study, I kept following the question that first drew me to engineering. Reading Henry Petroski's To Engineer Is Human sharpened the way I thought about failure. His argument that failure is one of the ways engineering knowledge is built changed how I understood safety factors. I had seen them as something added after calculation; I now see them as a recognition that responsible design has to account for uncertainty rather than hide it. I have tried to keep that way of thinking practical. In a school STEM club, I helped younger students redesign a wind-powered vehicle after repeated axle failures. We changed one variable at a time and tested whether the problem came from friction, alignment or load transfer through the chassis. That process felt similar to the EPQ: in both cases the useful work came from isolating the source of failure rather than rushing to a fix. Explaining each change to younger students made me more aware that engineering is collaborative. A good idea is not much use if you cannot justify it clearly, listen when it does not work and improve it with other people.