The interview process was long, to say the least. It included a recruiter phone screen, two technical phone screens, and a project, all leading up to an on-site interview. For the on-site, my first task was to give a presentation before being interviewed for several hours by members of the team I would potentially be working with.
That being said, the interviews were useful and relevant. The first technical phone screen was a straightforward coding challenge where I was given a CoderPad and allowed to work until completion. The project was actually quite interesting, not terribly difficult, and a lot of fun. While the presentation was stressful, it felt almost like a victory lap. The questions asked during the interviews were mostly relevant, with only one trick question, and nothing felt overly forced.
And, you get to ride in a Tesla after it's done. That was by far the best part.
The main feedback I would give is that the entire process was lengthy. I also felt the second technical phone screen was not particularly useful.
The offer extended was fair, and the compensation was well in line with other companies of similar size.
Overall, I believe Tesla has done well in overhauling some old processes, and it's definitely an improvement compared to what has been noted before.
Imagine it is raining over a 100m stretch of 2-d road. Each raindrop falls onto a random position. Once it hits a stretch of road, it expands to a length of 5cm. Write code that tracks each raindrop and determines when the road is entirely saturated.
The following metrics were computed from 1 interview experience for the Tesla UI Engineer role in Palo Alto, California.
Tesla's interview process for their UI Engineer roles in Palo Alto, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Tesla's UI Engineer interview process in Palo Alto, California.