- Read some of the other posts on this disccusion forum. You may have to go through the first 10-15 discussions, but you will see some good advice.
- For your phone interview: You need to be consise with your answers - else you confuse everyone. If there it is a conference type call - you may get into some discussions once these people feel that you know your stuff. This is the direction you want to head. You want to go from an interrogation to a discussion and if you play the game right you can do this.
- Make sure you have a copy of your resume in front of you. OK to have a cheat sheet or two - just don't let anyone hear papers shuffling.
Know your OOA&D definitions, such as polymorphism
, inheritance, etc.
Know the difference between an interface and an abstract class.
Know that Java does not support multiple inheritance the way C++ does.
Know that you implement an interface (can implement more than one).
Know that you extend an abstract class (can only extend one).
Know about the access modifiers: public/friendly(default)/protected/private. Be able to explain in one or two sentences for each case. This is where you can get tangled up in a phone conversation and confuse the heck out of the interviewer and yourself.
Know AWT Event Model - tough to do over the phone - but you may get hit on a question.
Know the two ways to start a thread
- "extending Thread" or "implementing Runnable". Know that the method is "run" but to run a thread you use "start".
Regarding SQL - I have not had anyone ask me questions about this on a phone interview. Other's here have and may be better able to help you in that department.
If you put in the 3 or 4 months of study for the SJCP - you will be ok on the interview.
Now. If you wipe out. Then use this interview as a learning experience. Take notes.
And don't take it personally. This is why the job search needs to be a full time job on your part. So that if you are rejected by this company - you chalk it up to experience - and the next day/week you interview with another company.
Basically, you hope you get the job, but if not, who cares and you go right to the next one - trying to learn from your mistakes and tweak your presentation. Knowing this is the best way to calm your fears.
The worst thing to do is write to and interview with one company at a time. Because you build up your hopes/dreams and then have them dashed by rejection. Then you feel like crap, kick the cat and feel like more crap because you kicked the cat.
The more of these you do (I've done about 50 on-site interviews in past 8 years) - the better you get. And that too calms your fears.
Let us know (either way) how the interview went/questions asked. And if you got the job.
[This message has been edited by John Coxey (edited March 02, 2001).]
[This message has been edited by John Coxey (edited March 03, 2001).]