Knorr-Bremse logo

Knorr-Bremse Embedded 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
Average Typical difficulty
57.1% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Knorr-Bremse.

Showing 3 of 7
Knorr-Bremse logo
Knorr-Bremse

Embedded Software Engineer

Engineering · more than a year ago

Mid Difficult Positive experience No offer 3 rounds
Interview process
Technical screen Technical screen Recruiter call
Interview formats
Technical

The interview process included two technical interview rounds, followed by an HR round. The technical questions covered areas like C, communication protocols, Linux Operating System, RTOS, CANoe, and scripting languages, with a specific emphasis on the CAN bus protocol.

Confirmed questions1 question
  • What are the methods for detecting errors on a CAN Bus?
Knorr-Bremse logo
Knorr-Bremse

Embedded Software Engineer

Engineering · more than a year ago

Senior Average Negative experience No offer 3 rounds
Interview process
Technical screen Recruiter call Offer
Interview formats
Technical Behavioral

Worst Experience Ever Because of following reasons 1.Arrogant Hr experience during final round. 2.Lack in transparency when process was started. 3.No respect for time for person who is interviewed. Initially when interview process was started no information was given regarding payroll(whether it will be direct or third party). Process started as a senior person currently working at KB referred me so it was obvious to be direct pay roll offer. Below Both rounds were conducted on same day. First Interview Round with Technical Head for 1hr30min- Very basic questions related to C and Micro- controllers were asked.Some basic programs were told to write on Notepad. Second Interview with Manager 1hr 15min- Similarly as first, basic C questions and micro-controller related were asked. Now here is the problem starts which is UNETHICAL,IRRESPONSIBLE and lacking in TRANSPARENCY. After two days,HR who was communicating for whole process says that "Are you interested to work as third party pay role"?And then I asked isn't this important information which should be told at the start.I was told that position for internal pay has been filled. The question here raises is if internal position is filled and I have clearly communicated my interest about not working for third part pay role.Why third round was organized? Do HR heads in this organisation have value for others time?In this pandemic situation we developers are already working more than 10hrs.We manage extra time for interview which goes for 1hr 30min.And what we find is lack in transparency. Hr was just trying to blame for one or other reason and Not accepting mistakes which they did in this process. I was only interested in direct pay role so I rejected the offer

Confirmed questions4 questions
  • Questions on C-Pointers
  • Questions on C-Structures
  • Questions on C-Bitwise operations
Knorr-Bremse logo
Knorr-Bremse

Embedded Developer

Engineering · more than a year ago

Entry Average Positive experience No offer 3 rounds
Interview process
Technical screen Technical screen Recruiter call
Interview formats
Technical Technical Behavioral

The interview process included a technical test focused on C/Embedded concepts. Shortlisted candidates then went through a technical interview, and some even had a second technical interview. After that, HR interviewed the shortlisted candidates. Overall, it was a good experience, and they asked basic questions on C/Embedded, talked about projects, and covered CAN/data frame concepts.

Confirmed questions1 question
  • Can you explain bit toggling functions?

Knorr-Bremse Embedded Engineer Interview Questions

Quoted word for word from Knorr-Bremse interview reports.

Can you explain what you did during your educational gap?

Read report

Formats, difficulty and experience

Across all 7 Knorr-Bremse interview reports.

Interview formats

Technical 68.8%
Behavioral 25%
Coding 6.2%

Interview difficulty

Easy 0%
Average 57.1%
Difficult 42.9%

Candidate experience

Neutral 28.6%
Positive 57.1%
Negative 14.3%