Morningstar software engineer candidates describe online tests or take-home coding, short technical conversations, behavioral rounds, and sometimes Java, SQL, or system design questions. Formats vary by team and level.
$115K
Avg. Base Comp
$135K
Avg. Total Comp
3-4 rounds
Typical Rounds
Not reported
Process Length
Morningstar software engineer candidates describe a process that varies by team and level, but it leans toward practical discussion over pure algorithm drilling. One candidate began with a manager phone screen and take-home coding problems, then sat a 2-3 hour panel that mostly walked through those submitted answers alongside resume and behavioral questions. Another reported an online test, a technical talk with the team lead and manager, an HR behavioral round, and a final technical manager round over about a week, ending in an offer.
Technical content differs by report. One candidate was asked about Java concurrency (executor services, thread pools, deadlock versus starvation), Spring beans and MVC flow, exception handling, and writing a singleton. An associate-level candidate reported a LeetCode medium, an OOP design assignment, and a SQL question on the third-highest salary. A senior .NET candidate reported writing an API that merged two calls, a code review round spotting bugs in existing code, and a rate limiter design question.
Behavioral prompts reported include why you want the role, your career story, a weakness, and a hard problem you solved. Several candidates also describe slow or missing communication after interviews, so follow up politely and keep applying elsewhere. For preparation, review the language and stack on your resume, practice explaining your own code and tradeoffs aloud, and rehearse concise behavioral stories.
Synthesized from 9 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 Morningstar process.
I got a referral that got my foot in the door, and the process moved pretty quickly from there. The first round was a one-way video where they asked general questions about why I wanted to work at Morningstar and what I knew about the company — nothing too intense, just getting a sense of my interest and fit. That fed into a series of four back-to-back behavioral interviews, each about thirty minutes, where they dug into my experience and how I approach problems. Those were the most exhausting part, honestly, just the repetition of telling similar stories from different angles.
The technical side came next. There was a LeetCode medium problem I had to solve, which tested algorithmic thinking under time pressure. Then they gave me a project-based assignment focused on OOP principles — they'd prepped a scenario and we discussed my approach to design and architecture. I remember one technical question about SQL that asked me to find the third-highest salary for managers, which was straightforward enough with a self-join or window functions. There was also a string problem where I had to count character frequencies in a mixed-case string like "AaDDBCbEe" and return the counts — simple enough but you have to be careful about case sensitivity. The rounds felt structured but a bit repetitive by the end. Overall, the experience was manageable and the interviewers seemed approachable, but I didn't move forward.
Prep tip from this candidate
Practice LeetCode medium difficulty problems and be ready to solve them under time pressure. For technical rounds, prepare OOP design questions where you discuss architecture decisions out loud, and refresh SQL specifically on window functions and self-joins for salary/ranking problems — those came up directly.
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 Morningstar
Design a secure, real-time, scalable portfolio management system with notifications and caching.
| Question | |
|---|---|
| Search Timeout | |
| SageMaker Deployment Architecture | |
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| Closest SAT Scores | |
| Employee Salaries | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Merge Sorted Lists | |
| String Shift | |
| Comments Histogram | |
| Top 5 Turnover Risk | |
| Like Tracker | |
| Find the First Non-Repeating Character in a String | |
| Bagging vs Boosting | |
| Total Spent on Products | |
| P-value to a Layman | |
| Maximum Profit | |
| Prime to N | |
| Cumulative Distribution | |
| Top 3 Users | |
| Over-Budget Projects | |
| Google Maps Improvement | |
| Hurdles In Data Projects | |
| Over 100 Dollars | |
| Minimum Change |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report different openings: a phone screen with an engineering manager, an early HR phone screen, or a one-way video about interest in Morningstar. Expect questions about motivation and background. The format likely depends on the team and level.
Several candidates describe an online assessment or coding problems done on their own before live interviews. One reported a C++ exercise and another a couple of take-home problems. Difficulty is reported from easy to medium, so practice explaining your solutions as well as writing them.
Reported technical rounds include a 2-3 hour panel that reviewed take-home answers, 30-minute coding and code review sessions, and conversations with the team lead and manager. Topics candidates mention include Java, Spring, SQL, OOP design, debugging, and rate limiter design. Questions vary by role and interviewer.
Candidates report behavioral questions about past projects, a difficult problem, motivation for the role, and weaknesses. Some had several back-to-back 30-minute behavioral interviews. Prepare distinct stories so repeated questions do not feel identical.
Some candidates report a final technical manager round, and one had a separate system design round on a later day. Outcomes were mixed: one candidate reported an offer within about a week, while others reported rejection or long silence after interviews.
