The interview process involved:
The recruiter call took around 30 minutes, the 4-hour assessment took 2 hours, and the technical calls were 45 minutes each.
The assessment was a satellite coding challenge regarding making connections between satellites and users, using Python or C++. I saw another post on here better describing the assessment in detail.
The technical calls both started by asking about a project you worked on. The first got more into details, asking to "describe as if you were onboarding this to someone new." The second was more about "what would you have done differently?"
Later, they asked technical questions regarding topics taught in college (be prepared to brush up on old notes), but which were not as practical in my career. Questions included:
What is a linked list?
What is a page fault?
Difference between threads vs. processes?
How do processes communicate with one another?
Are there issues with threading in Python?
The following metrics were computed from 144 interview experiences for the SpaceX Software Engineer role in United States.
SpaceX's interview process for their Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.
Candidates reported having good feelings for SpaceX's Software Engineer interview process in United States.