Tester (Project Rewire)

As a Tester at Project Rewire, your main responsibilities will include creating and executing both functional and automated tests, developing test schedules and plans, and monitoring the quality of deliverables from your scrum team. You'll also engage with stakeholders to finalize user acceptance tests and review requirements with a testing perspective, ensuring that bugs and risks are addressed early in the development process.

To qualify for the Tester role at Project Rewire, candidates should have at least 5 years of experience in the field of testing, accompanied by a proven track record in test automation. Relevant certifications like TMAP, ISTQB, and/or CAT are essential, along with expertise in tools such as Playwright, Selenium, and Azure. Strong time management skills and a results-oriented mindset are also critical for success in this role.

A Tester at Project Rewire should be well-versed in various testing tools and software. Key tools include Playwright (Typescript), Selenium/SpecFlow (.NET/C#), Cypress, Swagger/Postman, and Browserstack. Familiarity with Microsoft Azure, particularly its boards, pipelines, and cloud applications, is also crucial to effectively manage and execute testing in the modern development environment.

The temporary team at Project Rewire focuses on building an improved digital claims handling process. This involves creating user-friendly digital claim funnels for various damage products while ensuring generic building blocks are established for accelerated service delivery after the initial claim funnel. Your contribution as a Tester will be vital in achieving these goals with a strong emphasis on quality.

In a Continuous Delivery/Continuous Integration environment at Project Rewire, a Tester contributes by collaborating with team members to ensure that testing is integrated seamlessly into the development process. This involves not just functional testing but also proactively identifying and addressing risks early on, thereby maintaining high-quality standards throughout each stage of development.

When asked about your experience with automated testing tools, highlight specific frameworks you've worked with, such as Selenium or Playwright. Discuss how you've implemented automated tests in past projects, any challenges you faced, and the impact your testing had on overall product quality.

To answer this, you can explain your approach to balancing quality with deadlines. Discuss techniques like risk-based testing, prioritizing critical features, and making use of automated testing to speed up the process. By emphasizing your time management and prioritization skills, you demonstrate your ability to adapt to fast-paced environments.

In your response, mention the key components you include in test plans such as objectives, scope, resources, schedule, and risk assessments. Share how you adapt your test plans to fit project needs and stakeholder requirements, which underlines your thoroughness and attention to detail.

Discuss your practice of integrating testing into the CI/CD pipeline, ensuring tests are run frequently and feedback is immediate. Mention techniques like test automation, continuous monitoring, and collaboration with development teams to rapidly resolve issues and maintain high software quality.

Highlight your communication skills by providing examples of how you've previously advocated for testing perspectives during requirement discussions. Explain how you involve both developers and stakeholders in test planning, ensuring that everyone is aligned on expectations and potential risks.

Explain the use of risk assessment techniques such as brainstorming sessions, analyzing previous projects, or utilizing tools to track issues. By showing that you take a proactive approach to risk management, you convey your commitment to delivering quality results.

Address common challenges like maintaining test scripts, ensuring they remain relevant as features change, and handling flaky tests. You can also mention your strategies for overcoming these challenges, showcasing your problem-solving capabilities.

Use the STAR method (Situation, Task, Action, Result) to describe the context of the bug discovery, your testing process, and the actions you took to document and communicate the issue. Highlighting how your attention to detail prevented major issues illustrates your value as a Tester.

Mention the various resources you engage with, such as online courses, communities, blogs, and webinars. Sharing example certifications or training shows your commitment to professional growth, reinforcing your dedication to being an effective Tester.

Discuss your involvement in UAT processes, including how you helped define acceptance criteria with stakeholders. Provide examples of how you've facilitated UAT sessions, gathered feedback, and acted upon it to enhance product quality, demonstrating your comprehensive understanding of the testing lifecycle.