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 online. The process took 3 months. I interviewed at Tesla (Fremont, CA) in Feb 2020
Interview
I applied for the Software Engineer (Front-end) position in November 2019. The recruiting HR reached out to me in the first week of December. I was asked to attempt a coding assessment. After that, radio silence for almost a month. I reached out to the HR in the first week of January 2020 and they set up a phone interview with a potential team member. After the interview, they invited me over to meet with the team. After a few abrupt delays, they flew me to California in the third week of February 2020.
It's been over a month, there has been absolutely no communication from the HR. They aren't even replying to my emails. I understand that there might be a slow down in various processes due to COVID-19 but I was hoping to get any kind of update.
Interview questions [1]
Question 1
Javascript (ES6)
CSS
Server side
Front-End (React)
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.