liveBook · Manning

External hiring

As explained in Think Like a Software Engineering Manager

An external hire is a person recruited from outside an organization to fill an organizational role.

When a team needs skills or capacity that existing staff cannot provide, external hiring recruits someone from outside the organization. The decision should follow an assessment of growth, new initiatives, support needs, attrition, budget, and job-market conditions. Compare it with internal growth rather than treating either path as automatically correct. section 7.1.1 section 7.3

Use external hiring deliberately:

  • Define the role’s success criteria, required skills, team needs, location, compensation, benefits, and application process. section 7.1.1 section 7.2.6
  • Explain the consequences of not hiring, including project delays, burnout, or competing priorities, and use capacity data when leadership questions the need. section 7.1.1
  • Balance external candidates with internal opportunities so the team gains missing skills without weakening career development, trust, retention, or contextual knowledge. section 7.3.2 section 7.3
  • Hire gradually and iteratively, considering existing skills, diversity, seniority ratios, team size, communication, and disruption risk. section 7.2.6

Balancing internal moves and external hires

A team with six open positions moved two senior engineers to a sister team. To preserve a sustainable senior-to-junior ratio, the manager externally hired engineers early in their careers. In another team with four openings, existing skills, diversity, team size, and communication needs shaped a gradual hiring plan. section 7.2.6

When internal growth is the better choice

Bob, a senior developer familiar with critical products, had learned product-management practices from a departing manager and received mentoring from a sister team. Supporting his transition could preserve company context while advancing his career. section 7.3.2

How Think Like a Software Engineering Manager covers it

How deep it goes
Explains rationale, trade-offs, staffing considerations, and gradual planning, but stops short of detailed recruiting or interviewing mechanics.
Examples
Uses six-position and four-position staffing scenarios, internal transfers, early-career hires, and a product-manager transition.
What it assumes
Assumes responsibility for team staffing and basic organizational awareness, while explaining the decision from business needs and workforce capacity.
What you can do after
Evaluate staffing needs and choose a balanced, gradual hiring strategy using team capability, business impact, and career-development considerations.
How it connects
Connects external hiring with internal growth, job descriptions, career development, team culture, retention, and onboarding.

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.