Marsh Solutions Architect interview questions & guide 2026

Interviewers at Marsh look for depth of knowledge and the ability to articulate "why" behind your technical choices. The following questions are representative of the patterns you will encounter during your assessment.

System Design & Architecture

These questions test your ability to build robust, scalable, and secure systems while managing real-world trade-offs.

• Explain the difference between microservices and containerized architectures.
• How would you design an Active-Active strategy in the cloud to ensure high availability?

Preparation for Marsh requires a balance of technical rigor and business acumen. You should be prepared to defend your design choices, not just describe them.

Technical Competency – You must demonstrate mastery over cloud-native design principles and API standards. Ensure you can articulate the benefits and drawbacks of various architectural patterns, especially regarding performance and cost.

Executive Communication – You will often interact with stakeholders who are not engineers. Practice distilling complex technical constraints into clear business impacts, focusing on how your architecture supports the bottom line.

Strategic Problem Solving – When presented with a scenario, always start by clarifying constraints. Interviewers want to see how you weigh competing priorities like latency, cost, and maintainability.

The interview process at Marsh is designed to test both your technical architecture skills and your ability to function in a collaborative, consulting-heavy environment. You can expect a sequence that includes an initial screening with a recruiter or hiring manager to establish baseline expectations, followed by a series of technical deep-dives.

The process is rigorous and expects candidates to be prepared for both high-level system design and low-level technical specifics. Because the role is customer-facing, you should be prepared for role-play scenarios that test how you handle client requirements and stakeholder pressure. Expect the tone to be direct and professional, with a heavy emphasis on your ability to justify your technical decisions under scrutiny.

This visual timeline illustrates the typical progression from initial screening to final technical evaluation. You should use this to pace your preparation, ensuring you have enough time to review both your architectural fundamentals and your behavioral stories before the later-stage deep-dives.

System Design & Cost/Latency Constraints

You will be judged on your ability to design systems that are not only functional but also efficient.

Be ready to go over:

• Cost optimization – How to select the right cloud resources to balance performance and budget.
• Latency reduction – Strategies for caching, CDN usage, and efficient API design.

As a Solutions Architect, you are the primary technical owner of your assigned projects. You will spend your day evaluating existing infrastructure, designing new modules for the MMB Health suite, and providing guidance to engineering teams on implementation best practices.

Your role involves significant cross-functional collaboration. You will work closely with product managers to understand the roadmap and with operations teams to ensure that your designs are maintainable and secure. You aren't just designing for today; you are building for the future of Marsh, ensuring that the systems you architect remain flexible enough to adapt to changing insurance regulations and market demands.

A competitive candidate for Marsh possesses a blend of deep technical experience and the ability to influence others.

• Must-have skills – Expert knowledge of cloud-native architecture (AWS/Azure/GCP), RESTful API design, and security protocols (OIDC/OAuth). You must have a strong background in containerization and microservices.
• Soft skills – Proven ability to communicate with executive stakeholders, lead technical discussions, and mentor junior staff.
• Nice-to-have skills – Experience in the insurance or health-consulting sector, knowledge of legacy-to-cloud migration patterns, and familiarity with automated CI/CD pipelines.

Q: How long should I spend preparing for the system design round? A: Dedicate at least 30% of your prep time to system design. Focus on drawing out architectures on a whiteboard or digital tool, ensuring you can explain the trade-offs of your choices.

Q: Is the technical interview purely coding? A: No. While you may be asked about implementation details, the role focuses on performance tuning and architectural logic rather than algorithmic, LeetCode-style coding challenges.

Q: What is the culture like for architects at Marsh? A: The culture values collaboration and professional maturity. You are expected to be an owner of your designs while remaining open to feedback from engineering and product teams.

Q: What if I don't have experience with a specific cloud provider? A: Focus on the architectural principles—load balancing, database sharding, caching, and security. These concepts are transferable, and demonstrating a strong grasp of the "why" is more important than memorizing specific service names.

• Own your diagrams: Be prepared to walk through a diagram from a past project in detail. Be ready to explain why you chose a specific database or why you opted for a particular service-to-service communication pattern.
• Speak in trade-offs: Never present a solution as "perfect." Always acknowledge the trade-offs (e.g., "This design provides high consistency but introduces a slight latency penalty").
• Prepare for ambiguity: In the customer role-play, ask clarifying questions early. Don't assume the requirements; verify them.

The Solutions Architect role at Marsh is a unique opportunity to shape the technical future of a global leader in professional services. By mastering the balance between technical precision and clear executive communication, you will position yourself as a candidate who can solve complex problems while driving business value.

Your preparation should focus on articulating the "why" behind your designs, practicing your ability to distill complexity for stakeholders, and staying sharp on core system design principles. For further insights, practice questions, and strategic resources to guide your journey, you can explore additional interview preparation materials on Dataford.

The module above provides a window into the compensation expectations for this role. Use this data to benchmark your expectations and understand the total compensation package, which typically includes base salary and potentially performance-based incentives for senior-level architectural positions.