booksreddit.com:Cracking the Coding Interview

Cracking the Coding Interview, Fourth Edition: 150 Programming Interview Questions and Solutions

675

In 4 days I have a technical interview with a company I really want to impress. I’m terrible at technical interviews. How can I best prepare?
Now in the 4th edition, Cracking the Coding Interview gives you the interview preparation you need to get the top software developer jobs. This book provides:* 150 Programming Interview Questions and Solutions: From binary trees to binary search, this list of 150 questions includes the most common and most useful questions in data structures, algorithms, and knowledge based questions.* Ten Mistakes Candidates Make — And How to Avoid Them: Don’t lose your dream job by making these common mist…

More about the book on Amazon

Most upvoted comment

Most popular programming book on Reddit. rank no. 45

In 4 days I have a technical interview with a company I really want to impress. I’m terrible at technical interviews. How can I best prepare?(r/technology)

From the book Cracking the Coding Interview:

>There are many scary stories floating around about Google interviews, but it’s mostly just that: stories. The interview is not terribly different from Microsoft’s or Amazon’s. However, because Google HR can be a little disorganized, we recommend being proactive in communication. A Google engineer performs the first phone screen, so expect tough technical questions. On your on-site interview, you’ll interview with four to six people, one of whom will be a lunch interviewer. Interviewer feedback is kept confidential from the other interviewers, so you can be assured that you enter each interview with blank slate. Your lunch interviewer doesn’t submit feedback, so this is a great opportunity to ask honest questions. Written feedback is submitted to a hiring committee of engineers to make a hire/no-hire recommendation. Feedback is typically broken down into four categories (Analytical Ability, Coding, Experience and Communication) and you are given a score from 1.0 to 4.0 overall. The hiring committee understands that you can’t be expected to excel in every interview, but if multiple people raise the same red flag (arrogance, poor coding skills, etc), that can disqualify you. A hiring committee typically wants to see one interviewer who is an “enthusiastic endorser.” In other words, a packet with scores of 3.6, 3.1, 3.1 and 2.6 is better than all 3.1s. Your phone screen is usually not a strong factor in the final decision. The Google hiring process can be slow. If you don’t hear back within one week, politely ask your recruiter for an update. A lack of response says nothing about your performance.

>Definitely Prepare: As a web-based company, Google cares about how to design a scalable system. So, make sure you prepare for questions from “System Design and Memory Limits” Additionally, many Google interviewers will ask questions involving Bit Manipulation, so please brush up on these questions. What’s Different: Your interviewers do not make the hiring decision. Rather, they enter feedback which is passed to a hiring committee. The hiring committee recommends a decision which can be—though rarely is—rejected by Google executives.

Permalink

More details about a book.

Additional Information

Subreddits

cscareerquestions

Number Of Links

9

Sum Of Upvotes

90

Amazon Price

$49.49

Book Binding

Paperback

Type Code

ABIS_BOOK

Book Author

Gayle Laakmann

Book Edition

4

Book Publisher

CreateSpace Independent Publishing Platform

Book On Amazon

Cracking the Coding Interview, Fourth Edition: 150 Programming Interview Questions and Solutions

Post Title

In 4 days I have a technical interview with a company I really want to impress. I’m terrible at technical interviews. How can I best prepare?

Reddit Gold

0

Post Permalink

/r/technology/comments/16t68k/google_buys_1_billion_plot_of_land_for_new/

More about the book on Amazon