1. What is a QA Engineer at Marsh?
As a QA Engineer at Marsh, you serve as a critical gatekeeper for the software solutions that support global insurance, risk management, and insurance broking. Your primary objective is to ensure the reliability, security, and performance of complex platforms that facilitate high-stakes data transactions for clients worldwide. In an industry where accuracy is paramount, your work directly impacts the integrity of the firm’s digital infrastructure.
This role requires a blend of rigorous technical testing and a pragmatic understanding of business requirements. You will collaborate closely with software developers, product managers, and operations teams to identify defects, streamline testing workflows, and advocate for high-quality software standards. It is an environment that values consistency and clear communication, making it an ideal space for engineers who take pride in meticulous problem-solving and systematic process improvement.
2. Common Interview Questions
The interview process at Marsh focuses on verifying your technical competency while ensuring your approach aligns with the team’s operational standards. While questions vary by team and region, the following categories represent the typical focus areas you will encounter.
Technical Proficiency and Testing Fundamentals
These questions assess your foundational knowledge of QA methodologies, testing lifecycles, and your ability to apply these concepts in a professional environment.
- Explain your process for creating a test plan for a new feature.
- What is the difference between regression testing and re-testing?
- How do you handle a situation where a bug is found late in the development cycle?
- Describe your experience with automated testing tools versus manual testing.
- How do you ensure that edge cases are covered during your test design phase?
Behavioral and Situational Scenarios
These questions aim to understand how you handle pressure, work within a team, and manage professional disagreements regarding software quality.
- Tell me about a time you had a conflict with a developer regarding a bug. How did you resolve it?
- How do you prioritize your tasks when you have multiple features to test under a tight deadline?
- Describe a time you identified a critical issue that others missed. What was the impact?
- How do you communicate technical risks to non-technical stakeholders?




