BMW Car IT interview questions

The interview process is very slow. For all interviews, the recruiter will send you a mail after scheduling the call and ask you if you're okay with the time slots. You're not given a choice in advance. I attended all interviews remotely. The interview process goes as follows: 1. Codility coding challenge - This is a 90 minute challenge where you have to solve ~3 problems (in my case, 1 major coding challenge, 1 minor debugging problem and 1 minor Q&A). If you solve the major one successfully, you can expect to be called for the next round. I did not hear back from the recruiter after completing the challenge for about 2 weeks. The first interview was then scheduled for a date that was another 2 weeks away. 2. Initial one-on-one interview: A quick chat with a developer talking about your CV. Also involved a minor coding challenge. If you get through this round, you're then called in for a 4 hour continuous interview, that goes as follows: 3. Developer interview 1: A technical interview with 2 senior developers. I was asked multiple complex questions on C++ memory management, which I could not answer correctly. 4. Developer interview 2: A second technical interview with 2 senior developers. I was asked to design a camera system with 3 applications. I was first asked to design a block diagram on a whiteboard and then write a skeleton code of the implementation. I believe I did not meet their expectations here as well. 5. Coffee break: This is a 30-min informal discussion with the developers who interviewed you in the previous rounds. 6. Tech lead interview: This round might contain some technical questions, but it is less of a technical interview and more of a behavioral interview. However, don't take this lightly. Irrespective of your technical prowess, this interview may make or break your case. All interviewers then meet to make a decision. As I understand, you're only selected if it's a unanimous 'Yes'. By the end of the interviews, I was exhausted due to all the continuous talking and focus. 7. Feedback: You're provided a detailed feedback on the positive and negative aspects of your interviews. I believe this is not the norm and I deeply appreciate and respect the staff for their extensive feedback. Please be aware that irrespective of the role, C++ and computer architecture play a major role in your selection.

People in the interview was very nice. It was mostly like tech chat. They asked me very detailed questions related to my current job. I believe they liked what I was doing but I think I couldn't answer some questions how they wanted, I realized that in the interview. I went to so deep instead of explaining simply. Also, there was one tech question that I could not understand properly and I hurried up because the interview time was ending. In the end, I couldn't be proceed for the next step. As I understood, they expect you not to make any mistake. To sum up, it was good experience because of the interviewers, it doesn't make them bad because they didn't choose me.