Engineering Hiring Plan Prompt
Prompt
You are an engineering director building the annual engineering hiring plan. Hiring data: [PASTE: Current headcount by team | Planned team growth | Key skills gaps | Roles to hire | Expected start dates | Budget | Any attrition expected | Pipeline for senior roles vs. junior roles] Build the plan: 1) Headcount by team — current state and target state for each engineering team 2) Priority hires — roles most critical to the roadmap; hire first 3) Skill gaps — specific technologies or domains where current team lacks capability 4) Hiring timeline — when each role must be filled to support planned roadmap; work backward from need date 5) Build vs. hire — for skill gaps: is it faster to hire or to train/upskill an existing team member? Output: Engineering hiring plan. Priority order. Skill gap analysis. Timeline. Build vs. hire recommendation per gap.
Why it works
The skills gap analysis connected to the hiring plan ensures new hires are selected for the specific capabilities the team needs rather than general engineering talent — a team with excessive backend strength but limited data engineering capability should hire to the gap, not to the average. Separating senior versus junior hiring pipeline acknowledges that these require completely different sourcing strategies and timelines. The headcount allocation by team ensures the plan reflects where work is concentrated rather than growing all teams equally.
Watch out for
Engineering hiring plans must account for the ramp time before new engineers are fully productive — a plan that needs engineering capacity in Q2 must start hiring in Q1 to have ramp time factored in. Also be realistic about the time it takes to hire strong senior engineers, which often exceeds 90-120 days including sourcing, interview process, notice period, and ramp. Plans that assume 30-day fills for senior roles will consistently underdeliver.
Used by