
BMW of North America Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 79 interview experiences · FREE TO READ
Which role are you interviewing for?
30 roles · 79 reportsCandidate interview experiences
First-hand accounts from people who interviewed at BMW of North America.
Analyst
Very good, first round is behavioral and second round is technical question, very impressed, two interviewers, and after that is the second round, it fine, I would give it very good comment
- Why are you interested in this company?
- Why are you a good fit for this role?
- What is your greatest weakness?
Powertrain and Chassis Engineer
The interview process was pretty straightforward. It started with a short phone call, then I had a technical interview with the manager. He was a really friendly and enthusiastic guy. I basically showed a couple of slides about what I know for the role, and he asked me a few straightforward technical questions about powertrains.
- Can you share an instance where you needed to explain a technical topic to someone without a technical background?
Software Engineer
First, a recruiter called to chat about your background, if you're a good fit, and what you're looking for salary-wise. Then there was a technical screen, which was one round of coding and some core Java stuff. After that, there were 3 more technical rounds where you did coding challenges, talked about Java fundamentals, and discussed system/architecture. Finally, there was an onsite round with the team and hiring manager for behavioral and technical deep dives.
- Recruiter screen covering background, role fit, and salary expectations.
- One round of coding and core Java questions.
- Three rounds with coding challenges, Java fundamentals, and system/architecture discussions.
Senior Frontend Engineer
The interview process was pretty fast and okay. It was a bit weird that even though the role is Senior, I only spoke with what seemed like Junior developers. Maybe they weren't officially Junior, but it was obvious from their limited experience and lack of 'why.' One of them actually thought Scrum Master was a technical role, which surprised me and I pointed it out. The onsite interview was supposed to go until 4:45pm, but I'd told the recruiter days before I had to leave by 4:30pm for another interview. The team lead at BMW apparently knew, but didn't tell the developers. When 4:30pm came, I told the developers I had to go, and they seemed surprised. I also mentioned to the BMW team that I was looking at other full-time roles since this was a contract. For some reason, they didn't like hearing that. Maybe if they wanted me to be interested, they should make the offer more appealing and hire full-time instead of contract. Honestly, I wasn't impressed and expected more from BMW Solutions. Oh well.
- Tell me about your background and any technical questions.
- Can you answer some questions about React?
- Let's discuss JavaScript.
BMW of North America Interview Questions
Quoted word for word from BMW of North America interview reports.
“Find the common ancestor of two nodes in a tree.”
Read reports →“Can you remove a node within a Linked List?”
Read reports →“Can you write a method to take m raised to the n, and do it optimally?”
Read reports →“Can you write a method to change a value from little endian to big endian?”
Read reports →“What are ways to accelerate the training process in deep learning?”
Read report →“What's a new technology that could be used in car manufacturing today, even if it doesn't exist yet but would be a good idea?”
Read report →“Can you explain the Backpropagation Neural Network (BPN) in detail?”
Read report →“Can you explain how a decision tree functions?”
Read report →“How would you debug a small block of code?”
Read report →Formats, difficulty and experience
Across all 79 BMW of North America interview reports.