- Reading time: 4 minutes
- Price: Free download
- Published: 17th September 2026
- Word count: 911 words
- File format: Text
Why do you want to study this course or subject?
A customer at the repair shop where I work on Saturdays once asked whether the photos on her cracked phone were really gone. They were not: the storage chip was fine, and once my supervisor connected it to a working board they reappeared. That gap between what a device appears to have lost and what it still holds is what pulled me towards digital forensics. Data is rarely erased in the way people assume, and the work of establishing what is genuinely there, how it got there and when, seems to me both technically demanding and genuinely consequential.
My Computer Science course introduced file systems only briefly, so I read around them. Working through explanations of FAT32 directory entries, and how deletion often only alters a pointer while the data remains until overwritten, made me understand why forensic practice insists on write blockers and hashing before anything else. I have also read about the Daubert standard and the way courts assess expert evidence, which changed how I think about the subject. A recovered file is not automatically useful; its handling has to be documented well enough that someone hostile to the conclusion can check it.
Psychology has been an unexpectedly relevant subject. Studying memory and reconstruction has made me cautious about accepting confident accounts of what someone did on a device, and interested in how investigators avoid fitting evidence to an existing theory. I want a degree that teaches the technical detail alongside that discipline of proof, because I would rather be someone whose findings hold up under questioning than someone who simply knows how to run a tool.
How have your qualifications and studies helped you to prepare?
My A levels are Computer Science, Maths and Psychology. Computer Science has given me the most direct grounding: I program in Python and have covered data representation, networking, and the basics of encryption, including why hash functions are used for integrity checking rather than confidentiality. Learning how a hash changes completely with a single altered bit explained the forensic habit of imaging a drive and verifying the copy before any analysis, which I had previously taken on trust.
Maths has been harder and more useful than I expected. Discrete topics such as binary and hexadecimal arithmetic, logic and modular arithmetic now feel practical rather than abstract, since reading raw data in a hex editor means counting in sixteens and keeping careful track of offsets. Statistics has taught me to be careful with claims about how likely something is, which I think matters when explaining technical findings to people who are not specialists.
For my Computer Science coursework I built a small Python tool that scans a disk image for JPEG file signatures and extracts the sections between them, effectively a simple file carver. Testing it on images I created myself showed me how fragmentation breaks the assumption that a file sits in one continuous block, and why real carving tools are far more sophisticated. I documented its limitations honestly in my write-up rather than presenting it as more capable than it was.
Psychology contributes the essay writing and evaluation skills I lacked. Assessing studies for sampling problems and researcher bias has improved how I judge sources generally, including the technical blogs I read, which vary a great deal in reliability.
What else have you done to prepare outside of education, and why are these experiences useful?
I have worked Saturdays in a phone and laptop repair shop for over a year. Most of the job is screens, batteries and charging ports, but I also handle data transfers, and I have learned to explain clearly what can and cannot be recovered before taking someone's money. Customers often hand over devices containing everything about their lives, and being trusted with that has made me careful: I do not look at anything I do not need to, and I log what I have done to each device. That habit of restraint and record keeping seems close to what forensic work requires.
At home I buy broken laptops cheaply, repair them and pass them on to relatives. This has taught me about drive imaging out of necessity, since I wanted to preserve someone's files before replacing a failing hard disk. I also run a small home server for file storage and have set up user accounts and logging on it, which gave me my first real look at how much a system quietly records about activity.
At college I help run the coding club, mainly by preparing short exercises for students newer than me. Explaining pointers or loops to someone who is stuck has improved my patience and made me better at finding a simpler way to say things. With a friend I also organised a lunchtime session on password security, where we demonstrated how quickly short passwords fall to a wordlist attack on a set we had created ourselves. Keeping it to one clear demonstration made it far more effective than the longer talk we first planned.
Outside college I cook for my two younger brothers on weekday evenings while my parents are at work, which keeps me organised and means I am used to working steadily through things that need doing rather than waiting for enthusiasm.
This example has 5,067 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.
Why this example works — strengths and ways to improve
This is a thoughtful, well-evidenced statement with genuine subject understanding and honest reflection on modest projects. Its main problem is length: at a stated 5,067 characters it exceeds the 4,000 limit, so you need selective cutting. Some evidence repeats across answers, notably hashing, and a few final-answer items add little.
Subject motivation
That gap between what a device appears to have lost and what it still holds
Your repair-shop anecdote leads naturally into a precise idea about data persistence rather than a generic passion claim. The later point about findings holding up under questioning shows you understand that forensics is about proof, not only recovery. This gives your motivation real intellectual direction.
Academic preparation
I built a small Python tool that scans a disk image for JPEG file signatures
The file carver is strong, accessible evidence that connects your coursework to the subject. Linking hexadecimal arithmetic and offsets to reading raw data makes Maths feel purposeful. Your reading on FAT32 and Daubert shows initiative beyond the syllabus, though Daubert is US-specific and might benefit from a brief note on why it interested you.
Evidence and reflection
how fragmentation breaks the assumption that a file sits in one continuous block
This is genuine reflection: you explain what testing taught you and acknowledge the tool's limits. The psychology point about fitting evidence to a theory is equally thoughtful. Weaker moments are generic skill claims, such as patience from the coding club, which tell me less than your technical insights do.
Relevant experience
I do not look at anything I do not need to
Your repair job gives concrete, believable evidence of discretion and record keeping, and you link it sensibly to forensic practice. The home server and laptop imaging add depth. The cooking paragraph says little that is specific to the course and is a natural candidate for removal when you reduce length.
Credibility and voice
I documented its limitations honestly in my write-up
Your voice is measured and plausible for a school applicant. You describe your experience as modest and never claim professional authority, which builds trust. Phrases like taking hashing practice on trust before understanding it show self-awareness rather than inflated expertise.
Structure and format
This example has 5,067 characters across the three answers.
Each answer is well over 350 characters, but the total exceeds the 4,000 limit by roughly 1,067 characters. Hashing appears in both answer one and answer two, which duplicates evidence. Your structure is otherwise clear, with each answer doing a distinct job.
What you’ve done well
- The repair-shop opening leads to a precise technical idea about data persistence and so earns its place.
- Your file carver project is reflected on honestly, including fragmentation and the tool's limitations.
- Psychology is linked convincingly to bias and evidence evaluation rather than being forced in.
How this draft could improve
- Cut about 1,100 characters to fit 4,000, starting with the cooking paragraph and the generic coding-club skill claims.
- Keep the hashing explanation in only one answer, probably answer two, and use the freed space elsewhere.
- Tighten the reading paragraph by stating more briefly why Daubert changed your thinking.