Along with my series about interviewing tips, I thought you might need a few tips for editing your resume. Here they are:
- Write a first draft of your resume. Write it in reverse chronological order, with your most recent job first. Now, put it away for a few days, while you do other things. Your subconscious will work on it while you work on the rest of your job search. Your subconscious is working on the details.
- Now it's time to do the hard work of the details for your resume. Especially for the most recent work on your resume, fill in the details. Assume you will write in prose here. Use good grammar. Don't worry about the length of your resume yet. You can trim later. For each line of your resume, explain what you did, how you did it, and how you added value to the organization. Use numbers about time saved on projects, cost saved on projects, customers added or retained, revenue added, that kind of thing. If you can't describe how you added value, does that line belong on your resume?
- If you have keywords, put those on the bottom of the resume, after all your experience. Do not clutter the most valuable part of your resume, the top, with keywords. Yes, I know the ATS wants to see keywords. The ATS is a robot. The ATS doesn't care where the keywords are. The human reading your resume does care.
- Check for typos. This is where you can run your resume through Grammarly's online grammar check and see what Grammarly says. Does Grammarly say, “Schlub. Not readable. Inconsistent grammar.” Or, does Grammarly say, “Professional. Your previous managers, your colleagues, even your mom would be proud.”
- Ask other people to review your resume. Does it make sense? Would they want to hire you, based on this resume? Have you boxed yourself into a job that doesn't exist, or a domain that is shrinking? This is the time to ask.
- Now, see how long your resume is. If it's longer than two pages, what do you need to trim?
You've heard “the devil is in the details,” right? You want a hiring manager to see you as a unique individual, someone who cares enough to provide a great resume, and someone who has done terrific work.
When I checked some text in Grammarly, it did find the commonly misused “Principle Engineer” problem. Yes, I know some of you are called “Principle Engineers” instead of “Principal Engineers.” Some HR person does not know the difference and it has spread like wildfire through technical job titles and job descriptions.
Principles are rules, tenets, laws, things like that. People are not principles.
Principals are leaders. People can be principals. There is a nice post on the Oxford Dictionary site, Principle vs. Principal that explains it well.
Why do you want to do all the work of Step 2, with the details? Why do I insist on articulating your value like that?
Because you need to explain what you have done in your jobs, so that you can answer questions well in the interview. You leave the stories of your career for the interview. You summarize the details with numbers in the resume. Is this difficult? Oh, yes. Is it worth it? Oh, yes.
Your resume is a piece of writing, the same as any other writing. It represents you to people you don't know. Do you want it to say, “I'm a schlub,” or do you want it to say, “I'm a terrific person. Here's what I've done in the past. I've told you the details of my previous work. I've checked that I've represented that work properly. Here I am! Now, interview me.”
That's what a great resume can do for you.