NZ Interview Process
A detailed guide to the New Zealand tech interview pipeline, CV format, and how it differs from Chinese interviews.
NZ Interview Process
The New Zealand tech interview process is generally less intense than US Big Tech interviews but more structured than many Chinese companies. Understanding the typical pipeline, preparing your CV in the right format, and knowing the cultural expectations will significantly improve your success rate.
CV Format
Your CV (resume) is the first impression. NZ has specific conventions that differ from both Chinese and American formats.
NZ CV Essentials
- Length: 2-3 pages. Not one page (US style) and not four or more pages
- No photo: Do not include a photo. This is a strong convention in NZ
- No personal details: Do not include date of birth, marital status, nationality, or gender
- No Chinese name in characters: Use your English name or romanized name only
- Format: Clean, professional, no fancy graphics. PDF format preferred
CV Structure
Header
- Full name (English)
- Location (city, or "Relocating to Auckland")
- Email, phone, LinkedIn URL
- GitHub/portfolio URL if relevant
Professional Summary (3-4 lines) A brief summary of your experience, key skills, and what you are looking for. Tailor this for each application.
Example:
Senior Software Engineer with 8 years of experience building distributed systems in Go and Java. Led teams of 5-8 engineers at [Company]. Looking for senior or staff engineering roles in Auckland where I can contribute to product-focused teams.
Technical Skills List your key technologies, organized by category (Languages, Frameworks, Cloud, Tools). Only list technologies you are genuinely comfortable being interviewed on.
Work Experience (most recent first) For each role:
- Company name, your title, dates (month/year)
- 1-2 lines describing the company if it is not well known in NZ
- 3-5 bullet points of achievements, not responsibilities
- Use metrics where possible: "Reduced API latency by 40%", "Led migration serving 2M daily users"
Education
- Degree, university name, graduation year
- No need to list GPA unless it is exceptional
Other (optional)
- Open source contributions
- Conference talks
- Relevant certifications (AWS, etc.)
Common CV Mistakes by Chinese Applicants
- Listing every technology ever used — Be selective. A long list of 30+ technologies looks unfocused
- Describing responsibilities instead of achievements — "Responsible for backend development" tells the reader nothing. "Designed and built the payment processing service handling $50M in annual transactions" tells a story
- Including a photo or personal information — This immediately flags your CV as non-local
- Using Chinese company descriptions — Briefly explain what the company does if it is not known internationally
- Too much focus on education — NZ values work experience more than academic credentials for experienced engineers
The Interview Pipeline
A typical NZ tech interview process has 4-6 stages and takes 2-4 weeks from first contact to offer.
Stage 1: Application and Initial Screen
What happens: You apply through a job board, company website, or recruiter. If your CV matches, a recruiter or HR person will reach out for an initial chat.
Format: 15-30 minute phone or video call
What they assess:
- Basic communication in English
- Motivation for the role and for moving to NZ
- High-level experience match
- Visa situation (they need to know if they will sponsor)
- Salary expectations
Tips:
- Be ready to explain why you want to work in NZ (not just why you want to leave China)
- Have a clear answer about your visa status
- Give a salary range, not a single number
- Ask about the team, the work, and next steps
Stage 2: Technical Screen
What happens: A more technical conversation, usually with an engineering team lead or senior engineer.
Format: 45-60 minutes video call. May include a light coding exercise or technical questions.
What they assess:
- Depth of technical knowledge
- Problem-solving approach
- How you explain technical concepts
- Experience relevant to the role
Tips:
- Practice explaining technical decisions in English
- Be prepared to discuss your most complex technical projects
- It is okay to say "I don't know" — NZ interviewers respect honesty
- Ask thoughtful questions about the tech stack and engineering practices
Stage 3: Coding Assessment
Format varies by company:
Take-home assignment (most common in NZ):
- Typically 2-4 hours of work
- Build a small application or solve a problem
- Deadline is usually 3-7 days
- You then discuss your solution in a follow-up call
Live coding (less common):
- 45-60 minutes of coding on a shared editor
- Usually a practical problem, not algorithmic puzzles
- Think building an API endpoint or implementing a feature, not LeetCode
What they assess:
- Code quality and structure
- Testing approach
- How you handle requirements and edge cases
- Your ability to make pragmatic trade-offs
Tips:
- For take-homes: Write clean code with tests. Include a README explaining your decisions and trade-offs
- For live coding: Think aloud. NZ interviewers care about your process as much as the result
- Ask clarifying questions before diving in
- NZ interviews rarely require heavy algorithm or data structure knowledge (unlike FAANG)
Stage 4: System Design (Senior+ Only)
What happens: For senior and above roles, you will be asked to design a system or discuss architecture.
Format: 45-60 minutes, whiteboard or virtual whiteboard
What they assess:
- Ability to think about systems at scale (appropriate to NZ scale, not Google scale)
- Trade-off analysis
- Communication of technical decisions
- Consideration of non-functional requirements (reliability, monitoring, cost)
Tips:
- NZ system design questions tend to be more practical and less theoretical than US FAANG interviews
- Focus on pragmatic solutions, not over-engineering
- Discuss monitoring, deployment, and operational concerns — NZ teams value engineers who think about the full lifecycle
- It is fine to reference your real-world experience as examples
Stage 5: Culture Fit / Values Interview
What happens: A conversation focused on how you work with others, handle conflict, and align with company values.
Format: 30-45 minutes with a hiring manager or team members
What they assess:
- Communication style — can you express yourself clearly?
- Collaboration — how do you work in a team?
- Conflict resolution — how do you handle disagreements?
- Growth mindset — how do you learn and improve?
- Alignment with company values
Tips:
- Prepare specific stories about teamwork, conflict, and learning from mistakes
- Use the STAR format (Situation, Task, Action, Result) for behavioral questions
- Be authentic — NZ culture values genuineness over polished performances
- Show that you can give and receive feedback constructively
- Demonstrate interest in the team and company, not just the technology
Stage 6: Reference Check
This is critical in NZ. Unlike China where reference checks are often perfunctory, NZ employers genuinely call your references and ask detailed questions.
What they ask references:
- What was it like working with this person?
- What are their strengths and areas for development?
- How do they handle pressure and conflict?
- Would you hire them again?
How to prepare:
- Choose 2-3 references who know your work well and will speak positively about you
- Contact your references in advance to let them know they may be called
- If your references speak limited English, let the employer know — some will accommodate this
- Former managers are the strongest references. Colleagues are acceptable if managers are not available
- NZ references are typically from the last 2-3 roles, not from 10 years ago
Stage 7: Offer
What happens: If all stages go well, you receive a verbal offer followed by a written offer letter.
Typical offer includes:
- Base salary
- KiwiSaver employer contribution rate
- Leave entitlements
- Benefits (health insurance, professional development, etc.)
- Start date
- Probation period (usually 3-6 months)
- Notice period (usually 4 weeks after probation)
Tips:
- It is normal to take 2-5 business days to consider an offer
- Negotiate respectfully — see the Salary Benchmarks section for guidance
- Ask for the offer in writing before accepting verbally
- If you have competing offers, it is acceptable to mention this (without being aggressive)
How NZ Interviews Differ from Chinese Interviews
| Aspect | China | New Zealand |
|---|---|---|
| Algorithm focus | High (LeetCode-style common) | Low (practical coding preferred) |
| Take-home assignments | Less common | Very common |
| Culture fit interview | Rare as formal stage | Almost always included |
| Reference checks | Often formality | Genuinely conducted |
| CV format | Can include photo, personal info | No photo, no personal info |
| Salary discussion | Often late in process | Usually in first call |
| Number of rounds | Can be 6-8+ at big companies | Usually 4-6 |
| Timeline | Can take months | Usually 2-4 weeks |
| Communication style | Can be indirect | Direct but friendly |
| Post-interview feedback | Rare | Common (many companies share feedback) |
Preparing Your English for Interviews
Technical Communication
The biggest challenge for many Chinese engineers is not technical knowledge but expressing that knowledge clearly in English. Practice:
- Explaining your current project to a non-technical person in 2 minutes
- Describing a technical decision you made and why
- Talking through code as you write it
- Asking clarifying questions naturally
Common Phrases That Help
- "Let me think about that for a moment" — Perfectly acceptable to pause
- "Could you clarify what you mean by...?" — Shows engagement
- "In my experience at [Company], we approached this by..." — Grounds your answer in reality
- "That's a great question. I haven't encountered that specific scenario, but here's how I'd approach it..." — Honest and constructive
- "What does the team's current approach look like?" — Shows you think collaboratively
Practice Resources
- Practice technical discussions with friends or language partners
- Record yourself explaining technical topics and listen back
- Join English-language tech communities and participate in discussions
- Consider mock interviews with NZ-based engineers or interview coaches
After the Interview
Following Up
Send a brief thank-you email within 24 hours of each interview stage. This is not mandatory in NZ but is appreciated and keeps you visible.
Example:
Hi [Name], thanks for taking the time to chat today. I enjoyed learning about [specific topic discussed]. I'm excited about the opportunity and look forward to the next steps. Best regards, [Your name]
Handling Rejection
Rejection is normal and not personal. If you receive a rejection:
- Thank them for their time and ask if they can share any feedback
- Many NZ companies will provide constructive feedback — this is valuable
- Stay in touch. The NZ market is small, and people move between companies. Today's rejection may lead to tomorrow's opportunity
Managing Multiple Processes
If you are interviewing with multiple companies (which you should be), communicate timelines openly. It is acceptable to say:
"I'm also in the process with another company and expect to have a decision by [date]. I want to make sure I can give your opportunity proper consideration."
NZ companies generally respect this and may accelerate their process if they are interested in you.