Filed under: Developer
Dev Chair : Resume tips
Resume
- Tailor your resume for the job you are applying to:
- Don't mention the Waterfall model or UML skills if you are applying for an Agile development role unless you state explicitly that you want to learn the new process, and vice versa.
- Don't include MCSD or MCP logo if the company is not interested in certifications. You're probably very proud of your certs but some people love them and some hate them. To me, a certification means you know the answers to the certification exams questions, not necessary how to apply that knowledge. And with the rapidly changing field of software development and the glacial update cycle of certifications, what you know from the certification probably is not what the employers are looking for anymore.
- Include skills that you are actually proficient in. Don't include skills, tools or packages that you only have a passing familiarity with. Mentioning VB when you only experimented with it in college between Quake sessions doesn't count. The temptation is always there to embellish the resume with lots of diverse skills, especially for college graduates with limited work experience. But all that does is open up opportunity for the interviewer to grill you on areas that you have no answer for.
- Leave out skills that are taken for granted or irrelevant. Conversely, don't include skills that every computer users would know. For example, mentioning Microsoft Office skill when applying for .Net programming job. They don't add anything to the resume, and at best detract from it.
- If job hunting through a recruitment agency, verify what they send out as your resume. Recruiters tend to be mostly ignorant of the software development field and our terminology so they may butcher your resume. Some may be just plain greedy and would alter a resume in order to get you an interview.
- Proof read your resume. Don't send out resume with spelling mistakes in it. Microsoft Word has spell-checker and grammar checker built-in. Use it.
- Don't provide web site address if it is not current. The worst thing you can do to yourself is to show potential employer a web site from the 90's with clashing colors, use of <marquee> tag, and an out-of-date bio and resume. Blogs are all the rage but not appropriate for a resume, unless you are applying for a blog-related job!
Think of your resume as a precision guided weapon instead of a dumb 2000 lb. iron bomb. Yes, it takes effort to tailor your resume for each job. But if you do not care about the job enough to do spend the time, then why bother applying in the first place?
With Halloween fast approaching, it's a great time to get in some practice defending your territory against zombies. In Graveyard Shift, you take aim at zombies and other creepy-crawlies, blasting them into splatters of cartoony green guts. It's a casual first-person shooter, and it's very easy to get the hang of - use the mouse to aim, click to fire. Graveyard Shift has at least 15 levels, and it might even have some secret stages I haven't unlocked yet.
They key to getting good at Graveyard Shift is learning to use ...
Reader Comments (Page 1 of 1)
Mike said 5:40PM on 3-20-2007
Firstly, I don't think I'd want to take résumé (or resumé) advice from a person who cannot correctly spell the word.
Secondly, I think the certification advice is bad. Obviously you've never taken one of those certification exams. Unless a person was outright cheating, the certification is a good indicator that the person at least has a base knowledge on the subject. Of course, you don't hire someone based on that alone, but it's a good piece of information to pile on.
Third, is this site losing focus? I like to come here and read posts about software and nice free things I can download. There are enough sites covering résumé tips, DCMA tomfoolery, **AA shenanigans. Please, stick to what made this site useful.
Reply
Alex Rudloff said 12:08PM on 3-20-2007
Mike: "Resume" is the US centric spelling of résumé, and is aptly spelled for many of us. Most everyone else uses CV anyhow.
This is great advice. I feel the need to echo the point "Include skills that you are actually proficient in."
Honesty is the best policy when job hunting. The last thing you want to do is lose a great job after you've landed it because you don't know what you're doing!
Reply
Garth Braithwaite said 12:07PM on 3-20-2007
to the comments above -
I am sure you have valid points, but if you don't like the topic that is being presented you don't have to read the post. It is usually pretty easy to tell from the title of the article whether or not you might be interested in it.
I love DS's technical focus, but I also welcome any random comment or fact they think I might find interesting. If it doesn't appeal to me I just scroll past it.
Reply
kevjohn said 3:46PM on 3-20-2007
Rudloff: No, the last thing you want to do is not to get the job in the first place! Wouldn't it be better to lose a job you land rather than to not have landed the job in the first place? If nothing else, you just might learn a few things before they give you the boot. And you'll have a paycheck or three to show for your deceit and ineptitude.
Reply