{ Cracking The Coding Interview: 150 programming Q&A } 5th edition Part I

Chap 1. The interview process

TOP 10 mistakes:

1. practicing on a computer

2. not rehearsing behavioral questions

3. not doing a mock interview

4. trying to memorize solutions

5. not solving problems out loud

6. rushing

7. sloppy coding

8. not testing

9. fixing mistakes carelessly

10. giving up

If possible, you can tell the interviewer you know the question.

Chap 2 Behind the scenes

Tell some cultures of famous IT companies such as MS, FB...

Chap 3 Special situations

Don't ignore test.

Program and Project Managers:

Handling ambiguity, customer focus (attitude), customer focus (technical skills), multi-level communication, passion for technology, teamwork/leadership.

Chap 4 Before the interview 

1. Getting the right experience:

take the big object classes, get an internship, start something.

2. Building a network

a good network should be broad and close.

use websites such as meetup.com to find alumni.

walk up and say hello to people.

be open about your interests, and talk to people about theirs.

follow up by adding linkedin or fb.

be helpful when others are in need.

3. Writing a great resume

"accomplished X by Y resulting Z"

Languages: Java(expert), C(proficient), Python(prior experience)

Chap 5 Behavioral questions

Fill the grid with key words:

common questions	Project 1	Project 2	...
most challenging
what you learned
most interesting
hardest bug
enjoyed most
conflicts with teammates

Q1: What are your weaknesses?

pay good attention to details, but also helps me to avoid bugs.

Q2: most challenging part of the project?

don't say "I have to learn new languages and technologies".

Q3: ask interviewers a question?

1. Genuine questions: what's the ratio of testers to developers to program managers, what is the interaction like, how does project planning happen on the team.

2. Insightful questions: what technology or tools do your company use frequently, how do you handle the problem Y?

3. Passion questions: I'm not familiar with technology X, but it sounds like a very interesting solution. Could you tell me a bit more about how it works?

Be specific, not arrogant.   Limit details.   Give structured answers. (Nugget first 重申问题, SAR: situation, action, result)