How to do interview

There are many keys you may want to pay attention to during the interview.

Typically, a tech-interview will have 3 parts:

-1- First part, ask the candidate' bio, such as their career history, projects on hands
The purpose is often to warm up, and know the stuff that the candidate might be good at
The interviewer are looking for 1) the candidate is a problem solver, 2) the candidate can "get things done", 3) passions in the back, 4) how easy to communicate with the candidate

-2- technical questions....

-3- "interview of the interviewer" -- ask question.
There are suggestions (Take Control of Your Interview) that:

To only ask questions about areas where you have something positive to contribute if the question leads to a spirited discussion. And the best way to make this happen is to plan in advance.

how to get started.

1. List your three things you want the interviewer to know about you that you think they are unlikely to find out if they ask all the questions;
2. Write a one-paragraph description of for each thing that you could use to 'coat tail' onto another question;
3. Think of a question you could ask for each thing that would naturally lead to a discussion.

Some other good links:
Ref = http://stackoverflow.com/questions/11368/what-is-the-best-interview-question
1. asked to describe the architecture of the project I was currently working on.
2. Tell me one thing that we're doing badly that you think we should do differently
3. Tell me about yourself
For this, it's a really open question, but if you do better, you can take this opportunity to show your expertise, what you have done, and your advantage, experience, how did you solve the most difficult questions...

Ref = http://www.joelonsoftware.com/articles/fog0000000043.html
which is a good place to start the Joel Test,. It hsa questions/resources for self-testing/answering

The Joel Test- 12 steps to Better Code

1. Do you use source control?
2. Can you make a build in one step?
3. Do you make daily builds?
4. Do you have a bug database?
5. Do you fix bugs before writing new code?
6. Do you have an up-to-date schedule?
7. Do you have a spec?
8. Do programmers have quiet working conditions?
9. Do you use the best tools money can buy?
10. Do you have testers?
11. Do new candidates write code during their interview?
12. Do you do hallway usability testing?

♥ ¸¸.•*¨*•♫♪♪♫•*¨*•.¸¸♥