Before you open the role, make sure you are solving the right hiring problem.

Most hiring mistakes do not look like hiring mistakes at the start. They look like urgency. Growth. Team pressure. A role that needs filling.

Then six weeks later, delivery is still slow, the team is frustrated, and everyone is quietly wondering whether the problem was the hire, the brief, or the environment they walked into.

This page is where I keep the patterns I see most often across NZ tech hiring, especially when the role is important, hard to fill, or expensive to get wrong.

Book a 15-minute role diagnostic Try the Cost of Delay Calculator

This is not generic recruiter content.

This page is built from real hiring conversations, replacement briefs, failed ramps, search resets, and the awkward moments after someone starts when the team realises the problem is not as simple as they thought.

Sometimes the issue is the person.

A lot of the time, it is not.

It is the role shape. The stage of the company. The expectations sitting in different people’s heads. The manager capacity. The interview process testing confidence instead of work.

That is why this page exists. Not to give you fluffy hiring tips. To help you spot the problems that get expensive later.

If any of these feel familiar, the risk is probably already costing you money.

Start here. These are the first three things I’d want a CTO, founder, or hiring leader to read before opening a role or restarting a search.

Hiring Risk

You did not hire the wrong person. You hired into the wrong environment.

A lot of bad hires are not talent problems. They are stage, scope, expectation, and manager problems wearing talent language.

See why this happens →

Delivery

You added two engineers and delivery still got slower.

More headcount does not fix a messy system. Sometimes it just makes the drag more expensive and harder to hide.

Read the hidden cost →

Interview Signal

Your interview tested knowledge of the work, not the ability to do the work.

Great talkers pass process all the time. Practical signal gets missed because teams test fluency instead of execution.

See what gets missed in interview →

What this advice is based on

I do not sit in theory.

I sit closer to the aftermath.

The replacement brief after the “great hire” did not land.
The hiring manager saying, “I still don’t know how we missed it.”
The founder who thought they needed leadership when they still needed a builder.
The team that added people but never fixed the bottleneck underneath them.
The interview process that filtered for confidence, polish, and familiarity, then wondered why the work still stalled.

These are not roles you fill. They are decisions you live with.

15 minutes

A fast role diagnostic to help you pressure-test the brief before you search.

NZ context

Built around the reality of hiring in New Zealand, not generic overseas advice.

Real patterns

Drawn from actual searches, failed ramps, and replacement briefs.

1 next step

If something here feels familiar, book the diagnostic.

Who this is for

This page is for CTOs, CIOs, founders, delivery leaders, and hiring managers making important technical hires.

It is for teams where getting the hire wrong costs more than a fee.

It is not built for job seekers. It is not built for generic career advice. It is built for leaders trying to make better hiring decisions under pressure.

Before you spend money on search, make sure the role makes sense.

If the brief is fuzzy, the process is slow, or the team is not aligned on what good actually looks like, the search gets expensive fast.

That cost usually shows up later as delay, rework, frustration, or another hire. A second set of eyes on the role can save a lot of wasted motion.

Book a 15-minute role diagnostic