Scaling ICT Capacity in NZ with a Talent Pool of 40,000. Do the Maths.
New Zealand has roughly 40,000 ICT workers.
That's the entire pool. Government. Private sector. Finance, health, telco, retail, utilities, startups. Every CTO with a transformation roadmap, every IT manager with a backlog, every procurement officer with a panel requirement — all fishing in the same pond.
Now think about what that means when your hiring plan says "we'll recruit when we need to."
The Pool Is Not as Deep as You Think
Stats NZ puts the technology workforce somewhere between 38,000 and 45,000 depending on how you draw the boundaries. Let's be generous. Call it 45,000.
Of those, roughly 10–15% are actively looking at any point in time. That's 4,500 to 6,750 people across the whole country. Not all of them are the calibre you need. Not all of them have your specific stack. Not all of them want to work in your sector, your location, or your culture.
By the time you filter for an Azure infrastructure architect with health sector experience who wants a permanent role in Wellington — you're looking at a market that could be measured in dozens of people.
Not hundreds. Dozens.
And on the day you post your role, you're not the only one posting it.
Everyone Has the Same Idea at the Same Time
This is the part that breaks hiring plans.
Budget cycles in New Zealand are remarkably synchronised. The fiscal year turns. MBIE updates the rules. Treasury signs off on capital. Suddenly every agency, every bank, every insurer has headcount approved and the same six capability gaps to fill — simultaneously.
February is chaos. March is chaos. Post a role in April after three months of internal approvals and you're entering a market that's been running hot since January.
The contractors who were available in November are placed. The permanents who were quietly considering a move have already accepted offers. The specialists who'd consider switching are fielding calls from three directions.
You didn't miss the market because you were slow. You missed it because you planned like the market would wait for you.
It doesn't.
"We'll Hire When We Need To" Is Not a Strategy
I hear this constantly from IT leaders who've come through a cost-cutting cycle. Headcount was trimmed. They managed. Why carry extra capacity?
Here's why.
In a talent market of 40,000 people, the time to build a relationship is before you have the requirement. The contractor who becomes your go-to cloud lead, the solution architect who knows your environment, the infrastructure specialist who's available on four weeks' notice — those relationships don't materialise the moment you need them. They're built in the months before.
When you "hire when you need to" in a constrained market, here's what actually happens: you wait 6–10 weeks for a permanent hire who may or may not be right. Or you take the first available contractor instead of the best one. Or you stretch your existing team past the point where good work is possible and start accumulating technical debt that'll cost three times as much to fix.
The constraint doesn't disappear because you ignored it. It just becomes more expensive.
What the Good Orgs Do Differently
The organisations that consistently secure the right capability aren't lucky. They're just not surprised by the maths.
They know their own demand curve. They've mapped what they're building over the next 12 months. They know when they'll need cloud capacity, when the security audit hits, when the legacy migration begins. That foresight is worth three months in a tight market.
They keep their bench warm. Not permanent headcount that adds to OpEx. A known set of contractors and specialists who've worked in their environment — who know the answer is yes before the question is fully asked. Relationships with suppliers who can place someone in days, not weeks.
They split run from build from scale. Run capability — keeping the lights on — should be stable and largely internal. Build capability — project delivery — can flex. Scale capability — surge capacity for peaks — should be pre-arranged, not scrambled for. If you're trying to run, build, and scale with the same permanent team, the maths on that doesn't work either.
They don't wait for the vacancy. They're visible in the market before they need to be. They talk to people before a role exists. They know who's coming off engagements in 90 days. They treat supplier relationships like infrastructure — something you maintain, not something you build in a crisis.
The Retention Problem Compounds the Supply Problem
This gets worse.
NZ's ICT workforce isn't just small — it's leaky. Senior people leave. Australia, UK, Canada, US. The talent that walks out doesn't get replaced by equivalent talent coming the other way. The graduate pipeline is growing, but not at the pace the market demands.
So if your retention is ordinary, you're not just losing people. You're pushing them back into a pool you'll be competing for six months from now when you try to replace them.
The cost of losing a mid-to-senior ICT professional in New Zealand isn't just the recruiter fee. It's the institutional knowledge walking out the door, the 6–10 week time-to-hire, the 3-month ramp, and the hit your team takes carrying the load in between. Add it up. It's almost always north of $100K. Often significantly more.
Retention isn't a nice-to-have in a market of 40,000 people. It's supply chain management.
Do the Maths Before You Write the Job Ad
New Zealand's ICT market is not going to dramatically expand in the next few years. Offshore talent helps at the margins. Graduate pipelines take years to mature. The fundamentals don't shift.
If your growth plan, your transformation programme, or your operational baseline requires ICT capability — and most of them do — then the question isn't "can we recruit when we need to?"
The real question is: have you built the infrastructure to access the right people before you need them?
If the answer is no, you're not behind on hiring.
You're behind on strategy.
Lexel specialises in placing mid-to-senior ICT talent across New Zealand's public and private sectors. If you're mapping your capability pipeline for the next 12 months, we're worth a conversation before the market moves.