Advanced Computer Science (Cloud Computing) MSc postgraduate personal statement example

Personal statement example

On the morning GCSE results were released last August, the secondary school where I work as an IT technician watched its parent portal slow to a crawl for about forty minutes. Nothing broke, exactly; pages simply took so long to load that the office phones started ringing instead. The portal runs on a single virtual machine hosted by an external supplier, and when I later looked at the monitoring graphs I could see the processor pinned at its limit while, for the other three hundred and sixty-four days, it barely ticked over. That mismatch between fixed capacity and uneven demand is the problem I most want to understand properly, and it is why I am applying for postgraduate study in cloud computing.

I graduated with a BSc in Computing with Mathematics. My final-year project explored the same question on a small scale. I built an image-resizing service, split it into containers, deployed it on a free-tier Kubernetes cluster and wrote a load generator to simulate bursts of uploads. I compared the default horizontal pod autoscaler, which reacts to CPU utilisation, with a simple rule I wrote that scaled on queue length instead. Queue-based scaling responded noticeably faster to sudden bursts in my tests, but it also over-provisioned during short spikes, so the honest conclusion was that neither approach suited every workload. Writing that evaluation taught me to separate what my measurements showed from what I hoped they would show, and to state the limits of a test setup with three nodes and synthetic traffic. My supervisor's main criticism was that I had not considered cold-start latency, and I would like to study that gap formally rather than patch it from blog posts.

Modules I enjoyed most were distributed systems and operating systems, particularly the material on consensus and on how schedulers make decisions with incomplete information. Since graduating I have been working through Designing Data-Intensive Applications by Martin Kleppmann, slowly, because its chapters on replication and partitioning keep sending me back to my old lecture notes. It has made me realise how much of what I call cloud engineering is really trade-offs between consistency, availability and cost that need careful reasoning, not just configuration.

My job is mostly practical and unglamorous: imaging laptops, managing user accounts, fixing projectors before assemblies. It has still been useful. I wrote PowerShell scripts that cut the time to set up a classroom set of thirty laptops from most of a day to around two hours, which freed me to help the network manager plan moving the school's file storage to a cloud service. I was not making the decisions, but I sat in on supplier calls and noticed how often questions about data location, backups and licensing mattered more to the school than raw performance. I would like my technical understanding to be strong enough to explain those trade-offs clearly to people who are not specialists.

Outside work I sing bass in a church choir, and I maintain the small website the choir uses for its rehearsal and reading rota. It is a static site rebuilt automatically from a shared spreadsheet, hosted for nothing, and the most demanding traffic it ever sees is the Thursday before Christmas. It is a modest project, but keeping something running for volunteers who simply need it to work has made me careful about simplicity and documentation. I also cycle to work most days, which is where I tend to think through whatever bug I left the evening before.

I want a masters degree because I have reached the edge of what I can learn reliably on my own. I can deploy and script things, but I want a deeper grounding in the theory behind distributed and elastic systems, and the chance to do a substantial project with proper evaluation. I would bring steady habits from work, a willingness to measure before claiming, and real interest in making services behave sensibly when demand is uneven.