Two remote jobs at once: the math, the risks, and what to check first

The r/overemployed subreddit has 430,000 members. Fortune ran a story in 2025 about workers pulling in over $1 million a year by holding five jobs simultaneously, all within a standard 40-hour week. The pitch is obvious: remote work created the conditions, AI tools reduced the workload, and most companies would never know.

The math looks obvious too. Two salaries instead of one. Double the income. Why wouldn't you?

Here's a more useful framing: the people who succeed at this have already answered several questions you probably haven't seen asked in the same place. This guide covers what they are.

What overemployment actually means

Overemployment has a specific definition that matters: holding two or more full-time jobs simultaneously without the employers knowing. It's not freelancing. It's not a side hustle. Both positions are W-2 employment, both companies believe you're working exclusively for them, and you're managing two sets of standups, deadlines, and Slack channels in parallel.

The practice exploded during the pandemic when remote work became widespread, and it's grown since then. Senior engineers are most commonly cited because the work is often asynchronous, deadlines are self-managed, and the skills transfer cleanly. Junior engineers and team leads are less represented for opposite reasons: juniors lack the speed to operate at full capacity in two jobs, and leads have too many synchronous obligations to hide the conflict.

The actual financial math

The headline number is compelling. Two $150K jobs equals $300K gross. But the after-tax reality is different, and most overemployment content skips this part.

At $150K as a single filer in 2026, your effective federal income tax rate is roughly 22-24%, which leaves you with around $114K after federal taxes. At $300K, your effective rate climbs to around 30-32% federal, and your marginal rate on everything above $191K is 32%. The second $150K job doesn't net you another $114K. It nets you closer to $90-95K after federal taxes alone. Add state income tax if you're in California, New York, or New Jersey, and the second job's take-home shrinks further.

You also face a tax management problem. With two W-2 employers each withholding at single-job rates, you'll almost certainly under-withhold throughout the year and owe a lump sum in April. The solution is to file a new W-4 with one employer to withhold additional tax, or pay estimated quarterly taxes. Most overemployed workers find this out by surprise in their first year.

The math still works for many people. But $150K + $150K does not become $300K after taxes. It becomes roughly $195-210K in most US markets. That's a real number worth knowing before you start.

Three things that get people caught

The overemployment community talks a lot about security. But the actual failure modes are usually simpler than people expect.

Scheduling conflicts under pressure. Most of the time, two jobs run independently. But production incidents don't coordinate. A system failure at Job A at 2pm doesn't know you're in a required all-hands at Job B. Senior engineers get caught most often during these moments: two simultaneous emergencies that require undivided attention, and both managers notice the delays.

Document metadata and code commits. Files carry timestamps and user properties. A Word document edited on a company-issued laptop with another company's registered username is a visible record. Git commit history is public within an organization. If you're pushing code to two different GitHub organizations from the same machine, the history is there. Some engineers use separate machines and separate accounts to manage this. It adds operational overhead most people don't anticipate.

Benefits enrollment conflicts. US health insurance doesn't allow enrollment in two employer-sponsored plans as a primary member. If you attempt to enroll in both, the insurers will flag the conflict during coordination of benefits. This is one of the cleaner discovery paths for HR departments who suspect something but can't prove it otherwise.

The point is that most people who get caught aren't caught by surveillance software or keyloggers. They get caught by operational slip-ups: a wrong Slack account logged in, a meeting booked over another meeting, a response time that's consistently off during peak hours.

The legal reality

Overemployment is legal in the United States. Getting caught, however, almost always results in termination.

The US is an at-will employment country in 49 states. Your employer doesn't need a specific reason to fire you. Discovering you've been working for a competitor simultaneously, or simply discovering you've been employed elsewhere, is sufficient. Whether you had a formal exclusivity clause or not, most companies will terminate immediately.

The contracts worth reading before starting are the ones covering three areas. First, non-compete and exclusivity clauses: some employment contracts explicitly require disclosure of other employment or prohibit working for any company simultaneously, regardless of industry. Second, conflict of interest policies: most tech companies have policies that require disclosure of any financial interest in a competing business or employer. Third, IP assignment: if you write code or develop any work product, your employment contract almost certainly assigns ownership to the employer. Work done for Job B on Job A's time, or using Job A's tools, creates a real IP ownership dispute.

The criminal risk is narrow but real. Billing both companies for the identical hours (submitting timesheets showing 8am-5pm at both organizations on the same day) is fraud. This is rare as a prosecution target but it happens, particularly in consulting and contracting arrangements where billing is direct and documented. For W-2 employment, the risk is almost entirely civil and contractual, not criminal.

The burnout reality

The r/overemployed community is honest about this when you read it carefully. Burnout is one of the most common reasons people leave the second job within a year.

The promise of "working within a 40-hour week" assumes a certain kind of work: async, self-directed, well-understood scope. Senior engineering work at a well-run company often fits this. But tech companies have on-call rotations. They have quarters where scope expands suddenly. They have reorganizations that put you in more meetings. The two-job math that worked in Q1 stops working in Q3 when both companies are pushing toward a product launch at the same time.

The people who sustain overemployment long-term are deliberate about which jobs they take. They look for companies with strong async cultures, limited oncall obligations, and clear scope. Finding two of those at the same time is harder than finding one.

The question worth answering first

Most people who look into overemployment are motivated by money. If that's you, there's a question worth answering before you start the operational complexity of managing two jobs: are you already below market at your current one?

The median software engineer salary in the US in 2026 ranges from $130K at entry level to over $200K at senior and staff levels. The range depends on company, location, and tech stack. If you're a senior engineer earning $140K in a high-cost market, you may be $40-60K below what the market would pay you at a comparable company. A negotiated raise or a new offer doesn't require managing two Slack workspaces.

A $40K raise at your current job is worth more after-tax than a $60K second job. It doesn't come with scheduling conflicts, burnout risk, or the operational overhead of keeping two employers from comparing notes. And it's available to more people than the overemployment path is.

Before you take on a second job, check where you actually sit in the market. PayScope lets you upload your resume and see where your exact profile (role, level, location, experience) benchmarks against current market data. If you're already at market, the second-job math looks different. If you're not, you have a more direct option.

If you do decide to pursue overemployment, your single-job market rate tells you which companies are worth the risk of a second engagement and which ones are already paying you enough that the additional exposure isn't worth it.

How to use salary data in this decision

The decision to work two jobs is partly financial and partly operational. The financial part is the more tractable one to analyze before you start.

Start with your current compensation against market data for your specific role, level, and city. PayScope pulls from current job postings, not self-reported surveys, which gives you a better picture of what companies are currently willing to pay rather than what people claim they earned last year. If you're significantly below market, the conversation with your current employer comes first. See our guide on using data to negotiate a better salary.

If you're at market or above, and the decision is genuinely about income diversification or financial independence rather than correcting an underpayment, the overemployment math can work. The people who succeed at it long-term approach it as a deliberate career and financial strategy, not a hustle layered on top of an already stressful job.

Frequently Asked Questions

Is overemployment legal in the US? Yes. Holding multiple jobs simultaneously is legal in the United States. Your employer can terminate you for it under at-will employment, and contract clauses may restrict it, but the act itself is not a crime. The exception is fraud: if you bill both companies for the same hours, that crosses into criminal territory.

How do most overemployed workers get caught? The most common paths are scheduling conflicts during urgent situations, metadata in documents or code, and benefits enrollment conflicts. Surveillance software is rarely the issue. Operational slip-ups are.

Do I have to pay taxes on both jobs? Yes. Both W-2 employers will report your income to the IRS. The issue is withholding: each employer withholds at the rate appropriate for your salary with them alone, which understimates your total tax liability. File an updated W-4 with the higher-paying job to withhold more, or pay estimated quarterly taxes to avoid a large April bill.

What roles are most common in the overemployed community? Senior and mid-level software engineers dominate r/overemployed, followed by DevOps, data engineers, and product managers. The common factor is work that's largely asynchronous and outcome-based rather than time-logged and collaborative.

Can I lose my benefits if caught? Yes, and usually benefits are only part of it. Termination typically means losing health coverage, unvested equity, and any accrued PTO depending on your state. If your employment contract has a clawback provision for signing bonuses, that may also apply.

Is it worth checking my market salary before taking a second job? Almost always yes. If the goal is more money, underpayment at your current job is the simpler problem to fix first. A market rate analysis takes 10 minutes and tells you whether you have a negotiation to have before you take on the operational complexity of a second role.

Before you take on a second job for the money, find out if your current employer is already underpaying you. Upload your resume to PayScope and see where your salary sits against current market data for your exact role and location. If there's a gap, that's the conversation to have first.