Wage theft and unpaid overtime in tech in 2026 — when exempt status doesn't apply

Wage theft and unpaid overtime in tech in 2026 often hides behind job titles, equity grants, startup urgency, and the phrase “you are exempt.” Exempt status is not magic. A company cannot avoid overtime rules simply by paying a salary, calling someone a manager, giving them a laptop, or saying the culture is high ownership. Exemption depends on actual pay structure, duties, salary thresholds, and state law. When those pieces do not line up, unpaid overtime can become a legal and financial problem for the employer and a burnout problem for the worker.

This guide is not legal advice. Wage-and-hour law is fact-specific and state rules can be stricter than federal rules. But tech workers should understand the pattern: misclassification, off-the-clock work, unpaid on-call time, bogus contractor status, and comp-time promises are the common failure points.

Wage theft and unpaid overtime in tech: the basic framework

Most U.S. employees are either nonexempt or exempt from overtime. Nonexempt employees generally must be paid for all hours worked and receive overtime pay when they work beyond applicable thresholds. Exempt employees are excluded from certain overtime requirements if they meet specific tests. Those tests commonly involve salary basis, salary level, and duties. Some states have their own higher thresholds or different rules.

The key is duties, not vibes. A customer support specialist, QA tester, implementation coordinator, junior analyst, IT help desk worker, content moderator, data labeler, sales development rep, or operations associate may work in tech and still be nonexempt. Some software roles qualify for computer-related exemptions; some do not. A fancy title does not decide the answer.

If you are hourly, nonexempt salaried, or otherwise eligible for overtime, the company generally has to pay for time it knows or should know you worked. That includes work before clock-in, after clock-out, during lunch, on weekends, in Slack, on customer escalations, and sometimes during on-call periods depending on restrictions.

Exempt status: what has to be true

For many white-collar exemptions, three questions matter:

1. Are you paid on a salary basis?
2. Do you meet the current federal and state salary threshold?
3. Do your actual duties fit an exemption category?

The duties test is where tech companies often get sloppy. “Manager” does not mean exempt unless the role has real management authority and meets the applicable executive criteria. “Operations” does not automatically mean administrative exemption. “Analyst” does not automatically mean professional exemption. “Technical” does not automatically mean computer exemption. If your day is mostly following scripts, closing tickets, executing checklists, labeling data, triaging support queues, or performing routine QA with little discretion, exemption may be questionable.

States can impose stricter tests. California, New York, Washington, and other jurisdictions can be more protective than federal law. Remote work adds complexity because the law of the state where you work may matter.

Common tech roles where classification deserves a second look

Watch classification carefully in these roles:

• Customer support and technical support.
• Trust and safety operations.
• Data annotation, AI evaluation, and content review.
• QA testing that is manual, scripted, or routine.
• IT help desk and internal support.
• Sales development and business development representatives.
• Implementation or customer onboarding coordinators.
• Junior marketing operations or revenue operations roles.
• Office operations, recruiting coordination, and people operations.
• “Founding team” generalists at startups doing nonexempt work.

Some employees in these functions are properly exempt. Many are not. The question is the actual job, not the department.

Off-the-clock work is still work

A company cannot solve overtime by telling employees not to record extra hours while expecting the work to get done. If a manager knows the queue is impossible, asks for weekend cleanup, praises late-night Slack responses, or assigns deadlines that require extra time, the company may have knowledge of the work.

Common off-the-clock examples in tech:

• Logging into Zendesk before the shift to clear tickets.
• Staying late to finish customer escalations after clocking out.
• Answering Slack or PagerDuty alerts during unpaid time.
• Completing required training outside scheduled hours.
• Preparing call notes, demos, or QA reports at night.
• Working through unpaid lunch because the queue is understaffed.
• Joining “optional” all-hands or standups that are functionally expected.

If you are nonexempt, track all time worked. Do not donate labor because the team is busy. A manager can discipline unauthorized overtime under policy, but the company generally still must pay for hours worked.

On-call time and pager duty

On-call rules depend on how restricted you are. If you can use the time freely and only occasionally respond, the on-call waiting time may not be paid, though response time usually is. If restrictions are severe, response expectations are immediate, you cannot leave home, alerts are constant, or your personal time is effectively controlled, more of the on-call period may be compensable.

Tech teams often blur this by giving nonexempt employees pager duty, customer escalation rotations, or weekend monitoring without clear pay rules. Ask:

• Am I exempt or nonexempt?
• Is on-call time paid, and at what rate?
• Is response time rounded or recorded exactly?
• Are minimum call-in payments required by state law or policy?
• Does overtime apply when on-call responses push weekly hours over the threshold?
• Is there a written on-call policy?

Equity, mission, or “startup mindset” does not replace wages.

Contractor misclassification

Another wage-theft pattern is calling someone an independent contractor when the company controls the work like an employee relationship. In tech, this can show up in QA, content moderation, design production, growth marketing, data labeling, recruiting, and operations. If the company sets your schedule, controls how work is done, provides tools, supervises closely, integrates you into the team, and prevents meaningful independent business, contractor status may be questionable.

Contractor classification rules vary by jurisdiction. Some states use strict tests. The risk is not only overtime; it can include payroll taxes, benefits, unemployment insurance, workers’ compensation, expense reimbursement, and paid leave.

If you are a contractor working full-time for one company, using company systems, attending daily standup, and being managed like staff, keep records.

Documentation playbook

If you suspect unpaid overtime or misclassification, create a private record outside company devices:

• Daily start and stop times.
• Meal breaks actually taken.
• Slack, email, ticket, or pager timestamps.
• Manager requests for after-hours work.
• Screenshots of schedules, queues, or deadlines.
• Paystubs and time records.
• Job description and actual duties.
• Performance feedback praising availability or responsiveness.
• Names of coworkers with similar schedules.

Do not secretly record audio unless you know the law in your state. Do not take confidential customer data. Keep the record focused on hours, instructions, and pay.

Scripts for raising the issue internally

Start with classification clarity:

“Can HR confirm whether my role is classified as exempt or nonexempt, and which exemption applies? I would also like the written policy for recording overtime and after-hours work.”

For off-the-clock expectations:

“I am regularly spending about [X] hours per week on ticket cleanup and customer escalations outside my scheduled hours. Should I record that time, and should we adjust priorities to avoid unauthorized overtime?”

For on-call:

“Before I join the rotation, can we confirm how on-call availability and response time are recorded and paid for nonexempt employees?”

For workload:

“I can complete A and B within scheduled hours. Completing C by Friday would require overtime. Should I record the overtime, or should we move the deadline?”

These scripts do two things: they ask for compliance and create a written trail.

Retaliation risk and escalation

Wage questions can make weak managers defensive. Keep your tone factual. Avoid accusing people casually in public channels. If the issue is systemic or the response is hostile, escalate to HR, payroll, legal, a trusted executive, or an outside employment attorney. Government labor agencies may also handle wage claims depending on the jurisdiction.

Retaliation for raising wage issues can itself create legal risk for the employer. Retaliation can look like sudden schedule cuts, worse assignments, discipline, firing, threats, immigration pressure, or performance narratives that appear after the complaint. Document timing.

If you are on a visa, extra caution is reasonable. Talk to an employment lawyer or immigration-aware advisor before escalating if job loss could affect status.

Startup myths that do not erase overtime

Myth: “We all wear many hats, so overtime does not apply.”

Reality: Startup chaos does not replace wage law.

Myth: “You have equity, so extra hours are part of ownership.”

Reality: Equity does not automatically make a nonexempt employee exempt.

Myth: “We offer comp time instead of overtime.”

Reality: Private-sector comp time rules are limited. A promise of future time off may not satisfy overtime obligations.

Myth: “You chose to work late.”

Reality: If workload and expectations make late work necessary and management knows, the company may still owe pay.

Myth: “Everyone in tech is exempt.”

Reality: Many tech workers are nonexempt or misclassified.

Candidate checklist before accepting an offer

Ask these questions if the role is support, operations, QA, implementation, sales development, trust and safety, data work, or any hourly-adjacent function:

• Is the role exempt or nonexempt?
• If exempt, which exemption is the company relying on?
• What are normal working hours?
• Is overtime expected, allowed, or paid?
• How is on-call time handled?
• Are after-hours Slack and customer escalations common?
• Are time records required?
• Does the role report to a manager who has handled nonexempt teams before?

A company that answers clearly is lower risk. A company that jokes about hustle, refuses classification detail, and normalizes unpaid nights is telling you something.

What not to do if you suspect unpaid overtime

Do not delete time entries to make a budget look clean. Do not agree in writing that hours were not worked if they were. Do not move work to a personal email account or hide it from timekeeping systems. Do not take confidential customer data to prove a point. And do not assume that being salaried means the issue is impossible.

The safer path is boring: record time accurately, ask policy questions in writing, preserve pay records, and get advice before escalating dramatically. If a manager tells you not to record overtime, write a neutral follow-up: “Confirming my understanding from today: I should not record time spent on [task] after [time], even if the work is required. Is that correct?” Many problems get solved when expectations are put plainly in writing.

The bottom line

Wage theft and unpaid overtime in tech in 2026 are not limited to warehouses or hourly retail jobs. They show up in high-growth companies, AI operations teams, support queues, QA groups, and startups where legal process lags hiring. If you are nonexempt, record every hour. If you are labeled exempt but the duties do not match, ask questions. If the company expects work outside paid time, document it. Exempt status has rules. When those rules do not apply, overtime does.

Related guides

• 401(k) match norms in tech in 2026 — by company size and stage — A guide to 401(k) match norms across tech companies in 2026, including startup vs public-company patterns, vesting schedules, true match value, mega backdoor Roth availability, and offer-stage questions.
• Accessibility Accommodations in Tech in 2026 — The Request Process and What's Reasonable — Accessibility accommodations in tech in 2026 cover far more than ramps and screen readers: remote work, flexible schedules, assistive software, meeting norms, interview adjustments, and sensory-friendly office expectations. Here's how to request accommodations clearly, what is reasonable, and what to document.
• Arbitration Clauses in Tech Employment in 2026 — What You Give Up and Whether to Push Back — Arbitration clauses can change how employment disputes are handled, what claims can be brought together, and how much leverage employees have. This guide shows tech workers what to inspect before signing and when to negotiate or opt out.
• Being out at work in tech in 2026 — the honest playbook on disclosure, allies, and policies — A practical guide for LGBTQ+ tech workers deciding how, when, and whether to be out at work, with scripts, policy checks, ally mapping, and risk flags for interviews, onboarding, and team life.
• Burnout Warning Signs in Tech in 2026 — What to Notice Before You Crash — Burnout in tech usually shows up before the dramatic collapse: slower recovery, cynicism, decision fatigue, body-level dread, and a shrinking life outside work. This guide gives practical warning signs, manager scripts, recovery moves, and decision rules for engineers, PMs, designers, data people, and tech leaders.