Rating: 
Summary: I like this book
Review: This is a book about programming interview---we don't need the topics as "How to write a resume here!!" I've been to Microsoft's interviews couple of times, what they were looking for is a solid knowledge in algorithms and strong problem solving skills. This is just what this book aimming at.
Rating:
Summary: Tricks and puzzles in job interviews
Review: This is a fascinating book that has a lot of challenging (and fun) puzzles. They were all gleaned from actual programming job interviews with companies such as Microsoft. This book will make you less stressed out for your next interview... it'll prepare you!
Rating:
Summary: Great book!!
Review: This is a really good book for people preparing for tech interviews. Its also a great read for developers already working as it gives a pretty good explanation of different coding concepts like data structures, etc...One of the good things about the book is that the authors try to give multiple solutions to a problem.
Rating: 
Summary: of questionable value
Review: This may be valuable for new grads getting their first job, or people who want to do sanity a check before looking for a new position.In the bulk of this book, the author covers what he feels are common programming related interview questions. Almost all of the examples are in C, except for a few oddballs (one is done in Perl, which doesn't exactly lend itself to clarity). I don't understand why the author chose C. He states it is the "language of choice" for interviewers. Most universities are making their grads think OO these days. While they may have a few projects in C, the majority of their experience is going to be in C++ or Java, or C# in the near future. If a new grad is going to interview, and they state that they aren't that great with C but they know C++ or Java really well (which is probably true for most new-grads), I would be very, very surprised if this was an issue. What if it was an issue? As a new grad, would you want to work somewhere where your interviewers could only think in C? Regardless, the common feature here is OO. The book misses the boat on this point. I have been working in the Java space for quite some time and the non-OO examples were hard for me to follow, and I found myself not wanting to follow them because they seemed inelegant. I would have preferred to see them in (OO) pseudo code. The rest of this book covers interviewing tactics, a few logic puzzles, and a small section on resume writing. The sections on interviewing tactics and resume writing assumed a very low experience level and seemed more like they were written for high-school grads than for college grads let alone experienced software developers. The puzzle section was fun.
Rating:
Summary: There are interviews and there are interviews
Review: Whew! What a surprise this book was! I've been going to programming interviews for a dozen years and I've NEVER been put under a hot-seat and asked to do impromptu coding of linked lists, binary trees and the like. My programming interviews seem to always revolve around the languages and products I've used, with the "buyer" trying to find an exact match for everything they have. Like... "Do you know Sybase?" followed by 7 or 8 Sybase questions... "Do you know servlets" followed by 7 or 8 Java servlets questions... "Do you know Rational Rose?" followed by 7 or 8 Rational Rose questions... etc. And I've NEVER had an interview with technical staff go beyond 2 hours: in the book they mention a FULL DAY'S interview... with lunch! I operate in the New York City-area application development arena. Is it me or is it these authors... it's like these folks operate on a different planet than I do. I think in fact they probably do: and I think this book is mistitled. I think any second edition should be retitled "SOFTWARE ENGINEERING Interviews Exposed", because I think that's the arena they've really been operating in. Plus, they mention showing up to an interview sans necktie: that would be instant "flunk" where I come from... even if the staff IS dressed casually themselves. Maybe an even better title would be: "WEST COAST SOFTWARE ENGINEERING Interviews Exposed" (not that there's anything wrong with the west coast).
| 
