
MSD Associate Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 13 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at MSD.
Associate
So the process is pretty standard: you send in your application with your CV and maybe a cover letter if you feel like it. Then there's some testing, followed by screening questions, and finally an assessment day. The assessment day includes a presentation, a CBI, and a situational interview. The whole thing takes about 3 weeks from start to finish, whether you get the job or not.
- Can you tell me about a situation where you sought input from others before making a decision?
Associate Director
A recruiter reached out on LinkedIn in June and we had an initial chat. I got some basic company info, but not much detail on the specific team I'd be managing as an Engineering Manager. We both thought it sounded good and decided to move forward. It took about 1.5 months to get the first interview scheduled. Oddly, before even having any interviews, I got two requests to submit my feedback. The first interview was labeled a 'technical round'. They didn't give much info, just that it would 'assess my technical knowledge'. The interview itself was online with two engineers who seemed disengaged and perhaps not very experienced with interviews. The main interviewer started by reading company details with lots of jargon. When I asked about the team, they were unsure. The other interviewer was distracted, making lunch for his kids. After that strange start, we got into technical questions. It was a mix of random topics: 'Java vs. Python?', 'DB schema implementation?', 'Low-level index implementation?', and 'polymorphism?'. The most memorable moment was when discussing API design and auth tokens; the interviewer asked what types of auth tokens exist, and when I admitted I didn't know and asked for the answer, he suggested Chat-GPT might know. Despite my 15+ years in engineering and management, some 'academic' questions stumped me, though I felt they weren't crucial for daily work. A few days later, an automated email stated they were moving forward with other candidates. No personal contact or feedback was provided. Overall, it felt disorganized, and I'm glad I didn't pursue it further, as the internal workings likely reflect this chaos.
- Could you explain the differences between Java and Python?
- How would you go about implementing a database schema?
- What is polymorphism in object-oriented programming?
Associate Director
The process involved an exam, a presentation where I discussed myself and my experience, and a technical interview focusing on my experience and validation background. They asked questions about conflict resolution and why I preferred MSD over a consulting role, and the differences between them.
- Can you give me an example of a conflict you experienced?
- Can you give me an example of how you resolved a conflict?
- What made you want to join MSD instead of a consulting firm?
MSD Associate Interview Questions
Quoted word for word from MSD interview reports.
“What is polymorphism in object-oriented programming?”
Read reports →“What are the different types of authentication tokens that exist?”
Read reports →“Could you explain the differences between Java and Python?”
Read reports →“What was the difference between MSD and consulting?”
Read reports →“How would you go about implementing a database schema?”
Read report →“Why did you choose MSD?”
Read report →“Can you share your five-year goals?”
Read report →“What made you want to join MSD instead of a consulting firm?”
Read report →“What motivates your interest in this company?”
Read report →Formats, difficulty and experience
Across all 13 MSD interview reports.