Computer Science – Future Networked Systems (M.Sc./P.Grad.Dip) postgraduate personal statement example

Personal statement example

The reading on my optical power meter was minus 27 dBm, which meant the customer in the end terrace would get a connection, but only just. Tracing the loss back along the drop cable to a tight bend behind a gutter bracket took twenty minutes. Fixing it took two. For the last two years, as a fibre broadband installation technician, I have spent my days at the physical edge of networks, and I now want to understand properly how the systems built on top of them are designed, measured and kept reliable at scale.

My degree in Electronic and Computer Engineering gave me a mixed foundation. I enjoyed signals and embedded systems, but the module I returned to most was networking, taught largely from Kurose and Ross's Computer Networking: A Top-Down Approach. I liked how the layered model made complicated behaviour readable, and also how often real systems blur those layers. For my final-year project I built a small LoRa sensor network for a volunteer-run orchard near my parents' house. Six battery-powered nodes reported soil moisture and temperature to a single gateway, which forwarded readings to a lightweight database and dashboard I wrote in Python.

The interesting part of the project was the trade-off I had expected to be a minor setting. Higher spreading factors let the furthest nodes, sited behind a stone wall, reach the gateway reliably, but they increased airtime and drained batteries faster. I logged packet delivery and battery voltage over eight weeks and adjusted reporting intervals and spreading factors node by node, rather than applying one setting everywhere. The final configuration gave the volunteers usable daily data from every node through the summer. It was modest, but it taught me to treat a network as something to measure rather than assume, and it earned one of the stronger marks in my cohort's project assessments.

Work has extended that habit in ways a lecture could not. I install and test connections, configure customer routers and explain to people why a mesh unit on the landing helps more than a faster package. I have noticed how many complaints about slow broadband are really about home Wi-Fi interference or a congested evening period, and I became curious about what happens beyond the cabinet. In my own time I have been reading about TCP congestion control, comparing loss-based approaches such as CUBIC with BBR, which models bottleneck bandwidth and round-trip time, and I have run simple experiments on a virtual network using Mininet to watch how they share a constrained link. I have also read about QUIC and why moving transport functions into user space changes how quickly protocols can evolve. I understand these topics only at an introductory level, and that is precisely why I want structured postgraduate study in networked systems, distributed computing and the software that now manages networks.

Outside work I sing tenor in a community choir and help coach on Saturday mornings at a youth cycling club, where I mostly mend punctures, plan safe routes and keep twelve-year-olds in a line. Neither is related to networking, but both rely on reliability, preparation and patience, and the club has made me better at explaining things clearly to people who did not ask for an explanation.

I would bring to a master's course practical experience of how networks behave in real buildings, a completed project that combined hardware, radio and software, and a steady working discipline. I hope to leave it able to contribute to the design of networks that are efficient, resilient and fair to the people at the far end of the cable, and I am ready for the depth of study that requires.