Senior QA Automation Engineer (Java) | Hybrid - #35385

As a Senior QA Automation Engineer (Java), 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.

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 (Java) to take ownership of quality assurance for their established software products, ensuring reliability and performance from development through to production.

This is a great opportunity for someone who enjoys shaping testing strategies, driving test automation, and improving software quality through a proactive, shift-left approach. You will play a key role in strengthening existing testing processes, working closely with developers, and leveraging AI tools to make testing more efficient and effective.

Duties and Responsibilities:

· Release Quality Across Environments

• 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 Across the Monolith and Services

• Build and maintain regression coverage across the monolith, the microservices and the front end, aimed at the customer journeys that matter most and the areas that break most often
• Follow the test pyramid, and judge coverage by what it would catch, not by a percentage

Automated Testing in the Pipeline

• Move repeated manual testing into automated suites that live with the product and run on every change

Performance and Load

• Prove the product holds up at real customer volumes
• Load test the screens and processes customers use most with JMeter or equivalent, watch how the application and database behave under that load, and compare the result with production monitoring in New Relic

 Integrations and Data

• Test the B2B integrations and data flows customers depend on, including cXML orders and invoices, ERP connections and data moving between platforms
• Write SQL against Oracle and SQL Server to set up test data and check what actually landed

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 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
• 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 / Qualifications:

• At least 5 years of solid experience testing Java-based web applications in a commercial product environment with live customers, including regression testing on a mature codebase and personal accountability for release readiness
• 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
• Proficiency in writing, maintaining, and executing automated test scripts using Java. Hands-on experience with Selenium WebDriver or Playwright for UI automation and REST Assured or Postman for API and integration testing
• Practical experience with performance testing tools such as JMeter or Gatling, and integrating automated test suites into CI/CD pipelines using Jenkins or Azure DevOps
• ·Hands-on experience writing SQL queries and validating data using Oracle and SQL Server. Experience testing XML-based and REST integrations, including cXML, and working across multiple application environments
• Experience using monitoring tools such as New Relic to investigate application behaviour, identify issues, and support defect analysis
• Hands-on use of AI tools in daily testing work, such as drafting test cases, generating test data or analysing failures, with a clear sense of where their output cannot be trusted
• ·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