Civil Engineering Personal Statementfor Imperial

When the Grenfell Tower Inquiry's final report was published in September 2024, I read beyond the headlines I knew and focused on the refurbishment decisions that shaped the building's behaviour in a fire. What unsettled me was not only the scale of the disaster, but the fact that technical decisions about materials, detailing and compliance had such public consequences. I started reading about how engineers judge acceptable risk and how regulations try to anticipate failure before it happens. Civil engineering began to feel less like applied maths in isolation and more like the point where calculation, evidence and responsibility meet. That is why I want to study it. I am especially drawn to structural design because it sits exactly at that boundary between abstract modelling and real use: a calculation matters only if it survives contact with materials, maintenance, regulation and the people who depend on it. At university, I want to understand more rigorously how engineers balance efficiency with robustness when failure carries consequences far beyond the drawing board.

My studies have given me the framework for that interest, especially through mechanics. I liked the clarity of resolving forces and taking moments, but I also became aware of how much those idealised models leave out. A bridge can satisfy equilibrium on paper and still be vulnerable because of poor detailing, maintenance or instability. That tension shaped my EPQ, where I asked how accurately school-level truss calculations predict the failure of small bridge models. I wrote a Python script to calculate reaction forces and member forces under a central point load for Warren, Pratt and Howe trusses, then built each design from balsa wood with card gusset plates. I loaded them with sand in measured increments and recorded mid-span deflection. The most useful part was where the modelling began to fail. My early results were inconsistent because the joints slipped and the load was slightly off-centre, and the Warren truss that my script predicted would be strongest failed early when a compression member buckled near an imperfect joint. That forced me to think beyond axial-force calculations and read about slenderness and Euler buckling, but it also made me more careful about what my model was assuming: ideal joints, perfect alignment and members behaving more cleanly than real ones do. The project taught me that mathematical reasoning is most useful when I am clear about the limits of the model I am using.

Outside lessons, I tried to test those ideas in settings that were less controlled. J.E. Gordon's Structures: Or Why Things Don't Fall Down helped me understand why stiffness and safety factors matter, while Roma Agrawal's Built showed me that structures are shaped as much by construction, inspection and human use as by calculations. Together, those books moved me away from looking for a single neat answer and towards thinking in terms of trade-offs. I then applied that more directly through an Industrial Cadets Gold project. Working with four other students, I helped compare options for a small pedestrian bridge linking two parts of a local park that become difficult to access after heavy rain. I modelled a deck and truss arrangement, calculated member forces for a simplified Warren truss, and compared steel, timber and fibre-reinforced polymer against span, cost and embodied carbon. What made the project useful was how quickly a tidy design became harder to defend once drainage, inspection, accessibility and corrosion were considered alongside strength. I had initially preferred steel because it allowed a slimmer section, but our mentor kept pushing us to justify whole-life performance rather than appearance. That made me realise that a design only becomes convincing when you can explain the compromises behind it, which is exactly the kind of judgement I want to develop further on a civil engineering course.