Get your FREE 30 page Developing SOLID Applications guide!

Rethinking The Technical Resume

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.


Lessons Learned From An Impromptu Job Search

When I lost my job on October 12th, I knew that the PHP community was an invaluable resource for finding a new one. What I didn’t expect, though, was the outpouring of support and assistance I would receive from that community. I learned a lot of lessons from the job search, and thankfully, largely due to the involvement of the PHP community, I have a long-term contract that is both paying the bills and letting me form my own consulting company – a long term dream I’ve had (more on this in a future blog entry).

I wanted to share some of the lessons I’ve learned, because I think that they are important, and they helped me to find a position quickly, effectively, and easily. I actually had more than one opportunity to choose from – something that’s almost unheard of in the current economy.