There are many reasons why web workers (and other independent contractors) choose to accept one job over another. Sometimes it’s simple economics: if you’re not overflowing with offers of work, you may not be able to afford choosiness. Other times, you might choose on the basis of your emotional chemistry with the client, the pay rate, or the way the job fits into your schedule.
But as a longstanding contractor myself, there’s one rule of thumb that I try to keep in mind when choosing between potential jobs:
Only take a job where you’ll learn something.
This rule of thumb has worked well for me, and it has resulted in some of my most-saleable skills – things I might not have gotten around to on my own were I not getting paid to learn. But the strategy for doing this can be a bit tricky. Here are the most common objections that I hear:
Clients want to pay for the things I already know, not the things I want to learn. It’s certainly true that most contractors are in the business of selling their current expertise, not their availability as trainees. But there are ways to make this palatable to customers (current or future). One way to do that it to emphasize the parts of the job that you already know, and your track record of learning quickly. Another is to have a good stable of past reference clients who can help put new clients into their comfort zone. A third is to negotiate on rate – agreeing to put in hours at a lower rate or even entirely “off the books” as you’re coming up to speed on new things.
There isn’t any work with learning to be had. That may be true, and if you’re looking a rent payment in the eye, you may have no choice but to take a completely boring, routine piece of work. But don’t make the mistake of thinking too narrowly about what you can learn. Often I don’t know going into a job where my growth areas will be – it could be experience with a bug-tracking or source code management system I haven’t used before, it could be finding out about new ways to handle videoconferencing, it could be picking up details of useful tools by reading the source code that was written before I got there. Don’t think in terms of “what new skill will I add from this job?” but rather “what can I take away from this job to make me a better contractor on the next one?”
I already know everything in this field. Really? Congratulations. If you’re that much on top of your current game, I’d suggest taking a job that’s outside of your current field so that your prospects for employment will be that much better in the future. That doesn’t mean that you need to move from coding to, say, online translation. But it does mean that you might move from one web language to another. The more you know, the less chance you’ll find yourself out of a job due to lowered demand or competition from others who also know it all.
As an independent web worker, you probably already use your down time to make yourself more marketable. By staying attuned to the possibility of using your “up” time for learning too, you can enhance your career prospects that much more quickly.
photo credit: stock.xchng user jusstas