I was approached by an external headhunter who knew the VP of HR over there. Eventually, I had a one-on-one with the internal recruiter, which went pretty well. Then I had an initial phone screen with a software director there. He was very technically oriented; we talked about how I would go about troubleshooting a wonky Wi-Fi connection. He seemed very impressed.

Had the face-to-face interview. Things did not go so well. They asked me questions about TCP, how to bring up Linux in a new embedded system, pthreads, etc. I was flailing so badly, I could hear the sighs of exasperation from the director that phone-screened me and the software engineer they sent my way.

The guy finally came out and told me I wasn't what they hoped for (a bit smugly, I found). I concurred and was sent on my merry way. However, they did alienate me to the point that I returned the Roku I bought from them to try out. It's interesting, but nothing I haven't seen before (just in a smaller package). To me, they are just a one-trick pony within a low-margin consumer market.

So if you want to go, go because you'd like to work on their tech (which seems interesting), but bring your A-game. Anything less, and you are mud to them.

Describe the flow control that happens in a TCP connection.

You power on a Linux system. What happens (in exquisite detail) while it boots up?