|
I'm about to do my first phone interview in a few days (I'm the one who is being interviewed), and am wondering about how to approach it (how to prepare, what to expect, and so on...). The job is for a software engineer. How do these things usually go? What would you advise for someone about to do a phone interview? |
|||||||||||||||||||||
|
|
Excellent advice on phone interviews for software engineers has been distilled into five questions by Steve Yegge, he once wrote a rather extensive piece on it (based on his own experiences): The Five Essential Phone-Screen Questions. |
|||||
|
|
For all the phone interviews I have done for an entry level programmer they usually ask you some basic questions about concepts in general, features in your language, your background with other technologies, and some behavioral questions. From my experience they usually last about an hour and usually consist of drilling in you a variety of areas covered below. If you know when your interview will take place, I recommend you have the area cleared of all distractions (kids, loud noises, cellphone). I also recommend if you get nervous being put on the spot, print out some practice questions and have a friend or family member practice drilling you on those questions. OOP: What is a class, interface, abstract class, inheritance, polymorphism,encapsulation ... etc. Design patterns: Can you name a design pattern and when you would use it? Algorithms: What is the difference between merge sort and quick sort? What is Big 0 notation? Language specific questions: What is a delegate? Can you tell me how many bytes an int uses? Can you tell me what keyword X does in this language? Behavioral questions: How do you go about solving problems? Do you brute force it or do you Google it? Do you like working alone or with a team? |
|||
|
|
|
Other useful advice borrowed from telesales. Stand up while you're talking to them and smile for as much of the interview as you can. They can't see you, but it changes your voice and instils energy, confidence and cheeryness. It might sound daft, but people can hear you smile even if they don't register it as that. As for what to expect. It will be a screening exercise mainly, they usually just blast you with technical questions relevant to the job with the intention of spotting chancers. It's fairly time critical, so don't hesitate, if you really don't know the answer, say so and move on, if you know most or some of the answer, don't waffle, try and get as much of the answer out as possible. And keep smiling. |
|||||||
|
|
|||||||||||||
|
|
There are two types of phone interviews:
In my experience the HR phone interview is rather short. They will ask you some basic HR style questions to get a quick feel about you and if you're a good fit for the company. Speak clearly and confidently. Ask a few questions yourself about the company culture, dress code and the like. The technical phone interview is slight more tricky. In my experience they are longer, about a half hour to an hour sometimes. They ask a series of questions designed to see what you know. There might be a longer problem solving problem, but probably not as difficult as what you'd experience in an in person interview. For this interview I'd suggest you have a pen and some paper ready. The person you're interviewing with is probably someone you'll be working closely with, so try and communicate as much as possible. Phone interviews are harder b/c you lose the body language element, so you have to make sure you communicate clearly what you mean when you speak. For either interview I'd suggest keeping your resume and a pen and some paper close at hand. Also, find a quiet room where you can talk at a normal voice and they will be able to hear you. Talk with your head up and clearly so that you don't sound like you're mumbling. Again, being confident and collected is the way to go. Answer the questions to the best of your ability, don't ramble or mumble and ask your own questions at the end. |
|||
|
|
