The Traditional Resume is Dead

Ok I got your attention with the title, right? Now let me explain. My name is Ben. I’m a life long techie living in Langley, BC. I’ve had my fare share of diversity when it comes to work experience, including: self employment, entrepreneurial tech start-ups, and multinational corporations.

When my last position came to an ammicable end, I did what all reasonable people would do. I cleaned up my resume and formatted it for a single sheet of 8-1/2x11 paper. Then I matched it with a well written cover letter and sent it to every job posting I could find in my field of expertise.

I learned very quickly that this doesn’t work for techies like me. Why? Because technical jobs have a vast array of acronyms, technologies and 3rd party tools. To list my skills and experience within each area on a single page is difficult at best. To make matters worse, I found that many employers had administrative staff filtering resumes by keywords. Although I understand the need to cut-down the stack before they hit the manager’s desk, the administrative staff often don’t know what all these silly acronyms and industry jargon mean. Their boss said find someone with ‘.net’ and my resume said ‘C#’ or their boss said ‘JavaScript’ and I put ‘jQuery/AJAX’ on my resume. If you knew the industry you’d know these examples are like peas in a pod - they really mean the same stuff.

So… I created this website to showcase my traditional resume in an “enhanced mode”. I’ve also got a small portfolio to showcase some of my work. I hope this is helpful for potential employers or clients to get a better picture of who I am and what I can do. If you’re a potential employer, you probably already have my faxable, photocopy-able, single-page black on white resume. This site will simply expand on that to include more descriptive information and samples of my work.

Latest Posts

Rebuilding my website with Jekyll!

3 minute read

I’m rebuilding my website with the static site generator Jekyll. Jekyll is quite popular in part because it’s what powers GitHub pages.