J'ai passé un entretien chez SpaceX (Redmond, WA) en juil. 2024
Entretien
A recruiter reached out to me and we had a phone call. Then I did the 2-4 coding assessment on an optimization problem. The next step was a 45 minute phone call where I had to describe a previous project in depth and then answer some coding-related technical questions.
The final step was an on-site in Redmon, WA.
1. Tour of the Starlink factory (very cool)
2. 15-20 slide presentation on a software project for which presentation + Q&A occupied 1 hour (this took a ton of time for me to prepare)
3. 30 minute lunch with the recruiter
4. 45 min System design interview
5. 45 min Behavioral questions + follow up questions for the presentation
6. 45 min whiteboard coding
The negatives
- They ghosted me after the final interview instead of telling me I didn't get an offer. They didn't even respond to my follow up.
- The charge for my hotel was supposed to go to SpaceX, but their travel team didn't set it up correctly, so my credit card got charged instead. I'm trying to get reimbursed for this $350 charge.
- I had to spend hours digging up my SAT/ACT/GRE scores and undergrad/college GPAs even though I have been out of school over 6 years.
So, they demanded that I put a ton of effort into preparing and interviewing there, but didn't have 5 minutes to send me a rejection email. Very disrespectful.
J'ai passé un entretien chez SpaceX (McGregor, TX)
Entretien
Applied online has two round. First being an phone call with recruiter and the second being online with a team of engineer asked about my previous experience and then had a short coding leetcode style question
Questions d'entretien [1]
Question 1
Explain a recent debugging problem and how you solved it.
J'ai passé un entretien chez SpaceX (Sunnyvale, CA)
Entretien
Basic questions about python vs c++, am I authorized to work in the US, stack vs heap, projects and my experience mentioned in my resume, quick introduction about myself and why i wish to work at spacex.
J'ai passé un entretien chez SpaceX (Hawthorne, CA)
Entretien
Recruiter screens usually hit: time/space complexity of common operations, why O(log n) beats O(n), array vs hash map vs linked list tradeoffs, and Big-O of sorting. Want me to drill you on these?
Questions d'entretien [1]
Question 1
recruiter called, they has a few big O questions and basic DSA