Quality Assurance Manager

Company Overview

Markmonitor, now part of the Markmonitor Group following its acquisition by Com Laude (a global corporate registrar) in January 2026, is a premier provider of enterprise domain portfolio management, brand protection, domain strategy, registration, and anti-abuse solutions. Serving thousands of the world’s leading brands and managing extensive domain assets for high-profile clients across 80+ countries, the company operates in a highly international environment with regional headquarters in Boise (US), London (UK), Tokyo (Japan), and additional offices/support in multiple countries.

This global footprint involves cross-border transactions, digital services delivery, intellectual property management, and compliance with diverse regulatory and tax regimes worldwide.

The QA Engineer role is dedicated to testing software before it’s put into production service. This is a role with broad responsibilities, all contributing to the quality of the Engineering software features delivered to customers. This includes building a testing framework and collection of tests that run at various parts of the software development lifecycle. The QA Engineer is an integral part of quality from the requirements phase to production service deployment — including defect management as issues are reported in both pre and post-production deployments.

• Test Analysis:
  Review stories and perform test analysis (including data and environmental factors).
• Test planning:
  Define good test conditions and select among testing techniques to ensure proper test coverage.
• Requirements interpretation:
  Understand the product usage to help define expected outcomes from business requirements.
• Technical discussion:
  Drive discussion around the technical aspects of the product to identify the best times to run tests.
• Data planning:
  Define data needed to run within system tests and be aware of system touch points and data transfer between systems.
• Test planning & consensus:
  Create test plans and gather consensus for project and incremental enhancements.
• Collaboration:
  
  Collaborate with Engineering and business stakeholders as part of analyzing testing needs.
• Testing scope:
  Ensure both positive and negative testing is included in analysis.

• Test Execution:
  Write manual tests or automated scripts and define suites of tests for specific purposes (e.g., smoke, regression, feature-based).
• Quality standards:
  Ensure test code is peer reviewed and follows the same standards as any other software in terms of maintainability and scalability.
• Automation health:
  Ensure automated tests are running smoothly.
• Executable suites:
  Create executable test suites that are easy to debug and where result reports are clear and accessible, e.g., in pipelines.
• Bug reporting:
  Raise bugs with sufficient data and debug information for others to easily take the next steps.
• Bug scope:
  Raise bugs relating to deliverables not matching business requirements; cross-system functionality issues; usability/performance issues; and security concerns.
• Environments:
  Define what environments are needed to run particular suites of tests.

• Quality & Risk:
  Understand client usage of software to help define bug severity and participate in team triage as required.
• Process improvement:
  Understand the software delivery process and look for ways to improve QA activities such as automation and test strategies.
• Feedback loops:
  Initiate proper feedback loops relating to user experience and issues, looking for trends or underlying issues.

• Teamwork:
  Drive continuous improvement and actively discuss quality implications of integrations in team meetings.
• Knowledge sharing:
  Take responsibility for learning and share findings or lessons learned.
• Coaching:
  
  Provide coaching on test techniques, testability, and test setup.
• Automation governance:
  Ensure test automation runs regularly, feedback loops are defined, and results are reviewed.
• Code collaboration:
  Participates in code reviews.

• Minimum of 3 years of experience in writing and executing software tests.
• Experience with troubleshooting software issues.
• Good communication skills.
• Demonstrable…