Human-centred computing personal statement example

Why do you want to study this course or subject?

Most weeks at the library I sit beside someone trying to finish an online form that was clearly never tested on a person like them: a housing application that logs you out after ten minutes, a bus pass renewal that asks for a document number printed in grey on grey. The person opposite me usually assumes they are the problem. They are not. Those half-hours convinced me that the interesting part of computing is not only whether a system works, but whether it works for the people who have no choice but to use it. That is what drew me to human-centred computing rather than a general software degree. I want to study how interfaces are designed and evaluated, how accessibility standards actually get applied, and how research with users turns into decisions a development team can act on. My Access course has given me the technical side I was missing, and I have enjoyed it more than I expected: writing Python to tidy a messy spreadsheet of library event bookings was oddly satisfying, and it showed me how much of usability sits in data structures and defaults rather than in colours and buttons. I am also interested in the awkward questions, such as who is consulted when public services move online and who gets designed out. Returning to study at 31 is a considered decision. I have seven years of listening to people describe problems in their own words, and I would like to combine that with the methods and programming skills to test solutions properly rather than guess at them.

How have your qualifications and studies helped you to prepare?

I am studying an Access to Higher Education Diploma in Computing and Mathematics at my local college, one evening a week plus two daytime sessions, while working four days at the library. The computing units have covered programming fundamentals, databases and systems analysis; the mathematics units have taken me from a shaky GCSE grade to comfortable work with algebra, functions and probability, which I now use without dreading it. For my systems analysis assignment I documented the booking process for the library's meeting rooms, interviewed two colleagues about where it goes wrong, and produced a set of requirements and a simple relational database design. The tutor's feedback pushed me to separate what users said they wanted from what the observed process actually needed, which was a useful distinction and one I have thought about since. Alongside the diploma I have taught myself HTML, CSS and enough JavaScript to build a small site listing our community group timetables, and I have worked through an introductory Python course, finishing the exercises on file handling and dictionaries. Reading has been a large part of my preparation. Don Norman's The Design of Everyday Things gave me vocabulary for things I had noticed but could not name, particularly affordances and the gap between how a designer imagines a system and how it is understood in use. I have also read Steve Krug's Don't Make Me Think, which is practical and blunt about testing with small numbers of people, and I follow the government design blog for examples of accessibility work on real services. I have started looking at the Web Content Accessibility Guidelines and found that reading them properly is harder and more interesting than the summaries suggest.

What else have you done to prepare outside of education, and why are these experiences useful?

My job at the library involves front desk work, stock management, and running a weekly digital drop-in that I proposed and now organise. Regulars bring universal credit journals, hospital appointment portals, photo printing and, most often, phones that have updated overnight. I have learnt to ask what someone is trying to achieve before touching their device, to let them do the tapping so they can repeat it, and to write short steps on paper afterwards. I keep a notebook of recurring sticking points, and the pattern is rarely a lack of intelligence: it is unlabelled icons, timeouts, and error messages that say what went wrong without saying what to do. Before the library I worked in retail, latterly as a keyholder on a homeware shop floor, which taught me to stay calm with frustrated people, train new starters clearly and notice when a process is generating the same complaint repeatedly. I also spent two years helping with stocktakes, which is where I first started using spreadsheets seriously. Outside work I play tenor horn in a community brass band and sit on its small committee, where I look after the rehearsal rota and email list. Coordinating thirty volunteers with different availability has been better training in constraints and compromise than any of my jobs. I am part of a Saturday coding meet-up at a cafe in town where four of us work through problems together; explaining a loop to someone else is the fastest way I have found to discover whether I understand it. Studying part-time while working full-time has made me organised about deadlines, and I expect to bring that habit, and a fair amount of patience, to a full-time degree.

This example has 4,912 characters across the three answers. Use it for ideas and structure. Your own UCAS answers must fit within 4,000 characters in total, including spaces.