DOL clarifies overtime rules for tech workers, job titles do not decide exemption

What the overtime rule really means for tech workers

The biggest mistake tech workers make is assuming that a better-sounding title automatically means exempt status. It does not. Under the Fair Labor Standards Act, most U.S. employees are owed at least the federal minimum wage and time-and-a-half for hours over 40 in a workweek, unless a legal exemption applies. For people in engineering, product, support, and data roles at NlckySolutions, the real question is not what your badge says. It is what you actually do all week.

That distinction matters because exempt status changes pay, expectations, and leverage. If a role is truly exempt, the company can expect longer hours without extra overtime pay. If it is not, then labeling it as salaried or giving it a technical title does not erase wage-and-hour obligations. In a workplace built around sprint deadlines, incident response, release weekends, and client commitments, the line between “professional responsibility” and unpaid overtime can get blurry fast.

Why job titles do not decide exemption

Federal rules are blunt on this point: titles are not determinative. The computer employee regulation at 29 CFR 541.400 says job titles vary widely and change quickly in the computer industry, so the label alone cannot decide exemption status. That means a worker called developer, analyst, engineer, or even architect is not automatically exempt just because the title sounds advanced.

For NlckySolutions employees, that is the core takeaway. A salaried position is not automatically outside overtime rules unless the legal tests are satisfied. Companies often use titles as shorthand for career ladders, pay bands, or internal prestige, but the law cares about duties and pay structure. If the job description sounds impressive but the day-to-day work is mostly routine production, coordination, or support, the title may be doing more work than the law allows.

How the computer exemption actually works

The Department of Labor says the computer employee exemption generally covers computer systems analysts, computer programmers, software engineers, and other similarly skilled workers in the computer field. But the exemption is not a blanket for anyone near a keyboard. The job has to meet both the pay test and the duties test.

On pay, the DOL says the exemption generally requires a salary basis of at least $684 per week. There is also an hourly path: qualifying computer employees can be paid at least $27.63 an hour and still fit the exemption. The department is currently enforcing the 2019 salary level of $684 per week and the $107,432 annual compensation level for highly compensated employees while litigation continues.

The duties test is the real dividing line. Qualifying work usually means one or more of these:

• Applying systems analysis techniques and procedures, including consulting with users to determine hardware, software, or system functional specifications

• Designing, developing, documenting, analyzing, creating, testing, or modifying computer systems or programs, including prototypes, based on user or system design specifications

• Designing, documenting, testing, creating, or modifying computer programs related to machine operating systems

• A combination of those duties that requires the same level of skill

That list matters because it separates true exempt technical work from work that merely happens on a computer. If the job is mainly building systems, writing code, testing software, or shaping technical specifications, the exemption may fit. If the work is mostly using software to complete another function, the exemption may not.

Where misclassification risk shows up inside a tech team

The DOL warns that employees whose jobs are highly dependent on computers are not necessarily exempt if they are not primarily engaged in qualifying computer-analysis or programming duties. That is a major point for support teams, project coordinators, QA-adjacent roles, technical operations staff, and analysts who spend more time routing issues than solving them at the code or system-design level.

At NlckySolutions, the red flags are usually practical, not abstract. You should pay attention if your role includes any of these patterns:

• Most of your time goes to ticket triage, customer hand-holding, or internal coordination rather than systems analysis or programming

• You are expected to answer after-hours pings, join release weekends, or handle incident response, but your role description does not actually describe exempt-level duties

• Your title is advanced, but your work is largely repetitive, scripted, or dependent on prebuilt tools and templates

• You spend much of the week documenting, tracking, or escalating issues instead of designing, developing, or modifying systems

• Your salary is fixed, yet the company treats your schedule like an hourly worker’s schedule when crises hit

• You are told the role is exempt because “everyone in tech is exempt,” which is not how the law works

The point is not that every long week means misclassification. The point is that overtime status should match actual work, not internal mythology. If a team mixes coding, support, project coordination, and management, the classification question gets harder, not easier.

Why the 2024 rule still matters even after it was vacated

The modern overtime fight in tech cannot be separated from the rulemaking mess around 2024. The Department of Labor published a final overtime rule on April 26, 2024, with an effective date of July 1, 2024. That rule would have raised the standard salary threshold in phases and added a mechanism for automatic updates to salary and compensation thresholds.

Then the rule was stopped. On November 15, 2024, the U.S. District Court for the Eastern District of Texas vacated the DOL’s 2024 final rule. The department says it is now applying the 2019 rule’s $684 weekly salary level and $107,432 annual compensation level for highly compensated employees while appeals continue in other federal cases.

For workers, that means the legal floor is not where many employers thought it might be in mid-2024. For employers, it means payroll systems and classification audits cannot rely on old assumptions about a higher threshold that never survived the litigation. For NlckySolutions, the practical consequence is simple: compliance has to track the current rule, not the version that once looked likely to take effect.

What to ask if your title and duties do not match

If your title sounds technical but your day-to-day work feels closer to support, coordination, or production operations, the best move is to compare your actual duties with the exemption test. Start with the written job description, then compare it with what you really did over the last few months, especially during crunch periods.

A useful checklist is:

• Do you primarily perform systems analysis, software design, development, testing, or modification?

• Are you paid on a salary basis of at least $684 per week, or on the qualifying hourly basis of at least $27.63?

• Does your work require the same level of skill as the specific computer-related duties listed by the DOL?

• Are you being treated as exempt because of title alone, rather than because the duties test is clearly met?

• If the company expects constant availability, is that expectation consistent with the legal classification it has chosen?

Those are the questions that matter when title inflation runs into wage law. The safest assumption is not that a technical title protects a company, or a worker, from overtime rules. The safer assumption is that actual duties control.

For tech workers at NlckySolutions, that is the real line in the sand: if the job looks like exempt computer work, the law may back the exemption. If it mostly looks like support, coordination, or generalized computer use, the title may be decoration, not legal protection.