When interviewing someone just out of school, these kinds of experiences perk my interest:
- Past Internship/Co-op Experience
- Working on an open-source project
- Doing some kind of undergraduate research
To me these are worth more than personal projects because you're accountable to someone and often working on a team. If you have none of the above information, I'll try to find a class group project, though I loathe to do this.
Most important to me is that I see experiences that show you enjoy programming. I will ask questions about the experiences to see how excited you are about your past projects. This is more interesting to me than if you remember obscure information. For sure, being knowledgable is important, but I'd rather have someone who is excited and knows how to look something up via the documentation/stackoverflow, than someone who has memorized the latest Java/C#/C++ libraries.
Also I will try to probe about
- In past project X did you have to deal with team conflicts? How were they resolved?
- Were others ever skeptical about your approach? How did you handle their concerns/questions?
- What unforseen technical challenges occured, how did you handle them?
- When did you have to take a leadership role? When did you have to take a back-seat to someone else ideas?
- Name a situation that you disagreed with your boss/professor/leader-person. How did you handle the disagreement? What was the end result.
- How did you plan for this project? What technical challenges did you forsee?
- What design approach did you take? What made the design difficult?
- How did you document your changes? What challenges came up communicating with everyone?
- How much time did you set aside for testing? How were bugs evaluated?
- What kind of source control did you use? Why did you choose this tool over others?
Any experiences that allow you to have informed answers to these questions will greatly benefit how you are viewed by future interviewers (like me).