Start Date
Immediate
Expiry Date
29 Jan, 27
Salary
60000.0
Posted On
31 Oct, 26
Experience
5 year(s) or above
Remote Job
Yes
Telecommute
Yes
Sponsor Visa
No
Skills
Industry
Retail & E-Commerce
ABOUT THIS VACANCY
As a QA Engineer at Metafoor Software, you will work on BRIXXonline and VBSonline, two administrative real estate management systems used daily by real estate organizations, municipalities, and other organizations with complex real estate processes.
Processes such as invoicing, service charge settlements, and notice periods involve hundreds of combinations of settings. It is precisely there that errors occur that affect customers.
At our company, quality assurance is currently divided among developers who mainly enjoy building. That is no longer working well enough. Therefore, we are looking for someone who makes quality a profession.
You are the first QA Engineer in the team and are given the space to structurally establish testing, test scenarios, and test automation.
You get involved early, not just when something is finished. Together with the Product Owner and UX Designer, you attend refinements, think through scenarios that others overlook, and determine where the real risk lies.
WHAT ARE YOU GOING TO DO?
THE DEPARTMENT
You will join a compact development team where product, support, and implementation are closely linked. Communication lines are short, and your work is directly visible in the product and with our customers.
You are the first QA Engineer at Metafoor Software. Therefore, you do not inherit an existing test pipeline, but are given the freedom to set one up yourself: the approach, the scenarios, the automation, and the way the team works with it.
For knowledge of our core processes, you can rely on the Product Owner, support, and developers who know the system inside out.
A new product that we are building from the ground up serves as a proof of concept for this way of working, with QA and UX at the table from day one. We then apply that approach to the heaviest components of the existing system.
What we are ultimately aiming for is simple: fewer support tickets and fewer surprises for customers after a release.
YOUR BACKGROUND
ABOUT THIS VACANCY
As a QA Engineer at Metafoor Software, you will work on BRIXXonline and VBSonline, two administrative real estate management systems used daily by real estate organizations, municipalities, and other organizations with complex real estate processes.
Processes such as invoicing, service charge settlements, and notice periods involve hundreds of combinations of settings. It is precisely there that errors occur that affect customers.
At our company, quality assurance is currently divided among developers who mainly enjoy building. That is no longer working well enough. Therefore, we are looking for someone who makes quality a profession.
You are the first QA Engineer in the team and are given the space to structurally establish testing, test scenarios, and test automation.
You get involved early, not just when something is finished. Together with the Product Owner and UX Designer, you attend refinements, think through scenarios that others overlook, and determine where the real risk lies.
WHAT ARE YOU GOING TO DO?
THE DEPARTMENT
You will join a compact development team where product, support, and implementation are closely linked. Communication lines are short, and your work is directly visible in the product and with our customers.
You are the first QA Engineer at Metafoor Software. Therefore, you do not inherit an existing test pipeline, but are given the freedom to set one up yourself: the approach, the scenarios, the automation, and the way the team works with it.
For knowledge of our core processes, you can rely on the Product Owner, support, and developers who know the system inside out.
A new product that we are building from the ground up serves as a proof of concept for this way of working, with QA and UX at the table from day one. We then apply that approach to the heaviest components of the existing system.
What we are ultimately aiming for is simple: fewer support tickets and fewer surprises for customers after a release.
YOUR BACKGROUND