I applied through a recruiter. I interviewed at Tesla (Palo Alto, CA) in Dec 2016
Interview
1. Coding Challenge (3-4 hour problem submitted via email).
2. 2 Phone Interviews (1 hour) - Technical questions
3. On-Site Interview (full day) - Prepare a 15 min. presentation followed by one on ones with ~5 people. You're brought to the engineering floor and assigned a conference room (where you'll stay for the entire duration of the interview; lunch will be brought to you). I was told by the recruiter that the on-site is strictly non-technical and just a chance for others to see whether there'd be a good culture/personality fit, however, each interviewer ended up asking me technical problems anyway. One interviewer brought in my coding challenge solution and asked me about any bugs/optimizations that could've been done.
Questions range from the typical technical coding problems to C++ basics.
Interview questions [2]
Question 1
What is a virtual function and how does the compiler handle them?
Remembering the coding question about finding a peak element gives me a sense of relief. It was nearly the same as one I had practiced on PracHub a few days prior. The interview process began with a recruiter screening my resume, followed by a technical phone interview where we discussed data structures and algorithms. The onsite included two additional rounds focusing on coding and behavioral questions. Overall, the experience was straightforward, and I felt well-prepared, ultimately leading to an offer that I happily accepted.
2 Technical Coding Screen, followed by onsite. Interesting problems and role related. Friendly recruiting coordinator. On site - in person, several rounds, includes presentation and question & answers. Highly role related and based on past experiences.
pretty chill. asked about evaluation metrics, calculate 2 metrics given a data log. has_collided, radial TTC. A few questions from my resume. How did you determine xyz, what are the factors, and what could be some other factors?