Michael Beresford:
- Not sure who SAIC is (can you elaborate).
- Sounds like this may be a "help desk" position. Or might be supporting (on the user end) a product that was written in C++ or VB.
- You need to ask some questions during the interview.
-------------
- Given that you don't know C++ or VB and that the job requires it - I am about 90% sure that it's going to be a production support / help desk / end-user training type position.
I don't see it being a VB /C++ developer position. They are definitely hiding something from you. I could be wrong - but I've seen these before.
- Reason being, production support is essentially the "9th Plane of Hell" - and nobody really wants to do it. Low pay - Long hours - Totally nerve racking.
----------------
- What to expect from interview.
1. I highly doubt that you will go beyond basic definitions of OOA&D. I would say: inheritance,
polymorphism, object, class, encapsulation is all you gotta know. Be able to give a simple
Java definition of each. It's going to be simple stuff.
2. The interview will more than likely focus on your resume. You might get some managerial type questions - but again, very basic. I see neither a major technical nor major managerial interview comming your way.
3. What I do see is what I call the "incompetant interviewer" scenario.
What I mean by this is:
- The interviewer will do 90% of the talking. He will tell you all about the company. You will then ask "Tell me about how you got started with this company - your career with this company". The interviewer will clasp his hands behind his head - lean back - and go on the biggest b.s. rant you ever heard.
- He will base his hiring decision on "gut instinct" - rather than on a methodical interview process. The most important decision a manager can make (hiring someone) and this bozo will go with his "gut instinct."
Michael, you can bet your sweet hiney this is what's going to happen. I've just seen this scenario replay itself out time and time again.
- Your goal is not to fall asleep. Make sure you pee before you go to interview - because guaranteed, when this guy gets finished you are going to have to go. Either from laughing inside or from being stuck in this guy's office for 3 hours.
------------
- Now suppose that I am wrong? That's never happened before - but there is always a first time.
- Pay attention, go with the flow. I still say it's going to be a more managerial type interview than anything. This has been my experience in the past.
- Why else would they bring you in?
-----------------------------------------
I'm not done yet...
Michael, suppose that you really want this job. Lowball them with the following sweetie-pie phrases: "I want to make a contribution", "I want to be a team-player".
Dream some others up. This is what they want to hear - so give it to them.
Dress professionally - always play your part of the game. Just in case you do get surprised.
Remember: It's you who want to turn down the job - not them to turn down you.
-------------
OK - After your interview - please let us know how things went.
John Coxey
(jpcoxey@aol.com)
[This message has been edited by John Coxey (edited March 30, 2001).]