I have now done IT contracting (switched from permanent) for about 5 years, 8 contracts or so. I came here for the money (of course) but also for what I thought would be excitement and risk: genuinely fighting for business, doing pilots and trying to convince clients to keep me on. What I've found for the most part once an "interview" is landed with a client (shouldn't it be "discussion" and not "interview" when we're talking contracts?!), is that most of them are looking for a permanent-type worker who they can only pay for a few months.
Half or 3/4ths of said interview is technical questions of the kind that reminds you of exams in university.
If you 'pass' this interview you are made part of the company's plans for the next half-year or more.
Once on the job they are willing to give a good amount of independence in *how* you get work done. Some of them (some) are even open to suggestions as to *what* you will do there. But for the most part you must get used to the client's pace and the client's ways of doing things.
I guess what I hoped for in the contracting world is clients asking you to come on for a day or two (yes I am advocating initial one or two day contracts), at most a week, where the contractor has to think on his feet, perhaps hit the books/internet at night, come up with ideas, do mock-ups and pilots. Then if they like you they engage with you, otherwise you leave. This is what I expected. What I've found is very different.
What I've found is basically permanent work for shorter durations (but still paying twice as much as permanent work). I am happy with the money but unhappy with the lack of excitement. People outside the IT contracting world like family and friends get excited when I tell them I work on contracts, on a freelance basis. I often find I have to make up stories about high-risk high-reward (or bore them with the truth). There is nothing risky about this, except a few days or weeks now and then on the bench between contracts.
Half or 3/4ths of said interview is technical questions of the kind that reminds you of exams in university.
If you 'pass' this interview you are made part of the company's plans for the next half-year or more.
Once on the job they are willing to give a good amount of independence in *how* you get work done. Some of them (some) are even open to suggestions as to *what* you will do there. But for the most part you must get used to the client's pace and the client's ways of doing things.
I guess what I hoped for in the contracting world is clients asking you to come on for a day or two (yes I am advocating initial one or two day contracts), at most a week, where the contractor has to think on his feet, perhaps hit the books/internet at night, come up with ideas, do mock-ups and pilots. Then if they like you they engage with you, otherwise you leave. This is what I expected. What I've found is very different.
What I've found is basically permanent work for shorter durations (but still paying twice as much as permanent work). I am happy with the money but unhappy with the lack of excitement. People outside the IT contracting world like family and friends get excited when I tell them I work on contracts, on a freelance basis. I often find I have to make up stories about high-risk high-reward (or bore them with the truth). There is nothing risky about this, except a few days or weeks now and then on the bench between contracts.
Comment