Cogman
Lifer
Your best bet is to work in a small company. If you go to work for Big Software Co, you're likely to end up on a large team, responsible for some small aspect of their enterprise-y solution. Smaller companies tend to have more of a "we need stuff done" mindset, and you're more likely to get a project where you have more power over your own work.
After university, I didn't even bother applying to large companies (even though I had an internship at RIM), and I've been pretty happy with the ~150 person company I ended up working at. Two highlights/examples:
-Built a new CMS that works much differently than anything I've seen out there: Easy to use for writers, very developer-friendly, uses git as a backend, produces highly optimized code.
-made a Android Forex trading app (http://www.appbrain.com/app/com.oanda.fxtrade), where I had total control over the code and tons of input into the usability/flow of the app.
But yeah, try going for a smallish, consumer-oriented tech company and you're more likely to get lucky in your job search.
Small note, while I am still in university, you want to be careful with HOW small the company is 🙂.
I worked a summer for a 4-5 person sized company... Yeah. It was a father and son thing, with the father as the head programmer and the son as the salesman. The father wrote some of the worst code I've seen in my life, and he was in charge of pretty much the whole business background.
If you are going to work for a company that small, I would almost suggest starting your own. It is a fresh type of hell when you get the assignment to finish something written so poorly that it was literally faster to rewrite. (which is what I did, I got the same functionality, and clean code in under a day. It would have taken months if I had to tried to use the original. Oh, and I improved the speed of the program by about 1000x.)