Software Engineer applicants have rated the interview process at Tesla with 3.2 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 43% positive. To compare, the company-average is 55% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 34 days to get hired, when considering 149 user submitted interviews for this role. To compare, the hiring process at Tesla overall takes an average of 33 days.
Common stages of the interview process at Tesla as a Software Engineer according to 149 Glassdoor interviews include:
Phone interview: 26%
One on one interview: 19%
Skills test: 15%
Presentation: 12%
Group panel interview: 9%
Background check: 6%
IQ intelligence test: 4%
Personality test: 4%
Other: 3%
Drug test: 2%
Here are the most commonly searched roles for interview reports -
I applied through an employee referral. The process took 7 weeks. I interviewed at Tesla (Fremont, CA) in May 2018
Interview
The interview process leading up to the on-site interview was very prompt and lots of communication. 1 phone interview with the recruiter, 1 with engineering manager, and 1 on-site interview. The on-site interview consisted of a presentation, then 1:1 interviews with 6 software engineers. There were a a few technical questions: algorithms, SQL, functions. There was also a coding challenge that had to be completed on one of the interviewer's computer. There were some behavioral/cultural questions. Overall, the on-site interview went great and I felt prepared. I felt that the recruiter's communication after the on-site interview was slow and lacked transparency. I did not receive interview feedback until 1.5 weeks later. The feedback was great and positive, but they decided to hire someone with more experience. I have not heard back about other similar opportunties.
Interview questions [1]
Question 1
What goals do you have the first 6 months of working at Tesla?
3 45 min rounds virtual, mix of technical data structures and algorithms style questions and behavioral questions. Around leetcode medium difficulty, strings and array based. Short talk about what the team does.
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.