Skip to main content

NZ Tech Talent: The Reality

The NZ tech talent market is competitive and small. What we have learned about hiring and retaining developers in a market with unique constraints.
5 August 2019·6 min read
Isaac Rolfe
Isaac Rolfe
Managing Director
Last month I spent three weeks trying to hire a senior full-stack developer. Good salary. Interesting work. Flexible hours. We had four applicants. One was qualified. That's the NZ tech talent market in 2019. Not a crisis, exactly. But a constraint that shapes every decision we make about how we grow, how we structure projects, and how we compete.

The Numbers

New Zealand produces roughly 2,500 IT graduates per year. Not all of them stay. The pull of Sydney, London, and San Francisco is strong, especially for ambitious graduates who want to work at scale. Meanwhile, the demand for developers keeps growing as every industry digitises.
4,000+
unfilled tech roles in NZ in 2019
Source: NZTech Sector Report, 2019
The gap between supply and demand isn't closing. It's widening. And for enterprise specifically, the gap is worse because enterprise development requires skills that take years to develop. You can teach someone React in six months. Teaching someone to navigate stakeholder politics, manage technical trade-offs in real time, and communicate clearly with non-technical clients takes years.

What We've Learned About Hiring

Stop Competing on Salary Alone

In a small market, salary competition becomes a race to the top that smaller companies can't win. The large consultancies and government departments can always offer more. We stopped trying to match them.
Instead, we compete on three things that matter to the developers we want:
The work itself. Our projects are varied, complex, and consequential. Developers building a health platform that serves a million users, or a logistics system that changes how a national organisation operates, find that more compelling than maintaining a legacy system at twice the salary.
Autonomy. At RIVER, developers make architectural decisions, participate in client conversations, and own the outcomes of their work. There's no layer of project management between the developer and the client. For experienced developers who've been in large organisations where they had no influence over direction, that autonomy is valuable.
Growth trajectory. Small teams mean developers get exposed to the full stack, client-facing work, and leadership opportunities much earlier than they would in a large organisation. The developer who joins us today is leading projects within eighteen months.

Hire for Trajectory, Not Just Capability

The perfect candidate, experienced enterprise developer with strong technical skills and client communication ability, is almost impossible to find in NZ. There aren't enough of them, and the ones that exist are usually happy where they are.
We've had more success hiring people with strong fundamentals and the right disposition, then investing in their development. A graduate who's curious, communicates clearly, and cares about outcomes can become an effective enterprise developer faster than you'd expect, if you give them real work and real mentorship.
I'd rather hire someone who's 70% of the technical skill we need but asks great questions than someone who's 100% of the skill but works in isolation.
Isaac Rolfe
Managing Director

Look Beyond the Obvious Pool

Some of our best hires have come from unexpected backgrounds. Career changers who bring domain expertise from the industries we serve. Self-taught developers who built real products, not just tutorials. People returning to the workforce who bring maturity and perspective that fresh graduates lack.
The NZ talent pool is small. Expanding what you consider "the pool" is more productive than competing harder for the same candidates everyone else is chasing.

Retention Is the Real Game

In a market where hiring is hard, retention is everything. Losing a senior developer doesn't just cost you a salary. It costs you months of hiring, months of onboarding, and the institutional knowledge that walked out the door.

Projects, Not Just Positions

Developers leave when they're bored. Enterprise work has a natural advantage here because the projects change. Different clients, different domains, different technical challenges. But you have to manage the rotation deliberately. Leaving someone on the same project for two years when they're ready for a new challenge is a retention risk.

Visibility Into Impact

Enterprise developers rarely see the impact of their work the way consumer product developers do. The app doesn't have a download counter. The dashboard doesn't go viral. But the impact is real, and making it visible matters.
We share client feedback with the team. When a client tells us the system we built changed how their organisation operates, the developer who built it hears that directly. When user adoption numbers climb, the team sees those numbers.

Flexibility Is Expected, Not a Perk

In 2019, flexible work arrangements aren't a differentiator. They're a baseline expectation, especially in tech. Remote days. Flexible hours. The ability to leave early for a school event and make up the time later. These aren't perks we offer. They're how we operate.

The Bigger Picture

NZ's tech talent constraint isn't going away. If anything, it's intensifying as more organisations pursue digital transformation and compete for the same limited pool.
The companies that thrive in this environment will be the ones that develop talent rather than just acquiring it, that retain through meaningful work rather than golden handcuffs, and that expand their definition of who can be a great enterprise developer.
We're a small market. That's a constraint. But it's also an advantage. In a market where everyone knows everyone, reputation travels fast. Being known as a place where good developers do great work, grow their skills, and enjoy their careers is the most effective recruiting strategy we've found.