Complexity science and engineering postgraduate personal statement example

Personal statement example

My degree in Mathematics with Physics gave me two habits that sit oddly together: a taste for exact solutions, and a growing suspicion that most of the systems I care about do not have any. Solving the harmonic oscillator was satisfying; watching a queue of people dissolve and re-form at a station barrier was more interesting. A master's in complexity science and engineering is the route I want because it treats that second kind of problem as a discipline rather than an inconvenience.

My final-year project was an agent-based model of pedestrian movement through a station concourse, written in Python. I began with a simple social-force approach, giving each walker a target, a preferred speed and repulsive interactions, and then added a barrier line and two entrances. The behaviour I had not anticipated was how sensitive throughput was to the width of the gap between barriers: below a certain width, lanes stopped forming and clusters jammed intermittently rather than steadily. Calibrating anything was harder than coding it. I had only rough counts from a fifteen-minute observation at my local station, so I learned to be honest about what the model could and could not support, and to present results as sensitivity ranges rather than predictions. My supervisor's main criticism, fairly, was that I had not tested whether my findings survived changes in time step; repeating the runs taught me more about numerical artefacts than any lecture had.

Alongside my degree I read steadily outside the syllabus. Melanie Mitchell's Complexity: A Guided Tour gave me a first map of the field and pushed me towards cellular automata, which I experimented with for a few weeks. Strogatz's Sync led me back to coupled oscillators with more patience than I had shown when they appeared in a dynamics module, and Barabási's Network Science, which is freely available online, took me through degree distributions and preferential attachment properly. I worked through parts of it with NetworkX, partly out of curiosity about my cycling club: I built a small graph of which members had ridden together over a season, using our published ride sign-ups, and looked at clustering and how the club's few long-distance riders connected otherwise separate groups. It was a toy analysis with obvious data problems, but it made abstract measures concrete and showed me how quickly interpretation outruns evidence.

Ordinary responsibilities have shaped my interests as much as reading has. I help my mother run the volunteer rota for a community minibus that takes people to a weekly market and a health centre. Each driver has constraints, passengers change plans, and a single cancellation propagates through the week. We manage it with a spreadsheet and a group chat, and what strikes me is how much the scheme's resilience depends on informal substitutions nobody planned for. My library job has a similar texture: shelving, enquiries and holds interact in ways that no procedure fully captures, and I have become the person colleagues ask when the reservation system behaves strangely, because I will sit and trace what actually happened.

I want formal grounding in the areas I have only sampled: stochastic processes, dynamical systems, network models, and the computational and statistical methods needed to fit models to messy data rather than to admire them. I am comfortable with Python and have basic C, and I would like to strengthen my statistics considerably. In the longer term I am drawn to work on transport or infrastructure systems, where modelling has to inform practical decisions, and I would consider research if a dissertation suits me. I am applying because I would rather study these problems with proper method than keep circling them with spreadsheets and enthusiasm.

Review this personal statement

Latest reviews