Print / Illustration
About the Project
The main goals of this project were to convey personal identity through design. This project served to teach us how to use effective hierarchy and typography to improve the readability of resumés, as well as use color effectively to emphasize important elements. The constraints were: 8.5 x 11 inches paper, text margin 1/4 inch or larger and no bleed. The end product turned out to be a well designed, easy to read and eye pleasing resume. This piece is directed to managers and recruiters of potential employers.
My original resumé consisted of a black and white word document that used larger font sizes and bold to implement visual hierarchy. It was very bland and didn’t have much style.
I decided that when redesigning my resume, I would keep the original order of content. I feel that this order is the most effective. Objective, education and coursework, and skills generally tell recruiters what kind of career you are looking for and if you’re qualified. I like that particular order because objective will tell the employer clear and straight forward exactly what kind of career you’re looking for. Education and coursework tells the recruiter what you’re studying, how far you are in your studies, and how well you are doing. This can further define potential roles they can interview you for. The skills section will tell the recruiter what you specialize in. All these sections come together to send an important message of what you want and whether you’re qualified. Experience and projects can show you’re employer a few things. If you have previous experiences (industry or projects) in similar roles, it shows them that you’ve done this kind of job before, and you’re capable. Other roles on your resume will tell them what you’ve worked with, and maybe what some of your other interests are. I’m personally interested in all parts of technology development, and is the kind of person who wants to learn too many things at once. Because of that, I have many different experiences with careers that are not software development.
When I started redesigning my resumé, I knew i wanted a layout with better labels. I decided that they should get their own column, so that recruiters could more easily look for specific sections. I decided on all caps for my labels to make them really stand out. At first, I made them too big, and it looked awkward with the rest of the text. I ultimately decided to make the labels smaller with more tracking between the letters so readability would not be sacrificed. I also knew that I wanted to remove the column on the right dedicated to dates. Dates generally are of no particular interest by themselves, so I felt that it was not effective to keep dates aligned on the right, drawing unnecessary attention to them.
I wanted a hierarchy within the skills section, so recruiters could easily look for skills they were interested in, instead of searching linearly through bullet points. I chose to implement minimal hierarchy in the education section because it was difficult deciding which of those was most important. Besides the school, I would like viewers of my resumé to read whats left in the education section as it is ordered.
A logo seemed very appropriate for my resume. I wanted a logo that had a flat, elegant design, but also showed the engineer side of me. I went with a circle containing my name with a twist. The font for my logo was chosen to look like an old school computer font, perhaps a reminder of what it is like developing code in Vim, a traditional text editor that hackers deem one of the best.
I chose to use the color blue for my logo and the parts I wanted to stand out the most. This included labels, previous positions, and projects. I found that these are usually the main interests to recruiters and hiring managers. I chose blue because its very modern and used a lot in the technology industry, and that particular shade gives the resumé a nice kick.
With that covers the reasoning behind my design decisions. The end product, an easy reading resume with clear visual hierarchy.