TL;DR
Software Engineer Overtime and Unpaid Work: What’s Normal — If you’re constantly pushing past 8 hours, answering “one last email,” or fixing midnight bugs for free, you’re not alone. In many teams, unpaid extra hours are treated as loyalty, “startup hustle,” or the price of entry into high-paying tech.
But here’s the hard truth: there is a line between reasonable crunch and quiet exploitation, and most engineers don’t know where it is until burnout hits. This guide breaks down what’s actually typical, what’s a red flag, and how to push back without risking your reputation or your role.
Why This Question Keeps Coming Up Right Now
Layoffs across the tech industry since 2023 left many teams smaller but with the same workload. Add return to office mandates and growing pressure to show visible output alongside AI coding tools, and it makes sense that overtime is back on everyone’s mind.
If you want the fuller picture of where the software engineer job market in the US stands heading into 2026, that context is worth reading alongside this one, since pay and workload expectations move together.
Is Unpaid Overtime Even Legal? The Exemption Most Engineers Don’t Know About
Here is the part that surprises a lot of engineers. Under the Fair Labor Standards Act, most salaried software engineers are classified as exempt employees. That means employers are not required to pay overtime once you cross 40 hours in a week.
The federal threshold for this exemption stayed at $684 a week, or $35,568 a year, through 2026. If you are paid hourly instead, the federal cutoff is $27.63 an hour. Once you clear either number and your job duties fit the computer professional test, unpaid overtime is legal, not a loophole your employer is exploiting.
States set their own, often higher, bars. California raised its computer professional exemption to $122,573.13 a year, or $58.85 an hour, effective January 1, 2026.
Colorado’s exemption threshold moved to $1,111.23 a week the same year. These numbers matter because they define your legal overtime rules based on where you actually live and work, not just what your offer letter says.
How Common Is Unpaid Overtime for Software Engineers in 2026
The data backs up what most engineers already feel. Stack Overflow’s developer survey found more than a third of developers regularly work past 45 hours a week. A separate analysis of US developers puts the average workweek closer to 43 hours once overtime is folded in.
Gartner’s 2025 workforce research found that 41 percent of workers put in about 9 extra unpaid hours weekly, and that overtime expectations have crept up as companies lean on smaller teams to do more.
Burnout tracking firm eMonitor reports a 71 percent burnout rate across tech overall, climbing to 74 percent among software engineers and DevOps specialists specifically, driven largely by always-on incident response and crunch culture before launches.
Monster’s 2026 workweek survey found that 45 percent of full-time employees now describe themselves as at least somewhat workaholic, meaning working extra hours has shifted from an occasional deadline crunch into something closer to a baseline expectation at many companies.
Unpaid Overtime Exposure by Employer Type (2026 Snapshot)
| Employer Type | Typical Weekly Hours | Crunch Frequency | Unpaid Overtime Likelihood | Common Trade-off |
| Big Tech (FAANG-adjacent) | 42-48 | Seasonal, around launches | Moderate | Strong RSUs, bonuses |
| Venture-backed Startup | 45-55+ | Frequent, funding-driven | High | Equity upside, faster titles |
| IT Consulting / Agency | 40-50 | Client deadline driven | Moderate to High | Billable hour bonuses |
| Remote-first / Distributed | 40-45 | Lower, output based | Lower | Flexible schedule |
Crunch Culture: Where It Actually Comes From
Crunch culture rarely starts as an explicit policy. It builds up from sprint deadlines that do not move, incident response that does not respect business hours, and layoffs that shrink a team while its roadmap stays the same size.
That combination creates constant workload pressure, and engineers absorb it by working extra hours quietly rather than raising it as a formal issue.
Not every employer handles this the same way. Some companies build in slack for exactly this reason, while others treat overtime as free capacity. It helps to check which companies tend to manage engineering workload and pay more fairly before you accept an offer, not after.
Software Engineer vs Other Tech Roles: Who Absorbs More Unpaid Hours
Unpaid overtime is not distributed evenly across tech roles. DevOps and site reliability engineers carry heavier on-call burdens, since outages do not wait for business hours, and that pattern shows up clearly when you compare software engineer and DevOps salary and workload data side by side.
Product managers face a different kind of pressure, mostly meeting overload rather than after-hours coding, though the two roles get compared often enough that it is worth seeing how software engineer and product manager responsibilities actually differ before assuming one path is easier than the other.
Do Benefits and Perks Make Up for the Extra Hours
Employers often lean on benefits and perks to soften the overtime conversation instead of paying it directly. Unlimited PTO, wellness stipends, and free food sound generous, but they rarely translate into fair compensation for the actual extra hours worked.
A full breakdown of what software engineer benefits and perks are really worth is useful here, since some perks genuinely offset overtime and others are mostly for show.
Return to Office Is Adding a New Layer of Pressure
Return to office mandates rolled out across 2025 and 2026 added commute time on top of existing workloads, without removing after-hours expectations. Many engineers are now doing a full office day and still logging back on at night to keep up.
The shift toward what return to office actually means for software engineers connects directly to this overtime conversation, since commute time is unpaid too.
Does Freelancing Fix the Unpaid Overtime Problem
Going independent looks like an escape from unpaid overtime, since freelancers bill by the hour or project. In practice, scope creep and unpaid discovery calls eat into that advantage constantly.
Real numbers on freelance software engineer income show the trade-off clearly, since higher hourly rates do not always mean fewer unpaid hours once you count sales and admin time.
Unpaid Overtime and Your Path to Promotion
Some engineers work unpaid overtime because they believe it speeds up promotion. The evidence is mixed at best. Leveling, scope of impact, and how well you document your work tend to matter more than raw hours.
A structured look at how software engineer promotions actually happen is a better use of your time than assuming more hours automatically means faster growth.
Salary Transparency Laws Do Not Cover Overtime
Several states now require employers to post salary ranges in job listings, which helps with fair compensation conversations at the offer stage.
What these laws do not touch is overtime pay for exempt employees. Understanding how salary transparency laws actually work for software engineering jobs helps you negotiate a stronger base and total comp package, but it will not by itself protect you from unpaid overtime once you are hired.
What You Can Actually Do About It
A few things move the needle here. Know your state’s exemption threshold, not just the federal one, since it can change your legal standing on overtime entirely.
Track your actual hours for a few weeks before any performance review or negotiation, since vague impressions of working hard rarely translate into a raise. Benchmark your software engineer salary against national data before assuming your current pay already accounts for the extra hours.
Ask directly during interviews how the team handled its last crunch period, and watch for hesitation in the answer. Burnout risk is real, and companies that manage it well usually have a specific, confident answer ready.
Frequently Asked Questions
Is unpaid overtime legal for software engineers?
Yes, in most cases. Salaried engineers who meet the federal or state computer professional exemption are not legally entitled to overtime pay once they cross 40 hours a week.
How many hours do software engineers actually work per week?
Survey data puts the average around 42 to 43 hours, though more than a third of developers report regularly working past 45 hours during busy periods.
Which US states protect software engineers from unpaid overtime the best?
California, Colorado, and New York currently set stricter salary thresholds and duties tests than the federal FLSA, giving engineers there stronger overtime protections.
Is crunch culture still common in tech going into 2026?
Yes. Startups and companies near product launches or funding deadlines report the highest crunch frequency, while larger and remote-first companies tend to enforce steadier hours.
Can I get overtime pay if I am salaried?
Only if you fall below your state’s exemption salary threshold or your actual job duties do not meet the computer professional duties test, regardless of your job title.
How do I know if I am misclassified as exempt?
Compare your actual salary and daily duties against your state’s specific thresholds and duties test. If your pay is close to the cutoff or your work is mostly routine rather than independent technical judgment, it is worth a closer look.
Share Your Experience
If you have dealt with unpaid overtime, a rough crunch period, or negotiated your way out of one, share what worked and what did not in the comments. Real experiences from other engineers are usually more useful than another generic list of tips.
Shahzada Muhammad Ali Qureshi (Leeo)
I’m Shahzada — a software engineer by education and an SEO professional by trade. I built WhatIsTheSalary.com to go beyond just showing salary numbers — every page is manually researched across sources like BLS, Glassdoor, LinkedIn Salary, and PayScale to give you the full picture in one place. If you found what you were looking for here, that’s exactly the point.
