liveBook · Manning

Backfill cost

As explained in Think Like a Software Engineering Manager

The total cost of filling an open role after an employee departs, including hiring, onboarding, training, and related expenses.

Backfill cost measures what it takes to replace a departing employee. It includes direct spending plus the productivity and learning time needed before the replacement contributes fully. section 8.1

Use this rule of thumb to identify the main cost categories:

  • Backfill cost = hiring cost + onboarding and training + learning and skill development + unfilled time and other expenses. section 8.1
  • Include recruiting work, job advertisements, training, ramp-up time, and the workload absorbed while the role remains open. section 8.1 section 8.3.3
  • Treat lost institutional knowledge and productivity as additional intangible costs rather than assuming the invoice total captures everything. section 8.3.3

A $30,000 replacement

A replacement scenario totals $5,400 for hiring, $21,600 for onboarding and ramp-up, and $3,000 for miscellaneous expenses, producing a $30,000 backfill cost. Retaining the existing employee would cost an estimated $10,000, or one-third as much, before considering the knowledge and productivity lost through departure. section 8.3.3

How Think Like a Software Engineering Manager covers it

How deep it goes
Defines a cost equation and works through hiring, onboarding, ramp-up, and miscellaneous expenses without detailing accounting methods.
Examples
Uses a $30,000 replacement scenario contrasted with a $10,000 retention investment.
What it assumes
Assumes basic familiarity with employee departure, recruiting, onboarding, and training while defining the cost components directly.
What you can do after
Evaluate whether retention spending is cheaper than replacing an employee by estimating direct, ramp-up, and intangible costs.
How it connects
Connects attrition with employee retention, recruiting, onboarding, training, institutional knowledge, and productivity.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Think Like a Software Engineering Manager. The section links point to the parts of the book it draws on.