[madewulf]

There is a reason for part time programming jobs not to be common: in most case, you want the work to be finished as soon as possible.

Part time makes sens as an employer for jobs that require constant presence and not much context to be executed (think of a cashier, for example). Then you can fill a full time with multiple part time workers.

But for jobs like programming, part time makes less sense.

[newaccount74]

For cashiers, hiring two part time employees is preferrable to one full time employee, because you can have their shifts overlap to cover peak hours. It's the reason why cashier jobs are almost all part time. They don't hire full time cashiers because then they would be overstaffed during slow times of day.

For any job that requires coordination, there is a huge communication overhead when hiring multiple people. It's extremely inefficient to split work between multiple people, so companies prefer to hire people for as many hours as possible.

The only way a part time softwate job would make sense for employers is if the job is so simple it needs no coordination, and two part time employees would be cheaper than a full time employee.

[romanows]

Maybe as there are more and more older programmers looking at partial-early retirement, part-time, lower-paid gigs might make sense? I could see working part time improving CI/CD, docs, refactoring, etc. Stuff that the main developers might not have time to do, is largely orthogonal to product development, but that may not get done otherwise.