To obtain a software developer/engineer internship or full-time job, you can be sure your skills and programming methods will be evaluated through a process of technical interviews on phone and skype, and on-site at a prospective employer's location.

Depending on the size of the firm and responsibilities of the position, you may simply be asked a few questions about general programming knowledge, but most often there will be algorithm questions where you will be supplied with a whiteboard and a marker to present your answer. This is referred to as "whiteboarding." That's right, on a board for all to see - no Google or IDE to tell you when there is an error! The reasoning behind this is to observe your approach to problem-solving and learn how you think. The most important thing to do while answering the question is talk and think out loud so those observing can follow along.

In my on-site with Zebra, it was a three-on-one interview with the team I would be working with if offered a position. I made sure to talk about what I was writing on the board so that they could see my thought process. My approach was to break down the question they asked into smaller problems and solve them one step at a time. What was nice, when I got stuck, they provided small hints to push me forward to solve the larger question originally presented. Honestly, I left the interview feeling unsure, since I needed that little bit of help. However,
I subsequently received an offer for a software engineer internship position.
I believe the moral of the story is they may not expect perfection. Tackling
the problem in smaller parts to achieve a solution, with complex thinking and problem-solving skills exhibited along the way, demonstrated the aptitude to succeed as a software engineer at Zebra Technologies.

Tenacity in the search was helpful too. I learned about the opportunity on Glassdoor.com. However, from October to January I sent out in excess of 60 applications to different companies, and heard back from only four. Of the four, two were just coding sample questions from Google/Amazon. Therefore, it doesn't matter what year student you are or how qualified you feel, you should just send out applications to any position where you think you may be a match. It's up to the prospective employer to decide if you are qualified or not. What is the worst that can happen? If you don't get a call back or you don't get the position, at least you had practice for the next time.

Suggested resources to help prepare for interview questions: *Crack the Coding Interview by Gale Laakmann McDowell*, leetcode.com, hackerrank.com, or Project Euler.