"Technical challenge" - with two anxious interviewers staring at you across a table provide code / pseudo code of how to reverse a linked list in five minutes or less with them showing visible frustration if you weren't ready for this. No other questions about C or C++, just do you remember data structures class from 20 years ago which you haven't had reason to use since.
If you were communicating between the rocket's main computer and given sensors, would you use TCP or UDP and why?
Most of the questions I was asked weren't about my technical experience (although my experience was naturally discussed). Most of the questions from the managers I met with pertained to how I dealt with people, specifically difficult people, and how I excelled in a difficult and demanding work environment.
Is Python a strongly or weakly typed language? Can MQTT be configured to use UDP instead of TCP? And other off the cuff questions based on my resume.
What is the difference between "delete" and "delete[]"?
Why do you want to work at SpaceX? Other questions about my resume and trying to see if the experience matches what they are looking for.
Why do we care about reflections?
What is my experience with aircraft avionics?
What is an ADC, how does it work? What is the architecture "inside" an ADC.
You have a straight Hydraulic Line and two pressure transducers attached perpendicular to that line, one is reading 20 volts, and the other is reading 80 volts. Describe the process you'd take to determine why there was a difference, and how do you know which one was reading correctly (if any.)
Viewing 1 - 10 interview questions