You need a tech. Maybe it's a help desk person, maybe it's someone to run cable at three sites. Somebody tells you to just 1099 them because it's cheaper and easier. Sometimes that's right. Often it's wrong, and wrong in a way that costs real money when a state agency or the IRS comes asking. Quick note before we go further: this is general information from a company that staffs IT roles all day, not legal or tax advice. For your specific situation, talk to an employment attorney or your CPA.
Here's the part most people miss: you don't get to pick the classification. The work picks it. Whether someone is a W-2 employee or a 1099 contractor is decided by how the relationship actually operates, not by what the contract says and not by what's cheaper for you.
What actually decides it
The IRS and state agencies look at control. The details vary by state (California's ABC test is stricter than most), but the core questions are consistent:
- Who controls how the work gets done? If you set the schedule, dictate the process, and supervise the work day to day, that points to W-2. A contractor decides how to deliver the result you asked for.
- Whose tools are they using? A tech working on your laptop, in your ticketing system, with your admin credentials, looks like an employee. A contractor typically brings their own gear and their own methods.
- Is the work ongoing or a defined project? "Answer our help desk tickets 40 hours a week indefinitely" is a job. "Migrate our file server to SharePoint by March" is a project.
- Can they work for others? Real contractors have other clients. If you require exclusivity and full-time hours, you've basically described employment.
No single factor decides it. But if you're setting the hours, providing the equipment, directing the daily work, and the engagement has no end date, calling that person a 1099 contractor doesn't make it true.
What misclassification actually costs
If a worker you 1099'd should have been W-2, the exposure stacks up fast: back payroll taxes (both halves of Social Security and Medicare), unpaid unemployment insurance, penalties and interest on all of it, and potentially back overtime if they worked more than 40 hours in a week. Some states add their own penalties on top. And the trigger is often mundane: the contractor's engagement ends, they file for unemployment, the state sees no wage history, and now there's an audit of every contractor you've paid for the last few years.
There's also a quieter cost. Misclassified techs usually know they're getting a raw deal on taxes, and they leave the moment something better shows up. In IT, where good people are hard to find anyway, that churn hurts.
When 1099 genuinely fits
Contractors are the right call for a lot of IT work, and we place them constantly:
- A defined project with a clear deliverable and end date: a network refresh, an office move, a server migration.
- Specialized skills you need occasionally, not weekly: a firewall specialist for a few days, a developer for one integration.
- Field work across many locations, where a local tech does a site visit and moves on.
- Overflow coverage where the person genuinely runs their own business and serves multiple clients.
In these cases the contractor controls their methods, brings their own tools, invoices for the work, and moves to the next client when it's done. That's a clean 1099 relationship.
When W-2 is the honest answer
If you need someone in your systems every day, on your schedule, following your procedures, for the foreseeable future, that's an employee. Help desk staff, a sysadmin who owns your infrastructure, a developer embedded in your team for a year: these are W-2 roles in almost every reading of the rules. Yes, W-2 costs more per hour once you add payroll taxes, workers' comp, and benefits. It also buys you legitimate control over the work, which for core roles is exactly what you want.
The middle path: someone else's W-2
There's a third option that solves most of these headaches: the tech is a W-2 employee of a staffing firm, working on assignment at your company. The staffing firm handles payroll taxes, unemployment insurance, and workers' comp. You direct the day-to-day work without carrying the classification risk yourself, because the person genuinely is an employee, just not yours. This is how we place most ongoing contract roles, and it's why contract staffing exists as an industry. You pay a bill rate that covers all of it, and the compliance question goes away.
How to know you've got it right
Run the honest test. Describe the relationship out loud without using the words "employee" or "contractor": who sets the hours, whose tools, how long it lasts, who directs the work. If that description sounds like a job, pay them like a job, either on your payroll or through a staffing firm's. If it sounds like a business serving a client, 1099 is fine, and put a real contract behind it with a defined scope. When the classification matches reality, audits are boring, and boring is what you want.
Stuck on this, or want it done for you? That's the job.
Email us →