The interview process began with an HR screening, followed by a phone screen. This phone screen consisted of trivia-style questions covering C++, OOP, Data Structures, and Algorithms.
Next, there was a coding test to be completed at home within 8 continuous hours. A key restriction was that C++ STL containers were not permitted. During the first 60-90 minutes of this test, candidates could communicate with a "proctor" via email. This period was intended for clarifying questions, outlining the intended solution before coding, and receiving feedback. My "proctor" was helpful.
Following the coding test was an onsite interview, conducted virtually at the time. This included a 25-minute presentation to the team about a past project, followed by a Q&A session. None of the team members used their video cameras, although I did, which created a cold experience. Subsequently, there were approximately three technical interviews, each focusing on different design aspects. The questions presented were ambiguous.
The session with the hiring manager centered on behavioral questions. Two days later, HR called to inform me that I did not pass and provided some feedback.
C++, OOP, DS & Algorithms trivia.
8 hrs coding challenge.
Design a fault-tolerant system.
Describe how a mobile device works.
How would you design a simulation system?
Behavioral questions, e.g., how do you cope with stress.
The following metrics were computed from 17 interview experiences for the SpaceX Senior Software Engineer role in United States.
SpaceX's interview process for their Senior Software Engineer roles in the United States is very selective, failing most engineers who go through it.
Candidates reported having mixed feelings for SpaceX's Senior Software Engineer interview process in United States.