Sharing the recruitment process for the Marsh / Marsh McLennan Global Services Software Engineering role. The exact process can vary by campus, role and hiring batch, but this was the structure followed in my process.

DATED: 13th September
College: Tier 1.5
Fresher
on-Campus Drive
CTC: 15.4 (Joining bonus+TA+DA+ESOPS)

Overall Process

The selection process consisted of:

1. Round 1 – Online MCQ Assessment
2. Round 2 – Full-Stack Coding / Technical Assessment
3. Round 2.1 – Optional Coding/Technical Assessment
4. Final Interview Round

There is an important point regarding the second and third rounds:

If a third assessment is conducted, the better performance between Round 2 and Round 3 can be considered for the evaluation.

The cumulative evaluation includes the relevant assessment performance along with the ATS/resume-based score and Round 1 performance, after which shortlisted candidates move to the interview stage.

Round 1 – Online MCQ Assessment

The first stage was an online objective assessment.

The questions focused primarily on basic technical knowledge, aptitude and logical reasoning rather than advanced DSA.

Topics to prepare

• Programming fundamentals
• OOPs
• DBMS
• SQL
• Computer Networks
• Operating Systems
• Basic data structures
• Basic algorithms
• Logical reasoning
• Aptitude
• Pattern/series-based questions
• Basic output prediction

Based on candidate reports, the assessment can include logical aptitude, pattern recognition/missing-series questions and basic coding fundamentals.

For freshers, I would particularly recommend revising:

OOPs → DBMS/SQL → OS → CN → Programming fundamentals → Aptitude

Round 2 – Full-Stack Coding / Technical Assessment

The second stage was a hands-on technical/full-stack coding round.

This round is more practical than Round 1. Candidates should be prepared to actually write and explain working code rather than simply answer MCQs.

Depending on the role, preparation should cover:

Frontend

• HTML/CSS
• JavaScript
• React
• Components
• Props and state
• API integration
• Basic form handling
• Async/await
• HTTP methods
• Error handling

Backend

• REST APIs
• Node.js / Java / relevant backend language
• Authentication basics
• CRUD operations
• API validation
• Exception handling
• Database connectivity

Database

• SQL queries
• Joins
• GROUP BY / HAVING
• Subqueries
• Aggregations
• Normalization
• Primary/foreign keys
• Indexes
• Basic transactions

Coding

Expect problems around:

• Arrays
• Strings
• Hashing
• Searching
• Sorting
• Linked lists
• Basic recursion
• Basic trees
• Time and space complexity

The emphasis can vary significantly depending on the specific Software Engineering opening.

Round 2.1 – Optional Technical/Coding Round

A third technical/coding assessment may be conducted depending on the hiring process.

One important aspect of this process is that the third round is not necessarily an additional hurdle that simply gets added on top of Round 2.

The better performance between the applicable Round 2 and Round 2.1 assessments can be considered in the overall evaluation.

Therefore, if Round 2.1 is offered, it is worth treating it as another opportunity to demonstrate technical ability.

Preparation should be similar to Round 2:

• DSA
• Programming fundamentals
• Full-stack concepts
• SQL/DBMS
• OOP
• API development
• Debugging
• Problem solving

Shortlisting / Composite Evaluation

After the assessment stages, the candidate's overall performance is considered.

The evaluation is not based only on one coding question or one interview.

The process can take into account:

• ATS/resume-based score
• Round 1 MCQ performance
• Round 2 performance
• Round 2.1 performance, if conducted
• Overall technical performance

The relevant/better coding assessment result is considered where the optional third round applies.

Candidates who clear the required threshold are then moved to the interview stage.

Final Interview Round

This is where the process becomes much more discussion-oriented.

Based on recent Marsh McLennan candidate reports, technical interviews have included detailed discussion of the candidate's previous experience/projects, programming concepts and technologies mentioned on the resume. One August 2026 report describes a recruiter screening followed by two technical rounds, with questions around the candidate's framework, Java, OOP concepts and Selenium.

For fresher/software-engineering hiring, I would prepare the interview around the following areas.

1. Resume / Project Discussion

This is one of the most important areas.

Be prepared to explain every significant technology and project written on your resume.

Typical questions can include:

• Explain your project.
• What problem does it solve?
• Why did you choose this technology?
• Explain the architecture.
• What was your contribution?
• What challenges did you face?
• How did you debug the issue?
• Why did you choose SQL/NoSQL?
• How does the frontend communicate with the backend?
• How is authentication handled?
• How would you scale the application?
• What would you improve if you had more time?

A candidate report specifically mentions detailed discussion around the candidate's skills and projects, followed by Java/OOP and coding questions.

Do not put anything on your resume that you cannot explain technically.

2. Programming & DSA

The interview may include a coding/problem-solving component.

Topics worth preparing:

Easy–Medium DSA

• Arrays
• Strings
• HashMap/HashSet
• Two pointers
• Sliding window
• Stack
• Queue
• Linked list
• Binary search
• Sorting
• Trees
• Recursion

You should also be able to explain:

• Brute-force approach
• Optimized approach
• Time complexity
• Space complexity
• Edge cases

Candidate reports for Marsh McLennan have included basic coding such as counting vowels in a string and asking the candidate to explain the approach, pseudocode and complexity.

3. OOPs

This is particularly important.

Prepare:

• Class vs object
• Encapsulation
• Abstraction
• Inheritance
• Polymorphism
• Method overloading
• Method overriding
• Interface vs abstract class
• Constructor
• Access modifiers
• SOLID principles
• Composition vs inheritance

Be prepared for both theoretical and code-based questions.

4. Java / Programming Language Fundamentals

If Java is listed in the job description or on your resume, prepare:

• JVM/JDK/JRE
• String vs StringBuilder/StringBuffer
• Collections
• ArrayList vs LinkedList
• HashMap
• HashSet
• Exception handling
• Checked vs unchecked exceptions
• Interfaces
• Abstract classes
• Multithreading basics
• Garbage collection
• Streams/lambdas

Recent Marsh McLennan interview reporting specifically mentions Java and OOP concepts.

5. SQL & DBMS

For a Software Engineer/full-stack role, I would strongly recommend preparing:

INNER JOIN
LEFT JOIN
RIGHT JOIN
GROUP BY
HAVING
ORDER BY
Subqueries
CTEs
Window functions
Indexes
Normalization
ACID
Transactions
Primary/Foreign Keys

Typical interview questions can involve:

• Find the second/third highest salary.
• Find duplicate records.
• Explain different joins.
• Difference between WHERE and HAVING.
• What is an index?
• What happens internally when an SQL query executes?
• SQL vs NoSQL.
• Explain normalization.
• Explain ACID properties.

6. Full-Stack Concepts

Since the assessment is full-stack oriented, prepare the complete request flow:

Browser
   ↓
React / Frontend
   ↓
HTTP Request
   ↓
REST API
   ↓
Backend / Server
   ↓
Database
   ↓
Response
   ↓
Frontend

You should be able to explain what happens at every stage.

Also prepare:

• REST
• GET/POST/PUT/PATCH/DELETE
• HTTP status codes
• JWT
• Authentication vs authorization
• CORS
• Middleware
• API validation
• Error handling
• Database connection pooling
• Basic caching
• Deployment fundamentals

7. Behavioural / HR Questions

The final portion can move toward behavioural and managerial questions.

Prepare answers for:

• Tell me about yourself.
• Explain your strongest project.
• What was your biggest technical challenge?
• Tell me about a time you made a mistake.
• Tell me about a difficult problem you solved.
• How do you handle deadlines?
• How do you work in a team?
• Why Marsh McLennan?
• Why should we hire you?
• Where do you see yourself in the next few years?
• What are your strengths and weaknesses?

Keep these answers based on actual experiences, preferably using the STAR structure:

Situation → Task → Action → Result

What I Would Prepare for This Process

If I were preparing specifically for this hiring process, my priority order would be:

Tier 1 — Must Know

• OOP
• SQL
• DBMS
• Java/programming fundamentals
• Arrays & Strings
• HashMap/HashSet
• Basic React
• REST APIs
• Project explanation

Tier 2 — Important

• Linked List
• Stack/Queue
• Trees
• Searching/Sorting
• OS fundamentals
• Computer Networks
• Authentication/JWT
• HTTP
• Git

Tier 3 — Good to Know

• System design fundamentals
• Caching
• Load balancing
• Microservices
• Docker
• Cloud fundamentals
• CI/CD

Final Takeaway

The process appears to combine objective technical screening + hands-on coding/full-stack assessment + resume/technical interview.

The most important mistake to avoid is preparing only for LeetCode.

For this type of Marsh McLennan Software Engineering process, prepare across three dimensions:

1. Aptitude + CS fundamentals

2. Hands-on full-stack coding

3. Resume/project + technical interview

Recent candidate reports support this broader pattern: Marsh McLennan interviews have included project/experience discussions, Java/OOP, coding, logical reasoning and technology-specific questions, while current interview reporting also shows recruiter screening followed by technical rounds.

Because interview experiences vary by role and hiring batch, the exact questions and number of rounds should not be treated as fixed company-wide rules.