> Avoid ‘false accomplishments’. These are your responsibilities, described in the past tense. Until you’ve shown an impact, it’s not meaningful. That's just w

> Avoid ‘false accomplishments’. These are your responsibilities, described in the past tense. Until you’ve shown an impact, it’s not meaningful. That's just wrong. These are talking points and are the basis for your "experience", which is important to discuss. > Enrich your resume with numbers and accomplishments. Instead of ‘Was building a web application with [X] and [Y], write ‘Led the development of [X] feature, integrated it across [Z] products, resulting in extra [Y] in revenue’. You probably don't know the revenue at a company of any scale larger than 10 people. More importantly, these numbers likely mean nothing when applying at a different company (even if it's the exact same position in the same industry). > Omit the Summary and Objective sections. In 9 cases out of 10, summaries and objectives are not impressive. It's not supposed to be impressive, it's supposed to be informative and a talking point. > Use modern fonts. Use courier or some other common plain text fixed-width font. Format it as if it's being read like that, since someone may have to print it out and hand it around and maybe gasp copy-paste it (like web forms and other large-company-process-nonsense) in an intermediate form. Don't be an ass. Having interviewed hundreds of times and been interviewed hundreds of times (I keep lots of resumes), I would not recommend this blog post as a guide.