Mettler-Toledo logo

Mettler-Toledo Software Engineer Interview Questions
& Process

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

Based on 12 interview experiences · FREE TO READ

3.2 Rounds average
Easy Typical difficulty
50% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Mettler-Toledo.

Showing 3 of 12
Mettler-Toledo logo
Mettler-Toledo

Software Engineer

Engineering · more than a year ago

Mid Easy Positive experience Decline offer 4 rounds
Interview process
Recruiter call Technical screen Onsite Background check Offer
Interview formats
Technical Behavioral

Started with a recruiter call, then a technical interview with engineers. Next was an interview with the team manager and a product manager, followed by an HR chat. The whole thing from first call to offer was less than a week, which was super fast. I passed on the offer though because the tech stack is .Net Framework, which is older, and they plan to take a long time to upgrade. Also, I'd have to go on-site sometimes and work with people in different time zones. Everyone was nice and the speed was impressive, but the tech stack and other details weren't ideal for me. No coding was involved, just technical questions.

Confirmed questions1 question
  • Questions about .Net that are standard for a technical screen.
Mettler-Toledo logo
Mettler-Toledo

Software Engineer

Engineering

Entry Average Negative experience No offer 5 rounds
Interview process
Recruiter call Technical screen Onsite Phone screen Background check Offer
Interview formats
Technical Coding Other

After applying online, I had an initial HR call to screen my profile. The interview process was quite long. It started with a programming written test that had around 15 questions on data structures and Java, followed by an aptitude test with about 50 questions, and another paper on OS. After passing these, I had a technical interview round. I was told the manager wasn't available. Then, HR mentioned a telephonic HR interview to discuss salary and general stuff, promising to confirm the next day. I didn't get the call as promised, so I followed up. They said I'd get an email by the end of the day. Finally, I received an email stating my skillset didn't match the job requirements, and I was rejected. This felt like a waste of my time.

Confirmed questions1 question
  • Are your programming basics clear?
Mettler-Toledo logo
Mettler-Toledo

Senior Software Engineer

Engineering

Senior Average Neutral experience No offer 3 rounds
Interview process
Technical screen Technical screen Recruiter call
Interview formats
Technical Coding Technical Behavioral

I went for a walk-in interview for a .NET position in Coimbatore. The process started with a 3-hour written test, then a technical round, and finally an HR round.

Confirmed questions1 question
  • Written test covering algorithms like Pascal's triangle, prime numbers, and spiral matrix, as well as some design problems.

Mettler-Toledo Software Engineer Interview Questions

Quoted word for word from Mettler-Toledo interview reports.

How would you convert a number into words, like 125 into "one hundred and twenty five"?

Read reports

Formats, difficulty and experience

Across all 12 Mettler-Toledo interview reports.

Interview formats

Technical 43.8%
Behavioral 31.2%
Coding 21.9%
Other 3.1%

Interview difficulty

Easy 50%
Average 25%
Difficult 25%

Candidate experience

Positive 50%
Negative 25%
Neutral 25%