I am in my senior year, and I am preparing for some interviews. I am wondering what I should review, and what I should prepare for when I'm getting ready for these interviews.
What types of questions are asked during interviews?
What key points and suggestions can you give me that might help me?!
It really depends on the position for which you're interviewing, but normally interviewers ask about object-oriented programming and sql/database concepts (make sure you know what the different types of joins are...I've been asked about them in almost every interview).
Sorry to link, but this is a really good read for learning about interviews:
http://www.bearcave.com/misl/misl_tech/high_paying_job_no_experience.html
The author argues that the "modern" interview style of Google and Microsoft pretty much tests people's problem-solving skills rather than experience, and that a lot of businesses are adopting this style at their (and experienced developers' ) expense. Nonetheless, he gives useful information on the interview process used by these companies.
If you do plan to apply to such a business, doing Google Code Jam practice problems may be a great idea. Hacking a Google Interview is also a great resource.
Good luck!
what mfabish said is right.it depends on the position what you are looking for.
if its for a fresher.
Ask question related to OOPS concept.if the guy having good knowledge in OOPS , he can do most of the things in the software field.
Ask some questions related to SQL ,joins some system functions etc ....
Don't forget to ask questions in latest technology,what are the things there new in the corresponding fields .
OO-concepts are pretty standard, since all CS progams include them. Review how these concepts specifically work in whatever language the job is for, since terminology and rules can vary. One of the best ways to prepare is to actually write some code. Try implementing a basic data structure, like a linked list or a queue. I've found this to be a useful refresher in some of the basic language concepts, and will help immensely if you are asked to write any code during the interview.
It may also be helpful to review your own attributes. Look through your resume and write down some points about each thing on it, in case you are asked. Think about answers to some of the basic questions: "what was a significant achievement you made?" "tell about a time you faced conflict" "where do you see yourself in 5 years?" Being ready for these questions will make you more confident and more attractive.
It's great if you know the answers to the technical interview questions, but if you don't:
Nobody has all the answers. You just need to prove that you are capable of finding solutions to things you don't already know.
As others have pointed out there are the questions about OO Design, databases and whatever technology they are using.
In my experience they also like to know how you cope and work in a team environment, so they ask you about a significant group project towards the end of your degree and try to get you in to a discussion about what your role was in the team and how you managed and overcame the inevitable problems that occur when on a project. They are looking to understand whether you are a good engineer, not just someone who can recall facts.
If you are a fresher questions may be from the basic concepts of Programming and also from systems. If you are applying for a specific position then clear knowledge about the position and the related technical information should be known questions must be from this.
Check out the MIT "Hacking a Google Interview" course, especially the "materials" tab. I wish I'd had access to this sort of thing before my first technical interview at Microsoft way back when.
If you're interviewing at a big tech company like Google, Microsoft, Amazon, etc. expect to write lots of code on the whiteboard, solving problems that can be approached from "first principles" (ie., if you know how a computer works and you're smart you should be able to get the solution to the problem) rather than "quiz" problems (do you know what such-and-such word means?). Also expect some questions about designing systems, trade-offs of different data structures or storage types, etc.
Assuming that you're a really good programmer already, the best thing you can do to prep is practice interviewing. Get some friends together and take turns at the whiteboard answering some of the sample questions from that MIT course.