During my last job, I occasionally was invited to interview candidates for the web development team. Usually I’d receive a copy of their resume a few days beforehand with the instructions to review it, and I’d take a few minutes to read their resume and usually pop them into Google to take a look at their online presence. Throughout this process I began noticing things that I saw to be mistakes, probably propagated by the avalanche of resume advice that permeates the job seeking culture. This caused me to rethink my own resume, and I’ve wanted to share these things for a while.
It’s important to note here that I see the technical resume (and any resume, really) as a marketing tool. It is, in essence, the brochure that we build for ourselves highlighting what we can do for a customer (that is the employer). But technical resumes, like many resumes, aren’t written that way. Here are three common things I see as mistakes on technical resumes.
Imagine that you’ve just been offered a brand new job. That’s fantastic! Now, make sure you do the math and find out what it will cost you.
“Cost me?” you ask. Yes. Accepting a new job is exciting and often beneficial, but there are costs associated with it that you must consider before you sign the offer and tell off your present employer. Some of these costs are obvious, but others are less obvious. These costs are rarely fully explored, because we have a tendency to see the grass as greener someplace else, and if the offer we receive is substantially better than our current one, we are more inclined to accept it. But not counting the costs would be a huge mistake.