What they are for

A returnship is a structured re-entry programme: it exists because standard recruitment treats a career gap as evidence of unsuitability, and most returnships exist to correct that specific distortion.

A career break of more than a year or two sits badly in a conventional hiring process. Applicant-tracking systems flag it; shortlisting criteria penalise it; interviewers treat it as something to be explained away rather than a neutral fact about time. The result is that qualified people — predominantly women, because unpaid caring work falls disproportionately on women — are screened out before any assessment of their actual capability takes place. The break does the disqualifying, not the skill-set.

This is the structural problem a returnship is designed to address. It bypasses the standard pipeline at the point where the gap would otherwise end the application, and substitutes a fixed-term placement — typically twelve to twenty-four weeks — in which re-entry is treated as a transition rather than a proof of continued currency. The participant is assessed on what they can do now, after a supported period of reorientation, not on whether they have a gap-free CV.

The mechanism matters. A returnship is not an internship rebranded. Internships are entry routes; they assume no prior experience. A returnship assumes substantial prior experience and is calibrated to restore rather than provide it. The target participant has typically been in the profession for a decade or more, left for a defined reason — parental leave, elder care, a health episode — and now faces a market that has restructured its entry criteria around continuous service. The placement is supposed to bridge that structural mismatch, not train a beginner.

What it corrects, and what it does not

The gap-as-disqualifier problem is not evenly distributed across computing roles. It is sharpest in technical specialisms where tooling and platform conventions change quickly enough that a three-year absence produces a genuine skills gap — though one that can be closed with structured reorientation. It is less severe in project and programme management, business analysis, and architecture-level roles where conceptual currency matters more than familiarity with a specific release cycle. Programmes that understand this distinction design their content accordingly; those that do not tend to produce a generic refresher that fails the most technically experienced returners and over-serves the least.

The participant is assessed on what they can do now, after a supported period of reorientation, not on whether they have a gap-free CV.

What a returnship cannot correct is the structural conditions that caused the break to occur in the first place. If workplace flexibility, caring responsibilities and mid-career attrition are treated as upstream problems to be solved elsewhere, the returnship absorbs the outcome of those conditions without addressing any of them. It is a re-entry mechanism, not a retention mechanism; it operates at the far end of the pipeline rather than anywhere that would reduce the exits feeding it.

The conversion question is therefore the sharpest test of programme integrity. A returnship that consistently fails to convert participants into permanent roles is functioning as something other than a re-entry route — as a source of project-specific labour, perhaps, or as a reputational signal rather than a genuine pathway. What they are not is the companion question to this one: the characteristics that distinguish a real programme from its impostors are largely the characteristics that a conversion-rate figure would expose if organisations published it.

The evidence base

Conversion rates, programme numbers, and salary outcomes for returnship participants are poorly documented in the UK. Employers run programmes without reporting their results to any central body, and the absence of a regulatory reporting requirement means the evidence base is mostly case-study rather than aggregate. This matters because it makes the programmes difficult to evaluate at population scale: whether they are collectively moving the representation figures, or redistributing a small number of places among a small number of organisations, is genuinely unknown.

What is measurable in principle — placement completion rates, permanent conversion rates, role level at conversion relative to role level at exit — is not systematically collected. Until it is, the returnship occupies an unusual position: a widely discussed structural intervention whose structural effect on the pipeline remains undemonstrated.