Hiring Engineers You Won't Have to Replace

The most expensive hire is the one you make twice. Across departments that grew from a handful to 21+ people, the thing I got most deliberate about wasn't sourcing — it was hiring people who'd still be thriving two years later. Retention isn't a perk programme; it starts before the offer.

Hire for trajectory, not just the current level

Some of the best engineers I've worked with I promoted out of frontline support and L1 roles. They didn't interview as "senior" — they interviewed as people who got visibly better every month. Slope beats intercept. A motivated mid-level on a steep curve will pass a complacent senior inside a year.

Be honest about the job in the room

Half of early attrition is a mismatch nobody named at interview. If the role involves on-call, legacy code, or ambiguity, say so. The candidate who opts out because you were honest just saved you a six-month mistake. The one who opts in with eyes open stays.

Onboarding is a retention lever, not an HR formality

I cut ramp-up from eight weeks to under five by treating onboarding as a designed experience, not a pile of docs. People who feel competent quickly feel like they belong. People who flounder for two months quietly start looking.

Promote in public, and mean it

Identifying high-potential engineers and actually moving them up — with the title and the scope, not just the words — is the strongest retention signal a team has. It tells everyone else the ladder is real. I've watched that single practice change a team's whole relationship with staying.