Protip: don't ever reply to ads that ask for a "ninja" or "rockstar." Look for the more boring sounding jobs; they will have fewer people competing for the job,

Protip: don't ever reply to ads that ask for a "ninja" or "rockstar." Look for the more boring sounding jobs; they will have fewer people competing for the job, so you can probably make relatively better rates. Also, why do you only do remote work? Is there no one near you who needs a sysadmin? Could you travel? People value face-to-face interaction a lot more than online; if you only do remote work, then some guy in Bangalore can undercut your rates (hence the $20 an hour offers), and you're not really offering much over him. And as the original article says, don't charge per hour. Charge per week, or per incident. And charge rates that make sense for that kind of time frame. Read the original article; it has good advice. Once you charge per week (or per incident, based on a standard weekly rate), you can start talking about "OK, you want to spend less, which things should I not do", not "Well, I think I'm worth $50 an hour, but since I need the money, I'll take the job for $20" Yes, for systems administration it can work that way. Here where I work we don't really have any sysadmins (or everyone's a sysadmin, which is even worse). We have developers, and we have tech support who support customer systems, and we all kind of chip in on the system administration, but we don't have anyone who's job it is to maintain our own network. It finally got so bad that we've brought someone in to straighten it out. I don't know the details of how he's being paid, but I could easily imagine it as "it will cost $5000 for me to track down your problems, reconfigure your core router, set it up in a way that will be more maintainable in the future, and write the documentation for running that."