Posted on

I Used to Make this Resume Mistake

(You’ve got 3 days left to grab C# Implementation with Wwise and Unity or anything else on my store at a discount)

Since I started writing and being more public with what I do, I’ve had quite a few requests to look at or give advice on people’s resumes.

(That’s not an invitation to reply to this email asking for me to look at your resume, FYI)

More than anything else, even for the technical sound designer-oriented folks, there’s one big thing that makes me laugh or roll my eyes on a resume.

Okay, so I lied, there’s two things – but I’m only going to talk about one of them right now.

It’s putting a bunch of programming languages on your resume.  Including, and specifically, C++.

Poor Practices

When I read resumes that include something like

“Programming Languages: C++ (Learning), C#, Python, JavaScript, Java”

On the resume of a Sound Designer, Composer, or Technical Sound Designer with limited experience – I have a really hard time not rolling my eyes or laughing.

To some of you, that’s going to sound like I’m a total jerk who has no respect for you.  I’m not a total jerk (kidding) – but it is hard to take someone seriously who has dabbled in programming and then says they’re proficient in a number of programming languages.

Why?  Because that’s what I did! (of course…)

Until I really met some senior software developers and got to know them and their work – I truly had no idea the depth and breadth of expertise of skilled individuals within software development.  I’ve always had specific things I wanted to learn – web development, audio software development, mobile development, etc. – so I would go take a free (or cheap) online course, make a thing, and call myself “proficient”.  I felt really good about it too!

I’m betting with a few of you, that hits home pretty hard.

So here’s the thing – especially with lower level programming – understanding syntax is different than language proficiency.

You’d probably agree with me too if I cornered you on it.  For example, you might list Python on your resume like you “know” it – but do you feel comfortable going out and applying for Python jobs?

Additionally – my hypothetical example above illustrates another issue – what does “C++ (Learning)” even really mean?  What if you were interviewed by a company’s software developer and had to answer that?

“Well, I’m going through some tutorials on CodeAcademy”

That’s not a good answer – that’s just something you should’ve left off.

Don’t Pad Your Resume

From what I said above you probably think I’m totally against listing out your knowledge of programming languages on your resume.  I’m not.  If you’ve done more than a free online tutorial and you can your abilities to help a company (which is different than wanting to use your abilities) – I’m 100% for you leaving it on.

But the example above is a showcase in resume padding.  To my understanding, experienced software developers applying for jobs aren’t listing out that they know 4-5 different languages – they’re focused on one or two that they’re going to use on the job.  Usually the only reason you’re going to list off a bunch of languages “you know” is to appear to be more impressive of a candidate.

Except, to anyone who knows what they’re doing – it’s a loud indicator that you might not.

So here’s my suggestion for you…

Self-Evaluate

Consider if you know how to use some programming languages or not.  Completing a free tutorial doesn’t count (in my opinion) as resume experience.  On the other hand, creating a usable application, does!

So, if you’ve built your own demo game in UE4 or Unity and worked through the coding part and learned quite a bit – share that!

Perhaps you’ve built your own stand-alone applications that may not be audio related (I built something that saves and organizes my receipts for taxes, for example) – that totally counts!

Even class projects that required you working through real world code are relevant and worthy of sharing your experience with.

But if you just know some of the syntax, maybe you’ve built a personal webpage once or twice – be honest with yourself and ask if those things are really going to aid the company you’re working with.

Give Some Detail

In my opinion, your resume is a way to share your story.  I’ve said this a few times – mine is hard to get under 3 pages simply because it doesn’t tell my whole story if it’s shorter.

I imagine someone looking at my resume as if they’re looking at social media – it’s all highlights.  This person is seeing the best and most curated parts of me and my work that are also the most relevant and still tell a complete story.

If I’m just dropping a “Hey, I know 4 programming languages!” line item – what’s my employer supposed to take away from that?  There’s not much to glean, is there?

What if you include relevant project experience too (or, instead)?  That tells a different story.

So on my resume, instead of just putting “I know Lua”, I mention that I run my own website where I sell a set of REAPER actions written in Lua which people have paid for.  Even if they were free, I would still list that.  See how that gives plenty more context than “I know Lua”?  I can say from experience that being able to say I’ve sold my own software – even extremely minor stuff – has been a very impressive thing when I talk to potential employers

Be Ruthlessly Honest

You don’t want to start off on the wrong foot “faking it” with clients – especially over something so minor.  Nobody, seriously nobody, is going to pass you over because you only listed 2 programming languages you know instead of 5.

So, just be honest with yourself.  If you were asked about your experience in an interview – what would you say?  Do you have a cool story or an example you can share?  If you’ve just learned and never done anything with it, consider cutting the fat.

Last Word

Remember, especially for non-technical positions, most employers aren’t going to care that much about your programming experience for audio roles in AAA gaming.  Developers tend to be very protective over their game code, and with good reason!  If someone plays with it who doesn’t know what they’re doing, they can wreck the whole product!

So, as always, don’t struggle to be impressive – work to add value to other teams and people.


Copyright 2016-2021, NIR LLC, all rights reserved.