One little project of mine is helping people with resumes. I've done two as actual freelance jobs via a coworker, but the others I edited out of the kindness of my heart. Where's the line between asking people to pay you for your time and doing it to be nice? I mean, the same goes for a lot of occupations--my friends who know computers, for instance--but I don't think I've ever asked for any favors that take hours of their lives.
Anyway.
I figured since I already had some stuff written up about this topic I would share it with everyone. Consider this free advice from me. Here are the two main things to keep in mind when constructing a resume and/or cover letter.
1. A resume is your fact sheet. It's like calling HR and asking for a copy of an employment posting. Focus on the facts. How many jobs have you had? What were the tasks for each?
2. A cover letter explains how and why you do what you do. If you think of your resume as a thesis statement, your cover letter is the supporting information for that thesis statement. (Recall that concept from AP English?)
Resumes
- A resume is meant to get attention of someone quickly. Most companies--if they look at your resume at all—-will only consider it for an average of 10–15 seconds.
- If you are applying for an entry-level job, keep your resume to one page. If you have been working for a few years, over a page is okay. (Mine is currently two pages.)
- Resume design should have a level hierarchy. Your name should be the largest element (it's the first thing you want an employer to see), followed by the heading of each main section (education, work experience, etc.) and then the supporting text.
- You don't have to use in Microsoft Word resume templates. Most of them are ugly.
- Contact information is always a must, but it shouldn't take up too much room. I like to keep it at the top of the resume for easy reference (for the employer).
- Items in each section (such as each employment listing or degree you earned) should be arranged chronologically with the most current event listed first.
- When listing job descriptions, use active verbs.
- Don't write your objective at the top of your resume. Mention it in your cover letter.
- Specifics are good in a resume. The specific number of sales you oversaw; the specific (or approximate) number of employees you trained or supervised, etc., plug those numbers in.
- Do not list personal information (hobbies, skills, etc.) unless they relate to the job you are applying for. The fact that you own 15 fuzzy kittens might be important if you are applying to work for an animal hospital or something, but not if you want to be the CEO of a major corporation.
- A cover letter is optional but recommended when applying for an employment position.
- Show, don't tell. The recommendation comes as your opportunity to explain some of your past work experience and show them how you apply the characteristics you may mention in your resume. If you write, "My good communication skills helped me work with various departments," take a minute to explain how you used those skills. Did you spend time with these people or just email them? Was there a situation when your skills especially benefited to solve a problem? The cover letter is the time to mention these things.
- Do not restate employment tasks in a cover letter. Doing so is a waste of space.
- Cover letters should always be one page. Again, the company won't have a lot of time to read them.
- If the company you're applying for specifically lists tasks and requirements they are looking for, explain how your skills and abilities will specifically fit said tasks and requirements. Don't absentmindedly blab on about how great you are.
- Every sentence you write in a cover letter must have a specific purpose. Be direct and to the point. Don't imply anything; say exactly what you want them to know. They don't have time to figure out what you're trying to say.
Just because I've written all this down doesn't mean I'm not willing to help anyone ever again. However, for the sake of my time, I'll probably ask you if you've read this blog post first. :)
The end.
No comments:
Post a Comment