What is The Bare Minimum a Computer Tech Should Know Before Freelancing?

Bryce W

Administrator
Staff member
Reaction score
1,530
Location
Melbourne, Australia
I'd like to make a list of the BARE MINIMUM of what you should know before you start doing the most basic tech work as a freelancer. Id love for this to be a group effort to help build up this list and I'll keep updating this first post as you guys mention things that should be in this. This is what I have so far and by no means this is complete, thats why I'd love your input:


For Residential Clients:

Remove Tough Viruses - Such as Antivirus2009 using tools like Combofix, SmitFraudFix, Hijack This!, Process Explorer, Malwarebytes, Superantispyware and UBCD4Win.

General Hardware Understanding - Understand Power supply wattages and voltages. Understand motherboard and CPU socket types. Understand different RAM types and speeds. Understand motherboard slot types (AGP, PCI, PCI-E etc..) Understand hard drive types such as IDE and SATA and understand hard drive jumpers and their configurations.

Assemble a Computer - Not just putting to together, but understanding part speeds, possible bottlenecks and appropriate slot types.

Be Able to Troubleshoot Hardware Problems - Understand BIOS beep codes. Understand what it means if the fans spin up but no video comes up. Understand what it means when nothing powers up. Understand what it means when the computer powers up for 2 seconds then shuts down while still in BIOS bootup.

Recover Data from a Non Booting OS - Using a boot CD and an external hard drive.

Format a Computer - Wipe a drive clean and install an operating system.

Find and Install Appropriate Hardware Drivers - The ability install the drivers for peripherals like printers and scanners and also install the drivers for the parts inside the computer. Also to be able find a part number on the actual hardware and visit the manufacturers site to find the driver. To be able to identify the parts using tools like SIW.

Repairing a Damaged Windows - Be able to do a repair install, correct the missing/damaged file and to be able to do a chkdsk in a boot cd like UBCD4Win.

Know the Essential Windows Processes - Know what processes Windows needs to run and a rough idea of what each one does. For example, explorer.exe runs the desktop/icons/start menu.

Understand Windows Licensing - Know the differences between the OEM, Retail, Branded, Home, Professional, Volume and Corporate Licenses.

Setup a Basic Wired/Wireless Network - Know to setup a network with a modem, router and a few client computers. Understand how DHCP works and also know how to setup a basic computer to computer network. If wireless is involved, know how to apply encryption and understand signal strengths.

Basic Network Troubleshooting - Know how to find the systems IP, release and renew it. Know how to login to the modem/router and troubleshoot it. Is the internet details correct? is the modem getting an IP from the ISP? etc..


Theres plenty Ive missed here, lets get this ball rolling. What is the bare minimum a computer technician should know before going it alone?
 
Last edited:
My take on it is this:

If you want to freelance, go for it. As far as abilities go, just make sure you are only selling services you are capable of performing. You also need to make sure your client knows your limitations. If you price yourself accordingly you should get work accordingly.

I think there is a market for just about every level provided the price is right. It would be more expensive to hire some of us just to do something as simple as install a CD drive. Or you could hire someone for a little cheaper. Granted, that someone may quickly be out of thier league if there is something wrong other than the CD drive but that's life.

You wouldn't go to a brain surgeon to have a slinter removed from your hand. A nurse can handle that. Now that same nurse may notice a mole on your hand she doesn't like so then she would refer you to a specialist to have it looked at. The important thing is, you know you are seeing a nurse when you go in.

So, as long as the customer knows what thier money is getting them going in, go for it.
 
Basic Network Troubleshooting

I'd like to expand on the Basic Network Troubleshooting section

  • Understand how IP addresses work in a private network vs public Internet and how to identify what kind of IP address you are looking at.
  • A general understanding of masking/subneting
  • Understanding of what your Gateway is
  • Understand how and when to use static IPs
  • Know how to use Port Forwarding
  • tracert, ping

You use most of these in a residential scenario and will definitely use them in a business environment.

EP
 
My take on it is this:

If you want to freelance, go for it. As far as abilities go, just make sure you are only selling services you are capable of performing. You also need to make sure your client knows your limitations. If you price yourself accordingly you should get work accordingly.

I think there is a market for just about every level provided the price is right. It would be more expensive to hire some of us just to do something as simple as install a CD drive. Or you could hire someone for a little cheaper. Granted, that someone may quickly be out of thier league if there is something wrong other than the CD drive but that's life.

But, often clients don't know the difference between someone who can install a CD Drive and someone who can install a network and server. If they find that you can do one, they often expect you to be able to do the other.

I truly believe that you shouldn't even begin freelancing before you have at least decent level of fundamentals because the client will always ask for more and by human nature, we will want to comply... Which means the tech will likely get in over his/her head quite quickly.

And to add to the list further...
1) How to set up a router.
2) How to check for network vs. DNS issues.
 
Last edited:
one of the biggest things i have found out within my few months of operating, don't be afraid to tell the customer you don't know how to fix something! if your stumped with a problem, explain to them you can no longer help and point them in the right direction! its better to send away business, then try and half-ass the job.
 
How to warm up a hotpocket without turning the ends into a cinderblock and the middle into something hotter than lava.
 
Know how to communicate to your clients.

Have a decent grasp of the English language and use it without saying 'um' and 'like' all the time.

Also, learn how to speak geek to a layperson. Using a specialized vocabulary may impress your peers, but it will just frustrate and annoy your clients.

Get an idea of how to run a business. No, you will not know everything right away. You will have to learn as you go like everyone else. On the other hand, if you do not know how to do something basic like bill someone or keep a budget, then you need to learn.

Remember, running a successful business is not only dependent on your skill set, but how you appear to your clients. You could be a genius, but if your also a jerk no one will use you. In fact, I think image and marketing matters MORE than skills, how else would the geeksquad survive?
 
i think every tech should have a multimeter and understand how to use it.

I think that really depends on what kind of repairs you take on. I have a multimeter and understand how to use it. I've used it perhaps once in the last year where I couldn't have used a substitue method. I don't get into component level repairs - it's not usually financially viable at high hourly rates. The only time I'll get into this is where the parent system cannot be replaced for whatever reason.
 
Remember, running a successful business is not only dependent on your skill set, but how you appear to your clients. You could be a genius, but if your also a jerk no one will use you.

I could not agree more. I get a lot of my customers because they already had a bad experience with another tech. I treat my low end customers ( $50 job or less ) with the same respect I do the high end customers.
 
I would add strong, if not exceptional, customer service skills. I have ten years experience in retail, and it never fails to amaze me how rude some people (both co-workers and clients) can be.

Professionalism goes a long way.
 
I could not agree more. I get a lot of my customers because they already had a bad experience with another tech. I treat my low end customers ( $50 job or less ) with the same respect I do the high end customers.
Yep. You cannot service any customer properly without two important assets:
1) exceptional technical skillz, and
2) the exceptional courtesy to properly explain everything from start to finish on each job.

Treat every customer the same.
 
Yep. You cannot service any customer properly without two important assets:
1) exceptional technical skillz, and
2) the exceptional courtesy to properly explain everything from start to finish on each job.

Treat every customer the same.

very well said.

p.s. welcome back Wheelie long time no see.

Abe
 
Back
Top