Advanced Computer Science MSc postgraduate personal statement example

Personal statement example

Every morning at the housing association where I work, a repairs report is meant to be waiting for the operations team by half past seven. For three weeks last winter it kept arriving late, and the job of finding out why fell to me. The query behind it had been written years earlier for a few thousand records and now ran against several hundred thousand. Reading the execution plan, I found it scanning a whole table for every property because a join used a column with no suitable index. Adding the index and rewriting one subquery brought the run time from over forty minutes to under two. It was a small fix, but it changed how I think about my work. I want to understand systems well enough to predict where they will fail, rather than only repairing them once they do, and that is why I am applying for an advanced master's degree in computer science.

My undergraduate degree gave me a broad grounding: algorithms, operating systems, databases, networks and a compulsory module on formal methods that I found harder than anything else and, eventually, the most satisfying. I graduated with a 2:1 and did my strongest work in the later, more analytical units. My final-year project looked at a public bus-timetable API that was slow and occasionally unavailable. I built a small caching layer in Python, compared time-based expiry with an approach that refreshed entries according to how often each route was requested, and measured hit rates and staleness using a week of logged requests I generated myself. The adaptive approach performed better for busy routes but was noticeably worse for rarely requested ones, and explaining that trade-off honestly in my write-up taught me more than the code did. It also showed me how much I did not yet know about distributed systems and consistency.

Since graduating I have worked as a support developer in a team of four. Much of the job is ordinary: maintaining a tenant portal, fixing form validation, writing documentation that colleagues actually read. I have also taken on more substantial pieces, such as moving our scheduled jobs from a single server into containers so that one failing task no longer blocks the rest. I proposed the change, wrote the migration plan and ran it over two weekends with my manager reviewing each step. Working with non-technical colleagues has made me better at asking what problem someone really has before deciding what to build.

Outside work I have kept reading. Martin Kleppmann's Designing Data-Intensive Applications gave me a vocabulary for things I had met only by accident, particularly replication lag and the different meanings people attach to consistency. I worked through its chapters on transactions alongside our own database's documentation, which made both clearer. I have also started learning Rust in the evenings, partly out of curiosity about how its ownership model prevents whole classes of memory errors at compile time.

Not everything I do is computing. I play badminton for a local club and keep its fixtures spreadsheet in order, and I help my grandfather with the accounts for his allotment society, a task that mostly involves patience and a calculator. Both remind me that tools succeed when they suit the people using them.

At postgraduate level I hope to study distributed systems, data management and the theory that underpins them in much greater depth than my degree allowed, and to complete a substantial research project of my own. I am used to working steadily on real systems with real constraints, and I would bring that practical habit to more rigorous study. I would like the next problem I solve to be one I anticipated.