Moody's Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 69 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Moody's.
Moody's
Software Engineer
Mid Average Positive experience No offer 3 rounds
Interview process
Technical screen Take home Technical screen
Interview formats
Technical Coding
The whole interview process went on for about two months. After each interview stage, it took about a week or two to hear back about an update. In total, there were three rounds of interviews. This included a technical interview with a senior software engineer, a Hackerrank exam, and then another technical round with the VP and AVP.
Confirmed questions5 questions
- Could you answer some questions about .net?
- Tell me about your understanding of oops concepts.
- Do you have any questions related to sql?
Moody's
Software Engineer
Executive Average Negative experience No offer 4 rounds
Interview process
Recruiter call Technical screen Onsite Onsite
Interview formats
Technical Behavioral Coding
Started with a 30 min recruiter screen, then a 1 hour technical interview with the hiring manager who is a director. After that, I had a 1.5 hour behavioral and technical interview with 3 associate directors. The final interview was a 2 hour onsite with the VP and 2 directors. The technical questions were pretty straightforward, mainly LeetCode Easy-Medium. The final round was entirely resume-based and included a question on stochastic processes. Unfortunately, I was ghosted after the final interview.
Confirmed questions1 question
- Can you explain the differences between LinkedIn, Lists, and Arrays?
Moody's
Software Engineer
Entry Average Neutral experience No offer 3 rounds
Interview process
Recruiter call Technical screen Onsite Background check Offer
Interview formats
Behavioral Technical Coding System Design
So there were 3 rounds in total. The first one was 30 minutes with the hiring manager, mainly focused on culture fit. Then there was a technical round with 2 engineers. They asked some easy DSA and HLD questions. It was okay, although it got rescheduled twice. The final round was with a project manager and some senior management. This one was a bit strange; apparently, I was the first person to reach this stage, and they seemed quite unsure about whether they even wanted to hire someone. The rest of the team is located outside India, and the senior manager sounded very hesitant about hiring for the role. They mostly asked behavioral questions.
Confirmed questions2 questions
- Could you solve basic string DSA problems?
- How would you design Spotify?
Moody's Software Engineer Interview Questions
Quoted word for word from Moody's interview reports.
“What's a way to find and print duplicate elements within a list, using less than O(n) space and achieving O(n) time complexity?”
Read reports →“Can you explain how to run a PHP script using the command line?”
Read reports →“If you have a 3-gallon jug and a 5-gallon jug, how can you get exactly 4 gallons?”
Read reports →“What would be the output of this line of JS code?”
Read reports →“What is an abstract class, and can you provide an example of its usage?”
Read report →“Could you demonstrate an algorithmic solution for the Tower of Hanoi problem?”
Read report →“Can you explain why memory might become full even when it doesn't seem like a lot is being used?”
Read report →“Build a REST API; this would be better as a take home exercise instead of a live API that needs to make calls over the internet.”
Read report →“What are the basics of C# and .Net, and OOPS concepts?”
Read report →Formats, difficulty and experience
Across all 69 Moody's interview reports.