Skill Bar

The crime we’re commiting on resumes

I sat down and had a really long in depth talk with my classmate Philip Bergeron about our views some different things that build the graphic design industry and one thing really stood out. Resumes. There’s one trend that we’ve all seen that he really was against, the skill bars. He had come across something online that essentially said that “..the skill bars are pointless, why not just tell us you’re proficient at those thing?”. Well, I had a bit to say about that.

Skill Bars

While I’m a recent “offender” of that, I view those skill bars as a way to display proficiency. From a front-end web developer or a designer aspect, you’re working with a ton of programs or a lot of different coding languages. Some you’ve been working with for years, others get used for a week or two. I’m not going to lie about my experience to get me a job. If I don’t know a whole lot of PHP beyond what creates a WordPress post loop, I’m not going to say I’m proficient in it. I’m capable. I’m confident I can learn more as necessary, but I am not a master.

The skills bar is an opportunity to display our largest strengths and weaknesses. If I were to strip that from my resume and call myself proficient in everything I have listed would probably end with my future employer thinking I’m a PHP/JavaScript master when in reality, JavaScript is the hardest language I’ve dealt with yet and continue to wrestle on a weekly basis. Point being, it’s a small thing that says a lot about yourself.

My attitude is that if you push me towards something that you think is a weakness, then I will turn that perceived weakness into a strength.
-Michael Jordan

design, development, resumes

Posted on January 14th 2015