Msci Software Engineer interview typically runs 2 rounds: online assessment, technical rounds. Timeline is about 1 process; it can shift quickly into stack-specific questions.
$117K
Avg. Base Comp
$151K
Avg. Total Comp
2-3
Typical Rounds
2-4 weeks
Process Length
We’ve seen MSCI lean hard into whether candidates can operate inside a very specific technical environment, not just solve a clean algorithmic problem. In the experience we reviewed, the coding prompt itself was manageable in concept, but the interviewer quickly pushed for an iterative solution and expected the candidate to adapt without much steering. That pattern matters: it suggests MSCI is watching how you reason under constraint, not just whether you can recognize the right DP-style idea.
A recurring theme is that the conversation can pivot from general engineering into tools and architecture that may not appear on your resume. One candidate was asked about moving MBs/GBs to a customer and found that an S3 presigned URL answer didn’t resonate because the interviewer was looking for a Snowflake-oriented approach. The same round also touched Kubernetes host port mapping, reverse proxies, and Nginx, which made the evaluation feel like a quiz on their internal stack. That tells us MSCI values practical familiarity with their data delivery and infrastructure choices more than broad platform knowledge.
We also noticed how little feedback was given during the process. The candidate described the exchange as one-sided, with no real guidance when the solution stalled and no follow-up from HR afterward. For us, that’s a signal that clarity and precision matter a lot here: if you answer with a familiar but adjacent technology, it may not be enough. The strongest candidates are the ones who can quickly infer the interviewer’s preferred ecosystem and speak to it directly.
Synthesized from 1 candidate report by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Msci process.
The part that threw me off most was how quickly the interview moved away from the basics and into stack-specific questions I hadn’t prepared for. I went through an online assessment first, then technical rounds, and the coding question was about minimizing cost on an array where each position had a travel cost and I could choose to take or skip the current element and the next two. I suggested a recursive approach at first, but the interviewer wanted an iterative solution. I managed to get 2 out of 3 test cases passing, but there wasn’t much guidance or feedback during the process, so it felt pretty one-sided.
After that, the conversation shifted into technologies that weren’t on my resume. I was asked how I’d share MBs/GBs of data with a customer, and I answered with an S3 presigned URL since that was in my background, but that didn’t land. The interviewer seemed to be expecting a Snowflake-based answer instead. They also asked about Kubernetes host port mapping, reverse proxies, and Nginx, which made the round feel more like a quiz on their internal stack than a general software engineering interview. I’d interviewed there before and remembered more fundamentals and language basics, so this was a noticeable change. In the end I didn’t get an offer, and HR never followed up with feedback. My main takeaway is to be ready for both the coding problem and a lot of stack-specific questions, even if they’re outside your resume.
Prep tip from this candidate
Practice the minimum-cost array problem in an iterative form, since the interviewer pushed for that over recursion. Also be ready to explain Kubernetes host port mapping, Nginx/reverse proxy basics, and a Snowflake-style approach to sharing large files with customers.
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 Msci
Write a query to return whether each user's subscription date range overlaps with any other completed subscription
| Question | |
|---|---|
| Merge Sorted Lists | |
| Prime to N | |
| Find the Missing Number | |
| Rectangle Overlap | |
| Hurdles In Data Projects | |
| String Subsequence | |
| Google Maps Improvement | |
| Nearest Common Ancestor | |
| Groups of Anagrams | |
| Longest Increasing Subsequence | |
| Radix Addition | |
| Most Repetition | |
| Messenger Service Design | |
| Find Duplicate Numbers in a List | |
| Binary Tree Validation | |
| Dijkstra implementation | |
| Target Indices | |
| Filling Supermarket Bag | |
| Median O(1) | |
| 85% vs 82% | |
| RAG Strict Source Control | |
| Target Value Search | |
| Production Model Monitoring | |
| Implementing the Fibonacci Sequence in Three Different Methods | |
| Concurrent LLM Serving | |
| Check Matching Parentheses | |
| Moving Window | |
| Ticket Reservation Locking | |
| Finding the Maximum Number in a List |
Synthesized from candidate reports. Individual experiences may vary.
Candidates begin with an online coding assessment featuring algorithmic problems. One reported question involved minimizing travel cost on an array, where you must decide whether to take or skip the current element and the next two positions. An iterative solution was preferred over a recursive approach.
Following the assessment, candidates face a live technical coding round where interviewers expect optimized, iterative solutions. Partial credit may apply if some test cases pass, but feedback during the session is limited and the pace can move quickly without much guidance from the interviewer.
The interview shifts into questions about the company's internal technology stack, including Snowflake for data sharing, Kubernetes host port mapping, reverse proxies, and Nginx configuration. Candidates should be prepared for these topics even if they are not represented on their resume, as the interviewer may expect familiarity with MSCI's specific tooling.
