
A full-time job in the United States typically means 35 to 40 hours per week, with 40 hours being the most common threshold for benefits eligibility and overtime pay under the Fair Labor Standards Act. In my experience, most employers define full-time as 40 hours, but many industries have adopted 37.5 or 35-hour weeks, especially in professional services, tech, and government roles. The official definition can vary by country: for example, in the UK, the standard is around 35–40 hours, while in France it’s 35 hours by law.
For job seekers, it’s crucial to check the specific company policy and local labor laws, as benefits like health insurance, paid time off, and retirement contributions often kick in only for employees working 30+ hours weekly. According to the Bureau of Labor Statistics, roughly 80% of full-time US workers log between 35 and 44 hours per week. The table below summarizes common full-time thresholds across different regions:
| Region | Standard Full-Time Hours (per week) | Legal Minimum for Benefits |
|---|---|---|
| United States | 35–40 | 30 hours (ACA) |
| United Kingdom | 35–40 | 30 hours (for some benefits) |
| France | 35 | 35 (legal maximum) |
| Australia | 38 | 38 (under award) |
| Germany | 35–40 | 30 (for social insurance) |
So, when you’re evaluating a job posting, look beyond the number of hours. Ask about overtime policy, flexibility, and how the company measures productivity. A 40-hour week doesn’t always mean you’re working all 40—some roles include breaks, meetings, and training. The key is to align your expectations with the employer’s culture and your own lifestyle needs.

I’ve been job hunting lately, and I keep seeing “full-time” listed as 40 hours a week in most entry-level roles. Honestly, I’m hoping for something closer to 35 because I want to keep up my side projects and still have a social life. A few friends in tech say their companies count 32 hours as full-time, but that’s rare. I’d rather know upfront what the actual schedule looks like—some places expect overtime without extra pay, which is a dealbreaker for me.

After switching careers in my late 40s, I’ve learned that full-time hours can be a trap if you’re not careful. I’ve worked 40-hour weeks that stretched to 50 because of “lean teams.” The sweet spot for me is 35–37 hours—productive enough to get the job done, but with room for family and health. I always check the employee handbook before accepting; some companies define full-time as 30 hours for benefits, which is a huge plus if you value flexibility over pay.

From what I’ve seen across different companies, the 40-hour workweek is still the gold standard, but it’s slowly shifting. In retail and hospitality, full-time often means 30–35 hours, while in corporate roles it’s strictly 40. I’ve noticed that startups and remote-first companies are experimenting with 4-day workweeks (32 hours, paid for 40). That’s becoming a real selling point. The legal definition matters less than what the market actually offers, so I always compare job postings side by side.

As someone who works remotely, I’ve found that “full-time” is more about availability and output than hours on a clock. My contract says 40 hours per week, but I usually finish my tasks in 30–35. The real question is whether the company tracks hours or just results. I’ve seen colleagues who log 50 hours because they’re in different time zones, while others do 25 and get promoted. My advice: when you interview, ask how they measure success. If it’s by hours, stick to 40. If it’s by deliverables, you can negotiate the actual time commitment.


