Most interviews are a majority of talking about yourself. Anything on your resume is obviously fair game. Be prepared to talk about projects you've done in great detail and any particularly cool things you've done to show passion for CS, etc. How you solved some problem. They just want to know how you think so maybe you have some involved undergrad project/summer internship project/open source project on Github, especially for new grads.
There's usually a general flow to the conversation as they talk about the stuff they're doing. Have a few questions on hand to ask them, as you've hopefully been able to do some research on the company.
Assuming you're talking about software development, for the technical stuff, kind of depends on the level of company you're aiming for as obviously different companies, different standards.
If you're aiming for ~Google-level companies, then be prepared lots of algorithm type questions. I thought this guide was good, even if it's old:
http://steve-yegge.blogspot.com/2008/03/get-that-job-at-google.html
Smaller to mid sized companies are usually less demanding. They usually aren't good at interviewing people, so they may ask dumb things like syntax questions for the technologies they want, which gets really annoying but be prepared for that. A lot of them don't ask abstract questions because that requires lots of knowledge in case the candidate gives some non-orthodox solution that requires the interviewer to know what's going on to analyze the viability of the solution on the fly and that's hard.
Instead, they may ask general type concept questions for the technology they want. For example, if they want SQL, they may ask the difference between inner join and left join. If they want CSS, they may ask about display properties, etc.
Also, for lower-tier type companies, as long as you seem enthusiastic, team chemistry matters a lot more as entry level means lots of learning on the job anyway as long as you have some building blocks.
For software development, a few of them will usually ask you to code something in the language of your choice, on a piece of paper or whiteboard (so you can't Google the solution or rely on a "compiler" to fix all your errors). At the very least, please know how to code FizzBuzz and other very basic stuff (like prime number testing, very basic math stuff, etc.) in the language(s) that you're repping on your resume.
If it's a front-end job, then hopefully you have a portfolio/web site to show your work.
Unless you're a superstar, you probably won't get the first job you try for so just keep doing interviews for the practice until you get better at them eventually.
Facebook
Twitter