I’m occasionally asked how I got into the games industry and while my path is fairly straight forward I can ask almost anybody else at Codies and they’ll tell a different story of their own path into audio design. The core audio department here at Codies Birmingham consists of three audio designers, myself in a senior position as the project lead designer, James “Duke Uterus” Kneen in a senior position and Dave Gurney in a junior audio designer role. Here we share those three stories.
I never formally interviewed for a job in audio when I was originally taken on. I’d started out as a QA technician at Codies and got talking to the audio department and one of the audio programmers. As well as continuing with my general QA bug reporting I also went out of my way to add each and every audio related bug I could find for each project I worked on. The benefit here was that I was immediately identified by the audio department due to how few people in QA seemed to concentrate on entering audio bugs at the time. On top of that I’d make it my mission to go over and chat with the audio guys that I knew a couple of times a month – not so often that I’d become annoying but not too infrequent that they’d forget about me. The important thing to remember here was that I’d never normally get a great opportunity like this had I not worked in QA. I couldn’t exactly turn up unannounced at game companies for a chat with the audio guys. Even handing in CVs and show reels and bugging designers via email doesn’t have quite the same impact as being able to walk across the office and interact with people face to face.
Luckily, at this stage two great steps forward happened, firstly the audio guys mentioned that there might be some “dog’s body” work coming up. Generally this would be tasks such as chopping and organising assets or adding regions and markers to projects. The second step was that one of the audio teams really needed somebody to focus on audio bugs for a particular game – having seen my list of audio focused bugs on the database and knowing I had an interest in audio they approached QA management and asked if I’d be interested in some focused QA audio work. Even to this day this is quiet a rarity; it involved me temporarily moving over to the audio department and specifically working with the audio guys to identify as many audio bugs as I could, all while still under QA management and budget. You can read more about my QA job role here:
New beginnings – My first desk in QA.
After several months of working with the audio team they decided to take me on permanently in a junior capacity. It’s worth adding that before working in QA I’d been studying music technology for 3 years at college and a further 3 years at University. I then gained around 1 ½ years of QA experience which in itself provides great background knowledge when moving into games development. Two of my previous articles go into more detail on my time in education:
I’m actually the only member of Birmingham audio who started off in a QA role, Dave (our junior) completed a master’s degree in game audio before applying for the junior role we opened up. Both Dave and I enrolled on generalised audio / visual media degrees but Dave furthered his education with a game audio master’s degree where he got to grips with middleware such as FMOD and Wwise. At degree level neither of us went into game audio territory, the assignments I completed during my 3rd year were specifically massaged to steer towards game audio but there was no training with any middleware or any game audio practices.
Dave applied to us straight after his master’s so he had gained no previous professional experience. One of the audio designers at Codies contacted him through Linkedin after seeing his profile, at which point Dave sent in his CV and show reel for us to consider. James and I looked through all the CVs that were handed in before narrowing down the candidate list to around 6 or so or of our favourites. This decision was based on multiple factors such as the applicant’s previous experience, the quality of their show reel and how excited they seemed to be about working on racing games. For us it wasn’t essential that our junior be into racing or racing games but let’s say in a situation where two very similar applicants applied then somebody with a good interest in motorsport would have the edge. Not only would this mean the applicant is less likely to tire of the sort of audio design work we do but they’d also be more likely to be excited to attend recording sessions, watch reference footage and suggest and work on very specific features present in motorsport. This might include things like turbo systems, detonations, engine bundles, mechanical tools and so on.
David Gurney – We insist he wears this hat when working on critical tasks.
Once we had narrowed down our search we held a skype or phone call interview with each candidate. James and I went through each candidates show reel; before we gave them feedback we asked them to critique their own show reel to see if they understood where their short comings and strengths lay. We then provided our own feedback on the show reel before going over each applicants CV and asking them for further questions. Typical lines of enquiry here were questions such as “Why do you want to leave your current job?”, “What games do you play?”, “Do you play any Codemasters games?”, “How do you feel about re-locating?”. After narrowing our search down further we finally invited our candidates in for a face to face interview. By this stage we were finding it difficult to choose one applicant, there wasn’t a lot in it and in all honesty I’m sure any one of these guys would have fitted in just fine. The main goal here then was to talk to each candidate to see how well they would fit in and so we discussed their hobbies, games, audio and other generalised chat. Importantly though, Dave was also excited at the prospect of working on a motorsport game; he suggested ideas for systems and asked us how existing systems were implemented. He’d asked questions about recording sessions and what we’d be expecting from him. He showed a clear interest in what we were doing and how he’d like to help build upon our work if he were given the opportunity. James and I both felt it was important to take on somebody that we could get on with as a friend as well as a colleague; after all we have to work very closely with each other day in day out.
Unlike Dave and myself, James doesn’t have any formal education in audio design. James seemed destined for a job in the audio industry; he grew up with a passion for all things sci-fi and audio related. Sometimes I wonder if he’s part synth – both of the android and musical instrument varieties. The “Duke” as we affectionately call him here at Codies first became interested in audio when his parents bought him a portable cassette recorder when he was a child. He started off recording joke “radio” shows and silly sounds before moving on to recording episodes of Doctor Who. Listening back to these recordings sparked an interest in sound effects and synthesis. This passion stuck with James through his teenage years and the first wave of hip-hop only helped cement this passion. From here on out James decided that he’d like one day to become a sound designer. With no qualifications to speak of James decided to go down the experience route and seek out a tape operator position in a studio. Unfortunately James found this extremely difficult to secure and ultimately failed.
Exterminate! – Where it all began for James.
Although James remained passionate about audio and production he decided to seek alternative employment and instead tried to break into the games industry. James considered trying to start a career in QA (similar to my own route into games audio). By his early 30s he found himself working for Empire Interactive but rather than a QA role he found himself burning game builds to disc. This ultimately would form the basis of his path into game audio. After a few years James made the move over to EA in a similar role and during his time here he’d spotted the recording studio and over time became friends with the audio studio head. Not one to miss a great opportunity James sweet talked his way into using the studio for a few evenings a week. A junior audio designer role eventually came up and after cutting his teeth with the EA studio gear James decided to apply. Once again the Duke was on the cusp of making it into one of his dream jobs but it was not to be. Although interviewing well, James lost out to an applicant with current experience.
James “Duke Uterus” Kneen – He’s really not that grumpy, he really is that old though.
An audio assistant role eventually came up which James did secure – finally he was in! By this point James was into his late 30s, so a relatively late starter. James currently holds a senior audio designer role here at Codies Birmingham and readily admits how difficult his path to this position has been. I’d asked him for advice to pass onto up and coming audio designers seeking a position within the industry to which he replied:
“Securing a position in game audio is difficult, but not impossible. It’s about your attitude, passion for audio and your tenacity. If you keep on keeping on, you will do it. I am of course biased but I reckon it’s the most interesting and fun job on the planet.”
Three designers all with different paths into the industry; so where does that leave you if you’re seeking the best way to secure a job? Well you’ve still got to carve your own path out but here’s some general advice to help you along the way.
Let’s get the obvious out of the way first. The important points to remember are to network and gain some experience and while these steps are by no means sure fire ways to success they’ll greatly help you out. About a year ago I had a situation where two budding audio designers contacted me about work experience; one was a recent college graduate who was mainly interested in composition while the second was on a temporary contract in QA. Both prospective designers had graduated from sound related courses at college and both had at least started out on the right track; they’d done what many in my opinion fail to do. They had both contacted me and politely introduced themselves and shown some level of enthusiasm. As always I asked both of them for a show reel and a CV and asked them what they wanted to get out of any work experience. The guy in QA replied to tell me he would have to update his CV – I heard back from him about 4 months later! I politely informed him that unfortunately he’d missed the boat on this occasion as I’d taken on somebody else who’d replied with the information I’d asked for. The college graduate who applied was given a shot, despite primarily being interested in composition.
F1 2016 – Sound design by Brad, James and Dave.
A decent education does help and in all honesty these days I don’t know of many young audio designers without a degree or higher. That being said, you could land a 1st class honours followed up by a master’s in game audio and you’d still not be guaranteed a job. Considering most of the other candidates will also have a degree it probably won’t do a lot to help you stand out. Think of your education then as a good fundamental framework once you’ve landed the job. It’s pretty obvious when we’ve spoken to or taken on work experience designers which are from a University background and which are not. That’s not to say there aren’t exceptions to this rule.
Experience is great but none of us in Birmingham audio took the work experience path and although it’s a great way to get a foot in the door we quickly discovered our work experience graduate didn’t have enough knowledge to be considered anywhere near ready enough for a job in the industry. I have however dealt with one intern here at Codies as well as managed a handful of University students on weeklong work experience. What I will say here is that you should only take on whatever work experience you feel you can manage. Generally you’ll find yourself forking out for travel and accommodation as well as working a full time, unpaid job! On top of that jumping in head first to something you’re totally unfamiliar with may actually deter a future employer from taking you on. Before taking on any experience try and find out what software the company uses, ask what their day today workload consists of then prepare yourself. Work experience is valuable and not easy to come by so if you do land a temporary position utilise it and make the most of it. Jump on new or unique tasks; ask the designers what they are currently working on and how different systems work. Don’t be too pushy but make it clear that you are interested in learning all you can in the limited time you have at the company.
Apply for the right positions and tailor your CV and show reel to appeal to these positions. We had various applicants apply for the role which Dave ultimately ended up getting. Dave handed in a show reel which highlighted various types of sound design, but importantly it also included motorsport. Not only did this show he was interested specifically in the role he was applying for but it also highlighted his aptitude for tailoring assets to suit motorsport content. Contrast this with some of our other applicants who handed in show reels full of low budget mobile games and no examples of motorsport. Some applicants occasionally send in show reels which only highlight compositional skills rather than sound design ability. We were specifically looking for a full time sound designer and there was no mention of music in the job specification so highlighting these skills didn’t really give us any idea as to whether the applicant was suitable for the position. It’s important to note at this point that I’ve had quite a few composers contact me over the years asking for advise, work experience or just to pass on their show reel and CV. I’ve explained to each of them (including our previous work experience graduate) that generally speaking not many game devs will take on a full time in-house composer – it’s just not something that happens. My advice here would be to go freelance or work on some small indie projects. If you are clued up on sound design you could get into the industry and eventually you may even find that you’ll be suited to score some of the projects you’re working on but composition shouldn’t be your primary driving factor.
Some of the really great applications we received showed off actual middleware implementation and video of middleware projects in action. I personally find this an excellent and interesting way to highlight sound design ability as well as the ability to implement finished assets and take into consideration variety and dynamically altering soundscapes. Audio for games is quite a different skill from track laying for linear media such as film so highlighting this ability proves you’re able to fulfil some of the requirements for a job in game audio.
Finally, as James experienced, don’t be deterred by rejection. We’d actually turned down a previous applicant because we were only taking on one designer. It pained us to turn him away as he was just as good as the applicant we offered the job to but we had to make a decision. Several months later we called him again and offered him a job on another project. You’ll apply for jobs and most likely you’ll be rejected for quite a few of them. This could be through no fault of your own, maybe another applicant took the position for a lower salary, maybe you were just as good but a coin flip decided on another applicant for the one vacant position, maybe your skills were tailored for a different role. Refine your CV, ask the company for feedback on why they didn’t proceed with your application, continue working on your show reel and continue applying.