Software Testing for New Zealand Companies: Overlap and Privacy

A New Zealand company can run offshore QA from Bangladesh, but the live window is narrow: Dhaka (UTC+6) is 6 hours behind New Zealand in standard time and 7 in daylight saving, so a 9-to-6 day shares about 3 hours in NZST and 2 in NZDT, in your late afternoon. That makes the async handoff model, not live calls, the engine of the work.

This guide is for New Zealand founders, CTOs and QA leads. RAITHub is a QA and software studio in Dhaka, with no New Zealand office, delivering in English only, and is not SOC 2 or ISO 27001 certified. Read it as engineering and hiring guidance. Legal and data-protection points are general information; confirm them with a qualified New Zealand adviser.

How many working hours do New Zealand and Dhaka share?

About 3 in NZ standard time and 2 in daylight saving, in your late afternoon. Dhaka keeps UTC+6 with no daylight saving; New Zealand moves to NZDT roughly from late September to early April, which widens the gap. With both sides on a 9:00 to 18:00 day:

New Zealand time	Dhaka time (no DST)	What usually happens
09:00	03:00 (NZST) / 02:00 (NZDT)	Your morning; Dhaka is still overnight
15:00–18:00 (NZST)	09:00–12:00	The ~3 shared hours: stand-up, demo, live bug triage
16:00–18:00 (NZDT)	10:00–12:00	~2 shared hours during NZ daylight saving
NZ morning and midday	Dhaka overnight	Asynchronous; a written handoff is ready before you start

The overlap is your late afternoon, the Dhaka morning. It is narrow, so the engagement runs mostly async: you brief and review in your afternoon, testing runs through the Dhaka day, and a written handoff lands by your next morning. For a wider-window neighbour see QA testing company Australia; for the model itself see offshore QA testing services.

How does the async handoff model carry a 2 to 3 hour window?

A written daily handoff does the work a long overlap would otherwise do. Because the window is thin, the discipline matters more than for Australia or the Gulf:

• A written handoff every Dhaka working day: what was tested, what passed, what failed with steps to reproduce, and what is blocked waiting on you.
• Bugs in your tracker, not in chat, so nothing depends on being online at the same time.
• Clear priorities set in your afternoon overlap, so the Dhaka day runs without waiting on an answer.
• Tests in your CI, so results are visible to you whenever you look, not read out on a call.

The narrow overlap is a genuine trade-off: if your work needs same-time collaboration for most of the day, this is not the right fit. If most of QA can run from a clear brief and a written handoff, the window is enough.

What does the NZ Privacy Act expect before data goes overseas?

The Privacy Act 2020, through Information Privacy Principle 12, restricts disclosing personal information to an overseas recipient unless the recipient is subject to comparable safeguards, usually by binding them contractually to protections comparable to the Act (Office of the Privacy Commissioner: IPP 12). For QA, the cleanest way to meet that is usually to avoid the disclosure entirely:

• Test against synthetic data, not copies of real customers, so no personal information goes overseas.
• Keep production data in your own account, with testers deploying into it rather than hosting anything.
• Bind the recipient by contract to comparable safeguards, as IPP 12 contemplates.
• Sign a DPA defining the testers' obligations and your instructions.

RAITHub makes no Privacy Act "compliance" claim, and no vendor can take on your agency obligations. What it does is sign DPAs, follow your controls, and design testing so personal information stays in your environment. This is general information; confirm your position with a qualified New Zealand adviser and the Office of the Privacy Commissioner.

How big is the cost gap for a New Zealand buyer?

Wide, and mostly in the rate. One 2026 QA outsourcing guide puts manual testing at $80 to $150 or more an hour in North America and $60 to $160 in Western Europe, against $8 to $55 in India and Southeast Asia, with automation 20 to 50% higher in every region (QA Madness 2026 rates). Freelance marketplaces sit lower: Upwork lists a median of $35 an hour for QA engineers (Upwork).

Option	Market rate (2026)	Overlap with your NZ day
NZ or Australian agency	Comparable to Western Europe rates	Full to partial
Freelancer or crowdtesting	Upwork median $35/hr for QA engineers	Varies, knowledge leaves each time
Offshore managed QA (Bangladesh)	$8 to $55/hr band region; quoted per scope	3 hours NZST, 2 NZDT, plus async

Those are market figures, not RAITHub prices; RAITHub publishes no rates. A low rate times more hours or more rework is not a saving, so compare fixed quotes with scope and deliverables visible. See QA as a service pricing and in-house QA vs outsourced QA.

Where should the tests live?

In your repository, running in your CI, with bugs in your tracker. With a narrow overlap this matters even more: if the automated suite lives on the vendor's machines, you cannot see results on your own schedule, and you lose the suite when the contract ends. See QA gates for offshore teams and the test pyramid for SaaS.

Why RAITHub for QA in New Zealand?

• An async-first model built for a thin window, with a written handoff every Dhaka working day and 2 to 3 live hours in your late afternoon.
• A managed service, not seats. RAITHub manages its own testers. It does not offer staff augmentation.
• Tests and IP you keep. Automated tests and CI configuration go in your repository, with IP assigned to you and an NDA as standard; DPAs are signed where personal information is involved.
• Specialist breadth from one provider: manual and exploratory testing with UAT support, mobile testing on real iOS and Android devices, web application security testing against OWASP guidance, WCAG 2.2 accessibility audits, and automation, API and performance testing.
• Counted suites as proof. Sundor Skin runs 530+ automated tests. TheSkinProof, the founder's own venture rather than a client, runs 750+.

When a New Zealand company should not hire RAITHub for QA

• When live, same-time collaboration for most of your working day is essential. The 2 to 3 hour window is the main limit for New Zealand.
• When a customer or framework requires a SOC 2 or ISO 27001 certified vendor, or an accredited penetration test report. RAITHub holds neither certification and does OWASP-based testing, not certified pentests.
• When you need a legal accessibility certificate. A WCAG 2.2 audit reports issues and fixes but does not certify legal compliance; confirm with your adviser.
• When you want to manage the testers yourself. That is staff augmentation, which RAITHub does not offer.

How RAITHub would test this

• Scope: the journeys and roles that matter, the browsers and devices, and the test types across manual and exploratory, security and automation, API and performance.
• Rhythm: priorities set in your late-afternoon overlap, a written handoff every Dhaka working day, bugs in your tracker, results visible in your CI.
• Model: a monthly QA plan, a one-off audit or a dedicated team RAITHub manages and bills monthly.
• Contract: IP assignment, NDA, and a DPA where personal information is involved, designed so it stays in your own account.

Next step: a free 15-minute technical audit, then a written fixed quote. For the full service, see QA as a service. Ready? Ask for a QA plan or dedicated team quote.

Frequently asked questions

How many hours does a New Zealand team share with Dhaka?

About 3 in NZ standard time and 2 during daylight saving, in your late afternoon, with both sides on a 9:00 to 18:00 day. Dhaka keeps UTC+6 all year, so the gap widens when New Zealand moves to NZDT.

Can offshore QA work with only 2 to 3 shared hours?

Yes, if it runs async-first: a clear brief in your afternoon overlap, a written handoff every Dhaka working day, bugs in your tracker and tests in your CI. If your work needs same-time collaboration most of the day, the thin window is a genuine limit.

What does the NZ Privacy Act expect before data goes overseas?

IPP 12 restricts disclosing personal information to an overseas recipient unless they are bound to comparable safeguards. The cleanest answer for QA is to test against synthetic data so nothing is disclosed, and to keep production data in your own account. Confirm with a New Zealand adviser.

Is offshore QA cheaper than hiring in New Zealand?

On rates, clearly: Western manual QA runs $60 to $160 an hour or more, while offshore manual QA starts far lower. The total saving depends on hours and rework, so compare fixed quotes with the scope visible.

Will we keep the automated tests?

Yes, if they live in your repository and run in your CI from the start. RAITHub commits tests and CI configuration to your codebase and assigns the IP to you. Tests kept on a vendor's machines disappear when the contract does.

Does RAITHub have a New Zealand office?

No. RAITHub is based in Dhaka, Bangladesh, works with New Zealand clients remotely in English, and has no New Zealand office. It is an offshore partner, not a nearshore one.