- May 18, 2001
- 7,833
- 296
- 126
So yesterday I had a technical skills interview for a programming position. The interview was over the telephone, and lasted for about half an hour (the interviewer said that this was the allotted time for the interview). I can modestly say that I'm a very good programmer and I have the proof (commendations from employers, etc.). That said, historically I suck at technical skills interviews. I have the skills, but its like my mind goes blank at the onset, only to turn back on right when I hang up the phone.
For the interviewer, what is the goal of this type of interview? Last night the guy gave me 3 difficult problems to solve, and I probably had a good answer for only one of them. Are they really looking for an answer to the problem, or is their primary goal just to observe your thought processes and problem solving techniques?
I need good advice - I should have another such interview with a different company in the next week or two.
For the interviewer, what is the goal of this type of interview? Last night the guy gave me 3 difficult problems to solve, and I probably had a good answer for only one of them. Are they really looking for an answer to the problem, or is their primary goal just to observe your thought processes and problem solving techniques?
I need good advice - I should have another such interview with a different company in the next week or two.