Jetzt eintauschen
und EUR 5,00 Gutschein erhalten
Möchten Sie verkaufen? Hier verkaufen
Der Artikel ist in folgender Variante leider nicht verfügbar
Keine Abbildung vorhanden für
Keine Abbildung vorhanden

Den Verlag informieren!
Ich möchte dieses Buch auf dem Kindle lesen.

Sie haben keinen Kindle? Hier kaufen oder eine gratis Kindle Lese-App herunterladen.

Cracking the Coding Interview, Fourth Edition [Englisch] [Taschenbuch]

Gayle Laakmann , Gayle Laakmann McDowell
3.0 von 5 Sternen  Alle Rezensionen anzeigen (1 Kundenrezension)

Erhältlich bei diesen Anbietern.

Dieses Buch gibt es in einer neuen Auflage:
Cracking the Coding Interview Cracking the Coding Interview 4.0 von 5 Sternen (1)
Derzeit nicht verfügbar.

Kunden, die diesen Artikel angesehen haben, haben auch angesehen


  • Taschenbuch: 310 Seiten
  • Verlag: Createspace; Auflage: 0004 (15. Oktober 2008)
  • Sprache: Englisch
  • ISBN-10: 145157827X
  • ISBN-13: 978-1451578270
  • Größe und/oder Gewicht: 1,6 x 15 x 22,5 cm
  • Durchschnittliche Kundenbewertung: 3.0 von 5 Sternen  Alle Rezensionen anzeigen (1 Kundenrezension)
  • Amazon Bestseller-Rang: Nr. 344.377 in Englische Bücher (Siehe Top 100 in Englische Bücher)

Mehr über den Autor

Gayle Laakmann McDowell's interviewing expertise comes from vast experience on both sides of the desk. She has completed Software Engineering interviews with - and received offers from - Microsoft, Google, Amazon, Apple, IBM, Goldman Sachs, Capital IQ, and a number of other firms.

Of these top companies, she has worked for Microsoft, Apple and Google, where she gained deep insight into each company's hiring practices.

Most recently, Gayle spent three years at Google as a Software Engineer and was one of the company's lead interviewers. She interviewed over 120 candidates in the U.S. and abroad, and led much of the recruiting for her alma mater, the University of Pennsylvania.

Additionally, she served on Google's Hiring Committee, where she reviewed each candidate's feedback and made hire / no-hire decisions.

She assessed over 700 candidates in that role, and evaluated hundreds more resumes.

In 2005, Gayle founded to bring her wealth of experience to candidates around the world. Launched first as a free forum for interview questions, CareerCup now offers a book, a video and mock interviews.

Gayle holds a bachelor's and master's degree in Computer Science from the University of Pennsylvania and an MBA from The Wharton School.

In diesem Buch (Mehr dazu)
Ausgewählte Seiten ansehen
Buchdeckel | Copyright | Inhaltsverzeichnis | Auszug | Stichwortverzeichnis | Rückseite
Hier reinlesen und suchen:

Eine digitale Version dieses Buchs im Kindle-Shop verkaufen

Wenn Sie ein Verleger oder Autor sind und die digitalen Rechte an einem Buch haben, können Sie die digitale Version des Buchs in unserem Kindle-Shop verkaufen. Weitere Informationen


5 Sterne
4 Sterne
2 Sterne
1 Sterne
3.0 von 5 Sternen
3.0 von 5 Sternen
Die hilfreichsten Kundenrezensionen
1 von 1 Kunden fanden die folgende Rezension hilfreich
3.0 von 5 Sternen Good. Not very good. Recommended 24. April 2011
It's a good book for it presents a comprehensive list of exercises and topics important to review and practice for an interview. It's beneficial to code and code different programs that involve different algorithms, data structures, concepts, ... and the problems presented in this book are good for that. It's for this that I do recommend this book to any serious candidate: the more you do, the better.

Having said that, I found some times that the author sometimes didn't have much idea herself with coding and computer science. For example in Chapter 8 Recursion, she mentions that recursive algorithms may be very space inefficient but she doesn't even mention tail recursion. Other omissions were equally appalling.

Solutions were not all or very little explained, some contained errors, and I could improve further quite many solutions. Also few solutions were a surprise. In this respect reading On Lisp or Common Lisp by Paul Graham, for example, or books by Joshua Bloch in the Java world, gives you many more WOW! moments

Bottom line: get this book and review throughly all presented problems and concepts. Code first (think first), and then, if needed, check the solutions. Then get another set of problems (for example those in Programming Pearls) and code their solutions. Then code some more.
War diese Rezension für Sie hilfreich?
Die hilfreichsten Kundenrezensionen auf (beta) 4.4 von 5 Sternen  44 Rezensionen
34 von 35 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen Practice makes perfect 10. Mai 2010
Von Lei Gong - Veröffentlicht auf
My background: worked as a software developer for 5 years before changing companies and I needed to freshen up my interview skills. Having conducted dev interviews before, I wanted to be as prepared as possible.

I used this book as a practice guide for my interviews with Microsoft, Amazon, and Google. Got offered to two of the companies through practicing the questions in this book over and over again. I was only caught off guard by one or two questions during my interviews through at least 15 interview loops. Most of the interview questions at the above companies follow the same two dozen or so coding patterns and the questions in this book thoroughly covers them. Learn the coding patterns from this book and you won't be surprised or nervous during your loops. I tried not to act too surprised when 1/5 of the questions from my interviews were straight from the book.
48 von 52 Kunden fanden die folgende Rezension hilfreich
2.0 von 5 Sternen Nice collection of problems, but unpolished and full of errors, lacks explanation. 20. Februar 2011
Von RRS - Veröffentlicht auf
Format:Taschenbuch|Von Amazon bestätigter Kauf
I'm a software engineer at a billion-dollar company, with about 10 years of experience after college. I decided to interview at a promising early-stage startup and thus bought two interview books (this one and Programming Interview Exposed) to brush up on things and get back that interviewing magic. (I had been at my last job for over 5 years, so it has been a while.)

This book is good in some ways. The best thing about it is the set of problems in it. It's quite comprehensive: every area I could think of is covered. Even the knowledge-based chapters (e.g., on threading, or networking, or low-level programming) are surprisingly up-to-date and representative of the type of stuff that is asked. So if you want to get a big list of problems and at least a good stab at the solutions (if you're stuck), it's much better to get this book (as opposed to looking for problems on the Internet).

So why only two stars? The biggest issue is that there are tons of errors in this book. I can't tell you how many, but I know I personally found at least 5. Some are trivial -- the book may say something is O(n) space, when it's O(1) space. Some are egregious -- the smart pointer implementation, which is compressed to one page in the solution section, is utterly broken. (For example, operator=() fails to give up ownership of what it points to before the assignment, before taking ownership of the new object. That is a completely wrong solution to the problem! What if an inexperienced reader reads this section and becomes confused?) Books like this should not have mistakes, especially not a 4th edition.

Sometimes the problem isn't clearly stated, so that trying to solve it is very difficult without more explanation. Flipping to the solution reveals what the problem was, but then what was the point?

In general, when reading this book, once gets the sense that it was thrown together. It seems like it wasn't edited in the most basic ways; for example, URLs are referred to as "urls" all over the text. That doesn't really matter, of course, but it is indicative of the type of publication it is. It's like someone wrote up an elaborate text file and then basically just sent it off to be published. Very cheap and kind of unprofessional.

Finally, the book's solutions (while usually 100% correct) typically don't try to explain and expose the thinking process behind a solution. True, sometimes it's quite obvious, so there's no point. But sometimes, it's not obvious -- it would be helpful to a potential interviewee to get a glimpse into HOW to get to the solution, instead of basically just being given the solution. This isn't always the case in the book, but most of the time it is.

So, there you go. If you want a nice collection of problems that's representative and up-to-date, this is your book; but don't expect an error-free and carefully edited or explained work.
51 von 57 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen A 'Must-study' before taking a Tech Interview 27. März 2011
Von ginnie - Veröffentlicht auf
If you are planning to appear for a technical interview at any big software-firm, I highly recommend studying this book.

When I started my preparation, the entire process seemed really daunting. There is so much to study, and there is vast amount of study-material available out there. I was really confused on what/how to prepare. A friend of mine suggested me this book and so I read it.

To summarize, this book is an awesome compilation of problems, strategies and approaches you must know for doing well in a Tech interview.

It starts with chapters focusing on non-coding aspects (company-info, resume, behavioral etc.). I feel that, thoroughly covering just these first 30 pages is suffice for doing well in the 'HR' parts of tech-interviews.

After that, it contains 150 questions grouped by categories, covering all the relevant areas. And finally it has useful information, solutions and discussions for all the questions.

Qu. "If I memorize solutions for all these questions, Can I crack an Interview?" Ans. No Way!
Rather, if you slog through these questions, learning techniques; I am sure you will be able to solve questions on that day.

Solving problems through the book, I learnt different [ingenious] approaches. And with practice, I was be able to [/tried to] identify patterns in new questions that I faced.

I particularly love 3 chapters- "Recursion", "Moderate Interview Problems", "Hard Interview Problems". Because they contain some really neat algorithms :)

Hope this review helps.. And all the best for your interview :)
20 von 20 Kunden fanden die folgende Rezension hilfreich
4.0 von 5 Sternen "Cracking" vs "Programming interviews exposed" 13. Mai 2011
Von Margaret Gilligan - Veröffentlicht auf
"Cracking the coding interview" (4th ed, 2008) by Gayle Laakman is a
good book, but so is the very similar book "Programming Interviews
Exposed: Secrets to Landing Your Next Job" (2nd edn), John Mongan,
Noah Suojanen and Eric Giguère (2nd edn, 2007) . Which should you
choose? Here are the main differences:

- "Exposed" is much more readable: it explains the solutions in
English before giving code, whereas "Cracking" often just presents
code with minimal explanation. Another nice thing is that "Exposed"
presents the solution in stages, so you can read the first part of the
solution to get a hint, and then try again. By contrast, "Cracking"
just gives the key idea right away, so even a "peek" at the solutions
means it's game over (modulo coding issues, which are usually easy).

- "Cracking" has more questions, and they generally seem to be a bit
harder. They are sorted in order of increasing difficulty, which is

- "Cracking" gives solutions in Java, although the code seems to have
some errors (see other reviews on amazon). "Exposed" gives solutions
in a mix of languages (C++, Java, C#), although they only use one
language per question.

- "Cracking" contains some grammatical errors (for example, Gayle
often mixes up "eg" and "ie"). In addition, many explanations would be much clearer with
an example.

- Both books are similar in length (about 300 pages), and their "non
technical" advice is very similar.

- Overall, "Exposed" is easier to read, but "Cracking" has more
content. Tough call.

There is also the good book "Algorithms For Interviews" by Adnan Aziz
and Amit Prakash (2010), which contains much harder questions,
focusing on clever algorithms and not on implementation details. Do
not attempt this book before mastering "Cracking" and/or "Exposed",
you will find it demoralizing! But it's probably worth trying some of
these harder problems, to see how "fancier" algorithms (like Dijkstra,
or max-flow min-cut, or dynamic programming) can be applied in
creative ways.
39 von 44 Kunden fanden die folgende Rezension hilfreich
3.0 von 5 Sternen Still have many errors even in 4th edition 24. September 2010
Von laozi2000 - Veröffentlicht auf
In general this is a good book to cover technical interview questions and some very useful tips for how to prepare and act for the on-site interview on technical questions. However, there are still several obvious errors in the books, especially codes and some formulas. For example,

in page 47 Question: What is the running time of this code?
The two sample codes are exactly the same and the first one should be something not using StringBuffer().

And in page 258, in the middle paragraph
Time_Stamp(P2_1) - Time_Stamp(P2_N)
should be
Time_Stamp(P2_1) - Time_Stamp(P1_N)

Hope this error can be identified by readers and they can still get the job.
Waren diese Rezensionen hilfreich?   Wir wollen von Ihnen hören.
Kundenrezensionen suchen
Nur in den Rezensionen zu diesem Produkt suchen

Kunden diskutieren

Das Forum zu diesem Produkt
Diskussion Antworten Jüngster Beitrag
Noch keine Diskussionen

Fragen stellen, Meinungen austauschen, Einblicke gewinnen
Neue Diskussion starten
Erster Beitrag:
Eingabe des Log-ins

Kundendiskussionen durchsuchen
Alle Amazon-Diskussionen durchsuchen

Ähnliche Artikel finden

Ihr Kommentar