He Worked Four Full-Time Jobs. Every Reference Check Came Back Clean.
A growing share of remote workers hold two or more full-time roles at once, undisclosed, on the same hours. None of it shows up on a background check.
The story that put a name to the problem broke in the summer of 2025, when startup founder Suhail Doshi posted on X that he'd fired an engineer named Soham Parekh in his first week, then discovered Parekh was simultaneously working at three or four other venture-backed startups at the same time — and had been doing it for a year without any of them catching on. The post went viral not because the situation was rare, but because it wasn't. The subreddit built around the practice, r/overemployed, now has more than 430,000 members trading tactics for running two full-time paychecks without either employer noticing. Business Insider profiled a pseudonymous IT worker, "Damien," who scaled from a single $90,000 support role to five concurrent full-time jobs pulling in $746,000 a year, stopping only at five because a sixth felt like it would tip the balance.
None of this required forged documents or stolen identities. It required a hiring process that verifies whether a candidate can do a job, and has almost nothing built into it to verify whether that candidate is about to do five of them at once.
Why a curiosity became a line item
Overemployment has existed since remote work made it physically possible to be in two meetings at once, muted, from two different laptops. What changed in 2026 is the scale, and the reason is not subtle: AI tools now let one person produce enough visible output to look like a fully engaged employee on two teams simultaneously. A senior engineer using AI-assisted coding tools can close tickets, ship pull requests, and clear a sprint board fast enough that "busy" and "full-time" stop meaning the same thing to a manager glancing at a dashboard. The same automation that recruiting teams have spent 2026 celebrating for cutting screening time and drafting outreach is, on the other side of the employment relationship, quietly absorbing the workload of a second job.
Boards noticed the cost before they had a name for it. Workforce-intelligence vendor Abloomify, whose founding team built fraud-detection systems at Verafin before turning to this problem, puts a single over-employed senior hire comfortably inside the $500,000 to $2 million in hidden workforce waste many tech companies now carry — payroll paid for full-time capacity that never actually arrives. The gap is invisible by design. Nobody bills two employers for the same hour. They just deliver a fraction of one job to each, and the fraction that's missing doesn't show up as an absence. It shows up as a roadmap that slips a little, a review that takes a little longer to get back, a teammate who's reliably slow to respond between ten and noon — the kind of thing that has a dozen innocent explanations until it doesn't.
The tell was never the person. It was the pattern.
What makes overemployment hard to catch is that no single signal proves it. A quiet calendar, a camera that's off on calls, output that lags a peer with the same title — each one has a benign explanation on its own. A new parent protects their mornings. A senior hire blocks focus time because a manager asked them to. Someone batches Slack replies instead of answering in real time. The employer-side analogue to the KnowBe4 case that put fake North Korean IT workers on the industry's radar isn't a single dramatic failure — it's a slow accumulation of small ones, each easy to excuse, that only reads as a pattern when someone finally lines up calendar data, delivery data, and response-time data side by side. Security researchers describe the North Korean IT-worker schemes the same way: individually clean signals — a resume that parses, an identity that checks out, a reference that answers the phone — that only add up to fraud when someone looks at the full set at once, not the boxes ticked one at a time.
The instinctive corporate response to a hidden pattern is to go looking for it with more instrumentation: screen recorders, keystroke loggers, activity trackers pointed at exactly the employees a company trusts least to be telling the truth about their time. It is also, on the evidence, close to the worst available response. There is no meta-analytic evidence that monitoring software improves performance, and roughly one in six workers say they would quit a job over being surveilled this way — meaning the practical effect of chasing the small number of people running a second job in secret is to accelerate the exit of the much larger number of people who weren't.
The gate nobody built
Here is the part that gets skipped in most of the coverage of this trend: the hiring process that let a candidate onto the team never asked, in any verifiable way, whether this was the only full-time commitment they were making. It asked about the candidate's last job, their skills, their references — all self-reported, all checkable in the sense that a phone number connects to a real person who says nice things, none of it checkable in the sense of actually confirming exclusivity, availability, or what else that candidate was doing with their other forty hours a week. Parekh's references, by every account of how he operated for a year across multiple companies, held up long enough to get him through more than one process. A reference check that confirms someone worked somewhere and was good at their job is not the same thing as a reference check that would surface a pattern of six-month tenures running in parallel across employers who never talked to each other.
This is the same structural gap that shows up everywhere else self-reported material gets treated as verified material in hiring: a resume is trusted until someone checks it, a work history is trusted until someone traces it end to end, and a candidate's account of their current commitments is trusted almost by default, because there has never been a standard, systematic way to check it. Overemployment isn't a new failure mode. It's the same one — a hiring process built to evaluate a document and a conversation, rather than a verified trajectory — showing up on the other side of the employment relationship, discovered eighteen months in in a Google Workspace log instead of caught at the reference-check stage where it was actually checkable.
The fix that's spreading through 2026 — more monitoring, applied after the hire, aimed indiscriminately at a workforce that mostly deserves the benefit of the doubt — treats this as a surveillance problem. It is at least as much a verification problem, and verification problems are supposed to be solved before the offer letter, not eighteen months after it, with a screen recorder.
AgentR evaluates candidates against a verified trajectory — the specific work, at the specific employer, over the specific timeframe, corroborated beyond a document or a reference call that answers exactly what it's asked and nothing more. A hiring process that traces what a candidate actually did and when doesn't just catch a fabricated skill. It's positioned to catch the six-month tenures that overlap in ways a resume never has to explain. When the alternative to catching this at the gate is a company-wide monitoring rollout eighteen months later, the fix isn't more instrumentation aimed at everyone who didn't do anything wrong. It's better verification aimed at the point where it was always supposed to happen. Let's talk.