You're probably staring at an old CV right now. It still says “results-driven professional”, it lists every role you've had since the Android Ice Cream Sandwich era, and it somehow manages to feel both too long and too vague.
That's normal. For people in tech, cv writing new zealand is awkward because most advice out there was written for the general workforce, not for founders, engineers, growth leads, product people, or SaaS operators. A Kiwi tech CV has to do two jobs at once. It has to read cleanly for software, and it has to make sense to a human who wants proof you can ship useful work without turning your CV into a boast-fest.
That tension matters more in New Zealand than people expect. You can't lean on flashy design. You can't ramble. You can't assume the reader will connect your stack to commercial value on your behalf. You've got to do that work on the page.
A New Zealand CV has its own temperament. It isn't timid, but it is restrained. You're not trying to sound like the loudest person in the room. You're trying to sound credible, organised, and worth a conversation.
That catches out a lot of people from startup land. Founders and early hires are used to pitching, hustling, selling the dream. Fair enough. But on a CV, that tone can backfire. Kiwi hiring managers usually respond better to grounded confidence than chest-beating. Show the outcome. Skip the theatre.
This is the first cultural clue. New Zealand employers expect a two-page CV maximum, and CVs that go beyond that are “far less likely to be reviewed by the recruiter” according to guidance on NZ CV standards from Smart Write.
That tells you something important. In this market, restraint reads as judgement. If you can't decide what matters, the recruiter assumes you may not be great at prioritising in the job either.
Practical rule: If your CV needs three or four pages to “tell the full story”, it probably means you haven't edited hard enough.
For startup people, that can sting a bit. Startups produce messy careers. You've worn six hats, fixed support tickets, closed enterprise deals, written SQL, hired contractors, and rebuilt onboarding because nobody else would. Real work. Useful work. But your CV still has to compress that into signal, not noise.
There's also a social rhythm to New Zealand hiring. People often call it tall poppy syndrome, but on a CV it's less philosophical than that. It means inflated language tends to sound off.
A few examples:
| Weak wording | Better NZ-style wording |
|---|---|
| Visionary leader disrupting markets | Led product and go-to-market work for an early-stage SaaS team |
| World-class software engineer | Software engineer with experience shipping customer-facing features |
| Dynamic thought leader | Product operator with experience across roadmap, launch, and customer feedback |
The second version still shows value. It just sounds believable.
That same logic applies to achievement bullets. “Spearheaded digital transformation initiatives” says almost nothing. “Rebuilt onboarding flow after churn feedback from sales and support” sounds like someone who has done the job.
When I screen CVs for startups, I'm looking for people who can get to the point. Not robots. Not corporate wallpaper. Just people who know what changed because they were there.
That's especially true if you're applying to Auckland software firms, product teams, or venture-backed operators who move quickly. If you want a feel for the kind of businesses hiring across the local ecosystem, this directory of information technology companies in Auckland is a useful scan. Different firms, same pattern. They want clear thinking.
So the unspoken rule is simple. Be modest in tone, sharp in detail, and ruthless with space. A strong NZ CV doesn't shout. It lands.
A founder sends me a CV for a senior engineer. Strong background, real product experience, good companies. The file opens with a two-column template, icons instead of headings, skills hidden in sidebars, and contact details sitting in the header. By the time it lands in an ATS and then in a recruiter inbox, half the useful detail is gone.
That happens more than people think, especially with startup candidates who are trying to make a CV look polished instead of readable. In New Zealand tech hiring, readable wins.
Over 90% of medium-to-large New Zealand employers and virtually all recruitment agencies use Applicant Tracking Systems, according to CV Experts' discussion of ATS use in New Zealand. If your CV is hard for a system to parse, your experience can get flattened into gibberish before a hiring manager ever sees it.
For tech founders, developers, and SaaS operators, this is the trade-off. Fancy design can look sharp in a PDF. Plain formatting gets through systems cleanly and lets your actual work do the selling.
Use standard section names and keep them obvious:
A simple Word or Google Docs layout usually does the job better than a designed template. Black text, readable font, normal spacing. If you have a portfolio, GitHub, product write-up, or founder bio, link it. Don't build the whole CV like a landing page.
ATS-friendly formatting is not complicated. It is mostly about removing friction.
This matters even more in startup and SaaS hiring because your background is often messy in a good way. You may have worn product, ops, support, and growth hats in one role. Good formatting helps that story stay legible instead of looking vague or inflated.
If you want an outside view from a tech hiring platform, Underdog.io's resume guide is useful because it reflects how product and engineering teams scan applications.
ATS software matches terms. Human readers judge whether those terms make sense in context.
So if the role asks for TypeScript, AWS, stakeholder management, B2B SaaS, or onboarding optimisation, use those exact terms where they are true. Don't swap them for softer synonyms. Don't dump them into a giant skills block either.
A better approach is to put the right terms in three places: your summary, your key competencies, and your experience bullets. That gives the system enough signal and gives the recruiter proof. For product, growth, engineering, and revenue roles, the same logic behind keyword research for NZ hiring and search contexts applies here too. Use the language employers already search for.
One example:
The second version is easier for both software and humans to read.
I still see these all the time:
For Kiwi tech roles, none of that helps. Hiring managers want clean structure, clear chronology, and enough context to understand what you built, owned, improved, or shipped.
A good NZ tech CV is not designed to impress at a glance. It is designed to survive software, then make a busy recruiter keep reading.
Most tech CVs fall over in the same place. They list tools, stacks, and platforms as if the names alone do the selling.
They don't.
“React, Node, PostgreSQL, Docker, AWS.” Fine. Useful. But what did you change with them? Did you improve reliability? Ship a feature customers had been begging for? Clean up a reporting mess that sales had been nursing in spreadsheets for months? That's the part recruiters care about.
This is the gap. Existing NZ CV guides are broad, useful, and fine for many roles, but they offer zero tech-specific guidance on how to position GitHub, portfolios, side projects, startup experience, or technical impact. That leaves developers and founders doing a lot of guesswork.
The fix is simple in theory and harder in practice. Translate technical action into business meaning.
Try this pattern:
| Instead of this | Write this |
|---|---|
| Built internal tools in Python | Built internal Python tools used by ops and support teams |
| Managed AWS infrastructure | Maintained AWS environment for production workloads |
| Worked on onboarding flow | Shipped onboarding changes based on user friction and support feedback |
| Used SQL for reporting | Wrote SQL queries to support reporting for product or commercial decisions |
No invented numbers. No puffery. Just action plus context.
A technical skills section still matters. Put it in. Keep it clean. Group tools sensibly so it doesn't read like the world's driest shopping list.
For example:
That works because it's scannable. But it should never carry the whole burden. Actual persuasion happens inside the role bullets.
A hiring manager doesn't buy “Kubernetes experience”. They buy what you made more stable, faster, simpler, or easier to support.
Here are a few rewrites that tend to land better.
Developer examples
Weak: Responsible for frontend development using React
Better: Built and maintained React frontend features for the customer-facing product
Weak: Worked with APIs
Better: Integrated third-party APIs into the product and supported the handover to production use
Founder examples
Weak: Founded a SaaS startup
Better: Founded and ran an early-stage SaaS product across product, customer discovery, and go-to-market work
Weak: Managed all aspects of the business
Better: Led product decisions, customer conversations, hiring, and operational setup during the early build stage
Ops or growth examples
Weak: Ran lifecycle campaigns
Better: Built and managed lifecycle email journeys in tools such as HubSpot or Customer.io
Weak: Owned analytics
Better: Maintained reporting used by product and commercial teams to review funnel behaviour and campaign performance
This matters more in tech than generic CV guides admit.
If a side project shows code quality, product taste, commercial initiative, or domain depth, include it. Briefly. If your GitHub is active and relevant, link it near your contact details or under a short “Projects” or “Professional Links” section. Don't bury it on page two under hobbies.
A few sensible calls:
And yes, failed startup work can still help you. In fact, some of the best operator CVs I see come from people whose startup didn't work but who learned sales, product judgement, customer research, and delivery under pressure. That's not failure in a hiring context. That's reps.
A hiring manager in a Wellington SaaS company opens your CV between stand-up and a customer call. You have about 20 seconds to make them think, “Yes, this person has done the kind of work we need.” Generic language kills that reaction fast.
Here's a fictional example based on the kind of CV summary I see all the time from product people:
Product Manager with extensive experience in cross-functional collaboration, stakeholder engagement, roadmap ownership, and driving innovation across multiple product lines. Passionate about customer success and delivering business value in dynamic environments.
Every line is familiar. That's the problem. It reads like borrowed language, not lived experience.
Kiwi tech hiring managers, especially in startups and SaaS, look for signals of judgment, scope, and operating style. The weak version hides all three.
It's too abstract. “Cross-functional collaboration” could mean anything from leading a product squad to sitting in weekly update meetings.
It's too broad. “Multiple product lines” sounds senior, but tells me nothing about stage, complexity, customer type, or whether the person can work in an under-resourced NZ team where everyone does a bit of everything.
It also avoids the parts that make startup candidates interesting. Messy delivery. Customer contact. Trade-offs. Shipping with imperfect information.
Here's the same candidate, rewritten for a real reader:
Product manager with experience in B2B SaaS teams, working across roadmap planning, customer feedback, and delivery with design and engineering. Strong at turning input from users, sales, and support into clear priorities and scoped work. Comfortable in lean teams where product means discovery, writing tickets, release support, and checking what actually changed after launch.
That version gives shape to the work. It sounds like someone who has operated inside a real product team, not someone reciting job ad language.
A lot of NZ CVs fall apart under the summary. The title sounds fine, then the experience section drops into vague, low-value bullets.
Weak bullets:
Stronger bullets:
The difference is simple. Strong bullets show how the work happened.
That matters more in New Zealand tech than many generic CV guides admit. Hiring managers here often recruit for adaptable operators, not neat specialists. Founders want to know whether you can handle ambiguity, make sensible calls, and contribute outside a narrow lane. Developers, product people, and early-stage operators need to translate startup experience into plain evidence. That's the gap this guide is built to address.
Read each bullet and ask:
If the line could belong to anyone, rewrite it.
For candidates in product or design, local role expectations also shape how your CV is read. This user experience designer overview is a useful reference for the way NZ employers often describe UX and product-related capability in practical terms.
One last point. Don't waste space on a large referee section here. As noted earlier, that information usually sits outside the main selling job of the CV.
And once your CV is sharp, make sure LinkedIn tells the same story. LinkedIn career advice for professionals is a useful reference if your profile still reads like a vague personal brand exercise instead of a clear hiring case.
A sharp CV paired with a neglected LinkedIn profile creates friction. Recruiters notice that stuff straight away.
The problem usually isn't that LinkedIn is empty. It's that it tells a different story. Your CV says “product operator in B2B SaaS”. Your LinkedIn headline says “visionary leader | growth hacker | future of work enthusiast”. That mismatch makes people wonder which version is real.
Your headline should echo the same positioning as your CV summary. Not word for word, but close enough that the reader gets one coherent impression.
For example, if your CV frames you as a software engineer with strong customer-facing product experience, your LinkedIn should support that. Then use the About section to add more texture. In this section, a slightly more conversational tone helps. You can mention what kinds of teams you enjoy, what problems you like solving, and what kind of role you're after.
A practical resource on this side of the job search is LinkedIn career advice for professionals. It's useful for tightening the profile around a clear career story rather than treating LinkedIn like a static online CV.
A short cover letter can help, especially in smaller NZ tech teams where context matters.
Don't repeat your CV. Point to the overlap between your background and the company's actual situation. If they're hiring after a product reset, mention your experience working through ambiguity. If they're growing from founder-led sales into a more repeatable motion, speak to the handover points between product, customer, and commercial teams.
The CV proves you can do the work. The cover letter shows you understand this company's version of the work.
That combination is much stronger than sending one polished document and hoping the rest of your profile somehow catches up later.
A senior engineer applies for a Head of Product role at a Wellington SaaS company. The experience is there. They have shipped product, worked with customers, and led delivery through messy startup phases. But the CV still reads like an engineering task list. A good CV writer fixes that gap. A bad one just makes it prettier.
Hiring a professional CV writer makes sense when the problem is positioning, not effort. If you can explain your work clearly, tailor for each role, and cut old material without clinging to it, do it yourself. If your background is strong but the story is muddy, outside help can save time and improve the result.
It tends to be worth paying for help in a few specific cases:
Here is the difference in practice.
Before: “Led cross-functional teams to deliver key product outcomes in a fast-paced environment.”
After: “Owned the product roadmap for a B2B SaaS platform used by enterprise customers in NZ and Australia. Set priorities across engineering, customer success, and sales. Cut onboarding friction by fixing the handoff between implementation and product, which improved activation and reduced support churn.”
That second version gives a hiring manager something to work with. It shows context, scope, who you worked with, and what changed because you were there. That is the standard you should expect from paid help.
The problem is that many CV writers can write polished English but cannot read a tech career properly. They miss the trade-offs between platform work and product work. They flatten startup experience into generic leadership claims. They do not know that in smaller NZ companies, “Founder” can mean product lead, seller, recruiter, and customer support all at once. If they do not understand those realities, they cannot turn your background into a CV that gets traction.
Check four things before hiring one:
One more blunt point. A writer cannot invent substance. If your achievements are thin, the CV will still be thin. What they can do is help you frame real work in a way Kiwi hiring managers will read quickly and trust.
If you hire one, stay involved. The final version still needs to sound like you in an interview.
If you're building a team, reshaping your own operator profile, or trying to understand how the NZ tech market presents itself, NZ Apps is worth keeping on your radar. It covers the regional app, SaaS, and software ecosystem with practical resources for founders, operators, and technical decision-makers who need local context, not generic career fluff.
Add your NZ or Australian app or tech company to the NZ Apps directory and get discovered by founders and operators across the region.
Get ListedReach tech decision-makers across New Zealand and Australia. Sponsored and dofollow editorial links, permanent featured listings, and sponsored articles on a DA30+ .co.nz domain.
See Options