The Signal Is Usually a Roadmap, Not a Headcount Spreadsheet
Teams reach for hiring when the actual problem is a specific, dated commitment the current team can't hit without dropping something else. That's a capacity gap, and it has a fast fix. A team that's shipping slowly across the board regardless of headcount usually has a process problem, and adding people to it tends to make the process problem worse, not smaller.
It's worth separating the two before reaching for either fix. They look similar from the outside and need opposite responses.
The Hiring Cycle Has a Timeline Problem
A permanent hire is the right call when the need is durable — this role exists next year too. But sourcing, interviewing and onboarding a permanent hire takes months, and the roadmap that created the pressure usually doesn't wait. Extension exists for the gap between "we need this now" and "we'll have hired for this eventually."
Know What You're Actually Asking For
"We need more engineers" is rarely specific enough to act on well. The useful version names the stack, the seniority, and — critically — what the engineer would own in their first month. If that last part is hard to answer, the gap probably isn't capacity yet. It's scope that hasn't been broken down.
Teams that can answer that question get a useful match fast. Teams that can't usually need a scoping conversation first, not a role posting.