First, I would forget about interview-prep.
Second, I would try to get better idea about actual work, call friends from university that already work, and talk to them. I did learn this way that the day-to-day work in i.e. big corporations in a well run department is not really stressful, especially compared to a white-board interview. Some friend might even have an opening. Going through a referal is much better than just applying.
If you don't have friends with jobs already go ask on twitter. I think people around i.e. @sehurlburt form quite a friendly developer community and Stephanie herself often retweets i.e junior CVs.
Third, I'd figure out what position suits me. I would do this after I have realistic expectations about my work-environment. If programming itself is that stressful, I would probably advise-against doing ops-work, because baby-sitting servers can be even more stressful. But there are many positions that might fit you.
Manager - even though in many corps, people view getting to management as a promotion, there actually are junior managment position. Requires mostly people and organizational skills. Having a CS degree should help you stand apart.
Technical writer - mostly means writing documentation. If you have good writing ability, having a CS degree should be a plus.
QA - mostly software testing. Skill requirements can vastly differ, i.e. my boss expects me to be a decent coder, with some ops-experience. A friend of mine has 101 Javascript under his belt and in different corp mostly produces test-case documents in Word, another friend mostly clicks through a web portal based on a giant checklist. All of us have the title QA in their org.
You still might want to be a programmer. There are many levels of skill/stress/benefit ratios available.
If getting a job over a beer/coffer with a friend whose department/company has open position is not an option, I would go to a job-fair, or if I'd have a company I actually like, I'd wait for when they have an open-house, or something like that. I would talk to a recruiter there. That is how I got a job at RedHat as a QA more or less :-)