An opinionated guide to writing developer resumes in 2017

by Arthur Camara

This article is an up-to-date guide for developers who want to maximize the chances of getting an interview in 2017 at cool companies and startups.

What was a formality less than a century ago is now the very first step to landing any interview: sending your resume.

This lengthy printed document has now become a PDF, a web page, a LinkedIn profile, a Stack Overflow Developer Story, a Youtube video, a Github profile, or some combination of these.

Resumes as we know them are doomed. More efficient forms of job application and assessment will eventually emerge. But we're not quite there yet. And since this has yet to happen (or should I say, since we, the developers and entrepreneurs, have yet to make it happen), my colleagues and I will continue to receive and evaluate developer resumes every week, from all corners of the globe.

Over the past several years, I've seen how ineffective most candidates are in trying to communicate their experience, technical skills, and potential through resumes.

This article is an up-to-date guide for developers who want to maximize the chances of getting an interview in 2017 at cool companies and startups. It reflects my own opinions and views on do’s and don’ts.

We specialize in leveraging emerging technology to solve business problems, capitalize on opportunities, and build groundbreaking products and businesses.

Let's build the future together