This is the resume I used to get my job at Microsoft in 2019.
While it's certainly not perfect, there are a few things that helped me in the process and I'll show them to you, using colors ๐
A ๐งต with 7 tips to improve your resume and stand out
[1] Format
Don't worry about searching for fancy, and colorful templates.
A black&white plain old boring template works.
Recruiters & hiring managers care about your accomplishments and about you, not about the colors you chose for your resume (unless you are a designer)
[2] Write accomplishments with X-Y-Z
Most of my accomplishments were written using as a base the X-Y-Z formula (shared by Google recruiters)
"Accomplished [X], as measured by [Y], by doing [Z]"
Follow it as close as possible, but don't be afraid to write your own version of it
[3] Use strong verbs (red ๐ด)
Start every accomplishment with a verb in past tense.
- Strong Verbs (Led) >>>> Soft Verbs (Assisted)
- Try to use verbs relevant to the role. For PM I used: Led, Designed, Researched, Prioritized, etc.
[4] Relevant Skills (blue ๐ต)
I don't have a "skills section" full of Product Manager keywords like "cross-functional", "leadership", "prioritization", "Roadmap"
The keywords in blue are embedded in my accomplishments. I'm showing the context on how I used those skills.
[5] Show your impact (yellow ๐ก)
Not everything has to have impact. Impact shows that:
- You can do the job, do it well, and can make a difference
Anyone can "complete a project in time" but not everyone can "complete a project in time by doing x, and having an impact of y"
[6] Technical Skills (green ๐ข)
I write down all the technical skills that I know.
Many of these are taken from the job descriptions I was applying to.
- 'sprinkle' tech(hard) skills here and there
- Don't just put them in a skills section
[7] Other stuff
Number of pages doesn't matter as long as it's RELEVANT to the job
Tailoring your resume >>>>>> Everything else
Triple check for grammar/spelling mistakes
BONUS:
While I worked on my resume for a while (and there's still A LOT of room for improvement), what got me my recent jobs was the fact that I networked a lot.
Don't underestimate the power of networking.
That's a wrap!
If you enjoyed this thread:
1. Follow me @PMDiegoGranados for more of these 2. RT the tweet below to share this thread with your audience
Everything you need to become a Product Manager is here:
- FREE step-by-step guides to become a PM with or without experience
- Resume Templates
- The BEST Product Interview prep course ever created
But there's one thing you can do every day for 5 minutes to improve your Product Sense and get you ready for your next interview
The goal is to look at products you've never seen before and answer 3 key questions.
Here's a ๐งต on how I do it
The goal is to answer 3 key questions that can give us a rough idea of whether the product is really a good idea
-Who is the product intended for? (Users)
-What Problem is it trying to solve? (Pain-Points)
-Is the solution proposed better than alternatives? (Value proposition)
Nothing worse in Product Management than having the title of "Product Manager" but not really doing the job of one.
Unfortunately, this is much more common than we think.
When I look for new roles, I always check for 5 things that can help me avoid roles that are not PM ๐
5 Things I check to avoid bad PM roles
Job Description:
- Job should match title
- Focus on the impact, not level
- PM and PO are not interchangeable
During Interviews:
- Authority over backlog
- Succes is not # of features
Let me explain each one of them...
1/ Job Should Match The Title
Job descriptions that are not really a Product Manager role make it sound "exciting" including things such as:
- Ownership
- Work with customers
- Work with engineers
But the rest of qualifications and responsibilities don't match what PMs do.