Quality Assurance Manager

Markmonitor Inc.•Meridian, ID

2d•Hybrid

About The Position

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.

Requirements

Minimum of 3 years of experience in writing and executing software tests.
Experience with troubleshooting software issues.
Good communication skills.
Demonstrable proficiency in software engineering techniques and methodologies.
Work with team members to help plan, estimate, and develop solutions to unique technical problems.
Work independently with little or no direction.
Quickly raise issues or concerns to the team and drive discussion end to end.
Accountable for themselves and success of the team.
Facilitate trust and collaboration by contributing and soliciting feedback.
Proactively communicate with peers and offer constructive feedback, raise risks, concerns, and roadblocks.
A minimum of 3 years of relevant work experience.
Demonstrable proficiency in Java, Selenium, Playwright and Cucumber or related languages.
Fundamental understanding of core Agile principles and frameworks (Kanban, Scrum, etc.).
Good interpersonal skills with the drive to learn new technologies.
Good analytical and problem-solving skills.
Good aptitude to quickly learn new processes, skills, technology, and tools.
Ability to self-evaluate and quickly adapt to change.
Extensive experience working with cloud-based applications and cloud tools, preferably AWS.
Good verbal and written communication skills in English.
Capable of working tasks with medium-high risk/complexity/challenge and under pressure.
Demonstrable leadership, strong work ethic, proactive thinking, maturity, and creative capabilities.

Responsibilities

Review stories and perform test analysis (including data and environmental factors).
Define good test conditions and be able to pick between a variety of testing techniques to ensure proper test coverage.
Understand the product usage to help define expected outcomes from business requirements.
Drive discussion around the technical aspects of the product to be able to identify the best times to run tests.
Define data needed to run within system tests and be aware of system touch points and data transfer between systems.
Create test plans and gather consensus from the team — for both project and incremental enhancements.
Collaborate with Engineering as well as the business stakeholders as part of analyzing testing needs.
Ensure both positive and negative testing is included in analysis.
Write manual tests or automated scripts and define suites of tests for specific purposes (e.g., smoke, regression, feature based).
Ensure test code is peer reviewed and follows the same standards as any other software in terms of being maintainable, scalable, etc.
Ensure automated tests are running smoothly.
Create executable test suites that are easy to debug and result reports are clear and accessible, e.g., in pipelines.
Raise bugs with sufficient data and debug information for others to easily take the next steps.
Raise bugs relating to: deliverables not matching business requirements; cross-system functionality adversely affected; usability/performance issues; and security being compromised.
Define what environments are needed to run particular suites of tests.
Understand client usage of software to help define bug severity and take part in team triage as required.
Understand the team software delivery process and look for ways that the team can improve by focusing on QA activities such as automation strategy and test strategy.
Initiate proper feedback loops relating to user experience and issues, looking for trends or underlying issues.
Drive continuous improvement and be vocal in team meetings to discuss quality implications of integrations.
Take responsibility for learning and share findings or lessons learned.
Provide coaching to the team relating to test techniques, testability, test setup, etc.
Ensure any test automation is run regularly, proper feedback loops are defined, and results are reviewed.
Participates in code reviews.