Technology Scale-up Hiring
How should TA capacity be planned?
The short answer
TA capacity should be planned from expected hires weighted by complexity, geography and process workload rather than by vacancy count alone. Senior and specialist roles consume more research, engagement and stakeholder time than accessible repeat hiring. Scenario planning should include hiring peaks and slowdowns.
Capacity planning by vacancy count is one of the most common reasons TA teams are either overloaded or overbuilt. Twenty repeatable engineering hires and twenty specialist leadership hires are not the same workload, and pretending they are hides both risk and cost.
Weight roles by complexity
Group the hiring plan into role families and apply weightings for market difficulty, seniority, geography and stakeholder complexity. A weighted view of demand gives a much sharper picture of the capacity actually required than a raw vacancy list.
Include operational workload
Coordination, systems, reporting and candidate care take real time. Excluding them from the plan pushes that work onto recruiters, who then have less time for sourcing and stakeholder partnership. Model operations capacity explicitly.
Plan several demand scenarios
Growth plans move. Build a base case, an upside and a downside, and understand the fixed cost of each. The point is not to predict the future accurately but to know in advance which levers you would pull if reality drifts from the plan.
Use flexible capacity for uncertainty
Permanent headcount should cover the demand you are confident of. Embedded partners, retained specialist search and annual capacity agreements should cover the demand you cannot commit to a year in advance. Building fixed cost for every scenario creates the wrong risk profile.
What this means in practice
Translate the hiring plan into weighted role families, include operational workload, model scenarios and cover the uncertain portion with flexible resource so peaks do not force permanent hires you would later have to unwind.
The Saiyō view
Annual capacity agreements with Saiyō are usually a more efficient way to cover specialist and peak demand than adding permanent recruiters. Fixed internal capacity holds the baseline; embedded capacity absorbs the variance without inflating cost through the cycle.
Explored in depth
This topic is explored in more depth within How Technology Scale-ups Should Structure Talent Acquisition.
Frequently asked questions
See this in practice
Move from the concept to the way Saiyō delivers it.
Related questions
How should TA be structured in a 250 to 1,000 employee technology company?
TA should normally have a clear internal leader, business-facing recruitment ownership, reliable operations and flexible specialist search capacity. The exact team size depends on annual hiring volume, role difficulty and geography. A core-and-flex structure is usually more resilient than building permanent headcount for every possible peak.
Read the answerAnswerWhat roles belong in a modern TA team?
A modern TA team needs leadership, stakeholder partnership, recruitment delivery, operations and data capability, although these do not all need to be separate full-time roles. Specialist sourcing or headhunting may sit internally or be embedded. The model should cover the complete hiring system without assuming every capability must be permanently employed.
Read the answerAnswerShould sourcing and recruitment operations be separate?
Sourcing and recruitment operations solve different problems and should have clear ownership, even if one person performs both in a small team. Sourcing builds market access, while operations protects process, data and candidate experience. As volume grows, separating the capabilities often improves focus and accountability.
Read the answer