I used the same approach last time I was interviewing -- keeping a wiki of "everything I knew or sort-of-knew about computer science" and then trying to fill in

I used the same approach last time I was interviewing -- keeping a wiki of "everything I knew or sort-of-knew about computer science" and then trying to fill in the gaps. At a glance, a few things I would throw in are: * UTF-8 (a basic understanding of how wide characters are encoded) * streaming algorithms * lock-free data structures (what they are and why you probably shouldn't implement one) In some sense it's like trying to hold the entirety of CS in your head for one day. You might spend 30 minutes learning about something so you can mention it as an aside. But... I think it's worth it, more for the knowledge. Knowing that something is possible (e.g. encrypted search) opens doors in the same way that working cross-discipline can.