Advice on Becoming an Independent Contractor?

miyako asks: "I'm 20 years old and going to be graduating soon with a degree in Computer Information Systems. I was thinking recently about the job market available and I began to realize that I don't want to spend the rest of my life using my skills to make someone else money. I've been making money these last few years doing odd computer related jobs, programming, networking, graphic design, but never steadily or on a big scale. What I've come to realize is that when I graduate I'd prefer to work for myself doing contracting jobs. I thought that I would put the question out to Slashdot since a number of you seem to be doing this for a living or to supplement your income. What's the best way to get started, especially for someone without a lot of professional experience under their belt?" Update: 10/08 11:20 EDT by C : After press time, another worthwhile related question popped up. Rather than post another story, it's probably better to handle both issues together. So in addition to the current question, what legal aspects should Independent Contractors consider, especially when it comes to writing contracts? "Is it better to be a generalist, or to specialize in a few areas? What can I do to get myself recognized in the sea of other people doing the same thing? Is the market really there and is it strong enough that someone could make a living only doing this? What do I need to be aware of on the business end of things?

I realize that I might make significantly less, at least at first, than I could working for a company, but I would rather make less money and be more fulfilled working for myself. In short, what advice would Slashdot readers give a new graduate who is looking to start a business doing contracting jobs?"

While considering the issues an independent contractor needs to worry about when starting out, it might also help to consider the aspects a starting contractor will need to tackle when confronted with an important aspect of his job: writing contracts. With that in mind, we have this addition from Clanner: "I've been working as an IT Contractor recently, and I have a few opportunities to do some independent contract work (IE: not through a contracting agency) for a handful of clients. While I plan on consulting an attorney at some point, I'd like to get a few pointers from the Slashdot community as far as things to watch out for in contracts with customers. I'm looking for both items to avoid having in a contract as well as things that I should make sure are included. I plan on using a balanced contract, where neither party is at any severe advantage or disadvantage. I'm sure there are plenty of experienced hands at this in the Slashdot community, and I'd like to hear any suggestions you may have and about your experiences in this type of work (good or bad). Thanks!"

Comments

oops

[j0nb0y]

you picked the wrong field. Go to law school, or get your mba. Or at least your masters in something. With just a college degree, you'll be stuck low on the totem pole for the forseeable future.

Or maybe that's just what happened to me =[

Best advice for becoming IT consultant

[Safety Cap]

1. When you swipe the shopping cart, make sure you take the kind that don't have the auto-locking wheels
2. The motorists usually don't care that your windshield-washing bucket isn't filled with *cough* cleaning fluid
3. A "Will compute for food"-sign is novel enough to get an extra few bucks from the yuppies when they're stopped at the light; just make sure you deplace every few days
4. The best food scraps are found in Tai-food restaurant trashcans

Nobody will hire you.

[Dr. Bent]

You: "Hello. I'm an independent contractor with no experience, no support staff, and no financial backing whatsoever. I'm doing this because I don't want to work for "The Man." Did I mention I'm 20 years old? Please hire me."

Them: "Uh, no."

People become independent IT contractors after they have 20 years of experience and get fed up working for other people. They can do this because they have 20 years worth of personal contacts, industry knowledge and hands-on experience to draw from. You have none of those things.

You say you're willing to work for less. That's good, because you're going to be working for a lot less...like zero. Oh, and were you aware that you'll have to pay more in taxes at the end of the year because you're an independent contractor? Hope you like 1099 forms because you're going to be seeing a lot of them.

This is one of those things where, if you have to ask for help, you're better off not doing it. If and when the time is right for you to quit your 9-5 job and contract yourself, you'll know it. By that time, you won't have very many questions at all, which is a good sign that you might actually be sucessful.

You haven't even given yourself a chance to hate the 9-5 IT job yet. You might as well try. Who knows, you might actually enjoy it! Stranger things have happened.

Finally, an ask slashdot I can answer!

[YankeeInExile]

I have been contracting for most of my adult life.

My list of ten tips for success:

1. Find a niche. Learn some obscure system or language that will set you apart from the herd. Do you want to be one of 7,412 guys who spent the weekend installing distro and now call themslves Linux consultants, or the one guy who has experience integrating MumblefrotzOS with ObscureDatabase?
2. Go for breadth. (This contradicts number 1). While specialization is a good thing, you also will need to answer any question of the form Can you....? with Yes!.
3. Build a portfolio. Take on non-paying projects for non-profit groups that will give you absolute technical control and complete them and polish them well. Write good code. Document it well.
4. Set limits. Decide how much you want to work in a week, and then limit yourself to that schedule. Don't fall into the trap of thinking "I could go to the movies, or I could bill three hours on Project P." Have work time and play time.
5. Partner with a starving artist. Nothing will turn a potential client away from you as fast as a great piece of code with an ugly face on it. If you don't have an eye for UI, hook up with someone who DOES, and trade her skills for yours.
6. Do it because you love it. You will spend a lot fo time doing this. If you do not LOVE coding/software enginerring, go find a comfortable job where you can slack off and disappear in the organization.
7. It is okay to play hard to get. Do not take the project where the client comes to you and says, "well, we spent 90% of the budget hiring Joe Loser and we can't use anything he wrote - we want you to do the entire project for 10% of the budget." These people will not reward your hard work with loyalty. They will forever see you as a door mat.
8. Learn to write good contracts/specifications. Most clients really don't know exactly what they want, so you are not going to get anything like a reasonable specification out of them. That means you need to write a specification for what you intend to write, and then get the client to sign off on that. Add on time-and-material for any changes that deviate from that written specification.
9. Work with a mentor. Find a successful contractor that does something like you want to do, and work with them for a few years. Swallow a little pride and take the crumbs from their table - successful contractors always have more work than they can do personally, and will be glad to sub out simple projects to a newcomer.
10. Never fail to deliver on a contract. Bad news travels ten times faster than good news. Getting out from under a reputation as a flake is nearly impossible.

It can be done

[netfunk]

I have to throw in on this topic, since I've been doing this for several years now.

First, contracting is roughly akin to prostitution. You might think you're escaping some sort of pimp/whore relationship by not working for A Big Company, but you really are doing the same thing, just for multiple bosses. To be perfectly honest, you're trading a safety net for the possibility of more income.

That safety net is damned important, though. A lot of people don't have the stomach to function without it. There's nothing wrong with that, though.

Things like "health benefits" and "401k plans" and stuff go right out the window. You better get some health insurance out of your own pocket. (Listen to me...You Better Get Some Health Insurance!)

The people turning the Cogs of American Capitalism as 9-to-5 coders aren't as dumb as you suggest. Many of them are brilliant and talented, and they are focusing on building interesting things. Someone else is worried about finding revenue for them to do so.

And blahblahblah, money isn't everything.

So here's what I think: it's not the idea of a "normal job" that offends you. It's the idea of a boring job you can't stand. You don't want to maintain someone's else's shitty code, you don't want to write some buzzword crap pie that is neither spectacular nor innovative. I suspect that making someone else money is really secondary...it's a sour grapes response for being relegated to mediocrity.

Yeah, I can dig that.

So for you, based on the paragraph of you that I know, I would say: find an interesting job. I know, easier said than done, especially in this market. But there's bound to be something out there. Take some interviews (take them regardless of what else you do), and find the company that is building something interesting, and failing interesting, find the company that is building something beautiful. There's a lot of edification in elegance.

Ok, so about contracting.

Here's my advice. Find a vertical market.

My first paying jobs were writing Java code when no one did that. Later, when I was out of college and looking for work so I could be a Normal Person, I landed a job doing Linux and Mac development, because no one did that, but I did it for fun in my spare time, so I was naturally qualified for a job that couldn't be filled. If you're spending time on any open source project of any weight, chances are you are in a similar position. I just had the luxury of poverty...Linux was my primary OS out of need, but it paid off when command lines and C code and kernel builds were second nature to me. If you take these things for granted, that's good for you, and something you should try to convey in job interviews and contract pitches. Employers want smart people that can pick up new things above all else, right?

So I went to work for a company in Orange County doing Linux video games (you might have heard of them). When they went out of business, I moved in with my parents (turning in my membership card in the Normal Person Society), and started doing Linux and Mac game development, on my own, for companies that needed it. You know what? Nobody else did that. Now everyone needs a Mac port or a Linux dedicated server...people call me and ask if I'm available. I've been jokingly introduced at trade shows as "The Linux Game Industry". Vertical market, baby.

I don't live with my parents anymore, but I never got my membership in the Normal Person Society renewed. I guess that's a happy ending.

There are _always_ markets where people will pay top dollar for talented individuals. In the 90s, it was Java, and Linux, and embedded stuff, etc, but you can pull out any number of good examples for any era.

The world is filled with unemployed Visual Basic coders that took a college course on it because they heard there was money in it. It is _trivial_ to stand out from the herd. This is NOT measured in how many programming languages you know, but by what you can do, what you can pick up o