>>11753296Sure.
So, its hardware programming, and they use C++. Company-wide they use languages other than C++ as well, just because lots of engineers need to do a little programmer but are not full time programmers.
I had three 30 minute white board code interviews with three different people. None of them were really about writing out a working program at the end. That wouldn't actually have been possible. It was more about talking through a problem and writing code together.
The first one was about writing out a program to listen for a sequence of knocks over time, kind of like morse code, and then checking if it was a particular sequence, kind of like a password.
The second one about writing a function that turns an integer into a string.
The third one we actually wrote no code at all, even though we had a shared online code editor, and we just talked about different approaches to big architectural problems one might face when trying to build a system like Starlink. He seemed to be drawing from their actual programming challenges.
I am pretty sure the parameters of each code session was just the whim of the individual interviewer and I think each interviewer that talked to me could have chosen whether or not we would be coding together or just talking. In the interview sessions where we were not pair coding, we still talked about code, but it was mostly me talking about myself and the code I have written.
