After a recruiter call, I moved through a sequence of phone interviews that felt more structured than anything I’d done before. I then had another round with an engineer and, later, a hiring-manager call that ran long—about half an hour beyond what I expected—and stayed pretty chill. I kept noticing how much they wanted me to connect my background to their work.
Not long after, I was brought onsite for the final stage. The day included a panel presentation where I talked through my strongest technical achievements, and I also received constructive feedback before the rest of the on-site interviews continued. After that, I broke into one-on-one conversations with technical people, and the process ended with a hands-on or more practical component depending on the flow of the day.
2 months ago
Easy Negative United States
My interview started with a call that felt straightforward on the surface, but it quickly turned into a frustrating mismatch. The questions weren’t just general “tell me about yourself” prompts; I was asked about what I knew related to Starship, and then they moved into technical fundamentals.
What threw me off was that my technical background was treated as if it didn’t matter. Even though the role description and my own coursework were in electrical engineering, the technical questions focused heavily on mechanical engineering fundamentals. On top of that, the interviewer came across as negative and dismissive toward my experiences—downplaying the value of my projects and even challenging why my work should count for anything.
4 months ago
Difficult Neutral Seattle, WA
The timeline started with a recruiter conversation, and then I hit an assessment that was genuinely brutal. The OA took around four hours, and it set …
4 months ago
Difficult Positive McGregor, TX
My process moved quickly once it started: I did a short phone screen first, then a more involved technical round, and finally an onsite day. The initi…
7 months ago
Difficult Positive Redmond, WA
My process began with a recruiter phone screen where they asked me about my resume, and then the technical portion quickly became more hands-on. After…
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Structure & Timeline
The interview process typically begins with a recruiter call, followed by a technical assessment and a series of interviews, including a panel presentation and one-on-one sessions. The timeline can be quick, with multiple stages occurring in a short period.
Candidates can expect a challenging technical assessment that may include hands-on coding problems, often requiring knowledge of both electrical engineering and programming languages like Python. The technical interviews often involve deep dives into past projects and whiteboard-style questions.
Onsite interviews typically include a panel presentation where candidates discuss their technical achievements, followed by constructive feedback. This format is designed to assess both presentation skills and technical depth.
Candidates should be prepared for questions that assess cultural fit and alignment with SpaceX's values, with an emphasis on connecting personal experiences to the company's work. Some candidates reported feeling that their backgrounds were not valued, highlighting the importance of clear communication.
Cultural fitBehavioral questionsSTAR method
Difficulty & Pressure
The interview process is described as intense and challenging, with a focus on performance under pressure. Candidates may feel that the standards are set high, and the experience can be both educational and stressful.
High difficultyPressureStress-test
Preparation Insights
Candidates recommend thorough preparation, especially for technical assessments and presentations, as well as being ready to discuss projects in detail. Understanding the role's requirements and aligning experiences with the company's focus areas can be beneficial.