I think it depends on the management team and on the hire. Just like some people can work remotely effectively and others cannot... some people can work part-ti

I think it depends on the management team and on the hire. Just like some people can work remotely effectively and others cannot... some people can work part-time effectively and others cannot. I've had this be very successful one time with a senior developer who was working in roughly the same stack across side projects as well as what I had hired him for. He was able to time-slice very well. He could come in and in a fraction of the time of the rest of the team make a meaningful impact in both pushing his own features as well as reviewing others' code/architecture. I've found in running a consulting practice that if people need to split their time across projects that they generally do their best work when they can devote a consistent set of days to specifics projects/team (Project A on Mon-Wed, Project B on Thu, Project C on Fri). Trying to time-slice throughout the day of 4hr with Project A and 2hr with Project B and 2hr with Project C becomes too much context switching for most people. One other thing to keep in mind: if people do not work enough on a single project, they will not achieve enough momentum to do great things. Or if the rest of the team is working full-time, it may be too much effort to keep them in the loop of everything that has changed since it is moving at a faster pace than what their time allows. You can try to overcome this by not working on critical parts of the product or having their features not be depended upon by others.