Quality Engineer III

As a Quality Engineer III at Arch US MI Services, Inc., your primary responsibilities will include testing software product changes and maintaining quality assurance standards. You’ll collaborate with internal and external stakeholders to ensure products meet desired quality benchmarks. You'll also develop test plans using Cypress, automate UI tests, create functional and regression tests with ReadyAPI, and keep stakeholders informed about testing status.

To qualify for the Quality Engineer III position at Arch US MI Services, Inc., candidates should possess a Bachelor’s degree in Computer Science, Engineering, or a related field along with at least 9 years of experience in software testing. Essential experience includes functional testing of Services, API, UI, and backend testing, as well as proficiency in using tools like ReadyAPI, Zephyr, or HP ALM. Agile experience and automation skills are also critical for success in this role.

A successful Quality Engineer III at Arch US MI Services, Inc. should be proficient in using a variety of testing tools. Key tools include Cypress for UI testing, ReadyAPI for creating functional and regression tests, and Zephyr or HP ALM for test management. Familiarity with SQL for database queries and CI/CD tools such as Jenkins will also enhance your effectiveness in this role.

The Quality Engineer III role at Arch US MI Services, Inc. offers a hybrid work model. This means you will be working in the office two days a week and remotely for three days, as long as you're within a normal commuting distance from the office in Raleigh, NC. This setup allows for flexibility in your work schedule while ensuring collaboration with your team.

At Arch US MI Services, Inc., Quality Engineer IIIs can expect a supportive environment for professional development. We encourage continuous learning and provide opportunities to stay current with industry trends and technologies. Regular feedback and access to training resources are part of our commitment to help employees grow, enabling them to achieve their fullest potential.

In your response, focus on specific projects where you've executed functional testing. Include the tools you've used, such as ReadyAPI or other testing frameworks. Share your methodologies, how you ensure comprehensive coverage, and any challenges you've overcome during the testing process.

Explain your approach to automation, including the tools you've utilized such as Cypress. Discuss how you've automated UI test cases, integrated them into the development cycle, and the benefits this brought to your team. Be specific about your experiences and successes with automating tests.

Describe your familiarity with Agile principles, such as Scrum or Kanban, and how you've applied them in software testing. Give examples of how you've collaborated with developers, participated in Agile ceremonies, and contributed to continuous improvement in the testing process.

Discuss your experience with defect tracking tools like Zephyr or HP ALM. Explain your process for logging defects, communicating their severity to stakeholders, and ensuring they're retested and documented appropriately once resolved.

Highlight your commitment to continuous learning. Mention specific resources you access, such as online courses, forums, and industry publications. Share how staying updated has influenced your work as a Quality Engineer and enabled you to implement best practices in your projects.

Select a challenging bug from your past experiences. Explain the steps you took to identify, analyze, and escalate the issue. Describe the collaboration with your team to find a resolution and how this experience improved your problem-solving skills.

Share your approach to prioritization, which may involve assessing risk, product impact, and urgency. Describe specific strategies you use, such as backlog refinement, to ensure that critical testing tasks are completed efficiently.

Discuss the importance of clear and effective communication with both technical and non-technical stakeholders. Provide examples of how you’ve facilitated discussions, led testing status meetings, and ensured everyone is on the same page regarding quality expectations.

Emphasize your strategies for balancing speed and quality, such as effective planning, risk-based testing, and collaboration with team members. Share specific instances where you've successfully met deadlines without compromising on product quality.

Discuss which metrics you track—such as defect density, test case pass rate, or automated test coverage. Explain how these metrics guide your testing efforts and provide insight into the quality of the software being delivered.