Robinetta Elisa December 30, 2020 Resume
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.
Let me share with you a tip related to your technical skills summary based on my review of resumes over the years. After I check the list of skills, my next step is to look further in the resume to identify the specific jobs where that skill was used and determine how much experience a candidate has with the skill. The point is that listing the skill is simply not enough. Truthfully, I’ve found that most candidates never mention the technical skill anywhere else other than in the skill listing. In these cases, I will assume they really don’t have experience with that skill and are just listing it to catch my eye. Therefore, follow through and ensure that the skills you list are also spelled out in your job experience write-ups. Never assume that a resume reviewer will know that you did x, y, or z. More often than not, they do not make those assumptions or they could even be non-technical staff who are just following a checklist to screen the resumes. So, remember, that if an employer lists a technical skill on the IT job posting or ad, make sure it is on your resume in both your technical skills list and experience write-up.
Show any Training and Education – List any degrees you hold since most employers want to see these. If you have work towards a degree, but are still pursuing or have never finished but you may someday, list it as in progress.
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.
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.
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.
Tag Cloudfull stack developer resume examples accounting clerk resume examples water treatment resume samples benefits specialist resume informational resume sap implementation resume retail resume skills military resume service skill headings for resume customer service resume overview bricklayer job description resume produce clerk resume sample latex resume template github telecom domain experience resume cvicu nurse resume resume lead a team production director resume free resume illustrator template cna responsibilities resume free awesome resume templates microsoft word