Defining Non-Exempt Status Under the FLSA

Non-exempt employees are those who do not meet the specific criteria for exemption under the Fair Labor Standards Act (FLSA) and are therefore entitled to overtime pay. In the tech industry, this classification often applies to help desk technicians, data entry specialists, quality assurance testers, junior programmers, and many hourly contractors. The FLSA requires that non-exempt workers receive at least one and one-half times their regular pay rate for any hours worked beyond 40 in a single workweek. Understanding the boundaries of this definition is the first step toward compliance, as misclassification remains one of the most common areas of dispute in technology companies of all sizes.

The FLSA exemption tests—salary level, salary basis, and job duties—determine whether a worker is exempt from overtime. For example, software engineers earning above a certain threshold and performing high-level design work may qualify as exempt, while a junior developer paid hourly and performing routine bug fixes under close supervision likely does not. The U.S. Department of Labor has published clear guidance on these tests, and employers should review the official fact sheets to ensure proper classification.

The Unique Landscape of Overtime in the Tech Industry

Technology companies operate under pressures that few other industries experience: tight product release cycles, 24/7 system uptime requirements, and constant innovation that blurs the line between work and personal time. Because many tech roles involve project-based work with fluid schedules, overtime creep is a persistent risk. Non-exempt employees may feel compelled to stay late to fix a server outage or complete a sprint deliverable, even when their employer has not authorized overtime. Under the FLSA, however, unauthorized overtime must still be paid if the employer knew or should have known the work was performed. This creates a compliance challenge that requires proactive time-tracking and manager training.

Overtime Creep and Its Hidden Costs

Overtime creep occurs when employees regularly work a few extra minutes each day without formal recording. Over a month, those minutes can accumulate into hours of uncompensated labor. For tech companies with large teams of non-exempt support staff, this can lead to wage-and-hour lawsuits. The costs go beyond back pay: plaintiffs’ attorneys often seek liquidated damages, penalties, and attorney fees. A 2022 study by the Workplace Fairness Institute found that tech companies paid over $300 million in FLSA settlements in a single year, with a significant portion stemming from unreported overtime.

Misclassification Pitfalls Unique to Tech

One of the most frequent errors in the tech industry is misclassifying workers as exempt based on job titles alone. A "systems analyst" who primarily does routine maintenance rather than independent analysis might not meet the learned professional exemption. Similarly, a "software engineer" earning a high salary may still be non-exempt if their primary duty is testing code written by others rather than creative or analytical work. The Department of Labor’s duties test looks at actual job functions, not titles. Reviewing the FLSA duties test alongside each job description is essential before deciding on exemption status.

Calculating Overtime Pay Correctly

For many tech workers, overtime is straightforward: multiply the regular hourly rate by 1.5 for every hour over 40 in the workweek. However, complications arise when employees receive bonuses, commissions, or shift differentials. Under the FLSA, certain bonuses must be included in the regular rate calculation. For instance, if a non-exempt quality assurance tester receives a production bonus, the employer must recalculate the regular rate for that week and pay additional overtime on that bonus amount. Failure to do so can result in underpayment that compounds over time.

Example of Overtime Calculation with a Bonus

Scenario: A non-exempt junior developer works 45 hours in a week and earns $30 per hour base pay. Additionally, they receive a $200 spot bonus for fixing a critical bug. The regular rate for that week is re-computed: (45 × $30 + $200) ÷ 45 = $1,550 ÷ 45 ≈ $34.44 per hour. Overtime premium is then $34.44 × 0.5 × 5 = $86.10. Total pay for the week should be $1,550 + $86.10 = $1,636.10, not simply $1,475 (45 × $30 plus $200). Employers who skip the recalculation shortchange their employees and risk DOL audits.

State-Specific Overtime Laws Affecting Tech Companies

Federal law sets the floor, but many states have stricter overtime requirements. Tech companies operating in California, New York, Colorado, or Oregon must navigate additional rules, such as daily overtime, higher salary thresholds, or different break policies. Ignorance of state law is not a defense, and a single multistate company may need to apply different rules to different employees depending on their work location.

California: Daily Overtime and Double Time

In California, non-exempt employees must be paid overtime for any hours worked over 8 in a day (1.5×) and double time for hours over 12, in addition to the 40-hour weekly threshold. A help desk technician working 10 hours on Monday, 8 on Tuesday, and 8 on Wednesday would owe 2 hours of daily overtime for Monday even if the weekly total is under 40. California also requires meal and rest breaks, and missed breaks must be paid as an extra hour of wages. This complex framework demands robust scheduling systems, particularly for tech companies with on-call rotations or graveyard shifts.

New York: Higher Salary Thresholds

New York’s salary threshold for executive and administrative exemptions is significantly higher than the federal level, and it varies by region. In New York City, as of 2024, the minimum salary for exempt employees must be at least $1,124 per week (roughly $58,448 annually) for employers with 11 or more employees, compared to the federal threshold of $684 per week. Tech startups with many "junior" roles must ensure that low-salary employees are not incorrectly classified as exempt.

Colorado and Remote Work

Colorado has its own overtime laws and requires employers to provide detailed wage notices. With the rise of remote work, many tech companies now have employees physically working in Colorado while the company is headquartered elsewhere. That employee is subject to Colorado’s wage and hour laws, including meal periods and overtime rules. Colorado’s Wage and Hour Division offers guidance for employers with remote workers, but the burden is on the company to track the employee’s location and apply the correct laws.

Practical Challenges with Time Tracking in Tech

Tech companies often rely on software development tools like Jira, GitHub, or internal ticketing systems that track time spent on projects. However, these systems rarely capture the full picture: time spent answering team Slack messages, attending stand-up meetings, or troubleshooting after hours can go unlogged. For non-exempt employees, every minute of work must be recorded, whether authorized or not. Failure to do so puts the employer at risk, as courts will often credit the employee’s reasonable estimate of off-the-clock time if records are incomplete.

Email and After-Hours Communication

A growing area of litigation involves after-hours emails and messaging. If a manager sends a non-exempt employee a work-related question at 9 PM and the employee responds, that time is compensable—even if it takes only two minutes. Aggregated over dozens of employees over months, those small increments add up. Smart tech companies implement automated time-tracking tools that prompt employees to log work activity and restrict after-hours access to work systems. But policy must be coupled with culture: no one should feel pressured to check email at 10 PM to stay competitive.

Enforcement, Penalties, and Class Action Risks

The Department of Labor’s Wage and Hour Division can initiate investigations based on employee complaints or as part of targeted industry sweeps. In recent years, the DOL has increased scrutiny of the technology sector, particularly regarding misclassification of interns, contractors, and junior staff. Penalties for violations include back wages, liquidated damages equal to the back wages, and civil money penalties for willful or repeated violations. Private class action lawsuits are even more common, often alleging systematic failures to pay overtime to large groups of non-exempt workers. A single successful class action can cost a tech company tens of millions of dollars—and irreversible reputational damage.

To mitigate these risks, tech employers should conduct periodic audits of their wage practices, perhaps with the assistance of an employment law attorney. An audit would review time records, pay stubs, exemption classification, and state-law compliance. It also allows the company to correct inadvertent errors before they become the subject of a lawsuit.

Best Practices for Tech Employers

Fostering a culture of compliance while maintaining a fast-moving engineering environment is possible with deliberate systems and policies. Below are actionable best practices that go beyond the basics.

1. Use Purpose-Built Time Tracking Software

Generic project management tools are not designed for FLSA compliance. Invest in time-tracking platforms that integrate with your payroll system, allow employees to clock in and out easily, and provide audit trails. Require non-exempt employees to log all work time, even fractional minutes, and prohibit off-the-clock work. Notify employees in writing that any work performed outside of recorded time is a policy violation, but that if it occurs, they must report it to HR immediately.

2. Regularly Audit Exempt/Non-Exempt Classifications

Job roles evolve quickly in tech. A position that was correctly classified as exempt two years ago may now be performing non-exempt duties after a team restructuring. Conduct an annual review of all exempt positions, comparing actual duties against the FLSA duties test. Document the analysis and retain records.

3. Train Managers on Overtime Law

Managers are the frontline of compliance. They often authorize overtime indirectly by assigning tasks that take longer than the workday. Training should cover: (a) the prohibition on off-the-clock work, (b) how to approve overtime without pressuring employees, (c) the importance of accurate time records, and (d) the consequences of misclassification. Record training attendance and update it annually.

4. Implement a Clear Overtime Authorization Policy

While unauthorized overtime must still be paid, having a written policy that requires pre-approval sets expectations and reduces the amount of unscheduled overtime. The policy should state that employees who work without pre-approval are subject to discipline, but that they will still be paid. This protects the company from liability while also controlling costs.

5. Monitor Remote Work for Off-the-Clock Time

Remote work amplifies the risk of unreported overtime because the physical separation makes supervision harder. Use time-tracking software that captures idle time or prompts employees to confirm they are logging off. Establish office hours for communication, and remind non-exempt employees that they should not respond to work messages outside those hours unless it is an emergency and OT is approved.

6. Offer Work-Life Balance as a Preventive Measure

Excessive overtime is often a symptom of understaffing or unrealistic deadlines. Evaluate team capacity regularly and adjust resources to prevent burnout. By reducing the need for overtime, you lower your liability and improve retention. Non-exempt employees who consistently work 50-60 hours a week should raise a red flag for management.

What Non-Exempt Tech Employees Should Know

Employees also bear responsibility for protecting their rights. Tech workers—especially contractors and junior staff—can avoid exploitation by understanding basic FLSA protections. They should: (a) keep personal logs of all hours worked, including after-hours email responses, (b) report discrepancies in pay immediately, (c) never work off-the-clock even if a supervisor implies it is expected, and (d) contact the DOL or a private attorney if they suspect wage theft. Many states also have laws prohibiting retaliation against employees who complain about overtime violations, so raising concerns should not carry fear of termination.

For employees who may have been misclassified as exempt, the first step is to gather evidence of job duties, such as performance reviews, task lists, and communication records. That documentation can help determine whether the role truly meets the exemption criteria. Consulting with an employment attorney experienced in wage and hour laws is advisable before filing a formal complaint.

The Future of Overtime Rules in the Tech Industry

The Department of Labor periodically updates the salary threshold for exempt employees. The most recent rule, effective July 2024, raised the minimum salary for exemption to $844 per week ($43,888 annually), with scheduled increases to $1,128 per week ($58,656 annually) by January 2025. Tech companies using the "outside sales" or "administrative" exemptions must also monitor state-level changes, as many states are raising their thresholds faster than the federal government. Additionally, there is growing discussion around modernizing the duties test to account for changes in technology jobs, such as the rise of data scientists, AI engineers, and remote collaboration roles. Staying informed of these regulatory shifts is vital for long-term compliance.

In summary, overtime compensation for non-exempt employees in the tech industry requires constant vigilance. From accurate time tracking and proper classification to state-specific laws and proactive culture management, the stakes are high. By adopting robust practices today, tech employers can avoid costly litigation and build a workplace where employees feel fairly compensated—a foundation for sustainable innovation.