I was initially contacted by a recruiter, who was very responsive to my questions, and instructed to take an initial debugging test. The test was a multiple choice quiz debugging C code. The code itself wasn't hard to debug, but for multiple questions I didn't know if I could assume things such as if the arguments given were always accurate or if memory allocation always succeeded. I tried to use context clues to determine what I should assume but whether the code checked it's inputs or checked for a successful memory allocation varied from question to question and therefore there were multiple questions where I could have justifiably argued that there were multiple answers for the same question. After I took the quiz I very politely emailed the recruiter to tell her I felt good about the test, but that the quiz was ambiguous because it didn't clarify what we were allowed to assume. A few days later all I received was a boiler plate email telling me that I would not be moving forward.
Interview questions [1]
Question 1
Shown a piece of C code determine what the bug is, if any
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