.png){kind=logo}
Two different schedules get marketed under the same 'four-day workweek' label, and only one actually reduces total hours.
The UK's 2022 pilot remains the strongest evidence available, with most participating firms choosing to keep the shorter week after the trial ended.
Adoption still varies by role and by company, so candidates need to verify the details directly rather than trust a headline benefit.
The phrase ‘four-day workweek’ can hide a major difference in a job offer. One model cuts working hours. The other simply packs the same 40 hours into four longer days. For candidates, confusing the two can mean accepting a role that offers a different work-life balance than expected.
The reduced-hours model keeps pay the same while trimming the week to roughly 32 hours over four days, with output expectations recalibrated to match. Advocates often call this the '100-80-100' framework: full pay, 80% of the time, for the same output.
The compressed model works differently. It keeps all 40 hours but squeezes them into four longer days, so Fridays open up while the rest of the week stretches later.
Both get called a four-day week in hiring materials. Only the first one actually shortens the working week. A Friday off does not automatically mean fewer hours were worked. Anyone evaluating a listing should ask directly which model a company means.
The clearest data comes from a 2022 pilot coordinated by 4 Day Week Global, the Autonomy Institute, and researchers from Cambridge and Boston College. Sixty-one companies and close to 2,900 employees moved to a four-day week on full pay for six months.
The results were notable. Ninety-two percent of participating companies extended the shorter week past the trial, and 18 made it permanent. Reported burnout fell, with 71% of employees describing less of it.
Companies reported an average 1.4% increase in revenue during the trial. Revenue was also 35% higher on average than during comparable periods in previous years, although that figure should be treated as context rather than proof that the shorter week caused the growth.
A one-year follow-up added more detail: at least 54 of the original 61 organizations were still running the four-day week, and at least 31 had locked it in as permanent policy. None of this proves every company can hold output steady on fewer hours or that every tech role fits 32 hours. It shows a meaningful share of participants found a way to make it work.
Software engineering, product management, and design tend to adapt more easily to a shorter week. Work in these roles gets measured through projects and deliverables rather than constant coverage, and much of it happens asynchronously, which makes a trimmed schedule easier to plan around. QA, testing, data roles, and content or marketing functions often fit the same pattern.
Fintech and SaaS startups are among the companies testing shorter schedules, sometimes treating the policy as a hiring differentiator. Industry-wide figures on adoption by role remain thin, so broad claims about any one function deserve a skeptical read.
Customer support, sales, and account management resist a universal day off, since client availability does not pause for internal policy. A four-day arrangement in these teams usually means staggered schedules rather than one shared day away from work.
IT operations and infrastructure face a similar constraint: systems that need constant monitoring make rotating coverage more practical than a single company-wide day off.
Verification required: the entries below reflect historical reporting and deserve a check against a current source, such as a careers page or recent announcement, before treating them as current policy.
Lists like this one age quickly. Job boards such as 4dayweek.io track larger, more current versions, but confirming directly with an employer still matters, since public reputation can lag well behind actual policy.
A short list of questions separates a real reduced-hours role from a rebranded five-day job:
Is the week actually shorter, or just compressed into four longer days?
Does pay stay the same either way?
Is the workload lighter than a five-day role at the same company, or identical?
Do meetings, deadlines, and targets shrink to match the shorter week?
Does the policy cover this specific role and team, or only parts of the company?
Is fifth-day availability ever expected for on-call work or client coverage?
Does the policy apply during probation or ramp-up?
Is the arrangement permanent, or a pilot that could end?
Can an employee choose the day off, or is it fixed?
How are holidays handled when they land on the day off?
What happens to the schedule during launches, peak periods, or major deadlines?
Job titles rarely flag the policy on their own. Specific phrase searches work better than a general one:
'four-day workweek' AND software engineer
'32-hour workweek' AND developer
'four-day week' AND product manager
'compressed workweek' AND UX designer
'Monday-Thursday' AND tech jobs
'shorter working week' AND remote
Reading the actual benefits section, rather than trusting a headline claim, matters most. Asking a recruiter whether the policy applies to the specific team being hired for closes the remaining gap.
The four-day week has become a visible part of tech hiring, but adoption stays uneven across companies, roles, and which version of 'four-day' a company actually means. For candidates, the real question is not whether an employer advertises the benefit. It is what changes in hours, workload, pay, availability, and performance expectations once the offer is signed.
Employers that publish real numbers on retention, output, and policy details give candidates something to evaluate. Everyone else is just offering a headline. More companies will experiment with shorter weeks through 2026 and beyond. The gap between disclosed data and marketed benefit is likely to become the real dividing line between employers worth trusting and employers worth questioning further.
Also Read: Top AI Careers and Salaries in 2027
Also Read: 10 Careers with the Highest Job Satisfaction in 2026
1. What is a four-day workweek in tech?
A four-day workweek typically means working four days instead of five, but the schedule can vary. Some companies reduce weekly hours to around 32, while others compress 40 hours into four longer days.
2. Which tech roles are most likely to offer a four-day workweek
Software engineering, product management, UX/UI design, QA, data, content, and marketing roles may be easier to adapt to shorter schedules as much of the work is project- and output-based.
3. Which tech companies offer four-day workweeks?
Companies such as Buffer and Kickstarter have adopted four-day-week models, while other organizations have tested or offered shorter schedules for specific teams or eligible employees. Candidates should verify the current policy before applying.
4. Is a four-day workweek the same as a 32-hour workweek?
No. A 32-hour workweek reduces total working hours, usually to four eight-hour days. A compressed workweek keeps the same weekly hours but distributes them across four longer days.
5. What should candidates ask about a four-day tech job?
Candidates should ask whether hours are reduced or compressed, whether pay remains unchanged, whether the policy applies to their specific team, whether fifth-day availability is required, and whether the arrangement is permanent or still a trial.
