Online Form Test Assistant

HRS Talent Solutions; Timaru; Remote; NZD 62,000 - 66,000; Full time

Job summary

HRS Talent Solutions is seeking an Online Form Test Assistant to support our remote operations. The role focuses on testing web forms, documenting results, and reporting observations clearly to help improve user experiences.

You will follow a standard checklist, verify required fields, confirm successful submissions, and report issues with precise steps. Previous office admin or customer service experience is useful, and training will be provided.

Qualifications

• Experience in customer service or office administration is useful.
• Strong documentation and note-taking skills.
• Ability to follow checklists and provide precise observations.

Responsibilities

• Follow approved online form checklist with designated test data.
• Check required fields, submission and visible confirmation.
• Record page URL, steps and results with exact messages.
• Retest forms after fixes when requested.

Skills

Customer service

Documentation

Attention to detail

Remote work

Job description

Online Form Test Assistant

Office Administration | Online Form Testing | Remote
Full-time Pay: 62,400–65,520 per year

A contact form can look fine on the screen and still fail when someone tries to submit it. The Online Form Test Assistant follows a supplied test checklist for approved website forms, reports what happened, and verifies a correction when asked. This is remote website support at an introductory level. You will not write code, change live settings without permission, or inspect sensitive customer submissions outside the assigned environment.

Test what a visitor sees

A typical assignment may specify a form and a test record. You would open the page, complete the permitted fields with designated test information, submit it, and note whether the confirmation message appears. The checklist may ask you to check a required field or a mobile-width view. If the form rejects valid test data, record the exact field and message. If a notification does not arrive, report that observation rather than diagnosing the mail server.

The quality of the report matters. “Broken” is less useful than the page URL, date, browser, steps taken, and what appeared after submission. Avoid using a real customer's contact information in a test. If the team asks you to retest after a fix, use the same documented steps and record the new result. This is office administration applied to a digital workflow, with customer service in mind: a form failure can prevent a visitor from receiving help.

Test and report tasks

• Follow an approved online form checklist with designated test data.
• Check required fields, submission, and visible confirmation.
• Record the page URL and exact steps that produced a problem.
• Compare the result with the expected behaviour supplied by the site owner.
• Keep screenshots within the employer's designated tool.
• Retest a corrected form when requested.
• Refer technical fixes to the website team rather than changing code.

Customer service or office administration experience is useful because both develop careful documentation and empathy for a visitor's experience. Previous website employment is not required. The employer will teach its test process, forms, and reporting tool. You need patience for repeat checks and the ability to write observations without guessing at the technical cause.

A home office or other focused workspace is suitable. The hiring company will confirm which browsers and devices it needs checked.

A form may behave differently after an error. The checklist may ask you to leave a required field empty, see whether the correct message appears, then complete it and try again. Record whether the data already entered was preserved. If a successful submission shows a confirmation but the team cannot find the test record, report both observations separately. Do not assume the form reached the intended inbox merely because the page changed. A test should use a clearly marked address and reference so it is not mistaken for a real customer inquiry.

You may also compare the same form on a phone-sized screen and a desktop view. Note where a field becomes difficult to use or a button is hidden. The website owner will decide what needs fixing and when. Your report should describe the user-visible issue with enough detail that another person can reproduce it, not speculate about the underlying code.

This work relies on consistent test data and a reproducible record.

A form may appear to submit successfully while its confirmation email or internal notification goes to the wrong place. Test the whole approved path: page load, required fields, submission, visible confirmation and the expected routing evidence available to the tester. Use the designated test details, never a real customer's personal information. If the result fails only on a mobile screen or a particular browser, write down the conditions so the site owner can reproduce it. Report the observed behaviour rather than diagnosing code you have not seen or changing a live form on your own.