Surprisingly, not many people know just how to write a good developer resume. The Developer Story is a good approach but even that is missing the key element that makes a resume work _when you are looking for a job_.
Imagine this scenario:
- Farmer looking for horse to plough my fields and inspect my farm
- Horse 1: "I am a stallion! My coat shines in the sun, my mane is dark and glossy, and the very earth trembles as I run. I have come from the stables of Arabia, have been in the armies of Alexander, the greeks, and the mighty Theseus! I have ploughed the fields of Asphodel, and won 'prettiest horse' in the Reading village fair"
- Farmer: "Wow! You're...impressive"
- Horse 2: "I enjoy ploughing fields and I'm pretty strong"
- Farmer: "Great! I can offer you two apples, four sugar cubes, a nice warm barn..."
To be effective, Resume's shouldn't be all about how great we are (unless we are _really_ someone standout). Rather they should be tailored to the job we want.
The resume needs to get through the "hiring funnel". This means they must contain the keywords that the ATS and Recruiter need in addition to our technical accomplishments that the Hiring Manager and Interviewing Panel will want. This really is pretty simple but we get caught up looking inward and not paying attention to the actual audience of the resume. So most resume's end up hit or miss.
For anyone interested, I've written a book on how to do this. The book's description on Amazon contains the entire process so you don't need to buy it unless you want to. https://www.amazon.com/dp/B01KVVY9OA
>The book's description on Amazon contains the entire process so you don't need to buy it unless you want to.
Would you say this level of openness has an impact (positive or negative) on sales of your book? It's pretty refreshing but the cynic in me wonders if it hurts sales.
I'm not sure - maybe it does but the idea itself is pretty simple so I want to get it out there. I see a lot of people spending time making their resume's "look good" instead of being more result-oriented. I figured if I could explain how to write a resume well it would help.
The book itself has more detail and a step by step (chapter by chapter) process to get a great resume written out. So it's mostly helpful for the lazy ones! :-)
Imagine this scenario:
To be effective, Resume's shouldn't be all about how great we are (unless we are _really_ someone standout). Rather they should be tailored to the job we want.The resume needs to get through the "hiring funnel". This means they must contain the keywords that the ATS and Recruiter need in addition to our technical accomplishments that the Hiring Manager and Interviewing Panel will want. This really is pretty simple but we get caught up looking inward and not paying attention to the actual audience of the resume. So most resume's end up hit or miss.
For anyone interested, I've written a book on how to do this. The book's description on Amazon contains the entire process so you don't need to buy it unless you want to. https://www.amazon.com/dp/B01KVVY9OA