Research Associate Resume

cv template research scientist resume format data science associate examples for resident Resume Research Associate Resume

Joanne Neyla March 17, 2021 Resume

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.

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.

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.

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.

This technology presents some risks for you as a potential job candidate, so you must understand how they work. Many of these so-called applicant tracking systems do not recognize items in table format, text boxes, or other graphical elements. They are very text based. Therefore, you should avoid embedding anything important into graphical elements such as text boxes or tables to make sure they are not missed by these applicant tracking systems.

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.