What this subject area covers
Music technology and sound production sits between music, physics, computing and media. Courses under this heading vary a great deal in emphasis, so the first job is to work out which kind of course you are applying for and choose evidence that fits it. Broadly, the titles in this area lean in four directions:
- Music technology: how tools for making and handling sound work. This can include signal processing, synthesis, programming, interface design, acoustics and the history of electronic instruments, alongside creative use of those tools.
- Music production: making recorded music. This covers arrangement, recording, editing, mixing, the producer’s role in shaping a track, and often the music industry context around releases.
- Sound design: creating and shaping sound for a purpose, often for picture, games, theatre, installations or interactive media. The focus is on how sound supports meaning, narrative or interaction rather than on songs.
- Audio engineering: capturing and reproducing sound accurately and reliably. This covers microphones, signal flow, acoustics, loudspeakers, live sound and the technical standards behind them, with more physics and electronics than the other strands.
Many courses combine several of these. Read the module lists of the courses you are considering. If they are heavy in mathematics, programming or acoustics, your statement should show technical curiosity. If they centre on portfolios and creative briefs, show how you make decisions about sound. Your evidence needs to suit the actual mix rather than a general enthusiasm for music.
How this differs from neighbouring subjects
Statements in this area often slide into material that belongs in a different application.
- Music and composition centres on musical material: harmony, form, notation and the composer’s ideas. In music technology the sound itself, and how it is captured, generated or processed, is usually the object of study. Electroacoustic composition overlaps with both, so if you write about composing, say what technology let you do that you could not do otherwise.
- Music performance is about your own playing. An instrumental grade or band experience is relevant here mainly for what it taught you about sound: how your instrument behaves when recorded, or what a monitor mix needs to give a performer.
- Drama, theatre and production includes sound for stage, but as one strand of making theatre. If theatre sound is your main interest, explain whether you are drawn to the audio side (playback systems, cueing, designing soundscapes) or to production more widely. That answer may point you to a different course.
Interests that make good material
Strong statements usually narrow down from “I love music” to a specific question or problem. Some examples of the kind of interest that gives you something to say:
- Why a vocal sounds closer and more intimate with one microphone technique than another, and what is happening physically.
- How a particular producer’s records achieve their sense of space, and what you tried when copying it.
- The difference between sampling, subtractive synthesis and physical modelling, and why you prefer one for certain sounds.
- How loudness and dynamic range changed across decades of recorded music, and what that does to listening.
- How film or game sound tells the audience something the image does not, for example off-screen sound, silence, or sound that changes with the player’s actions.
- Why a room you know (a school hall, a church, a stairwell) sounds the way it does, and what you could change about it.
- Building or coding something: a patch in a visual programming environment, a simple effect, a controller, a modified pedal.
- Accessibility and audio, such as audio description, hearing loss and mixing, or sound in assistive technology.
You do not need several of these. One interest followed through properly is more convincing than a list of genres and software.
Choosing evidence for each strand
Music technology
Useful evidence shows you wanting to understand how the tools work, not just using them. Examples are learning what a filter or compressor does to a waveform, trying to recreate a classic synth sound from scratch, following a beginner programming course and applying it to audio, or reading about the history of a technology such as tape, MIDI or the sampler. If you have made something, describe what went wrong and how you worked out why.
Music production
Evidence here is about decisions. Finished tracks matter less than what you did and why: choosing to strip back an arrangement, re-recording a part because it clashed with the vocal, comparing your mix with a reference track on different speakers and finding the low end disappeared on headphones. Working with other people’s music, such as recording a friend’s band or producing for a school singer, is especially useful. It shows you serving someone else’s idea rather than only your own taste.
Sound design
Show that you think about sound in relation to something else: an image, a space, a story or an interaction. Redesigning the sound for a short film clip, recording and processing everyday objects, building ambiences, or making sound for a school play or a game jam all work. Reflect on intention. Say what the audience should feel or notice and whether your sound achieved it.
Audio engineering
Show that you care about accuracy, signal flow and problem-solving under constraints. Running sound for assemblies or gigs, troubleshooting feedback, setting up a multitrack recording, or measuring and treating a room are all relevant. Connections to physics and mathematics (waves, frequency, logarithms and decibels, electricity) are particularly worth making for engineering-leaning courses.
Relevant schoolwork
You can draw on many school subjects if you link the content to sound specifically.
- Music or music technology qualifications: name a specific task, such as a recording or composition brief, and what you learned about technique. Avoid simply listing the qualification.
- Physics: waves, resonance, interference and electricity relate directly to acoustics, microphones and loudspeakers. Linking a topic to something you heard or tried is stronger than stating that physics is relevant.
- Mathematics: trigonometry, logarithms and functions underlie waveforms, decibels and filtering. This matters most for technology and engineering courses.
- Computing: programming, logic and data representation relate to digital audio, sampling rates, bit depth and audio software.
- Media, film or drama: analysing how sound works in a scene or production supports sound design applications.
- Design and technology or electronics: building circuits or enclosures connects to hardware, controllers and effects.
Activities and preparation worth considering
None of these are requirements. They are accessible ways to give yourself something concrete to reflect on.
- Free or low-cost audio software is enough to practise editing, mixing and synthesis. What you learn by setting yourself a specific exercise matters more than the tool.
- Critical listening: take one track or film scene and write down what you hear in each layer, then compare it on different playback systems.
- Field recording with a phone, followed by editing and processing the results into something.
- Volunteering on sound or lighting for school events, places of worship, community theatre or local venues.
- Online or library reading on acoustics, recording history or synthesis, chosen to follow a question you already have.
- Game jams, student film collaborations or remix exercises that give you a brief and a deadline.
Expensive equipment, home studios and paid courses are not what makes evidence strong. Writing well about limited tools, and what those limits taught you, can be more persuasive.
If you have no direct experience
Plenty of applicants have not worked in a studio or run live sound. Ordinary experiences can still be relevant if you are honest about what they show.
- Hospitality or retail work: you may have noticed how background music, volume and room noise affect customers, or dealt with a basic PA system. This shows attention to sound in real spaces. It does not show technical audio skill, so do not present it as such.
- Caring responsibilities: caring for someone with hearing loss may have made you aware of how speech clarity, background noise or hearing aids work. This can support an interest in acoustics or accessible audio. Keep the focus on what you observed and wanted to understand, not on claiming expertise.
- Gaming: playing games can lead to genuine interest in adaptive sound, spatial audio or how sound conveys gameplay information. Hours played prove nothing by themselves. Analysing how a specific game uses sound does.
- Playing in a band or choir: this gives you experience of balance, rehearsal acoustics and how performers hear themselves. It is performance experience, so link it to sound decisions.
- Podcasting, streaming or video editing: these involve real audio tasks such as noise reduction, levels, dialogue clarity and microphone placement. Describe a problem you solved rather than follower numbers.
- Repairing or tinkering with electronics: fixing headphones or building kits shows curiosity about hardware. It does not amount to an electronics qualification.
- Listening habits: deep listening across genres is a starting point. Show what you noticed about how recordings are made, not just what you like.
What useful reflection looks like
Admissions readers can learn little from “I produced several tracks and developed my skills.” Reflection becomes useful when it shows how you think about sound. A pattern that works is to describe the problem, the decision, what you heard, and what you would do differently or still want to understand.
Weak: I have been using production software for three years and have made many beats.
Stronger: My early mixes sounded full on my headphones but thin on a phone speaker. Comparing them with commercial tracks showed I was relying on sub-bass that small speakers cannot reproduce. Adding harmonic content higher up helped, and it made me want to understand why our hearing fills in missing fundamentals.
The stronger version names a specific observation and a method, and it ends in a question that a course could answer. It does not claim the problem is solved.
Pitfalls specific to this subject
- Equipment and software lists. Naming every plugin or piece of hardware you own says little. Mention a tool only when you explain what you did with it.
- Confusing taste with understanding. Your favourite artists are relevant only if you analyse something about how their records sound.
- Overstating status. Calling yourself a producer or engineer on the strength of home projects can backfire. Describe the work accurately instead.
- Streams and followers as evidence. Audience numbers show reach, not what you learned. If a release matters, write about the process.
- Ignoring the technical side. If the course includes acoustics, maths or programming, a purely creative statement may suggest you have not read the course content.
- Ignoring the creative side. Equally, a statement that is all specifications can miss the purpose of the sound on portfolio-led courses.
- Treating the course as job training. Studying this subject is not the same as becoming a studio engineer or film sound designer. Career aims are fine, but show interest in what you will study, not only in where you hope to end up.
- Writing as a performer or composer. If most of your evidence is about playing or writing music, check whether a music performance or composition course fits better, or reframe the evidence around sound and technology.
For general advice on planning, structure and editing, read our personal statement writing guide.
Music technology and sound production personal statement examples