MilliporeSigma logo

MilliporeSigma Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 7 interview experiences · FREE TO READ

2.7 Rounds average
Easy Typical difficulty
71.4% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at MilliporeSigma.

Showing 3 of 7
MilliporeSigma logo
MilliporeSigma

Software Engineer

Engineering · more than a year ago

Intern Easy Positive experience Accept offer 1 round
Interview process
Recruiter call Technical screen
Interview formats
Behavioral Technical

We had a hour and a half meeting where I got to know the team. A couple of people asked me some small technical questions, but there wasn't any coding involved. It was a very entry-level interview, so there was no need to stress.

Confirmed questions1 question
  • Can you describe a situation where you collaborated with a team on a project?
MilliporeSigma logo
MilliporeSigma

Development Engineer

Engineering · more than a year ago

Entry Difficult Positive experience No offer 3 rounds
Interview process
Recruiter call Phone screen Panel Onsite
Interview formats
Behavioral Technical

Had a phone interview where we went over my resume and they asked one behavioral question. The second interview was 1:1 with an HR person, followed by a panel interview with engineers. Then we took a tour of the facilities. The questions were mostly like, "tell me more about this project you did at this job".

Confirmed questions1 question
  • Can you explain how you determined the necessary gear ratio for a design project from your past employment?
MilliporeSigma logo
MilliporeSigma

Software Development Engineer

Engineering

Senior Easy Negative experience No offer 3 rounds
Interview process
Take home Technical screen Technical screen
Interview formats
Coding Technical System Design

This was the single worst interview process I have ever taken part in. The recruiter for the Burlington, MA office ignored 2/3 of my follow up emails (1, 2, 4 weeks after 3rd round interview). He replied after the 2 week email only, saying he would get back to me by the end of the week. Two weeks later and over a month after applying I had to call and leave a voicemail to finally get a response. Feedback given was that uploading my Windows take-home project to github by file upload instead of the cli showed a lack of linux knowledge… This was not a requirement. Why would I choose to get a (Linux) terminal running on my Windows PC just to upload a few files… complete nonsense. As for the interview and take home. The take home assignment said that I should be prepared to discuss it at the 3rd round interview, at the interview they simply said, ‘we got it and it works’. No other discussion about it at all and it seemed to have 0 importance despite the large ask. This interview was a 45 minute technical trivia round covering everything from embedded programming, to containers, to Qt knowledge.

Confirmed questions6 questions
  • Could you design a todo application using QT and C++ that allows adding and removing todos, with the ability to assign a custom color to each and invert the text color?
  • Regarding embedded programming, what is the function of an infinite loop, and how can one break out of it?
  • Can you explain what a DMA is and what it is used for?

MilliporeSigma Software Engineer Interview Questions

Quoted word for word from MilliporeSigma interview reports.

What are some common problems or dangers associated with mutexes and semaphores?

Read reports

Regarding embedded programming, what is the function of an infinite loop, and how can one break out of it?

Read reports

Could you explain the concept of signals and slots within the Qt framework?

Read report

Could you design a todo application using QT and C++ that allows adding and removing todos, with the ability to assign a custom color to each and invert the text color?

Read report

Formats, difficulty and experience

Across all 7 MilliporeSigma interview reports.

Interview formats

Technical 42.9%
Behavioral 35.7%
Coding 14.3%
System Design 7.1%

Interview difficulty

Easy 42.9%
Average 42.9%
Difficult 14.3%

Candidate experience

Positive 71.4%
Negative 14.3%
Neutral 14.3%