How to Build a Data‑Driven Headcount Plan for Your Engineering Team

2017 is just a few days away, and headcount budgeting is a Q4 must‑do. To get HR approval you need to answer three questions clearly: how many people, at what levels, and what they will do.

Step 1: Define the work before the people

Since the headcount plan covers the whole year, you must align it with the annual task roadmap. For R&D this means planning the following:

1. How many new systems? What business needs do they meet?

My simple method is to assume one system requires one engineer. Currently we need 12 PHP engineers, leaving a gap of 2.

We also need to build a new search team; start with 2 engineers, and treat the team as a system that must avoid a single point of failure.

2. Which systems to upgrade? What problems exist and what hires will solve them?

The website will be fully covered next year, so we cannot open any “windows”. This requires higher‑skill engineers to raise the team’s professional capability.

Step 2: Set up the org chart before filling positions

1. Team organization structure

The team uses flat management and is divided into three groups: web & search, ucenter, and cms.

2. Fill‑in recruitment

Map existing staff onto the org chart; gaps become obvious. For example, the web team currently lacks an owner, so a senior engineer is needed to free the architect. The new search team must have senior engineers because junior staff cannot handle the initial workload.

Potential pitfalls: There is no annual OKR, so you can estimate for half a year and adjust mid‑year. Do not try to hire an owner directly; developing internal talent is more reliable, especially for senior roles. Separate headcount budget from promotions; treat them as distinct items. Do not count employee turnover in the new headcount; replace leavers at the same level to avoid misunderstandings. Prepare a well‑structured headcount budget PPT with clear rationale; it won’t be cut.