Cracking the PM Interview: How to Land a Product Manager Job in Technology

Cracking the PM Interview: How to Land a Product Manager Job in Technology by Gayle Laakmann McDowell (Author), Jackie Bavaro

This book provides an introduction to the career of a product manager and the interview process typically involved. There are examples of some of the types of questions asked and proper ways to solve them. There is also a section on resumes. You want to have accomplishments written in the past tense, not activities that you were told to do. It is good to tell stories when asked. Bring up accomplishments as you are going. Talking in bullet points is also good. 

Some of the book is dated. (Yahoo! and Twitter are not at the top of anyone's lists now.) It also spends a little too long on programming questions (they have other books for that.) There is other content like case studies that also feels repetitive from their other books, but overall, this book has a better variety of content.

Programming Interviews Exposed: Coding Your Way Through the Interview 4th Edition

The Fourth Edition of Programming Interviews Exposed is a solid refresher on core computer science fundamentals. It is fairly concise. It presents core principles and provides a few very well explained problems. It does not have the theoretical depth of a text book or provide a vast array of every type of problem you may see. This makes it a great book for somebody wanting to brush up. The problems are generally language agnostic, though Java seems to be most frequently used in examples. (C++, C# and JavaScript also make appearances.) It does go into bits of more high level technologies such as map-reduce, SQL and AI, however, the focus is on the fundamentals and the process for solving problems quickly.

Cracking the Coding Interview, 6th edition

Cracking the Coding Interview is an interview preparation book that emphasizes coding. It provides some general interview background, then dives deep into programming questions. The questions are organized by category and provide details answers. There is almost enough information there, to eliminate the need to go back to the old algorithms book.
The bulk of the book is the "question" section, with answers. They were divided into a number of different categories, with "C++", "Java" and "Hard problems" towards the end.
The questions seem to vary significantly. Some are nearly trivial, while others have multiple pages of code to answer. (This could be much more extreme than you are expected to find in an interview.) I found myself rushing through some sections as the answers just got to be too far "out there." They also seem to be somewhat dated. Map Reduce is treated as a cutting-edge solution rather than common implementation. There is also a ton of boilerplate (in Java) for many of the questions. It would be nice to explore different languages. Sometimes, the super complex java solution could be much more easily done with a different programming language.

Programming Interviews Exposed, 3rd edition

Programming Interviews Exposed is one of the earliest of the genre of "programming interview books". I had read the third edition, though the fourth edition is now available. It covers the entire interview process from job search to salary negotiation and the actual interview. For coding interviews, it discusses good practices and provides some sample questions and types. However, the goal is not to provide a library of possible questions, but rather to cover some high level topics and guide the thinking process. In doing so, it does a good job of helping you to mentally prepare for the programming interview, including some of the curve balls that may be thrown.

Ace the Programming Interview

Ace the Programming Interview is the "coding interview" book that always seems to be available at the library. I have never seen it recommended by a big tech company for interview prep. It was written by a European and has more of a British Focus. It also feels dated.
The first section of the book deals with general interview preparation. It talks about preparing a resume, going through the phone and in person interviews and even negotiating the offer. It also covers general preparation and pitfalls. Their is advice here both for interviewers and interviewees. The author points out some of the pitfalls that we we run into in interviews. Some times and interviewer will ask questions that are too specific, or expect a candidate to be able to provide the same type of answer that they have implemented for a given problem.
The questions and answers are interspersed with the review of CS fundamentals. The author seems to be moth experienced with windows technologies. However, others are also mentioned. The sections cover common things such as big O notation, as well as such topics ans choosing the appropriate tools.
Other interviews tend to focus more on the practical programming questions. This book has some of that. It also attempts to provide more coverage of language-specific programming questions. (Alas, that can make it quickly dated as languages evolve or go out of favor.) However, it shines more in the general theoretical questions. Why are software projects usually late? Why do programmers do certain things? It provides good insight for preparing for a general programming interview, but wont necessarily prepare you for the grind of Google or Amazon technical questions.