First step was an email telling me I had a coding assessment. Then I could let the recruiter know when I would be free to do that. There was 5 questions on coderpad. Macros, Debugging, State machine, Interpolation and bit manipulation.
Questions d'entretien [1]
Question 1
There was 5 questions on coderpad. Macros, Debugging, State machine, Interpolation and bit manipulation.
J'ai postulé en ligne. Le processus a pris 3 semaines. J'ai passé un entretien chez Tesla (Palo Alto, CA) en juin 2025
Entretien
4 rounds of interviews.
3 online and one in person at HQ.
Round 1
Skills mentioned in my resume and overall skills.
Basic c programming and C++
Deep dive into embedded concepts.
What and how did my experience impact the previous role
J'ai passé un entretien chez Tesla (Palo Alto, CA)
Entretien
Prescreening with HR going through resumes into a technical review of resumes and coding problems with someone on the hiring team. The coding problem wasn't something I saw on leetcode.
Questions d'entretien [1]
Question 1
went through resume, coding problem was to fill-in blanks for a typical system they'd use
J'ai postulé en ligne. J'ai passé un entretien chez Tesla (San Jose, CA)
Entretien
The interview process was quite drawn out. The recruiter took a while getting back to me despite multiple teams showing interest in my profile. Scheduling the phone interview took time, but the process was smooth. There was an online assessment as an initial screen, It was challenging but doable. The phone screen itself was a pretty bad experience. Just like interviewing is a skill not everybody has, being an interviewer is also a skill not everybody has. This guy who interviewed me was a manager I think, but not all managers make good interviewers. He barely spoke, which is not what you'd expect in a phone interview. I'm going to think multiple times before interviewing for Tesla in the future.
