Are job shares actually a thing, or is that a myth?

Question

Accepted Answer

They're real but rare in the United States, common in some specific industries (especially nursing, teaching, and parts of the UK and Australian public sector), and increasingly available in tech if you bring the proposal pre-formed. The "myth" framing comes from the fact that almost no employer advertises a job share — you have to build the arrangement yourself.

The basic structure: two people share one full-time role, splitting the hours, the responsibilities, and the salary. Common splits are three days / two days, with one day of overlap for handoff. Both people typically take half the salary and half the benefits, and report to the same manager. Done well, the employer effectively gets a 1.0 FTE for a 1.0 salary cost; done poorly, they get 0.5 FTE of confused work for 1.0 salary cost. The difference is in the operating discipline of the job-share pair.

The hardest part is finding the partner. Most successful job shares form between people who've already worked together — a former colleague, someone from a parents-in-tech network, a peer from a previous remote-work community. Cold-matching strangers into a job share rarely works because the partnership requires deep trust about handoff quality, judgment calls in the other partner's absence, and equitable workload distribution. If you don't have a candidate partner already, the search for one usually takes longer than the search for the actual role.

Once you have a partner, the proposal to a prospective employer needs to be specific. Not "we'd like to job-share" but: "we'd each work three days a week with one overlap day. We'd cover all your stated responsibilities between us; here's how we'd split the responsibilities; here's how we'd handle handoffs; here's how we'd report to you. We're each willing to interview separately so you can evaluate fit independently. Combined, we'd cost you 1.0 FTE; separately, you're getting two senior IC perspectives instead of one." A prepared proposal of that depth changes "no" to "let me think about it" in many companies.

The roles where job shares work best: senior IC roles with stable scope (think principal engineer, senior product manager, head of content), customer-facing roles with predictable cadence (account management for a portfolio of accounts), and operations roles where both partners can pick up work in the queue. The roles where they work poorly: roles with unpredictable escalations, roles that require deep relationships with specific external stakeholders who'd be confused by two faces, and roles in fast-moving early-stage companies where context is changing daily and handoff costs are crippling.

The legal and benefits structure is usually fine but check the specifics in your jurisdiction. In most US contexts, both partners are full part-time employees with prorated benefits. Some employers extend full health benefits to both partners as a recruiting incentive — worth asking about. Retirement plans, parental leave, and PTO usually prorate cleanly.

The deepest reason job shares are rare is cultural: managers are trained to think of "one role, one person" as the default and view the alternative as administratively complex. The administrative complexity is real but small; the cultural inertia is large. The job-share candidates who succeed are the ones who do the work of normalizing the arrangement for the manager — by bringing a clear proposal, by referencing other companies that have done it, and by making it cheaper for the manager to say yes than to figure out an objection.

If you want to explore job shares specifically, the network move is to join one of the parent-and-caregiver-in-tech Slack communities and post: "looking for a job-share partner in [your function]. I have [X years] of experience, [these strengths], and want a 60% schedule." The matches happen, slowly, and the resulting partnerships are some of the most stable flexible-work arrangements out there.

Are job shares actually a thing, or is that a myth?

More questions