MAERSK logo

MAERSK Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 82 interview experiences · FREE TO READ

2.7 Rounds average
Average Typical difficulty
53.7% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at MAERSK.

Showing 3 of 82
MAERSK logo
MAERSK

Software Engineer

Engineering · a year ago

Mid Difficult Negative experience No offer 2 rounds
Interview process
Recruiter call Phone screen Technical screen
Interview formats
Coding Behavioral

I'm sharing this because the silence after multiple interview rounds is frustrating. I interviewed for the Software Engineer role at Maersk and finished my second round in June. It's been nearly a month, with no updates, no replies to my emails, and no callbacks even after following up multiple times. Candidates spend time, effort, and trust in the process. At the very least, we expect basic communication—an update, a closure, or anything. This is about the experience companies provide to every candidate they interact with, not just me. I truly hope Maersk considers this.

Confirmed questions1 question
  • Could you solve LeetCode programming problems involving lists and dictionaries?
MAERSK logo
MAERSK

Software Engineer

Engineering · a year ago

Entry Average Positive experience No offer 5 rounds
Interview process
Recruiter call Technical screen Onsite Panel Background check Offer
Interview formats
Behavioral Technical Coding

It was good. The process kicks off with your resume being shared, then there's a screening and shortlisting. Once scheduled, you do your research and prep. It usually starts with a quick intro to check your communication skills. Then come the questions and your answers, where body language is important. You might have technical and behavioral rounds to test problem-solving, coding, creativity, and logic. You might get feedback, ask questions, and stay confident. This is often followed by an HR round, negotiation, and more assessment, sometimes in front of a panel. After everything, a decision is made, and if you're in, you get an offer, accept it, and start onboarding.

Confirmed questions0 questions

No confirmed questions were included in this interview report.

MAERSK logo
MAERSK

Senior Software Engineer

Engineering · more than a year ago

Senior Average Positive experience Accept offer 2 rounds
Interview process
Technical screen Onsite
Interview formats
Technical Behavioral

The interview was quite different from the usual Q&A or live coding. While those were part of it, the focus was heavily on my past experience and projects. Authenticity in my experience was key to passing. It wasn't about answering every question perfectly; the interviewer was more interested in my confidence and verifying if I had genuinely worked on the concepts I claimed to know.

Confirmed questions4 questions
  • Can you explain how you would store multipart data within a database?
  • Tell me about your experience with global exception handlers.
  • Describe a situation where you had to mitigate a performance issue. What steps did you take?

MAERSK Software Engineer Interview Questions

Quoted word for word from MAERSK interview reports.

Can you explain what a partition key is in Azure Cosmos DB?

Read reports

Can you convert 6005 to 6555 by replacing zeros with fives?

Read reports

What .Net Core library collection type would you pick for efficient sorting?

Read reports

Can you find two numbers in an array that add up to a given target sum?

Read report

Could you explain the difference between encapsulation and abstraction in Object-Oriented Programming (OOPs)?

Read report

Can you explain the difference between Web API, Web services, and WCF?

Read report

Could you implement an API that sorts numbers asynchronously, without requiring the client to wait for the result within the scope of a request?

Read report

Could you implement a function that serves a hand of cards from a deck, including the code for cards, the deck itself, and shuffling?

Read report

Formats, difficulty and experience

Across all 82 MAERSK interview reports.

Interview formats

Technical 40.1%
Behavioral 29.4%
Coding 21.8%
System Design 6.1%
Presentation 2%

Interview difficulty

Easy 15.9%
Average 70.7%
Difficult 13.4%

Candidate experience

Positive 53.7%
Neutral 13.4%
Negative 32.9%