Hi, I have almost one year of Java Experience, 2 years of C++ in a Unix environment (internship) experience and a master's degree in MIS. In my current job at a financial services company, I've been modifying servlets, simple beans (as opposed to EJB's) and JSPs. I also do a bit of Perl and unix but the main development is on the desktop. When I interviewed for the job, they asked me just some basic unix questions and object oriented methodology question. This was because I was being recruited from college for an entry level program. Now that I'm thinking of looking for a new job, I fear the technical interviews. How should I prepare for it? Should I study as if studying for the certification? By the way, I've got all the other points (mentioned in previous posts) covered.
[This message has been edited by Shama Khan (edited April 04, 2001).]
Shama Kahn: Basically prepare for the SJCP2 - this will help alot on the technical interview side. If you have read the other posts - they are about 20-30 levels down in the group discussion by now - you will have a good idea of what's expected. You will find it alot easier to get a job while you are still employed - than if you quit current job and then start looking. Employers want what another employer has. Some kind of mental thing - but it happens. Again, the core concepts, Threads, Access Modifiers are what seem to come up alot on the technical interview. Might want to review/go over your project notes - so you can bring them up during the tech interview. By this, I do not mean handing over code printouts - but rather refering to specific problems/points/issues that you had and that you resolved as you completed these projects. --------- With technical interviews - the problem is that Java is such a broad language that you are not going to know it all. So what you do is answer a few of the basic/classig interview questions and then turn the tech interview into a discussion. Hopefully, you get a chance to write code on the white board. Also, you need to kick butt in the managerial interviews as well. The goal being that both sides of the interview (managerial and technical) will complement each other. Sure, you will have weak points in both - but you learn from your mistakes. And you do not let your weak points pull you down into the "valley of death" during the interview. Good luck, kick some butt, and let us know how things went. John Coxey (email@example.com)
Evansville, Indiana, USA
He's dead Jim. Grab his tricorder. I'll get his wallet and this tiny ad:
Devious Experiments for a Truly Passive Greenhouse!