Coding Interview Questions

The other "big hitter" coding interview books which everyone knows about and which I review and compare frequently for our library purchasers include:Aziz,  Elements of Programming Interviews: 300 Questions and Solutions by Aziz, Adnan, Prakash, Amit, Lee, Tsung-Hsien 1st (first) Edition (10/11/2012) , 2012, 481 pages, 6 x 9, $25, 300 problems (mostly C++, concurrency in Java, discrete math in formulas and English)McDowell,  Cracking the Coding Interview: 150 Programming Questions and Solutions , 2011 (5th edition), 500 pages, 6 x 9, $23, 150 problems, (mostly all Java except of course the C, C++ question sections!)Guiness,  Ace the Programming Interview: 160 Questions and Answers for Success , 2013, 419 pages, 6 x 9, $20, 160 problems, (mostly Java and C# but some unusual JavaScript, SQL, Ruby and Perl examples too)Mongan,  Programming Interviews Exposed: Secrets to Landing Your Next Job , 2013 (ed. 3), 301 pages, 7.4 x 9, $18, 150+ problems (C, C++, C#, Java).All four of these are for VERY ADVANCED programmers, and assume you already know a LOT about trees, hash tables, arrays, matrices, etc. KARUMANCHI IS REFRESHINGLY DIFFERENT!Nara does NOT assume you're a veteran programmer or a recent high level grad in the dream interview! He assumes you (maybe) know a little IT and a lot of Engineering or Math, for example, or that you're an older manager who is great at systems and strategy but rusty on coding. OR, maybe you're on the embedded or data science side and your programming is very deep (circuit/assembly) or broad (data mining) but not necessarilly OOP style algos and data structures.There is no book quite like this, because, even though it is in a different category than the 4 biggies above, it should appeal to a much bigger audience, not only for a certain type of interview (a little or no direct coding but perhaps managing people who do?) but a vast range of newer job types. Example: "Data Scientist" is a brand new, warp speed growing occupation with starting salaries as high as 200K US, and some firms are even creating "CDSO" positions (Chief Data Science Officer).The other thing Nara does, is give progressively more detailed and complex solutions to the same problems-- allowing you to go as shallow or deep as you'd like. From my field (math) an example would be: If you can code at interpreter level in Maple or Mathematica or GNU, it will compile and run, but not nearly as fast as if you know C++, algos, data structures and even a little assembly.If the job description says you'll be tested with phony problems to actually code in the interview, the other big four above are the ticket, but if the position only needs you to UNDERSTAND algos and DS's, Karumanchi is awesome. It also is a great (good sized), up to date REFERENCE for all levels of IT from Data scientists to math, engineering, research, physics, chemistry, etc. Even "R" folks like me can learn a LOT. When I create tutorials, if the students want a specific language to supplement this, I have them review a specific, usually older and used text like Lafore ( Data Structures and Algorithms in Java (2nd Edition) ) or any other in Python, C++, R, etc. Highly recommended for that somewhat different, unique, but GREAT job-- go for it and good luck!Library Picks reviews only for the benefit of Amazon shoppers and has nothing to do with Amazon, the authors, manufacturers or publishers of the items we review. We always buy the items we review for the sake of objectivity, and although we search for gems, are not shy about trashing an item if it's a waste of time or money for Amazon shoppers. If the reviewer identifies herself, her job or her field, it is only as a point of reference to help you gauge the background and any biases.

I must confess that his book is one of the most awesome ones that anyone who is interested in data structures, algorithms, meta-heuristics, could come across. The book is good for someone looking out on an intermediate to advanced level stuff on aforesaid subject, and its has ample stuff for any newbie enthusiast too. While this book is an excellent one from the interview point of view, it would serve equally well to those who work, and those who love tackling teasers in their past time.The subject is dealt in great detail and problem solving is the primary focus, which I truly loved. It saves you a lot of time to have all kinds of questions aggregated at one place of varying difficulty, rather than having to look for them on internet or elsewhere. The best part about the book is the organization and approach to problems. It is not merely a question and answer book, it instigates you to think about the problem, come up with something and the compare it against what is provided as a solution. The language is lucid and easy to understand and the typical approach towards any problem is to come up with a solution anyhow (say O(n^2)) and then going on improving the complexity to O(NlogN) and then finally to an O(N). All the examples are annotated with comments and their space/time complexities.The approach is more of a critical-thinking one, the book helps you build an aptitude towards attacking a problem. While most books give you only the best algorithm towards a problem (and you never get to learn about the bad ones, which is necessary too), this book slowly builds up from just a possible solution to the best possible one. For those who think Levitin, CLRS, Cracking the coding is do-able, try cracking the whole of this!!!!

First, the book is poorly organized and has typos. If you are to write a book, no matter what subject, you must go to the end of the world to make sure there is absolutely no typos. It's just simply a turn-off. You can' judge a book by its cover but definitely can with a book with typos. Not only typos that I have problems with, there are many instances in the book where I found the sentences are cut short. That is, instead of adding two or more sentences to make the subject clear and complete, the author simply chose to stop short, probably in an effort to save space since this book attempts to covers so many areas. In addition, the table of content is a mess. For example, in the first chapter of Programming Basics, there are bullet items from page 13 to page 28 but from page 31 onward to page 71, there is only one item called 1.13.9 Message Passing, but in this section of 40 pages, it contains questions and answers of all sorts of subjects ranging from C++ smart pointers to Java this or that. Secondly, the material covered is not deep enough to make good impressions in a technical interview. This is probably because the author tries to cover so many subjects. For example in the database section, I don't see at least one insightful question about database except the common stuff like what is trigger or index. Also, as I read more thorough thep ages, I found some of the materials are either incomplete or partially or totally incorrect. For example: in the answer to adapter design patter, the author was correct in explaining the purpose of the pattern but the example given was not correct. The classic implementation of adapter is to publicly inherit the new interface and privately inherit the old component and let the old component participate in the implementation of the interface. None of that was given in the example.

I expected this book to have new problems but 75% of this book is the same as data structures by karumanchi and only the first few topics are differentIf you have purchased Data Structures and Algorithms book by Karumanchi already do not buy this one

Although all of narasimha books related to ds and algo have same questions and solns but these are enough to clear an interview.You need to do coding practice on online platforms side by side to clear coding rounds.This book covers all the concepts and approaches to a problem which makes it apt book to prepare for f2f rounds.It includes some questions related to topics like OS, Networking,database etc as well but this book is mainly for ds and algo.

Coding Interview Questions It's very apt for preparing for a technical interview,(the technical programming ones)All the necessary concepts and Subjects such are covered such as Computer Networks, Programming concepts, and Data Structures.A good preparation material for brushing technical skillset. Coding Interview Questions

The book is full of typos which really confuses the reader. Once a reader starts catching typos, it is natural that the reader loses confidence on the book content. I am surprised how people have given a good rating to this book. It is my earnest request to the author to do proofreading and bring out an errata. It will hugely help the book owners.On top of that the print is pathetic. Even in a dark room under a table map, the fonts are illegible.

Very help full and very simple language to under stand the book.