Learn to TEACH English with TECHNOLOGY. Free course for American TESOL students.


TESOL certification course online recognized by TESL Canada & ACTDEC UK.

Visit Driven Coffee Fundraising for unique school fundraising ideas.





Texas ISD School Guide
Texas ISD School Guide







Resume and Interview Tips

Top 14 Resume Mistakes IT Professionals Make
By:Eric Putkonen

1. Not knowing the purpose of resume
What is the purpose of a resume? It is not to be a complete history of you skills and experience. The sole purpose of the resume is to get you an interview. It's marketing. As such, it should be as short as possible (while conveying everything that must be communicated) and a single resume (ad) can not be used for everyone.

2. Not Targeted & Leaving Out Important Information
That brings me to #2. The best resumes I see, as a recruiter, are the ones targeted to the job for which they are applying. If you are a DBA that has done a lot of programming, if you apply to a programming position, leave off much of your DBA related information. It will only make you look like a DBA...not a programmer. Also, review the job descriptions carefully. Sometimes I find out that an applicant left out information that was listed in the job description. We didn't consider him because he did not list that experience. We are not psychics. If you don't list it on your resume, we don't know if you have the experience. Whatever is in your background that matches the job description, make sure it is on your resume. If the experience or skill does not relate to the position, you can safely leave it off your resume.

3. Lack of Specific Accomplishments & Just Listing Generic Duties and Responsibilities
Don't just list your duties and responsibilities. For one thing, everyone in your position can say the same thing. Secondly, what recruiters really want to see are your specific accomplishments. Quantify them. Did you decrease process time by 50%? Did you double the capacity of the network? Did you save the company $100K? What specific accomplishments did you have...and give the numbers with them. Figures are more impressive and seem more real. Also, this will differentiate you from everyone else. Your accomplishments are your accomplishments. Remember #2, list it only if it relates to the position.

4. Applying for Positions That You Don't Show You Meet the Requirements
As I said, the first thing I do is toss out everyone who is not a fit. They are adding to my work and clutter. Companies tend to automate the hiring process by using Applicant Tracking Systems (ATS). We know who is wasting our time...and we give even less time to people we keep seeing pop up. If we see an applicant who has applied to everything and never gotten far in the process, we are less likely to give them another shot. It is a bad policy to apply for everything and hope to get in. Later a position may come up that you match well, but you are tossed because "he applies to everything." I have seen candidates who have applied thirty or forty times to various positions. Everyone in the recruiting department knows who these people are by name and give no thought to ever bringing them in for an interview. Don't become known this way.

5. Visually Cluttered or Hard to Read
Don't type everything into paragraphs. Bullet points are your friends. You must keep in mind that recruiters usually give resumes 10 to 15 seconds on the first scan. When I have to review a couple hundred applicants, the first thing I do is toss out the people who do not meet the minimum requirements. So please make sure this is easy to spot in your resume. If we (recruiters) can't find it in 10 seconds, you lost the opportunity to have your resume fully read and ultimately the possibility of interview.

6. Assuming the Reader Will Know What You are Talking About
Somewhat related to #4 and #2. The first person who reads your resume may not be a technical person; many HR people are not very technical. So make sure type in your skills just as they are listed in the job description. For example, if the job description says you need J2EE, don't say you have Java EE experience...over vice versa. A non-technical HR person may not know it is the same thing. Another example is AS/400 and iSeries. The terms change over time, but don't expect HR to know this. Make it easy for HR by listing your skills in such a way that it is easily matched to the job requirements and description.

7. Typos and Grammatical Errors
Use spell check, proofread, and then give it to others to proofread. You don't want such errors in your resume. For one, it is seen as lacking attention to detail (something all companies want in employees). Also in this category, resumes having incorrect contact information. This happens, but don't let it happen to you.

8. Not Using Action Verbs or Being Repetitive with the Same Verb
Action words stress performance and motivation, but use a thesaurus. To see the word 'Developed' several times in a row does not look good and will to overlooked more. It is just psychology, more time is given to the unfamiliar. So vary the action verbs and be creative. If you are a programmer, you are not limited to developed, programmed, and designed. You could use saved, solved, attained, and other action verbs in a differently constructed sentence.

9. Having an 'Objective' in Your Resume
Often totally redundant, the objective often just says you are looking for a position that has been your title before in previous companies. The bigger danger is that a recruiter may be considering your resume for positions that would be a fit for your background but different than what you are doing. So, the recruiter may not call because it does not match your objective. Basically, you get pigeon-holed. Unless you are changing careers or fields of work different than your work history, no object need be listed on a resume.

10. Leaving Dates of Employment Out
Recruiters want to know when you were working somewhere. If you leave them out, that will be one of the first questions they ask you (assuming they call you). Please list both the month and year. Leaving this information out just looks like you are trying to hide something. It puts out a big red flag.

11. Graphics, Fancy Fonts, and Colors
I have not seen many good uses of graphics, fonts, and colors. Resumes should not have more than three fonts and two colors. This is my opinion because more than that it can go very wrong. Including graphics are a bad idea for IT professionals; graphics are something you might see for graphic designers. Considering most resumes go into an Applicant Tracking System, the images will likely be lost anyway and leave awkward voids.

12. Cutesy or Bad Email Addresses
Don't put on your resume that your email is something like "BigBoy69@whatever". In my career, I have gotten a few laughs by the email addresses people use. However, a bad email address on your resume shows a potential lack of judgment and awareness of audience (professional).

13. References on Request
Don't waste the space. We know references are available on request. Don't put this on the bottom of your resume.

14. Lie, Exaggerate, Not Disclose, or Get Ahead of Yourself
If you don't really have the skill or experience currently, don't say that you do. For entry level people, don't say you have a degree - if in reality you haven't graduated yet. It may cost you from ever being considered for employment at that company. Instead list your expected graduation date and the degree you should get at that time. The same goes for experienced IT people and their certifications. If your certification has expired, you can't say you have that certification - you have to mention when it expired. Versions could be important too. I have called candidates only to find they had used that software from 5 versions ago. All this is seen as an applicant trying to be deceptive. Pulling a fast one. I know times are sometimes tough and it is competitive out there, but this sort of thing could cost you from every being considered for employment again at a company.

With over 10 years in the recruiting industry, Eric spent most of his time recruiting IT professionals. In June 2011, he founded www.MinnesotaTechJobs.com - a hyper-niche job board focusing on only IT & Tech, only Minnesota, and only regular companies (no staffing agencies or consulting firms can post). Visit http://www.minnesotatechjobs.com to see other articles and posts in the "Ask an IT Recruiter" section.





Go to another board -