Comments on: Resume Advice

By: Malcolm

Malcolm — Fri, 15 Feb 2008 19:50:00 +0000

There are usually two ways to get considered for a job: either you know someone or you send a resume. Since we’re talking about resumes here, the main considerations are explaining the relevant experience, a reasonable and growing career arc, no unexplainable gaps, and no unexplainable series of short-term positions. It needs to be logically laid out and check your spelling. You’ll probably need a resume even if you know someone, so take your time.

Just as importantly, though, is how you submit a resume. Sending it to jobs@SomeCompany.com doesn’t usually get the results you want. Send it to someone specific or have a recruiter do it for you if you want to improve your chances.

By: Ian Schreiber

Ian Schreiber — Fri, 07 Dec 2007 08:13:00 +0000

Each company has its own hiring practices and procedures.

At the very least, if the instructions for applying on their website say “Send applications for programming positions to programming-jobs@gamecompany.com” or if you have to push a “send application for this position” button on their website somewhere, then rest assured HR (and everyone else) knows the position you’re after, and putting it in your objective is redundant.

For what it’s worth, I haven’t had an objective on my resume since I graduated college. The article linked to makes a good point that a unique objective can make you seem more like a human being… but if you’re networking properly within the industry, the people at the company where you’re applying already know you as a human being, so the whole importance of “make your resume stand out from the crowd” shifts to the importance of “make sure your resume shows how much you totally kick ass, and that you’re not just all talk”.

By: Patrick

Patrick — Thu, 06 Dec 2007 23:42:00 +0000

Everytime I update my resume I end up not getting a job, and everytime I get a job or hire somebody it ends up not involving a resume at any point. I’m lucky like that.

By: David

David — Thu, 06 Dec 2007 23:04:00 +0000

That's why the objective is a beast when it comes to creating a resume. It's more of a situation dictates, and a gamble. I didn't get my information from people who have never hired people before, I interacted and got feedback from people who worked in the software industry for many, many years and hired folks.

I'll talk to some more people and figure this out.

Thanks for the discussion, Darius.

By: Darius Kazemi

Darius Kazemi — Thu, 06 Dec 2007 22:27:00 +0000

HR knows you're looking for a programming job because you either submitted it through their online form, or in the email you sent, you included a line about, "Here's my resume and cover letter for the programming job you have open."

And you can say you want to program in your objective in a creative way. "I thrive in an environment where we're developing cutting-edge algorithms on limited hardware" is a pretty good way to say that (as an example).

University resume advice is almost always horrible.

By: David

David — Thu, 06 Dec 2007 22:17:00 +0000

Does HR review resumes to a certain extent? I'm willing to bet that they don't want to waste the time sorting resumes by spending time deciphering objectives. This is especially true for some place like Google, whom gets hundreds of resumes. I understand what happens when it reaches YOUR desk, but the objective is concerned with GETTING it to your desk. If you can't even do that, then you fail.

I appreciate the feedback. This does go against everything I've been told since day 1 here at the university; from several classes, and in our employment office.

I also understand that the university and the real world are two completely different animals.

By: Darius Kazemi

Darius Kazemi — Thu, 06 Dec 2007 20:44:00 +0000

David, I have to disagree. You really need to assume that nobody's going to read your cover letter when writing a resume. Many companies do read cover letters, but a lot of them don't.

And objective that reads "A position as a game programmer" is a waste of ink. I already know you want to be a game programmer because HR handed me your resume and said, "This guy wants to be a game programmer." I want to know what you're passionate about. You can do that in 20 words, you just need to work on it.

Remember, the resume is about snagging an interview. You're right that you don't want to bore someone to tears, but if I get two resumes, both with the same skill set, and one of them has an objective that in 20 words makes the applicant seem like an interesting person: who do you think I'm going to call for the interview?

Again, while you should always include a cover letter, the resume should stand on its own.

By: David

David — Thu, 06 Dec 2007 20:28:00 +0000

I tend to update my resume a lot since I've been in College. My first semester here, I wrote a resume and since then, I update it every few months, and tailoring it to specific career opportunities; internship, game programming, etc.

As for probably one of the most important aspects of a resume, the objective he gives a example for goes against all things that are holy. It's incredibly long, vague, and well, not really an objective.

Objectives are there to be brief and to the point. Your cover letter is designed to sell yourself, not your objective.

Good objective:
'A position as a game programmer'

Simple, and to the point. The reader doesn't need to waste time and he/she can get to the meat of the resume quicker.

But, what do I know? Nothing so far, because I'm not employed nor have I needed to hire anybody. I'd like to hear your feedback on why this is a good idea. Especially since the GDC is coming up and I could potentially be handing my resume to somebody.