But what that means is that there's a lot here that you could go through. It's much more important that you have that breadth of knowledge than you are really strong on graphs, but you don't know anything about recursion or dynamic programming. So there are three things that I want to talk about today. Because that makes sure that you actually cover all the topics that you need to. Object-oriented design, another thing that may or may not come up but is actually really valuable to have a good grasp on. So as you're studying I highly highly recommend that you go reach out beyond the book and use the book just as a guideline for what topics you need to study in more depth. And it doesn't even matter you don't even need the most recent edition any edition will do. Read the book twice with careful hand-writing practice on each question. Read the book twice with careful hand-writing practice on each question. Got Amazon offer. In the depth-first version, that's probably what you would initially think of doing. So for example if you were doing your interviews in Java you wouldn't need to study the chapter on C and C++. You don't have to go super deep in it but it is a valuable thing. And that leads me to my sort of core set of chapters that you should focus on. Especially because some of the later chapters are harder. Also, my Java Solutions to Cracking the Coding Interview, 6th Edition. When you're studying the first thing I recommend is do chapters one through five and seven through ten. Interview Cake is an awesome resource for more practice interview questions. I think that it's something that a lot of people are scared of which is why it's included in the book because questions like how many ping-pong balls fit on a 747, or how many windows are there in New York City seem like difficult questions to ask to answer. Covering the database chapter would be helpful and there's also the medium and hard problems at the very end that are gonna be useful if those if you get through everything else. If you break up your time evenly for each chapter you may find yourself running out of time as you're getting closer and closer to your interview. And third, make sure that you go outside of Cracking the Coding Interview and look at the other resources that are out there. So just to recap real quick. So how do you organize your time? But how do you know that their code is actually correct? And once you feel really good about arrays and strings you move on to linked lists. Contents Now in the 6th edition, Cracking the Coding Interview gives you the interview preparation you need to get the top software developer jobs. I used this book to prepare for my interviews with Microsoft, and Gayle's insight gave me a great idea of how to prepare and how to ace the interview. So chapters 1 through 5 and 7 through 10 basically cover all of the fundamentals that you would need to know for your coding interview. Introduction. Not only does it give practice problems and detailed answers, but it also gives you good advice about how to approach the problems as well as what to expect. So I hope those tips were helpful for you. So as you can see this is a really thick book. - Larry, Amazon.com "This book is a must-have for any interview candidate. With Cracking the Coding Interview, I think it is the best book for prepping for interviews and I highly highly recommend that you get a copy if you haven't already. And yes looking at yes the book does include a pretty good list of topics, but it doesn't really cover those topics in great detail. Sam has helped thousands of students through his blog and free content -- as well as 400+ paying students -- land jobs at companies such as Google, Amazon, Microsoft, Bloomberg, Uber, and more.