Location:Hybrid – minimum of 1 day onsite per week at our client’s office in Alabang, subject to business and team requirements

Working hours / Job Type:

Monday to Friday, 3PM to 12AM Manila time with 8 core working hours inclusive of 1-hour break

Company Profile:

Our client is a well-established UK-based enterprise software provider with a growing physical presence in the Philippines, delivering innovative, cloud-based platform solutions to international businesses. Backed by strong market presence and continued technology investment, the organization is actively executing a major digital transformation to build a unified, highly scalable, and AI-enabled ecosystem. This initiative includes embedding advanced machine learning capabilities and intelligent analytics into its next-generation platform, offering candidates the opportunity to drive modern tech innovation within a stable, growing global organization.

As their team continues to grow, they are now looking for a Senior Quality Engineer to take ownership of quality assurance for their established software products, ensuring reliability and performance from development through to production.

Overall purpose and responsibilities of the role:

As a Senior Quality Engineer, you will own the quality assurance process for an established software product, ensuring it meets quality standards from requirements through to production. You will define testing strategies, assess release readiness, and drive the shift from manual to automated testing integrated into CI/CD pipelines, with a strong focus on regression, integration, API, end-to-end, and performance testing. Working closely with developers, you will promote a shift-left approach, identify risks early, and leverage AI tools to improve testing efficiency while ensuring the accuracy and reliability of AI-generated outputs.

Duties and Responsibilities:

Release Quality on a Live Product

·       Decide whether a release is fit to go, and back the decision with evidence

·       Plan the testing for each release around what changed and what it touches, including the customer specific configurations the product carries

·       Sign off against the acceptance criteria, and say plainly when something did not run or did not pass.       

Regression and Test Coverage

·       Build and maintain regression coverage around the journeys that matter most to customers and the areas that break most often

·       Follow the test pyramid, with many fast unit tests owned by the developers, fewer integration tests, and a small, reliable set of end-to-end tests

Automated Testing in the Pipeline

·       Move repeated manual testing into automated suites that live in the same repository as the product and run on every change

Requirements and Acceptance Criteria

·       Get involved before the build

·       Review requirements and designs, ask the questions that make them testable, and agree acceptance criteria with the product owner and the developers

Non-Functional Testing

·       Check that the product holds up, not only that it works

·       Test performance, load and endurance at realistic customer volumes, including peaks such as month-end and year-end, and find where the system starts to degrade

·       Confirm the product behaves predictably when a dependency, integration or third-party service fails, and that it recovers cleanly

·       Verify that customer data stays separated, and work with security colleagues on access control, authentication and vulnerability checks

·       Cover compatibility across supported browsers, devices, screen sizes and integration versions, and test accessibility against WCAG 2.2 AA using automated tools and assistive technology such as screen readers and keyboard-only navigation

·       Test upgrade and migration paths, including moves between hosting environments, as well as backup, restore and disaster recovery

·       For international customers, check localisation, currency and time-zone behaviour

·       Use production monitoring such as New Relic to compare what you tested with what customers actually experience, and feed those findings back into test coverage     

Defects and Root Cause

·       Write defect reports a developer can act on without a conversation

·       For anything that reaches production, trace it back to its origin, add the test that would have caught it, and change the condition that allowed it

·       Work with support and incident management so customer issues are reproduced quickly and confirmed fixed

Quality Metrics and Reporting

·       Track and report the measures that show whether quality is getting better or worse: escaped defects, defect ageing, automation coverage, pipeline pass rates and test cycle time

·       Draw the numbers from Azure DevOps and the pipeline rather than compiling them by hand, and present them so the team and leadership can act on them

·       Use the trends to decide where testing effort goes next, and never to score individuals

Working with AI and as One Team

·       Use AI tools to speed up test design, test data and failure analysis, and review what they produce for the mistakes they actually make, such as tests written to pass rather than to find a fault

·       Work alongside the developers as a peer, help them write better unit tests, and contribute to the shared QA standard so good practice spreads across teams

Requirements

Must-have Skills / Qualification:

·       At least 5 years of solid experience in software testing on a commercial product with live customers, including regression testing on a mature codebase and personal accountability for whether a release was fit to go

·       Strong test design and analytical judgement, with experience in risk-based test planning, exploratory testing, and identifying the most effective testing level to detect defects early

·       Hands-on experience in test automation, particularly API and integration testing, using Playwright, Selenium, or comparable browser automation tools

·       Proficiency in writing, maintaining, and executing automated test scripts using C#

·       Strong problem-solving and analytical skills

·       Comfortable taking ownership of a feature or problem from development through production

·       Strong communication and collaboration skills within a distributed engineering team

Advantageous or Nice-to-Have Skills/Experience:

·       Bachelor’s degree in Information Technology, Computer Science, Engineering or related

·       ISTQB Foundation or equivalent certifications

·       Experience testing software built with coding agents

Hands-on testing of applications hosted on Azure, SQL Server queries to set up and check test data, and monitoring tools such as New Relic or Application Insights to investigate behaviour