J'ai postulé en ligne. Le processus a pris 2 semaines. J'ai passé un entretien chez SpaceX en mars 2024
Entretien
1 - Recruiter prescreening
2 - 4 hour assessment
3 - technical calls
recruiter call took around 30 minutes, 4 hour assessment took 2 hours, and the technical calls were 45 minutes.
The assessment was a satellite coding challenge regarding making connections between satellites and users (python or C++). I saw another post on here better describing the assessment in detail.
The technical calls both started asking about a project you worked on. First got more into details of "describe as if you were onboarding this to someone new" second was moreso "what would you have done differently." Later they asked technical questions regarding things taught in college (be prepared to brush up on old notes), but not as practical in my career- what is a linked list? what is a page fault? difference between threads vs processes? how do processes communicate? are there issues with threading in python? difference between tcp and udp?
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