I asked this on reddit. The one thing about tech interviews. They could ask anything. Literally any facet of technology. How do you prepare for being asked anything?
In the Gayle book, they go from binay trees, to bit manipulation to queues, etc, etc. Of course that won't even get touched in some technical interviews, it will be more knowledge based, (Describe polymorphism).
I rarely get the complex algorithms (I am not in Silicon Valley) but I get a great deal of logic questions or draw this abstract concept out on the board. And it is hard for me to deal with NOT knowing a problem.
For example, if SQL is on the job description, might as well cover every aspect of SQL which aren't really covered in the technical interview books. How do indexes work, etc, etc? Venn diagram outer joins.
Some interviews are just unfair and there isn't really anything you can do to prepare, so don't waste your time worrying about it. Try to get a good story out of it and pity the company (I know, cold comfort if you need a job).
Decent interviews will stick to what's on your resume: "you say you spent 10 years working on networking internals, can you tell me about how you'd design a reliable network protocol?"
You can find lists of common interview questions online for almost every technical topic, so look up "SQL interview questions" and make sure you can answer the common ones if you're worried about them.
In the Gayle book, they go from binay trees, to bit manipulation to queues, etc, etc. Of course that won't even get touched in some technical interviews, it will be more knowledge based, (Describe polymorphism).
I rarely get the complex algorithms (I am not in Silicon Valley) but I get a great deal of logic questions or draw this abstract concept out on the board. And it is hard for me to deal with NOT knowing a problem.
For example, if SQL is on the job description, might as well cover every aspect of SQL which aren't really covered in the technical interview books. How do indexes work, etc, etc? Venn diagram outer joins.