1.     Tell me about yourself.
Suggested response: I received a B.S. from San Jose State University in computer sciences with honors in 2009. I worked for xyz.com since then... (Highlight your education and companies you worked for in chronological order. The interviewers are not interested in lengthy details. They are not interested in where you were born or what your hobbies are, either.) Highlight the relevant experience, particularly the project you have done. Take for example, if it’s a system level/network company, talk about the OS class/project that you’ve had.  If it’s a database company, mention the database project etc.  Don’t be too short (<3-4 sentence), and don’t be too long.   The idea is to give the interviewer enough information so that he/she can ask more detail in the areas that he/she is interested in.  Also, the interviewer is looking for how well you describe yourself, which translates to how well you can communicate effectively.

2.     What are your strengths?
Suggested response:  I'm not only smart but also hard­ working. I'm a team player and communicate with people well.

3.     What are your weaknesses?
Suggested response: My weakness is that I always aim to be perfect, and I have the same expectation of other people. (The trick is to turn your weakness into your strength.)

4.     How do you know about our company?
Suggested response: Do your homework and learned something about the company before the interview.

5.     What areas or projects interest you? Describe how you can contribute to those areas or projects.

Suggested response: The interviewer will be impressed by candidates who researched what the company does and took the initiative to look for potential good fits on their own.

6.     Give me some specific examples from a previous project of how you contributed to the project team.

Suggested response: Of course, all candidates give platitudes about their programming skills. It's unlikely that a new hire will work alone. The interviewer wants to know how well this candidate will work as part of a team.

7.     What do you expect to be in the next 5 years?
Suggested response: I would like to … Don’t imply you will eventually take over your manager’s (the interviewer) position.

8.     Do you know LINUX (or any specific tool)?
Suggested response: I am very good at UNIX, which is an operating system very similar to LINUX. I can be very fluent in LINUX in a very short time. (Do not just say you don't know the tool when they expect you to. Say you know something which is very similar to the tool you are supposed to know. Generally speaking, it doesn't take a long time to learn any specific tools if you are given the job. But they don't want to give you the job unless you know the tools. This is the interviewer's mentality.)  It’s even better if you can give out example on how you acquire the skill to support the claim.  Say, you have worked on a project on Linux, and you used so and so tools to get your project done. Every candidate can claim they are good, so backing up your claim is very important. 

9.     We have several openings, one is in the user interface and the other is in the operating system. Which one do you prefer?
Suggested response I: I would like to talk to people on both projects to explore both opportunities and to determine which one is more suitable for me. (This question is usually asked of a new college graduate. The best strategy is not to reject any potential interview opportunity until you get a firm job offer. When both groups give you an offer, then it is your turn to decide which group to join.)

Suggested response II: Describe what you can contribute to either of the project. In so doing, you are not rejecting any opportunity but are actually providing specific information to help the interviewer to pick you. One example can be the following.

I have worked on user interface in my GUI project, where my driver meets "xxx benchmark" on yyy application. I am a computer game lover, my experience with ... games give me better intuition to design the next generation best intuitive human interface ... I also have hands on experience in OS, as shown in my ZZZ project where my codes achieves, ....I think my strength in both fields will bring the a unique contribution.

In every interview the interviewer needs to write evaluations and compare notes with HR and other managers. If your answer is directly quotable onto their evaluation forms that could be a good help for the interviewer's busy schedule and will consequently help your case.

10.  How will the company be benefited from your work?

Suggested response: This is typically asked of candidates with previous work experience, including part-time or internship work. Give some specific examples of what you learned from your previous projects. What are you especially proud of and why? What would you have done differently and why?       This will reveal if the candidate has the "big picture" of what affect his or her work has?

11.  Why should we hire you?

Suggested response I: This is typically asked near the conclusion of the interview. In few brief statements describe how you can help them and be useful to them if they hire you.

Suggested response II: I believe I can contribute my skills to your company (1) …. (2) …. (3)….   (Try to differentiate yourself from the other candidates)

12.  Do you have any questions for us?

Suggested response I: Ask for a question or two that was not addressed. Be brief though as the interview is coming to an end.

Suggested response II: Yes!  Could you please tell me …..?  (You must ask a question. Show your interest in the company.)