To qualify for the computer‑employee exemption under the FLSA, you must earn at least $684 per week, dedicate 50% or more of your hours to systems analysis, design, or programming, and hold a qualifying title—such as developer, systems analyst, or software engineer. Pay your weekly salary, not hourly, and document all duties, time logs, and payroll records for three years. By mastering these details, you remain compliant and position yourself to uncover even more protection.

Key Takeaways

• Businesses must meet the 50 % duty test and qualify as a computer systems analyst, programmer, or software developer.
• The salary test requires ≥ $684 per week ($35,568 annually) as of 2019; 2024/2025 adjustments were reversed.
• Eligible titles include computer systems analyst, programmer, software engineer, data scientist with analytic duties, and systems engineer.
• Maintain payroll, time logs, and job descriptions for 3+ years to support exemption claims.
• Common pitfalls: mislabeling titles, failing the duty test, or overlooking non‑exempt tasks like help‑desk work.

Is Your Role a Computer Employee Exemption?

If you routinely apply systems‑analysis techniques to design, develop, or test software, your position falls under the computer employee exemption. You should confirm that your primary duties revolve around these techniques: specifying systems, designing architecture, crafting or revising code, and authoring documentation. The exemption also requires a blend of skill, discretion, and independent judgment. Candidates in roles that only install or troubleshoot hardware, even in a computer‑centric environment, miss the core test. Similarly, a job limited to routine program fixes without significant design work or analysis falls short. Align your responsibilities with the Department of Labor’s definitions; misclassification can cost wage claims, penalties, and attorney fees. As the industry faces future trends in AI‑driven development and global standards in software engineering, staying aligned with exemption criteria safeguards your legal standing and maintains compliance. You can validate compliance via internal audits, expert testimony, precise job descriptions, and reliable documentation. The salary test requires a minimum weekly salary of $684, roughly $35,000 a year, or an equivalent hourly rate if paid hourly, to qualify for the exemption.

Check Eligibility: Salary, Fee, and Hourly Tests

Now that you’ve identified the primary computer duties in your role, you must verify that your compensation satisfies one of the three federal tests for exemption. First, confirm the salary basis test: you must draw at least $684 per week—$35,568 annually under the 2019 rule enforced—without deductions. Next, be aware that the rule vacated by the district court means the increased thresholds no longer apply. The 2024 increase to $844 has been struck down nationwide, and the 2025 jump to $1,128 has been invalidated, so revert to $684. Second, evaluate the fee basis test. If you earn fees, the average fee per week must equal the salary threshold; calculate by total fees divided by hours worked, averaging no less than $684 per week. Third, assess the hourly basis test, applying only to computer‑specific jobs. You need $27.63 per hour, unchanged through 2024 enforcement. Confirm each test passes alongside the primary duties, addressing any remedial classification concerns while anticipating future modifications that may arise from litigation guidance.

Calculate the 2024 $35,500 Salary Threshold

Seven hundred and eighty‑four dollars a week defines the 2024 salary threshold for a computer employee, yielding an annual standard of $35,568—commonly rounded to $35,500 in common financial parlance. Multiply $684 by 52 weeks: $684 × 52 = $35,568. The 2024 DOL rule briefly raised the benchmark to $844 weekly, but the November 15, 2024 Supreme Court vacatur reversed it retroactively, returning the threshold to the pre‑2024 level. As a result, your effective threshold remains $684 a week, matching the 2019 rule and sitting below the current executive, administrative, and professional exemptions. Tax implications follow accordingly: wages under $35,500 are treated as non‑exempt, subject to overtime and employer payroll‑tax liabilities, while wages above that figure qualify for overtime exemption yet trigger wage‑and‑hour reporting obligations and potential state adjustments. Benchmark comparison highlights a 15.7% increase over the 2002 baseline, but the 2024 pivot remains postponed. Stay vigilant; state laws may set higher limits. Employees whose salaries fall below the new threshold must undergo a mandatory review to ensure compliance with the updated exemption criteria.

Determine If Your Hourly Pay Meets the Test

Because the Department of Labor fixed the hourly threshold at $27.63 in 1996, the first step to determine your exemption status is to calculate the exact hourly rate you receive on a weekly basis. In practice, you must sum all pay components—base salary, overtime, bonuses tied to hours—and divide by the actual hours logged each week. This Pay analysis establishes your hourly rate; if it meets or exceeds $27.63, you satisfy the Hourly test’s numerical requirement. The test does not rely on a salary figure of $684 per week, allowing you to qualify on an hourly basis alone. However, your duties must align with the prescribed duties test, covering design, development, or system analysis with constant judgment. Be sure to document all calculations and relevant pay statements; accurate, reliable records fortify your claim and shield against audit challenges. Maintain these records for at least three years to comply with regulatory retention requirements.

The Department uses the hourly threshold of $27.63 as a key benchmark.

List of Job Titles That Qualify for the Exemption

After confirming that your hourly wage meets the statutory threshold, you need to verify that your role matches one of the duty‑qualifying titles outlined by the Department of Labor. By consulting your organization’s title library and the expansive Job matrix, you can precisely map each position to its statutory category. The following titles commonly satisfy the computer‑employee exemption:

1. Core technical roles—computer systems analysts, programmers, software engineers, and systems analysts who design or assess complex information systems.
2. Application‑focused specialists—applications programmers, systems analysts/programmers, software specialists, and systems specialists who develop or maintain business applications.
3. Engineering and data science—systems engineers, software developers, computer software engineers, advanced‑degree IT professionals, and data scientists performing analytic duties.
4. Databases and security—database analysts, developers, administrators, network designers, and security analysts who manage and safeguard data assets.

Both the pay thresholds and the primary duty of the employee must be satisfied; otherwise, the worker is not exempt.

Identify Primary Duties That Grant Exemption Status

In any workforce seeking computer‑employee exemption status, pinpointing the primary duties that truly dominate an employee’s daily routine is critical. You must identify Critical Duties that satisfy the FLSA definition. The core analysis should revolve around systems analysis, design and development, program analysis, testing, and machine operating system tasks. Each duty must consume at least 50% of the employee’s time and require specialized knowledge. If a combination of duties attains the same skill level, you may still deem one the principal task. Documenting the relative importance is essential for a defensible exemption claim. This also requires complying with the minimum salary requirement of $455 per week.

What Jobs Fall Outside the Computer Exemption

The computer employee exemption omits positions that hinge on hardware manufacturing or routine support tasks. If your daily duties involve field repairs, field hardware assembly, or other manual support activities, you fall outside the exemption. Employers who classify such employees as exempt risk counterclaims. The following list clarifies categories that are explicitly excluded:

1. Hardware manufacturers and assemblers who physically build or repair components.
2. Help‑desk and support specialists who troubleshoot without programming or systems analysis.
3. Data entry clerks, operators, or backup library managers with no primary computer‑analysis work.
4. Engineers or drafters using CAD or specialized software merely as tools, not for software development.

Your position will remain non‑exempt unless your primary function delivers comparable systems‑analysis or programming work. Neglecting these distinctions exposes you to wage and hour liabilities. Hence, scrutinize your role carefully; misclassification can trigger costly penalties under the FLSA and liability claims today.

To qualify for the computer exemption, employees must earn a minimum weekly salary of $455, aligning with the statutory threshold.

Avoid Common Mistakes That Hurt Exemption

Because misclassifying employees as exempt can trigger costly penalties, you must carefully evaluate every role against the FLSA’s computer‑employee exemption criteria. If you label a worker ‘Engineer’ without verifying that his duties meet the primary criteria—systems analysis, design, or programming—you risk a compliance breach. Your salary test must surpass the threshold; a nominal stipend for a senior developer, when calculated hourly, often falls short of the $35,000 APT benchmark. Training Gaps in duty analysis can mask non‑exempt work, while Benefit Mismatch in overtime calculations misleads payroll reviews. You’re also barred from making deductions for partial absences unless the entire day is missed for a state‑required commitment; any other reduction infringes the wage‑deduction rule. Conduct internal audits that list each exempt employee, verify their salaries, and record duties in detail; adjust any title or compensation that falls outside of the approved scope. Only then will your compliance stance hold. Exempt employees must receive full salary if they work any part of the workweek.

Document Duties for a Successful Audit

Avoiding misclassification as you process payroll is the only way to shield your organization from costly penalties, and guarantees timely compliance.

1. Gather detailed job documentation: job descriptions, time logs, and payroll records that confirm a weekly salary of at least $684.
2. Document actual duties with precise audit trails that capture system design, development, testing, and user consultations, and log the percentage of time each task occupies.
3. Conduct a duties test review, verifying that at least 50 % of hours focus on program creation or modification per 29 CFR 541.400.
4. Maintain an accurate, searchable repository of all records—including personal data, overtime calculations, and off‑the‑clock entries—for a minimum of three years, ensuring readiness for a federal audit.

The audit must verify each employee is paid no less than the federal minimum wage.

Steps to Reclassify a Non‑Exempt Employee

When you initiate a reclassification effort, you first pinpoint employees whose salary or duties fall short of the FLSA computer‑employee exemption threshold. Conduct a duties‑based audit. Interview managers and incumbents, dismiss outdated descriptions, and document each function against exemption criteria. Use this evidence to justify non‑exempt classification. Salary must always cover all hours worked, ensuring the effective hourly rate exceeds minimum wage. Revise job descriptions and policies through rigorous policy revision. Align titles with actual duties, update timekeeping, overtime, and benefits procedures, and adjust compensation structures. Engage stakeholders: hold briefings, issue notices, collect acknowledgments, and emphasize overtime benefits, not demotion, to preserve morale and compliance. Determine pay structure: calculate regular rate, integrate bonuses, establish overtime premiums, budget for added costs, and adopt accurate hour‑tracking methods. Implement changes with clear communication: notify employees, schedule one‑on‑one meetings, stress compliance benefits, and maintain ongoing classification reviews. Follow up quarterly to reaffirm compliance and address changes. Maintain quarterly reviews to sustain compliance and adapt to evolving FLSA criteria.

Frequently Asked Questions

Can Part‑Time IT Staff Be Exempt Under the Computer Employee Rule?

Yes, part‑time IT staff can qualify for computer employee exemption if their Work Hours and Pay Structure meet the statutory thresholds. You’ll demonstrate that the employee earns the minimum $684 weekly, not proration, and that their duties center on systems analysis, programming, or software engineering. Accurate hour tracking and a full weekly salary guarantee compliance, enabling the exemption despite non‑full‑time status, and five days per week as required legally today.

Does Remote Location Affect a Computer Employee’s Exemption Status?

Don’t be fooled into thinking geography dictates exemption—remote setting matters not. Your duties, salary threshold, and control of work remain decisive. The IRS and DOL treat all computing talent consistently, regardless of office GPS. Remote employees receive your full salary for any week, precluding overtime unless hours exceed 40 and wages fall below minimum. Therefore, geographic factor is irrelevant; exemption hinges on job functions, not location in this regulatory landscape.

What if an Employee’s Duties Shift During the Year?

Even if an employee’s duties shift, the exemption hinges on primary duties. If role reallocation moves them to non‑exempt tasks, your status vacuates unless the primary duty remains computer‑related. A duty rotation that keeps the core task exempt meets the FLSA shelf, but any shift during non‑exempt work voids exemption retroactively. Maintain salary tests document primary duties guarantee full compliance detail minimizes legal risk; you’re required to act promptly today.

Are Contractors Eligible for the Computer Employee Exemption?

You might think the exemption is a surefire ticket, yet you’re not Contractor Exempt under the FLSA. The Exemption Criteria hinge on employment status, not contract label. Only employees performing core duties—systems analysis, programming, software development—qualify, and even then fee‑based contractors must meet the $684 weekly threshold. Department of Labor issued guidance that employers must treat them as employees for duty analysis. Your misclassification could trigger audits and back‑pay liabilities.

Can a Non‑Technical Role Be Exempt by Performing Analysis Tasks?

You’re claiming exemption if your non‑technical role still fulfills the primary‑Duty test, proving that every task involves critical analysis of systems. By demonstrating that you design, modify, or evaluate software components, you meet role qualification. Cite recent DOJ and Department of Labor rulings that emphasize the duty of systems analysis, not just user support. Therefore, a non‑technical position can indeed qualify, provided its work aligns with the exemption’s criteria today.

Conclusion

Have you verified that your duties align with the 2024 computer‑employee exemption, not just your headline title? If your salary meets the $35,500 threshold and your primary tasks involve developing or managing information systems, you likely qualify. Yet employers still risk costly audits if they overlook discretionary judgment or fee‑based versus hourly nuances. By documenting your responsibility, scrutinizing pay structures, and consulting FLSA guidance, you’re positioned to defend the exemption status and you protect livelihood.

James Bateson

Lawyer