Interview started out with me getting to ask questions about company first. He wanted to make sure I got to ask what I wanted to know and we wouldn't run out of time at end. Very considerate. A couple soft skill questions. A couple trivia questions about space exploration. "Do you happen to know how many people have been on the moon?" "What was the most significant space related event for you in the last few weeks or months?" Technical question related to real-time systems, semaphores, what's a mutex. Then some coding questions. None of the "CS121 Datastructures and Algorithms" you get with some other companies. We used an online code sharing platform. Interviewer asked to find out if a given number is a palindrome, i.e. 12321 is, 1234 isn't, and you can't just convert number to a string. Worked out an algorithm, but got a little stuck under pressure on how to code it, iterative or recursive. Interviewer said he hated those coding exercises, too. Did another coding question which checked for off-by-one errors. Apparently I got it right first time, but then wrong after he asked "Are you sure?". Not so thrilled about that. They didn't go for the next interview step. Maybe it was the coding stumble, maybe it was because I didn't know how many people had been on the moon, maybe it was, because I put them under time pressure. I had another company with an offer waiting in the wings, and I didn't want to decline that firm offer just for the chance for another interview with BO, or start that job, and then 2 weeks later end up getting an offer from BO.