Fleur Daphné November 27, 2020 Resume
Do not put an Objective section on your resume. Why would you? What value does it add? Space on your resume is limited and is better used to provide a one paragraph (2-3 sentences) summary of your qualifications for the specific position. This summary should include years of experience, types of experience, and highlight the most important technologies related to the position. This section is used to make the resume reviewer’s screening process easier and improve your chances of passing the initial screening. Use it wisely and tailor it for each position.
Professional certifications from major vendors and professional associations typically carry the most weight and are well worth the investment of time and cost. They are definitely good things to have and can often give you an edge over other similar candidates being considered. In the computer programming area, certifications from Microsoft, Oracle, SAP, and the like are definitely in demand. Highly sought after certifications from professional associations include A+, Network+, and Security + from Computing Technology Industry Association (CompTIA); Certified Information Systems Security Professional (CISSP) from International Information Systems Security Certification Consortium (ISC)²; and Project Management Professional (PMP) from Project Management Institute.
Another common misconception is that a resume must be one page in total length. I am not certain I know how that idea became popular or why it has remained so engrained as it ultimately serves little purpose for most candidates and it can work to the detriment of a job seeker. The reason why is that a one page resume, for a person who has fairly extensive experience, can sell them short. This type of resume will either leave off critical information or it will be typed in a font size that is not easy to read.
Finally, make sure each job history write-up in your experience history (your job summaries) includes these details as well. When I get into a detailed resume review, one of the first things I do is map the summary to the details. I try to determine where and when you had the required experience for the computer programmer job. If I can’t find it called out in the details, I will assume you don’t have that experience, regardless of what your summary says. It is very important that you to pay attention to these details because, as a reviewer, I most certainly do. The job summaries are the key to getting past the initial resume screening. Take time to make sure the details line up with what you said in your experience summary and technical skills list.
Write About Your Results, Not Responsibilities – Don’t let your resume make the mistake of focusing on your previous jobs’ responsibilities. Your resume should focus on the computer programming work that you did and what you achieved. As a hint, avoid using the word responsibility or responsibilities on your resume so you don’t fall into this trap.
In writing about each of your previous jobs, discuss your results. Tell about what results were realized because of the work you performed. Be quantitative. Reviewers love to see numbers and results. Tell about how many desktops or users you supported, recount how many databases you administered, show a percentage of application or network uptime you maintained, provide a percent reduction of security incidents you achieved, etc. Get the idea? This is where you impress your reviewer.