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.
You must make it easy for a resume reviewer to find your experience with specific skills on your resume. To do this, always include a Technical Skills section. You can take several approaches for your technical skills summary. The most common is to show a bulleted list, a short table, or even a short paragraph listing your technology skill set. Some list skills on their resume organized by technical area, such as database, programming languages, networking tools, etc. Keep the list of skills brief and high level as an overview of your skills. You don’t typically need to specify versions in the skill listing. Remember, the primary purpose of the technical skills list is to make your skills easy to find. You give the resume reviewer a way to quickly see an overview of skills listed on your computer programmer resume, such as programming languages, databases, testing tools, etc.
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.
Offer Proof for Your Statements – The old adage that finding a job is a job holds true. The burden is on you to prove to a potential employer that you are the best candidate for the job. To do this, you must build your case from the ground up. This means you need to offer proof for every statement you make. For example, if you say you have 6 years of experience with Java programming or accounts payable, an employer should be able to go one-by-one through your position write-ups on your resume and identify those 6 years by themselves.
Avoid Flowery Language That Diminishes Your Achievements – You could have a comedy show with some of the statements people make on their resumes. You don’t want your resume to stand out for the wrong reasons. Avoid creative writing. Avoid big words and uncommon vocabulary. Avoid over the top statements that make you sound like you saved the universe. They immediately call your credibility immediately into question. Resume writer Don Goodman shares one of his favorite claims as ”Rocketed performance to stellar heights.” Says Goodman, ”People don’t speak like that; I have never heard an executive tell the HR person that they needed someone who could rocket performance to stellar heights. Remember, people hire people they like, so don’t make your resume read like an amateur poet wrote it.”
As I mentioned earlier, do not assume that a resume reviewer will be familiar with various terms and concepts that could substitute for the ones in the position announcement. That may or may not be true. Best advice is to use the potential employer’s terminology from the job posting since that is most likely what reviewers will be looking for. Again, do not assume that the initial reviewers are familiar with the technology involved with the position. They may not be. Be very clear that you meet all of their requirements by ensuring that your technical skills summary, experience summary, and experience details all generously use the correct keywords for the position you are seeking.