I applied online. I interviewed at SpaceX (Redmond, WA) in Dec 2016
Interview
1. 30 minutes bug finding test.
2. phone screen with a manager.
3. 6 hour coding challenge in C++
This was the worst experience I've had in a long time. I'm a very seasoned C++ developer with many years of industrial-strength C++ coding under my belt. Up to the 6 hours challenge everything was smooth. The 6 hours challenge was a nightmare. The question they give is very easy. But they impose many restrictions that are absurd such as not being able to use C++ standard library at all. This restriction is what makes the challenge take so much time, and it doesn't make the question any more interesting (just long and tiring). The idea is that you write the code and send it to the tester who runs it for you and tells you if you passed the tests or not. I was able to get my code to pass the all the test, and I wrote it very cleanly. Despite all these, They rejected me for a bogus reason that was related to a human mistake I made towards the end of the challenge when I accidently sent the wrong file to the tester (after time) which caused the tests to fail. I immediately sent him the correct file but apparently, that wasn't OK with him so he failed me. Not because I didn't succeed in getting correct code, not because I failed the test cases. But because I accidently sent the wrong file (a rogue copy that I had). Yes, over 6 hours of useless work, on an idiotic exercise with ridiculous constraints that are irrelevant to anything, just to be disqualified for a stupid mistake. Yup, that SpaceX for you guys. You decide if you want to engage with these people. I have made up my mind never ever to apply there again.
Interview questions [1]
Question 1
The coding challenge requires you to solve a not very complicated problem with many restrictions including not being able to use C++ standard library. I can't say more than that.
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?
Interview questions [1]
Question 1
recruiter called, they has a few big O questions and basic DSA
Phone call with a recruiter discussing SpaceX, its goals, my resume, professional experience, interest in the role, availability to work overtime, and ability to handle additional responsibilities when needed for the position.
Interview questions [1]
Question 1
They asked me to tell them about my professional experience.
Recruiting Call -> Several rounds of technical interview: very fundamental questions that probe your conceptual understanding. Make sure to study / review first principles as it gets theorectical. Quick 30 minute phone calls
Interview questions [1]
Question 1
Tell me about one project to showcase engineering skills