Your Job List


Leave a comment

Resume tip for IT contractors

The resume for a tech contractor shouldn’t look like a resume for someone looking for a full-time position. Here’s how to make yours different.

If you were a hiring manager looking for a contractor who can write C+ code, would it matter to you that one of the candidates has lots of tech contracting experience or whether he or she has specific experience in C+ coding? I would say the latter.

That’s why a contracting resume should look different than a normal chronological resume.  Instead of organizing your resume chronologically by the companies you’ve worked for, arrange it by individual project, with the projects that contain the wanted skill set first.

Continuing with the C+ analogy, let’s say that your last contracting job was actually migrating a small office to Windows 8. Since that’s not relevant to the direct needs of the hiring manager, you can push that down further on the resume.

The first project you list will be the one where your C+ skills were most in use.

Project title: Creating Desktop application for Windows

Duration: You can write this in hours, weeks, or months

Technology used: Lead with C+, but list all other technologies that lent themselves to project

Description: This is where you can describe the level of complication of the project (without, of course, giving away proprietary details), what project milestones had to be met and what intervals, etc.

This gives the hiring manager the information he or she is looking for right off the bat. And, once you have delineated all of your contracted projects this way, you can then copy and paste the order as needed when sending out future resumes for gigs that ask for different specialties.

Credit to the guys at TechRepublic for the original article.


Leave a comment

10 things I wish I’d known before becoming an IT consultant

Takeaway: Careful research, thoughtful planning, and honest self-assessment can help you make a successful leap into the IT consultant role. But the realities of the job will still surprise you.

 

Before opening an IT consultancy, I did my homework. I interviewed lifelong consultants. I read books. I even took personality tests to confirm that my psychological constitution matched the challenges I’d face as an entrepreneur owning and operating my own business.

Some lessons, though, you just have to learn yourself. If you’re a technology consultant, or if you’re considering branching out on your own, take a few tips from my experience of supporting hundreds of companies of all shapes and sizes. Here are 10 things I’d wish I’d known before becoming an IT consultant.

By Erik Eckel

1: Some people are never happy

2: Not all IT pros make good consultants

3: Some clients never intend to pay

4: Vendors abandon you

5: Clients expect a know-it-all

6: And one more thing…

7: Immediate service, but 60-day payment terms

8: Clients only remember what didn’t work

9: You’re almost always working

10: Follow-up is not optional

Check out the full post for all the detail.

Credit to TechRepublic for the original article.