Cloud computing postgraduate personal statement example

Personal statement example

My degree gave me a solid grounding in operating systems, networks and distributed algorithms, but the module that shaped my plans was a third-year unit on concurrent and distributed systems. Working through consistency models, and reading Kleppmann's Designing Data-Intensive Applications alongside the lectures, changed how I thought about failure. I had assumed that a well-written program was the goal; I came to see that the interesting engineering happens when machines disappear, messages arrive twice, and the system still has to give a sensible answer. A master's in cloud computing is the natural place to take that interest further, because it puts the architectural choices, the economics and the operational practice in the same room.

My final-year project was modest but taught me a great deal. I built an automated marking tool for a student coding club: submissions were run inside Docker containers with resource limits, results written to a queue and then to a small database. Getting the container isolation right took far longer than the marking logic. I learned to read logs properly, to test what happens when a container never exits, and to be honest in my write-up about what I had not solved, including the absence of any real scaling beyond one host. My supervisor's main criticism was that I had not measured anything systematically, and that stayed with me; I would approach a dissertation now with a measurement plan written before the code.

Since graduating I have worked as a first-line IT support technician at a further education college. The work is unglamorous, but it has made me a better engineer. I handle account problems, printing, laptop imaging and the steady stream of questions that come from staff who are already late for a lesson. Explaining multi-factor authentication to sixty people in a week has taught me how much of infrastructure work is communication, and how quickly badly documented systems become expensive. I keep our internal knowledge base tidy and rewrote several articles after noticing colleagues never used the originals.

Last term I spent two days shadowing our infrastructure team while they moved departmental file storage to a hosted service. I was there to observe and to help with small tasks: I checked share permissions against a spreadsheet, noted which folders had not been touched in two years, and sat in on the cutover call. I was struck by how much of the plan concerned rollback and communication rather than technology, and by the discussion of ongoing costs, which was not something my degree had prepared me to think about. Watching two experienced engineers disagree politely about whether to lift and shift or restructure the data first was more instructive than any lecture on migration.

Outside work I volunteer with a community food project, where I look after their shared drive and a booking spreadsheet that had grown unmanageable. Moving them to a cleaner structure, with a short written guide for volunteers who change every few months, was a useful reminder that the constraint is usually people, not software. I also run a small home server for family photo backups, mainly as an excuse to practise with infrastructure as code.

I would like to study distributed systems design, containerisation and orchestration, cloud security and cost-aware architecture in more depth, and to write a dissertation involving careful measurement of a system under load. My longer aim is to work as a cloud or platform engineer in the public or education sector, where budgets are tight and decisions have to be justified. I expect the mathematics of performance modelling to stretch me, and I have been revisiting probability and queueing theory in preparation.