Computer Science (Conversion) MSc postgraduate personal statement example

Personal statement example

Every night shift at the parcel depot where I work starts with a printed pick list. For my first few months I followed it line by line, which often meant walking from aisle 2 to aisle 14 and back to aisle 3 for consecutive items. When I began sorting my own lists by aisle before setting off, my shift finished noticeably earlier. Asking why the system did not do this already led me to the travelling salesman problem, and to the realisation that the questions I enjoy most at work are computational ones. I am applying for a conversion MSc in Computer Science to study them properly rather than in snatched evenings.

My degree was in French and Spanish, and computing arrived in it later than I expected. For my dissertation I compared how French and Spanish subtitles of the same television drama condensed spoken dialogue to fit the roughly forty-character line limits common in subtitling. I began by counting characters in a spreadsheet, which became unmanageable across twelve episodes, so I taught myself enough Python to parse the subtitle files, align lines by timestamp and flag where the translated text was much shorter than the original. The script was clumsy, with too many nested loops and file paths typed by hand, but it worked, and it let me argue from patterns across thousands of lines rather than a handful of memorable examples. My supervisor's main comment was that my method section was the strongest part of the work, which told me something about where my interests lay.

Since graduating I have tried to fill the gaps in that self-taught start. I completed Harvard's free CS50 course online, and the problem sets in C were humbling: managing memory by hand made me appreciate how much Python had been doing for me. The weeks on data structures were the most useful, because I could finally see why my subtitle script slowed down so badly as files grew, and how a dictionary keyed on timestamps would have avoided repeated searches. I have also been working through introductory discrete mathematics, which I find harder than programming but increasingly satisfying.

At the depot I am a shift coordinator, responsible for allocating pickers to zones and reconciling missed scans at the end of the night. With my supervisor's agreement, I wrote a small script that takes the exported pick list and reorders it by aisle and bay before printing. It is a simple sort, not an optimised route, but our team now uses it every shift, and building it taught me practical things no course had: that real data contains blank rows and inconsistent bay codes, and that colleagues will only adopt a tool if it is quicker than the habit it replaces.

Outside work I ring bells at a village church tower. Change ringing is built on systematically working through permutations of the bells, and learning methods by understanding their structure rather than memorising rows has made me comfortable with abstract patterns in a way I did not expect. I also spend Sunday afternoons helping my younger brother with GCSE maths. Explaining algebra to someone who would rather be elsewhere has made me more patient and clearer, both of which I hope will help in group projects.

A conversion degree appeals to me because I want the foundations I currently lack: algorithms analysed rather than guessed at, software design that survives contact with other people, and the theory behind the tools I have been using. In the longer term I am interested in natural language processing, where my training in how meaning shifts between languages might complement technical skills, and in the logistics software I see every night. I can bring persistence, careful attention to messy data and the habit of building things that people actually use, and I am ready to work hard at the parts I do not yet understand.