Mercedes-Benz Research and Development India logo

Mercedes-Benz Research and Development India Software Engineer Interview Questions
& Process

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

Based on 66 interview experiences · FREE TO READ

3 Rounds average
Average Typical difficulty
62.1% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Mercedes-Benz Research and Development India.

Showing 3 of 66
Mercedes-Benz Research and Development India logo
Mercedes-Benz Research and Development India

Software Engineer

Engineering · more than a year ago

Entry Average Neutral experience Decline offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Technical Behavioral

The interview process was good, involving classic questions about core technical concepts and personal aspects. They asked about previous experience and projects from graduation and post-graduation. They also inquired about how this job would benefit my career and my perception of the company's future role in the world.

Confirmed questions4 questions
  • Can you tell me about your core technical knowledge and personal background?
  • Could you describe your past experience and projects from your graduation and post-graduation studies?
  • In what ways do you believe this role will advance your career?
Mercedes-Benz Research and Development India logo
Mercedes-Benz Research and Development India

Technical Lead

Engineering · more than a year ago

Lead Difficult Positive experience Accept offer 3 rounds
Interview process
Recruiter call Technical screen Onsite Background check Offer
Interview formats
Technical Coding Behavioral Presentation

The interview process usually starts with a recruiter call, which is pretty informal, just to get to know each other and discuss the job's requirements and what the applicant is looking for. After that, you'll likely have an onsite interview at MBRDI ITPL on a weekday. This one is more in-depth, and you might even get to do some coding on a provided laptop. Whether you get to code depends on the interviewer; if they're more collaborative, they might help you remember things, otherwise, you're on your own. Then there's a managerial round focused on accountability and ownership, assessing your work behavior, mindset, and past experiences. You'll also learn about Benz's values. It's straightforward, but be honest about what you know. The final round is with HR, which can be trickier than the technical ones because Benz really values integrity and long-term relationships. So, be confident and truthful. There's a bit of a follow-up with HRs after, which can be a little annoying, but if you've done well, you should be expecting an offer. Just make sure you have the official offer before resigning. Good luck!

Confirmed questions5 questions
  • Could you discuss your understanding of circuit designs?
  • What is your level of expertise in software simulation?
  • Can you elaborate on your coding proficiency?
Mercedes-Benz Research and Development India logo
Mercedes-Benz Research and Development India

Software Engineer

Engineering · more than a year ago

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

I got referred and they called me for a technical phone interview 3 days in advance. The planning and the interview experience were good. It was one technical phone interview, followed by two in-person technical rounds, and then an HR round. I was told I cleared all rounds and they would get back to me. The HR process is extremely slow, taking 45 days to respond and 60 days for an offer, making me question their interest. Salary negotiation was very tough, they bargained like street vendors. Friends at Daimler said it's not worth joining due to poor work quality and salary. The Indian counterpart, MBRDI, is in early stages and gets unimportant, residual, and trivial tasks from Germany.

Confirmed questions2 questions
  • What questions did they ask regarding your system understanding from previous experience?
  • Can you describe your analysis capabilities?

Mercedes-Benz Research and Development India Software Engineer Interview Questions

Quoted word for word from Mercedes-Benz Research and Development India interview reports.

What is the output of the given Python code snippet involving a dictionary update?

Read reports

Describe how to calculate the frequency of each character in a given string.

Read reports

Write a program to insert an element at the ith position in a doubly linked list, considering boundary conditions.

Read reports

How would you sort a string without using any built-in sort functions?

Read report

What is the syntax for the Copy and assignment operators when dealing with a char array on the heap, and how would you manage copying if the initial size is 2 and you later need to copy data of size 5?

Read report

Explain the function of Q_OBJECT and MOC, and why are they necessary?

Read report

Can you explain the differences between abstract classes and interfaces in Java?

Read report

Explain the concept of returning by reference, why it's needed, and in which scenarios it should be used. What are the different methods for writing functions that return by reference?

Read report

Formats, difficulty and experience

Across all 66 Mercedes-Benz Research and Development India interview reports.

Interview formats

Technical 45.3%
Behavioral 32.9%
Coding 17.4%
System Design 2.5%
Other 1.2%

Interview difficulty

Easy 16.7%
Average 69.7%
Difficult 13.6%

Candidate experience

Positive 62.1%
Neutral 15.2%
Negative 22.7%