1. Careers
You can opt-out at any time. Please refer to our privacy policy for contact information.

Resumes for Tech Contractors

Increase Interview Calls With a Project-Based Resume


Businesspeople looking at resumes
a.collectionRF / Getty Images

If given the choice, most people would rather do their taxes than work on their resume. It's a painful, time-consuming process. And if you're a freelance contractor in the tech industry, you already know that a one-size-fits-all resume just won't cut it today. Your resume needs to be tweaked for each position you apply for, highlighting your most relevant experience for the project at hand.

Most full-time employees use a chronological resume, showing each company you worked for in reverse-chronological order, specifying "Company," "Position," "Years," and "Duties." This is a good format for full-time positions because it can show employers how stable you are, how loyal you have been, and how you have risen through the ranks, adding value to each employer over the years. Here are some tips and examples for resumes for full-time positions.

When you're applying for a contract position, a , chronological resume can actually do more harm than good. Unless your last position happens to be exactly what your new contract position requires, many managers will not even turn to the second page.

Project-Based Resumes

Instead of organizing your resume by the companies you have worked for, arrange it by each individual project instead. There are four sections for each project in a project-based resume: Title, Duration, Technologies Used, and a Description.

The title of each project should be a single line. Give each project a number (ie. Project 1, Project 2, etc.), followed by the "Project Name," "Company," and "Position."

In the second line type "Duration:"and then estimate how long you worked on it (ie. 6 weeks, 30 days, etc.)

In a new line, type "Technologies Used," or "Software Used," depending on the type of work you did. List the tools you used for the project in bullet points across two or three columns.

In the fourth section, write a brief paragraph about what the project entailed and what you did. Be certain to add any information that would be important to a new employer. If it's a long description, you can use bullet points here as well to highlight important points.

Why This Helps

First, and most importantly: When managers are looking for someone who can write C# code, or need someone to install a Cisco firewall, they really don't care how long you were working at XYZ Company. They want to know how much experience you have, what you did, and how many months, days, or years you worked in similar projects. They will scan the first couple projects you listed, look at what you did, add up the days you have spent doing similar work... and then decide to call you or not. A project-based resume makes the hiring manager's job easy, which means you are much more likely to get that call if you have the expertise they are looking for.

Second: You won't have to spend so much time tweaking your resume for each position you are applying for. Keep one copy of your full resume, listing all of your projects in reverse-chronological order as a template. When you apply for a new contract position, you can simply cut and paste the most relevant projects and place them at the top of the list. The less relevant projects can fill the following pages.

Third: Updating your resume after each project is simply a matter of adding it to the list when you are finished. You can spend less time drafting and revising your resume, and spend more time actually working on contracts and doing your taxes.

  1. About.com
  2. Careers
  3. Tech Careers
  4. Your Job Search
  5. Resumes for Tech Contractors

©2014 About.com. All rights reserved.