What to expect in the Moody's Software Engineer interview: resume-driven technical questions, string and backtracking coding problems, and system design, based on three candidate reports with different outcomes.
$133K
Avg. Base Comp
$160K
Avg. Total Comp
2-5 rounds
Typical Rounds
Not reported
Process Length
Three candidates describe the Moody's Software Engineer interview, and their experiences differ, so prepare for a technical process rather than a fixed script.
One candidate, who accepted an offer, says the questions started from the projects and technologies on their resume and then branched into system design, database concepts and how programming languages differ. They found it helpful to explain the tradeoffs behind their choices rather than just naming tools.
A second candidate, who did not receive an offer, had a recruiter chat followed by a coding interview. It ran in a web text editor with a language menu and run button. They were given two string-processing questions, the second of which involved backtracking. They report that multiple approaches were valid, so practice more than one solution and be ready to talk through tradeoffs. They also report that the interviewer ended the session earlier than the stated 90 minutes, so keep partial solutions readable at every stage.
A third candidate, who also did not receive an offer, describes five technical rounds: two coding rounds that seemed to reward clean, complete code over optimization, a hiring manager conversation that touched on compensation, and two system design rounds.
Two of the three reports mention slow or unclear communication after the interviews. Ask your recruiter about the number of rounds and the timeline early, and keep following up.
Synthesized from 3 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Moody's process.
I went through Moody's interview process for a software engineer role and ended up accepting an offer. The technical questions were tied closely to my resume, and they branched out from there into broader topics. I was asked about system design concepts, database concepts, and how specific programming languages differ from one another, so I found it useful to explain the tradeoffs behind the choices I'd made rather than just naming the tools I'd used. I don't have a clear picture of how many rounds there were or how long each one ran, so I'd confirm that with your recruiter. If I had to point to one thing, it's to be ready to go into real depth on every project and technology you list, because the questions kept returning to that material.
Prep tip from this candidate
Be ready to explain the projects and technologies on your resume in technical depth, since questions started there. Also review core database concepts, system design basics, and how the programming languages you know differ from each other.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Moody's
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Employee Salaries | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Closest SAT Scores | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Find the Missing Number | |
| Maximum Profit | |
| Bagging vs Boosting | |
| String Shift | |
| Prime to N | |
| Comments Histogram | |
| Top 5 Turnover Risk | |
| Like Tracker | |
| Find the First Non-Repeating Character in a String | |
| Size of Joins | |
| Total Spent on Products | |
| Google Maps Improvement | |
| P-value to a Layman | |
| Rectangle Overlap | |
| Cumulative Distribution | |
| Top 3 Users | |
| Over-Budget Projects | |
| Slacking Employees Salaries | |
| Hurdles In Data Projects | |
| Sum to N | |
| Minimum Change |
Synthesized from candidate reports. Individual experiences may vary.
One candidate reports a recruiter chat that was friendly and quick to schedule before the technical interview. Another describes a friendly recruiter throughout. Candidates may want to confirm the number of rounds and the timeline at this stage, since one report had no clear picture of round count.
One candidate reports a coding interview in a web text editor with two string-processing questions, the second involving backtracking, with several valid approaches. Another found the first two coding rounds fairly straightforward, with emphasis on clean, working code. Practice readable solutions and be ready to explain alternatives.
One candidate who accepted an offer reports that technical questions began with resume projects and technologies, then moved into database concepts, system design basics and differences between programming languages. Prepare to explain the reasoning and tradeoffs behind each project, not only the tools used.
One candidate describes a five-round technical process, with a hiring manager round that touched on compensation, followed by two system design rounds. This is a single report, so the order and presence of these rounds may differ for other candidates. Ask your recruiter what to expect.
