Millicent Safia November 27, 2020 Resume
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.
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.
List any Professional Certifications – Different employers place different emphasis on professional certifications. Many employers find these certifications very important, often even requiring them for certain positions. But there are also other employers who might prefer candidates with certifications, but do not require them. Still others do not pay attention to certifications at all. Since you have no idea what the company or reviewer believes about certifications, you should always list them if you have them.
You also want to provide a short listing of relevant technology training courses you have taken. Many candidates forget to list these items out. They can help further demonstrate your expertise and exposure to different technologies, especially for a less experienced candidate. I suggest putting Training last on your resume, just below Education. As an added bonus, listing these technology skill trainings helps add more key words to your resume and improve your results on resume screenings.
Other misconceptions include the use of an objective on the resume and writing detailed job descriptions. A job objective is usually a statement of what the candidate would like to do or the specific job they are seeking. The reason why this is not needed is that the cover letter should express interest in the position and there is no need to state it again. In addition, many objective statements are so specific that the candidate would be ruled out from other potential positions that may be related to the advertised job. In addition, many jobs I have seen listed on resumes includes wording that either came from job descriptions or have been written like standard wording from these types of descriptions, and that doesn’t necessarily explain the skills the candidate has and may contain jargon that is not easily understood by everyone reading it.
Nearly all initial resume screenings are done using a checklist of items that must appear in order to advance to the next level, regardless of whether it is screened by computer or staff. If you don’t have the correct ratio of keywords on your resume for the position, you don’t make the cut. So why do so many experienced candidates for computer programmer jobs not make sure that the correct keywords are on their resume for each individual position for which they apply? It’s usually a combination of attention to detail and desire to respond quickly.