Robert Bosch Software Developer interview questions
based on 233 ratings - Updated Dec 14, 2025
Averageinterview difficulty
Very positiveinterview experience
How others got an interview
44%
Campus Recruiting
Campus Recruiting
34%
Applied online
Applied online
7%
Recruiter
Recruiter
6%
Staffing Agency
Staffing Agency
4%
In Person
In Person
3%
Employee Referral
Employee Referral
2%
Other
Other
Interview search
233 interviews
Viewing 16 - 20 of 233 Interviews
Robert Bosch interviews FAQs
Software Developer applicants have rated the interview process at Robert Bosch with 2.5 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 100% positive. To compare, the company-average is 76.3% positive. This is according to Glassdoor user ratings.
Common stages of the interview process at Robert Bosch as a Software Developer according to 2 Glassdoor interviews include:
Phone interview: 33%
Personality test: 33%
One on one interview: 33%
Here are the most commonly searched roles for interview reports -
Direct Interview, Easy to answer also questions asked from computer network, operating system also puzzle where asked , you must be confident to answer the question , DBMS also they asked few questions joins , query
I applied online. The process took 2 weeks. I interviewed at Robert Bosch (Bengaluru)
Interview
Interview process was smooth. asked mostly about fundamentals of OOPS. Had another round with Data structures and algorithms, where mostly asked basic questions. Before interview, had basic coding round, where asked to code a sample problem.
I applied online. The process took 2 weeks. I interviewed at Robert Bosch
Interview
General HR screening, then a technical interview with the Section manager. I was asked some basic C questions but the interviewer was more curious about what my thought process looked like interpreting functional development on radar-aided safety functions.
Interview questions [1]
Question 1
I was asked some basic C questions but the interviewer was more curious about what my thought process looked like interpreting functional development on radar-aided safety functions.