Hey y'all, I'm a student right now and I'm looking to get into the game programming business after I graduate. My problem is, I've done a lot of stuff so far, but not much that is related to game programming. This is because I was mostly focused on getting my PhD in CS for a while, but I decided to pursue my long awaited dream of game programming first. I'm wondering if there's something I should remove/add to it so that I'm more likely to get an entry-level job in the biz. Resume Updated Resume [Edited by - napi1phi on August 30, 2009 8:33:33 PM]

It looks mostly okay for a beginning. You still need a lot of editing work.

Always remember that employers are interested in two things: 1) Will you do the job well, 2) Will you fit in? Everything on this paper should provide evidence toward both of these questions.

If it does not answer those questions, it will end up in the trash. If it does answer the questions and the employer doesn't like the answer, it will end up in the trash. You can fix the first issue by making sure every word provides evidence. The second issue is something you have no control over but it is a good thing because they are self-pruning the jobs where you would be a bad fit.



You are too young to have earned two pages. If you were in Europe and were using a CV (where multiple pages are normal) then it would be different. In the US, plan for one page for each 10-15 years of work experience.

Why did you separate the two GPA? You can list two bachelor’s degrees with a single perfect GPA.

Cut the "Wrote two games" line. If they are a game company then it deserves to have a few lines to itself. If it is not a game company then you should probably not have them.

Your coursework is vague as to what you actually did. For example, data structures and algorithms are core to computer science and mentioning that you had a class on them is useless. I notice you didn't list Calculus I, Calculus II, and Calculus III, which is much like listing data structures. I believe math majors should have a lot more math classes so that list surprises me. Instead of giving a transcript of courses just include the projects and topics that most interested you and that also are most needed for the job. You can use the space to include details of specific projects that really engaged you.

Your Work Experience seems confusing. Did you honestly simultaneously hold three real jobs while also attending college with a perfect GPA? It seems extremely unlikely. With my resume-reading glasses on, I would guess that you helped a friend of your family with their store computer a few times, and your other jobs were part of a school stipend. Maybe the lab assistant job was an actual job with scheduled hours for workers, direct reports, and hourly timecards. If it wasn't a full-time or part-time job, it usually doesn't deserve to be listed. School stipends where you are paid for a few hours of lab work with your homework should be listed with education, if you even list them at all. If you were employed with the lab then it is a different situation and should be listed as regular employment.

Vague statements are not helpful at answering the two employment questions. Saying "Troubleshoot lab computers and take the necessary actions to fix them" does not help employers know that you can do the job, nor does it let them know how your personality will fit in. "Maintain the store computer and wireless network" is similar in that it doesn't give any useful information about the extent of your abilities or say anything about you personally.

The blob of text with languages and technology is useless. You rattle off languages but have said nothing to this point to demonstrate any of them. What did you do that involved "C/C++"? ("C/C++" is not a language, and any good interviewer will question you about it either seriously or in jest.) What is your depth of knowledge in each technology? What did you do in C#? How much is "some" ASP and "some" 8088 assembly? Did you pick these up as part of a requirement for a class, or have you actually used them in a significant way? Without context, I will assume that almost all of it was just a few weeks of exposure during your coursework.

Stating you have "Exceptional" skills is not quantifiable. Exceptional compared to what? Judged by whom? You need a quote from authorities or specific external accolades, not your own assessment. If your boss gave you a written performance review and it said you were the best he had seen in 15 years, then that would be something. If a teacher wrote a letter of recommendation saying you were the best student they had seen in ten years of teaching that that would be something. But just saying you are "exceptional" is nothing at all.

You would be best served by cutting both blocks of text and incorporating them in the details of other sections. This provides context and a way to estimate your competency. With context and competency, an employer can decide if you may have the skills to do the job.

Activities section is a good start. Add more details about what you did in the contests, citing specific languages and technologies, rankings and awards. You already started this with a few details like top 18% out of 1675, and third place awarding some cash. You need more details. This is where you should put your list of languages and technology. For the gaming club, include a note of how many times you did it. Setting up two LAN parties for 15 and 16 people is much different than coordinating between 15 to 25 people in weekly events for 12 weeks.

The academic awards belong back in the education section or should be cut. Grants and scholarships should get cut. You are applying for a job out in the real world, not academic funding.

Cut the line about references on request. They are a waste of space. Every employer knows about references. If they want references they will ask you for them on a separate job application when you come in for an interview.



So it mostly contains good information. Add some details to everything. Eliminate the generic buzzwords and the stuff that won't provide employers evidence they need to hire you. Consider the zen of removing every unnecessary element that doesn't apply to the two hiring questions.

Quote: Original post by frobThe blob of text with languages and technology is useless. You rattle off languages but have said nothing to this point to demonstrate any of them. What did you do that involved "C/C++"? ("C/C++" is not a language, and any good interviewer will question you about it either seriously or in jest.) What is your depth of knowledge in each technology? What did you do in C#? How much is "some" ASP and "some" 8088 assembly? Did you pick these up as part of a requirement for a class, or have you actually used them in a significant way? Without context, I will assume that almost all of it was just a few weeks of exposure during your coursework.

Everything frob has said has been great advice. This point in particular I'd like to go into a bit more depth on.

I interview a ton of people and anytime I see a section on "skills" or "technologies" I ignore it. It tells me nothing about what they know and I can only assume they had passing experience with each skill they listed. If it isn't explained on the resume how much they know in it I assume they've only dabbled with it.

Sometimes on the phone interview I'll ask them questions that require much more then passing knowledge if they list it as a skill. A lot of the time I catch people for not knowing much at all in the particular topic.

-= Dave

Also, the most important thing is you don't really have much at all any game development experience.

According to your resume the only game you've developed was for a project during your school. That shows me that outside of class you do not like to work on hobby game projects which means we'd have to do a lot of training to get you up to speed. For me that would mean I'd toss the resume.

Try creating a game demo, real time graphics demo, game related physics demo, or perhaps an AI demo.

Any demo that demonstrates that you have a passion for developing games.

-= Dave

Quote: Original post by napi1phi
My problem is, I've done a lot of stuff so far, but not much that is related to game programming.

As an employer I would be wondering why, if you want to be a game programmer you have not done any game programming - or to turn it around, how do you know you want to do it for a living when you haven't done it.

As for your resume have a read of this http://www.obscure.co.uk/blog/2009/03/23/your-resume/.

Frob, Dave & Dan (Obscure) - My god, thank you so much! Your input was invaluable!

Frob - It's interesting that you hit my work experience right on the money. I was doing side jobs once a month for my family friends' store while working at school. Moreover, the summers were completely encompassed with my research positions.

I implemented almost all of the changes that you guys recommended and removed a lot of "padding" that was unnecessary for what my goal is (entry-level game programmer).

Also, my game programming experience IS limited at this point because I was just brought into it during Fall of last year (when I made SHAZAM for my class. It was the most fun I've ever had with programming). But, I currently have two side projects in the making: One first person shooter that utilizes OpenGL/GLUT in C++ and another first person game that utilizes Panda3D. It's my goal to at least finish the Panda3D one soon so I'll be able to start sending my resume off.

Here's the updated resume, more input is, of course, welcomed:

Updated Resume.

Quote: Original post by napi1phi
Also, my game programming experience IS limited at this point because I was just brought into it during Fall of last year ...

Good that you have identified the issue. Now you need to get on and address it. Start working on some game projects for your portfolio.

Good luck.

Quote: Original post by napi1phi
Here's the updated resume

It is much better.

There are four lines that wrap with 1-3 words. That is a poor use of space. Fix it. Either fill in the rest of the line with details or remove some words to add lines elsewhere. Use that space for additional details that show you can do the job and will fit in.

I agree with the advice that's been given. From here I would focus on actually working on game projects. Game recruiters are looking for how you can help them make a successful title. And how can you show them you can do that? By making your own successful titles!

Try to find others to work with if possible. Spend several months on the project and make something substantial. Cite the number of lines of code.

Best of luck!