The FLSA Exemption and 'Highly Compensated' Status: How US Labor Law Defines Overtime Pay for Game Developers

A standard AAA video game development cycle relies on a specific mathematical assumption: that the final 1,000 hours of a developer's year—roughly 20 extra hours a week for the 50 weeks leading up to launch—will cost the studio exactly zero dollars in additional payroll. That basis, the unpaid 60-to-80-hour workweek known as "crunch," is the foundation upon which modern $200 million game budgets are built. But that foundation is currently colliding with the Fair Labor Standards Act (FLSA), the federal law that dictates who gets paid for overtime and who does not.[5][6]

The stakes for the $180 billion gaming industry are existential. If a studio misclassifies its workforce, the back-pay liabilities for a 300-person team working 20 hours of unpaid overtime a week for a year can instantly exceed $15 million, before federal penalties are even applied. The legal shield protecting studios from those payouts is a set of FLSA exemptions—specifically the "computer professional" exemption and the "highly compensated employee" (HCE) status.[2][4]

Understanding how these exemptions work requires looking at the mechanics of the FLSA. Enacted in 1938, the law establishes the 40-hour workweek and mandates time-and-a-half pay for hours worked beyond that limit. However, Section 13(a)(1) carves out exemptions for "bona fide executive, administrative, and professional employees." To qualify, an employee must pass three tests: they must be paid on a salary basis, they must earn above a specific minimum salary threshold, and their primary duties must require advanced knowledge or discretion.[1]

For game developers, the "duties test" is notoriously murky. The FLSA includes a specific carve-out for computer professionals, which applies to systems analysts, programmers, and software engineers. Under this rule, a developer is exempt from overtime if they earn at least $684 per week on a salary basis, or $27.63 per hour. But the video game pipeline is not just programming. It requires animators, level designers, quality assurance testers, and audio engineers—roles that often do not meet the strict statutory definition of a "computer systems analyst" or "software engineer."[2][5][6]

"The tension lies in the creative nature of the work," notes Daphne Benford-Smith, an entertainment and labor attorney. "A technical artist might write scripts to automate animation pipelines, which looks like software engineering, but their primary duty is generating visual art, which the DOL often classifies differently." When a role fails the computer professional duties test, the studio must either pay them overtime or find another exemption.[5]

This is where the "Highly Compensated Employee" (HCE) exemption has historically served as the industry's ultimate failsafe. Introduced to simplify compliance, the HCE rule states that if an employee earns above a certain total annual compensation threshold, the rigorous duties test is relaxed. As long as they perform at least one exempt duty, they are disqualified from overtime. For years, studios used the HCE threshold to blanket-exempt mid-level and senior staff, regardless of whether they were coding an engine or designing a level.[1][4]

But the Department of Labor has aggressively rewritten that math. On July 1, 2024, the HCE threshold jumped from $107,432 to $132,964. On January 1, 2025, it escalated again to $151,164. This 40% increase in the exemption floor has fundamentally broken the compensation models of major studios. A senior level designer earning $125,000 in 2023 was safely exempt under the old HCE rule. Today, that same designer falls $26,164 short of the threshold.[1][3]

Because that designer no longer qualifies as a highly compensated employee, the studio must now prove they pass the standard duties test for a professional or administrative exemption. If they do not—and many creative roles do not—every hour they work over 40 in a week must be paid at 1.5 times their regular rate. During a standard three-month crunch period leading up to a holiday release, that single employee could rack up $15,000 in overtime pay.[4][6]

The financial exposure is forcing a structural pivot in how games are made. Studios are deploying three distinct strategies to mitigate the risk. The first is the brute-force approach: raising base salaries. For employees hovering near the $151,164 mark, it is often cheaper for a studio to give them a $10,000 raise to push them over the HCE threshold than it is to pay them for 400 hours of overtime.[4]

The second strategy is aggressive reclassification and time-tracking. Historically, salaried game developers rarely tracked their hours, viewing the job as a results-oriented creative endeavor. Now, HR departments are implementing strict time-keeping software to monitor exactly when developers log into their workstations and when they log out, ensuring non-exempt staff are either paid accurately or locked out of the network after 40 hours.[3][5]

The third, and most disruptive, strategy is the elimination of crunch itself. With the legal loopholes closing and the cost of overtime skyrocketing, publishers are increasingly delaying games rather than absorbing the payroll hit of a 60-hour workweek. "The economic incentive to mandate unpaid overtime is disappearing," researchers at Cardozo Law note, pointing out that the threat of class-action wage-and-hour lawsuits is finally outweighing the cost of a missed release date.[6]

Yet, the system remains fraught with uncertainty, particularly for Quality Assurance (QA) testers. QA is the most heavily crunched department in the industry, tasked with finding and documenting bugs in the final months of development. Because QA testers rarely write code, they almost never qualify for the computer professional exemption, and their salaries fall far below the HCE threshold.[2][6]

Consequently, QA testers are almost universally classified as non-exempt, hourly employees entitled to overtime. However, the industry's reliance on third-party contracting agencies complicates enforcement. Studios frequently outsource QA to external firms, creating a joint-employer dynamic where the studio dictates the hours but the agency issues the paycheck. When overtime is unpaid, determining which entity is legally liable under the FLSA becomes a complex jurisdictional battle.[5]

The Department of Labor's scheduled updates to the salary thresholds mean this pressure will only intensify. The FLSA rules now mandate that the HCE threshold will automatically update every three years, beginning in 2027, pegged to the 85th percentile of full-time salaried workers in the lowest-wage census region. Studios can no longer rely on static thresholds to protect their margins.[1]

The era of the blank-check development cycle is ending. As the legal definition of who deserves overtime expands, the video game industry is being forced to treat its labor force not as an infinite resource to be burned through before launch, but as a metered expense. The next major AAA delay will likely not be caused by a rendering bug or a design flaw, but by a payroll department enforcing a 40-hour hard stop.[4][6]