Hiring

Overemployed Background Check: Contractors on Two Jobs

No background check reliably finds a second job. How to handle overemployed engineers through contract terms and output, employee or contractor.

RE

CEO, Ruzora

6 min read

An overemployed background check is what managers search for when they suspect a remote engineer is working two full-time jobs at once. The search usually starts with a feeling: standups missed, PRs that slowed down in month three, a camera that's always off at 2 p.m. The bad news is that no background check reliably tells you about a second job. The better news is that you don't need one.

There's a legal wrinkle too. For employees, a hidden second full-time job can be a serious problem. For contractors, working for several clients is often the normal, legal shape of the relationship. Get that distinction wrong and you'll write a contract that doesn't hold up, or accuse someone of something they're allowed to do.

Key Takeaways

  • Being overemployed means secretly holding two or more full-time roles that each expect full-time hours.
  • Standard background checks verify past employment. They're poor at finding a current, concurrent job, especially one outside the US.
  • For independent contractors, the IRS says a contractor is "generally free to seek out business opportunities." Exclusivity has to be agreed, and it has classification consequences.
  • Manage it through the contract (hours, availability windows, conflicts) and through output you can see, not through surveillance.

Why background checks don't catch it

Employment verification databases are built on payroll. Equifax's The Work Number covers a lot of employers, 3 million by its own count in 2024, but it's built on US payroll data. A Wells Fargo HR page, for example, says its verifications are "only for employees who are working or have worked within the U.S." A contractor in Bogota billing two US startups as a freelancer won't appear in it at all.

International background check firms can verify past employers in many countries; Checkr says it covers more than 200 countries and territories. That's a check on history. Nobody sells a reliable live feed of who someone is working for this week. (Checking past employers properly is its own skill; see reference check fraud.)

When overemployment does get caught, it's usually because the work suffers or the hours collide. In one reported case, a New York state IT employee was arrested in October 2025 and charged with grand larceny for allegedly working a second job while on the clock remotely. Those are allegations, not a conviction, and the case involved a public employee, which is a different legal situation from a private contractor.

Employee vs contractor: different rules

EmployeeIndependent contractor
Other jobsOften limited by policy or contractNormal; the IRS says they're "generally free to seek out business opportunities"
What you buyTheir working time, under your controlA result or an agreed scope and availability
ExclusivityCommonPossible by contract, but it can weigh toward employee status
How to manage a conflictHR policy, conflict-of-interest rulesContract terms on hours, availability, deliverables, confidentiality

The IRS line comes from its guidance on financial control. The Department of Labor's 2024 independent-contractor rule also treated work that is exclusive of other employers as a sign of employee status (29 CFR 795.110); the department has since proposed rescinding that rule. This is general information, not legal advice. If you need exclusivity from a contractor, talk to counsel about how it affects classification.

Rows of people working at desks, each one possibly answering to more than one team
Rows of people working at desks, each one possibly answering to more than one team

What actually works

Write availability into the contract. Instead of "exclusive," specify what you need: core overlap hours (say 10 a.m. to 3 p.m. Eastern), response times during them, and attendance at named meetings. That's enforceable and doesn't depend on proving a second job.

Measure output, weekly. Merged PRs, reviewed PRs, tickets closed against estimates. A sharp drop around month two or three is a common pattern when someone takes on too much, whatever the reason.

Keep the camera habit. A short camera-on standup is the cheapest way to know the same person is engaged.

Ask directly at the start. "Will you be working with other clients during this engagement, and how many hours a week will you have for us?" Most honest contractors answer straightforwardly. The answer goes in the contract.

Skip the spyware. Activity trackers and keystroke loggers catch the clumsy, insult the good, and tell you nothing about quality.

A Concrete Version

A 30-person SaaS company hires a senior backend contractor at full-time hours, 40 a week, for 6 months.

  • Contract: 40 hours a week, overlap 10 a.m. to 3 p.m. Eastern, Slack replies within 30 minutes during overlap, other clients allowed if they don't overlap those hours and aren't competitors.
  • Months 1 and 2: about 9 merged PRs a week, solid reviews.
  • Month 3: 3 PRs a week, two missed standups a week, slow replies between 11 and 2.
  • Week 13: the engineering manager raises it on a call, citing the contract hours and the data. The contractor admits taking a second large client and offers to drop to 25 hours a week at a lower monthly amount.

The company accepts 25 hours for two months while it hires a replacement. No accusations, no background check, no lawyer. The contract and the data did the work.

The Honest Counterpoint

Some overemployed engineers deliver more than your single-job hires. If someone hits every deadline, attends every meeting and writes good code at 30 real hours, a lot of founders would take that deal. The problem is broken commitments, and a second job only matters when it causes them.

And chasing it has costs. Hidden monitoring erodes trust with the honest majority, and a contractor relationship that looks too much like employment can create misclassification risk you didn't plan for.

Where Ruzora fits

At Ruzora, our engineers are independent contractors, and the vetting happens before you meet them: a graded coding challenge and an on-camera AI interview, as separate evaluations. If an engineer has documented technical performance problems in the first 60 days, counted from their first working day, we replace them, and you pick the replacement from a shortlist.

Frequently Asked Questions

Can a background check find out if someone is overemployed?

Rarely. Background checks verify past employment, and US payroll databases like The Work Number generally don't cover foreign or freelance work. Current, concurrent jobs mostly show up through missed hours and output, not checks.

Is it legal for a contractor to work for other clients?

Usually, yes. The IRS describes independent contractors as generally free to seek other business. You can set availability and confidentiality terms, and some exclusivity, but exclusivity can weigh toward employee status. This is general information, not legal advice.

How do I tell if a remote engineer is overemployed?

Look for a drop in output after the first months, missed meetings during core hours, slow replies at consistent times, and a camera that's often off. Then ask directly and refer to the contract. See also resume fraud detection for problems that start before the hire.

The Bottom Line

You won't find an overemployed engineer with a background check. You'll find the problem in your contract terms and your weekly output data, and you'll fix it with a direct conversation. For engineers who were vetted before you met them, see our bench or request a shortlist.

Roberto Espinoza is CEO of Ruzora, which helps US startups hire pre-vetted senior LATAM engineers, with a vetted shortlist in 72 hours. See available engineers.

RE

CEO, Ruzora

Roberto is the founder and CEO of Ruzora. He works directly with US startup founders and CTOs on staff-augmentation and software-factory engagements, and personally reviews senior engineer placements.

Senior LATAM engineers

Get a vetted shortlist within 72 hours.

Tell us the role and the stack. Within 72 hours you're reviewing a vetted shortlist of senior LATAM engineers who match it.