3 ms·
If you think your job as an engineer is to write code, then sure -- part time makes sense. If you think your job as an engineer is to build a solution as a tea
by x0x0 5y ago
If you think your job as an engineer is to write code, then sure -- part time makes sense.
If you think your job as an engineer is to build a solution as a team, then one person hopping in and out of availability creates a hassle for an entire team. Can't have project meetings on Mon / Fri because X is never there. If a project with involvement by a part timer isn't done by eod Thursday, a fulltime person has 2 dead work days until the part time person shows up again. etc etc.
- bonniemuffin 5y agoI agree that someone working fewer days per week might be hard to fit into a full-time team culture, but someone working fewer hours per day ought to be pretty easy. For the "fewer hours per day" case, it's just like working across different time zones, which many companies are already well-acclimated to doing -- e.g. you need to schedule all your meetings with this person in the morning because their 5pm is at our 11am.
- x0x0 5y agoNot easy at all if you have remote workers. Someone from EST works 9am-1pm; someone from PST starts work at 9:30am. Daily overlap: 30 minutes. Yes it could be solved if you want to define core hours in the middle of the day, but I suspect people who want half time work don't view working in the middle of the day every day as the point of the exercise.
- Aeolun 5y agoBut this is great. If your company culture doesn’t depend on everyone always being there, it has a million benefits unrelated to productivity. Working becomes so much more relaxing.
- lupire 5y agoBut also less profitable per hour. Doing "line" work where you have no unique contribution means you have less negotiating power and so get paid less.