Louise Inaya June 6, 2021 Resume Sample
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.
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.
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.
My approach to resume writing involves the use of a skill set based approach and that means when a recruiter or hiring manager opens the resume they first read skill sets that have been acquired throughout the candidate’s career. More importantly, the skill sets listed are directly related to the job or career the candidate is interested in. This can change the entire perspective of the candidate when viewed by a potential employer as now they are viewed beyond the current job they hold. This is an especially helpful approach for anyone who is interested in changing jobs or careers.
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.
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 Cloudpurchasing resume resume writing workshop resume cover letter template word chemical project engineer resume logistics consultant resume resume template reddit medical coder resume template resume graduation date format high school student music resume motocross resume example medical assistant resume district loss prevention manager resume blank resume form for job application uga resume builder punctual resume medical technologist resume template proficient skills for resume unique summary for resume suspend resume ps4 resume with skills sample