Career Prep — Grad Level — Resync Bootcamp

Q: Q1. Should I mention bootcamp practice pages on my CV?

Yes. Frame them as "manual testing projects." Describe what you tested, what you found, and what tools you used. It is real, structured practice—treat it that way.

Q: Q2. What is the most important thing to include in a portfolio?

Your thinking process. Results matter, but employers want to see how you approach problems. Include why you prioritised certain tests, how you decided severity, and what you learned.

Q: Q3. Is ISTQB CTFL worth getting in New Zealand?

Often yes. Many NZ employers list it as desirable or required, especially government and large corporate roles. If you are studying for it, mention that on your CV even before you sit the exam.

1 The Hook

Meet Jordan. Six months ago they were working in hospitality in Auckland, unsure how to break into tech. They completed this bootcamp, treated every practice page like a real project, and wrote up their findings in a simple Google Doc. At their interview for a junior QA role at a Wellington SaaS company, the hiring manager asked about their "experience."

Jordan opened their laptop and showed the portfolio. "I found 6 planted defects across 10 practice pages, wrote 15 test cases for a rental booking site, and used browser DevTools to inspect form behaviour." The manager leaned forward. "That's real experience," they said. Jordan started the following Monday.

Your bootcamp work is real work. You just need to frame it right.

2 Your QA CV

You have no paid testing experience yet. That's fine. Everyone starts somewhere. What you do have is structured practice, documented findings, and a growing toolkit. Here's how to present it.

Section	What to Write
Projects	Manual Testing Projects — Resync Bootcamp Practiced structured testing on 10 realistic web pages simulating NZ business scenarios (retail, healthcare booking, government portal). Documented findings in consistent bug reports using a standard template.r>
Skills	Smoke testing, visual review, bug reporting, test case writing, browser DevTools, basic HTML/CSS inspection, keyboard navigation testing, accessibility awareness (axe DevTools).
Tools	Chrome/Firefox DevTools, Google Docs/Sheets, axe DevTools, basic GitHub familiarity.

NZ tip: If you are studying for ISTQB CTFL, mention it under "Professional Development." Many NZ employers recognise the cert, even if you are still preparing. It shows intent and seriousness.

Keep your CV to one page. Use plain language. Avoid buzzwords like "synergy" or "passionate self-starter." Let your project work speak for itself.

3 The Portfolio

A portfolio beats a CV every time. It proves you can do the work. You don't need a fancy website. A well-organised Google Doc or Notion page is enough. Include these three pieces:

Defect discovery summary "I found 6 planted defects across 10 practice pages, including typos, broken links, and inconsistent data. Each bug was documented with steps to reproduce, expected vs actual behaviour, and severity rating."
Test case sample "Wrote 15 test cases for an NZ rental booking site login flow, covering valid credentials, invalid passwords, empty fields, and session persistence. Organised using a clear pass/fail format."
Accessibility notes "Identified accessibility issues using axe DevTools and manual keyboard navigation. Flagged missing form labels, low colour contrast, and non-focusable interactive elements."

The Golden Rule

Show your thinking, not just your results.

Employers hire testers who can explain how they approach a problem. Include a short paragraph on each project explaining what you tested first, what you prioritised, and what you learned.

4 Common Interview Questions

These five questions come up in almost every junior QA interview in NZ. Practise your answers out loud. Use the model answers as a starting point, then make them your own.

1. "Tell me about a bug you found."

Model answer: "On Practice Page 05, an NZ event booking form, the date picker allowed past dates to be selected. I found it by trying to book an event for yesterday. The expected behaviour was blocking or greying out past dates. I documented it with steps, a screenshot, and severity 'Medium' because it could cause user confusion and bad data."

2. "What's the difference between testing and QA?"

Model answer: "Testing is the activity of finding defects. QA is the broader practice of preventing defects by improving processes. As a tester I find bugs. As someone interested in QA, I also think about why bugs happen and how the team could catch them earlier."

3. "How do you prioritise what to test?"

Model answer: "I start with risk. What do users do most often? What would cost the business money if it broke? I smoke-test the critical paths first. Then I go deeper into high-traffic areas. Low-risk edge cases come last. If time is short, I make sure the happy path works before anything else."

4. "What's your approach when you disagree with a developer about whether something is a bug?"

Model answer: "I check the requirements first. If it's ambiguous, I gather evidence: screenshots, behaviour on other sites, accessibility guidelines. Then I have a calm conversation with the developer, presenting the user impact. If we still disagree, I raise it with the product owner or QA lead. The goal is the right outcome, not being right."

5. "Why do you want to work in QA?"

Model answer: "I enjoy the detective work. I like understanding how software works, finding the edge cases others miss, and advocating for the user. QA lets me combine curiosity with structure. Every bug I find is a real person who won't have a bad experience. That matters to me."

5 NZ-Specific Advice

New Zealand's tech market has its own rhythms. Understanding them gives you an edge over candidates who treat every market the same.

✅ Government & AoG

Many NZ government agencies hire through All-of-Government (AoG) panel suppliers. Large consultancies like TechServNZ, Assurity, and Catalyst IT hold these contracts. Getting in as a junior through a panel supplier is a common path into public sector QA.

✅ Local Recruiters

NZ has several specialist tech recruiters. Build relationships with them. They often know about junior roles before they are advertised. Be honest about your level—good recruiters will guide you.

✅ Meetup Groups

Test Professionals Network (TPN) and WeTest NZ run regular events in Auckland and Wellington. Attending shows commitment. You will learn what local employers actually care about, and you might meet someone who is hiring.

✅ Common Expectations

NZ employers often look for: ISTQB Foundation cert (not always required but helpful), Agile/Scrum familiarity (mention if you have any), and independence (they want juniors who can self-manage and ask good questions).

One more thing: NZ teams value humility and teamwork. In interviews, share examples of collaborating, receiving feedback, and learning from mistakes. Technical skill gets you the interview. Character gets you the job.

6 Self-Check

Click each question to reveal the answer.

Q1. Should I mention bootcamp practice pages on my CV?

Yes. Frame them as "manual testing projects." Describe what you tested, what you found, and what tools you used. It is real, structured practice—treat it that way.

Q2. What is the most important thing to include in a portfolio?

Your thinking process. Results matter, but employers want to see how you approach problems. Include why you prioritised certain tests, how you decided severity, and what you learned.

Q3. Is ISTQB CTFL worth getting in New Zealand?

Often yes. Many NZ employers list it as desirable or required, especially government and large corporate roles. If you are studying for it, mention that on your CV even before you sit the exam.