In one particular technical context, "pair programming" is a de facto style of job sharing – AIUI it's not often described as such – that's generally been very successful, even if its adoption has been slow.
Two programmers "work on a task together." "They do not only write code, they also plan and discuss their work. They clarify ideas on the way, discuss approaches and come to better solutions."
The "Benefits" and "Challenges" sections frankly discuss some issues, for instance (in "Challenges") that "intense collaboration can be hard" and that job sharers may have "different skill levels," that may apply to other job sharing scenarios, as well.
In one particular technical context, "pair programming" is a de facto style of job sharing – AIUI it's not often described as such – that's generally been very successful, even if its adoption has been slow.
Two programmers "work on a task together." "They do not only write code, they also plan and discuss their work. They clarify ideas on the way, discuss approaches and come to better solutions."
https://martinfowler.com/articles/on-pair-programming.html
The "Benefits" and "Challenges" sections frankly discuss some issues, for instance (in "Challenges") that "intense collaboration can be hard" and that job sharers may have "different skill levels," that may apply to other job sharing scenarios, as well.