MSD Data Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 10 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at MSD.
MSD
Data Engineer Manager
Manager Average Positive experience No offer 2 rounds
Interview process
Recruiter call Technical screen Phone screen
Interview formats
Behavioral Technical
MSD is opening a new office in HYD and they're looking for a Data Engineer with managerial responsibilities. I made it to the second stage. The first interview was with the engineering manager, and it was mainly about my experience, the tools I've used, and how I'd fit into the role. The second interview was more focused on the management aspect.
Confirmed questions7 questions
- Can you tell me about your experience with databases and the tools you've used?
- How do you go about prioritizing your tasks?
- What's your approach to communicating with stakeholders?
MSD
Analytics Engineer
Entry Average Negative experience No offer 1 round
Interview process
Technical screen
Interview formats
Technical Coding
The interview was scheduled for 50 minutes but wrapped up in 15. The interviewer asked a few questions before diving into a technical discussion. I lacked direct experience with AWS Glue, the specific tech stack mentioned, so I tried explaining a similar pipeline I built using Databricks. However, the interviewer cut me short, asking specifically about AWS Glue and indicating he didn't want to waste time. My answers apparently weren't satisfactory, as he concluded the interview. Strangely, the recruiter contacted me weeks later, asking if I had attended, as her system was missing feedback and she wanted to schedule it if I hadn't. I'm unsure what's going on internally; it doesn't seem like candidates are being fairly assessed.
Confirmed questions1 question
- Can you explain what an AWS Glue Crawler is?
MSD
Data Engineer
Mid Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Technical Behavioral Coding
The interview process for the Data Engineering role at MSD was pretty good and seemed well thought out. It started with the usual 'tell me about yourself' to get things rolling. Then it got technical, diving deep into my data engineering skills. They gave me real-world problems to solve and asked about my experience with important tools and tech, checking out my problem-solving chops. This part was tough but fun, letting me show off what I know and how I'd tackle the job's specific issues. The last bit was about the 'softer' side of things. They wanted to see beyond just the tech skills, looking at my communication, teamwork, how I deal with changes, and handle conflicts. It was clear MSD wants people who are not only technically skilled but also a good fit for their team culture. Overall, it was a thorough process, covering a lot of ground. They combined a standard intro, a technical check, and a look at personality to make sure they find people who have the skills and also fit the company vibe and can work well with others.
Confirmed questions3 questions
- Could you tell me about a project where you built a data pipeline from the ground up? What issues came up and how did you fix them?
- Tell me about a time you worked with different types of people to reach a goal. How did you handle disagreements and what happened in the end?
- If we needed to make our data storage and retrieval better, how would you go about it? What tools or methods would you use, and what would guide your choices?
MSD Data Engineer Interview Questions
Quoted word for word from MSD interview reports.
“What are the differences between Java 8 and Java 7?”
Read reports →“Can you explain what an AWS Glue Crawler is?”
Read reports →“What are the reasons for using Apache Spark?”
Read reports →“Can you explain what Apache Spark is?”
Read reports →“Can you identify and rectify the issues in the provided code snippet?”
Read report →“If we needed to make our data storage and retrieval better, how would you go about it? What tools or methods would you use, and what would guide your choices?”
Read report →“Are you able to write code in javascript?”
Read report →“How do you communicate with stakeholders?”
Read report →“What statistical concepts did you apply or learn about in relation to your project?”
Read report →Formats, difficulty and experience
Across all 10 MSD interview reports.