4 ms·
Depends on how you structure your hours. Three days a week instead of 4 hours per day is usually better. In any case, everyone has to context switch when they g
by anthonyb 14y ago
Depends on how you structure your hours. Three days a week instead of 4 hours per day is usually better. In any case, everyone has to context switch when they go home and come back in the morning.
The real reason, I think, is that it's weird, which makes managers uncomfortable enough that it puts you down the list. There are ways to arrange it though - it definitely helps if you talk directly to the employer rather than through a recruiter.
It might also help if you have some contact with them first - perhaps think about segueing from either a full time role or a freelance contract into part-time work. Once they know you're good and get to know you, they'll be a bit happier to discuss it.
I work three days a week for a government department, which works out pretty well, and then the other two I work with my wife on her business. So it is possible - you just have to look.
- malandrew 14y agoI was even flexible with the work saying that I could do 2 full days (morning to night) or 4 half days where I would be with the team the entire 4 days, but my day would be broken up into two 4 to 5-hour segments (I normally don't lunch, just snack at my desk and keep working). This latter arrangement would have at least would have helped keep me in sync with what the rest of the team was doing. I would also add that the context switching between working on one backbone.js project (my startup) and another (the client's work) really isn't all that bad compared to context switching from a non-programming activity to programming.