Writing a good CV
-
@IRJ said in Writing a good CV:
I've never needed a CV. I like to an areas at the top of my resume called summary of qualifications. Thata where I have my bullet points about my career history and career goals. It's also the area that I mold towards the job I want.
Agreed - You don't want to list your qualifications below each previous employment, especailly if there is duplication of skills. List them once, and in one section, from the most important.
-
@IRJ said in Writing a good CV:
Certifications -
I am not sure I agree with how you've got those listed. You have put forth great effort to get (and maintain) them. Each should be listed as they are all a part of your skill set.
-
@gjacobse said in Writing a good CV:
@IRJ said in Writing a good CV:
Certifications -
I am not sure I agree with how you've got those listed. You have put forth great effort to get (and maintain) them. Each should be listed as they are all a part of your skill set.
I have them listed below this area. I just took a screenshot of the very top of my resume.
-
I wanted the "Summary of Qualifications" section to be the part that someone who only has 30 seconds reads. I list the certs individually below and include the certificate numbers and the dates so they can be verified right off my resume.
I do feel like my resume has given me a major advantage in the job market. Having a clear , concise area is very important. I do list some of these skills again under my job descriptions as they are relevant to my positions.
The Summary of Qualifications is my extremely short sales pitch. Alot of people have a similar area on their resume, but I have seen them include stuff like "customer service oriented" , "troubleshooting" , "support" , or other very general buzzword terms. It's a waste of time since customer service doesnt mean jack shit. If I am hiring somebody solely for customer service, I would hire them from Disney or hotel chain where that focus means much more to the actual job. Even then, it's a waste in my opinion. Who the hell is not going to say they are customer service oriented? Its not something like you specialize in unless you are a very specific position. Even in that case, it would be under your job description.
-
@IRJ said in Writing a good CV:
I've never needed a CV. I like to an areas at the top of my resume called summary of qualifications.
CV = Resume
-
A piece of advice that revolutionised my resume was this: your points should be something that no one else could say (if possible). If you pm me your email address I can show you my old and current resumes to compare.
-
@Kelly said in Writing a good CV:
A piece of advice that revolutionised my resume was this: your points should be something that no one else could say (if possible). If you pm me your email address I can show you my old and current resumes to compare.
You mean.... unique stuff not "knows Windows?"
-
Posting a snippet here for the sake of the thread's value:
Old:
- Reduced organizational IT operating costs by moving from costly closed source software to internally supported Linux based open source platforms and software
- Transitioned key IT systems from ad-hoc, as-needed to standardized, centrally managed, and strategy focused; achieving improved uptime, customer service, and reducing overall costs
New:
System Transformation – Mapped existing, fragmented IT systems and benchmarked against industry standards. Redesigned and deployed a centrally managed solution that improved uptime by 20%, reduced support tickets and customer complaints, and increased our ability to effectively predict and manage costs while utilizing existing infrastructure. -
@scottalanmiller said in Writing a good CV:
@Kelly said in Writing a good CV:
A piece of advice that revolutionised my resume was this: your points should be something that no one else could say (if possible). If you pm me your email address I can show you my old and current resumes to compare.
You mean.... unique stuff not "knows Windows?"
Good start
-
Another thing that held back my ability to create an effective CV/Resume is that I frequently didn't feel like I could assign a value to certain things, e.g. money saved, efficiencies created, etc. if I didn't have an empirical measurement of that thing. However, you are the expert on your systems and your work. You know when something is improved and can provide an educated estimate that is sufficient for a CV. Use that expertise. You don't have to lie or exaggerate. Instead give your best, professional estimate.
-
@scottalanmiller said in Writing a good CV:
@IRJ said in Writing a good CV:
I've never needed a CV. I like to an areas at the top of my resume called summary of qualifications.CV = Resume
lol I was thinking cover letter
-
@IRJ said in Writing a good CV:
@scottalanmiller said in Writing a good CV:
@IRJ said in Writing a good CV:
I've never needed a CV. I like to an areas at the top of my resume called summary of qualifications.CV = Resume
lol I was thinking cover letter
I figured. MOst of the world uses CV to mean what the US calls resume.
-
@scottalanmiller said in Writing a good CV:
@IRJ said in Writing a good CV:
@scottalanmiller said in Writing a good CV:
@IRJ said in Writing a good CV:
I've never needed a CV. I like to an areas at the top of my resume called summary of qualifications.CV = Resume
lol I was thinking cover letter
I figured. MOst of the world uses CV to mean what the US calls resume.
Curriculum Vitae... Story of my life.
-
Yeah sorry should of just all names for it in the OP
-
All good points thanks, will start building something over the next day or two.
-
@Kelly said in Writing a good CV:
Posting a snippet here for the sake of the thread's value:
Old:
- Reduced organizational IT operating costs by moving from costly closed source software to internally supported Linux based open source platforms and software
- Transitioned key IT systems from ad-hoc, as-needed to standardized, centrally managed, and strategy focused; achieving improved uptime, customer service, and reducing overall costs
New:
System Transformation – Mapped existing, fragmented IT systems and benchmarked against industry standards. Redesigned and deployed a centrally managed solution that improved uptime by 20%, reduced support tickets and customer complaints, and increased our ability to effectively predict and manage costs while utilizing existing infrastructure.If I'm reading your resume, I'm not sure if this tells me anything that useful. I guess it depends on how big of a company you worked for. It's like politics, of course you will say anything you implement was the best thing ever. I could take from this that you have experience with ways to measure uptime, but apparently that's not the case?
@IRJ 's advice is pure gold. I'm going to go update my resume now. Setting an overview and a context to read the rest of the resume can only have benefits.
-
@flaxking said in Writing a good CV:
@Kelly said in Writing a good CV:
Posting a snippet here for the sake of the thread's value:
Old:
- Reduced organizational IT operating costs by moving from costly closed source software to internally supported Linux based open source platforms and software
- Transitioned key IT systems from ad-hoc, as-needed to standardized, centrally managed, and strategy focused; achieving improved uptime, customer service, and reducing overall costs
New:
System Transformation – Mapped existing, fragmented IT systems and benchmarked against industry standards. Redesigned and deployed a centrally managed solution that improved uptime by 20%, reduced support tickets and customer complaints, and increased our ability to effectively predict and manage costs while utilizing existing infrastructure.If I'm reading your resume, I'm not sure if this tells me anything that useful. I guess it depends on how big of a company you worked for. It's like politics, of course you will say anything you implement was the best thing ever. I could take from this that you have experience with ways to measure uptime, but apparently that's not the case?
That is not how that reads to me at all.
-
How do you judge if a resume is successful or not? I really have no idea. As an employer, I was only really interested in who a person worked for, for how long, and what their job title was. Stuff about, for example, "system transformation", like Kelly's example, just went straight through me - it meant nothing to me. But for other employers, that stuff might be gold and just what they're looking for.
The other issue is that your resume normally has to go through at least two people - firstly, an employment agent, and then the employer. So who do you target, as they are two very different audiences? An agent will probably spend 20 seconds reading your resume, looking for keywords, whilst an employer might spend ten minutes, especially if they're interviewing you.
I do like to hear about hobbies, especially interesting ones. I think you can tell a lot about a person by his hobbies. But it's de rigueur to leave these off these days, sadly. Probably for the best.
-
@Kelly said in Writing a good CV:
System Transformation – Mapped existing, fragmented IT systems and benchmarked against industry standards. Redesigned and deployed a centrally managed solution that improved uptime by 20%, reduced support tickets and customer complaints, and increased our ability to effectively predict and manage costs while utilizing existing infrastructure.
Too many meaningless buzz words. The 20% sounds nice, but like @Carnival-Boy pointed out there is no way to confirm. What benchmarks did you use? Even if my company is working against NIST standards, I would still like to hear if you implemented against ISO standards. They are very similar in the way they are handled. But I have no way of knowing if you were bench marked against a major standard or something more minor like CIS or HIPAA. That stuff matters because they are different levels of compliance.
What centrally managed solution? How did you reduce costs?
It is very vanilla and vague. Not a single point is clear to me.
-
@Carnival-Boy said in Writing a good CV:
How do you judge if a resume is successful or not? I really have no idea. As an employer, I was only really interested in who a person worked for, for how long, and what their job title was. Stuff about, for example, "system transformation", like Kelly's example, just went straight through me - it meant nothing to me. But for other employers, that stuff might be gold and just what they're looking for.
Same here, that stuff looks like filler to me. I can't quantify it, so I ignore it.
