I haven't followed the recent updates to our interview process closely but we traditionally looked for general knowledge over specific knowledge. I'm not sure how much that has changed recently though.
Edited In Response To Parent Edit: Thanks for asking! We should definitely make it clearer if there are differences per role.
"looked for general knowledge over specific knowledge" - incidentally, I was rejected because I could not answer (to the interviewer's satisfaction) how to implement an in-memory LRU cache. I made some good recommendations but the interviewers were expecting a very specific answer which exactly matched http://www.programcreek.com/2013/03/leetcode-lru-cache-java/
> looked for general knowledge over specific knowledge
This is one commonly thrown BS regarding interviews. At the end of the day it is all about one-dimensional usual algorithmic questions.
Regarding LRU cache, I think this is one of less crazy interview questions. In one phone interview, I had to solve a DP problem, code it perfectly and pass all the test-cases on HackerRank in less than twenty minutes. I am not certain how many developers out there can pass such interviews without months of preparation in such situations. Tech interviews are basically programming contests. I am not against programming contests or algorithmic questions. But it seems the interview questions are getting crazier day by day.
Some orgs require only scripting, some go so far as to want application engineers who also know everything about AWS for devops/ops roles.
Disclaimer: I already asked via their google form for this information to be added in their docs.