I am an engineer with c, c++ back ground. And am mostly interested to work in data structures and algorithms kind of work. So, obviously asked those kind of questions? Is there any best resource where can I found the best interview questions?
Like to know sites/books: which discuss about general or HR kind of questions? which discuss about the technical questions?
One of the best books I know is Programming Interviews Exposed: Secrets to Landing Your Next Job by John Mongan , Noah Suojanen.
Steve Yegge has good tips on Get that Job at Google.
Warm-Up
- Study a data-structures and algorithms book
- Have a friend interview you
Mental Prep
- You should go in humble, open-minded, and focused.
- Feel free to ask for help or hints if you're stuck.
- Don't try to change the subject and answer a different question.
- It's OK (and highly encouraged) to ask a few clarifying questions, and occasionally verify with the interviewer that you're on the track they want you to be on.
Tech Prep Tips
Study:
- Algorithm Complexity
- Sorting
- Hashtables
- Trees
- Graphs
- Other data structures
- Math
- Operating Systems
It really depends on the place, thus I would say doing a lot of specific research for the company is the best thing to do.
For example, from what I have read, Google avoids asking silly interview questions like: "describe yourself in 3 words". On the flip side, they also ask brain teasers and problem solving situations that are pretty off the wall. If my memory serves me right, one question I read about had something to do with being shrunk down to the size of a nickel and thrown in a blender that was going to be turned on in 30 seconds. I have also read that they ask quite a few theory questions about runtime, etc.
I don't think anyone is ever going to have enough time to prepare for a huge set of possible interview question. Specific knowledge about the company is the best route to go.
My advice as someone who's had to hire:
Forget the canned interview questions. Employers are more interested in knowing that you have problem solving ability. In response to a question about sorting algorithms, I would rather hear that you know of a few (name them) and can develop the source code based on a description of how they work. I wouldn't hire someone who can write a O(log n) sort of the top of their heads - they're freaks and wouldn't fit in with a team very well (except possibly a team of freaks which would quickly drive a manager mad).
You should also show some interest in learning about the company and/or project that's interviewing. Find some real questions to ask about future direction of the team/product and possible career paths - managers love that stuff.
I recommend reading the Random Manager's Blog
It won't give you much technical advice about programming, but I think it is an excellent resource on everything else regarding technical interviews.
Start reading all the way from his first post if you have time.
I have only been asked to interview about 30-40 people so far, and here's what I think would have made some of them rank better in the interview process:
Be ready to talk and really explain your role in whatever previous projects you've worked on.
Do not get nervous. I know this one's hard sometimes, but after being on the other side of the table, I can really tell you, there's nothing to be nervous about. You want a job and they're looking to hire, plus the worst thing that could happen is that not getting picked.
Really, do not put stuff on your CV that you could not explain about. It will only make you look bad if they ask you about some topic you said you knew about and you don't know the basic stuff about it.
Make eye contact and try to bond with the interviewers, ask questions. It will definitely make you feel more confident and you will probably perform better.
Be humble, really. You'll most likely be part of a team anywhere you go and if the interviewers don't feel like you could integrate well into the team, you're toast.
I guess that's it...again, I'm by no means an expert interviewer but we regularly interview in 3 person panels and this is the most common stuff that comes up when we reject a candidate. Hope it helps.