Recent College Grad needs help

Question

Hi, I am a recent computer science graduate of DePaul university. I have been looking
for an entry level full time position for the past three months and I finally got a nible.
The problem is I have never had a phone interview and I really don't know what to
expect. I really need this job so I want to prepare myself as much as possible. The
position in and entry level programmer/analyst. Below is the job description, can
someone please tell me wher I can find some quick reference for COBOL and C++. I
took a class in both and did pretty well but that was school and this is real life. Again,
I really want this position and I am a really quick study. Can someone please tell me
what kinds of questions I should prepare to answer. I know the is a java forum but I
was hoping one of you professional programmers can point me in the right direction.
Any help would be greatly appreciated.
Role: Programmer Analyst (COOL Developer)
The Programmer Analyst is responsible for developing and managing the
application code and user interface (UI) components for a basic system
on the products and services team. (These systems can include the base TBA
System, desktop applications, IVR systems, or Internet/intranet applications.)
The Programmer Analyst works closely with other programmer analysts,
quality assurance analysts, and systems analysts, with tasks in the following
categories:
Planning and design. The Programmer Analyst takes the specifications
from the Systems Analyst and then determines the detailed tasks required to
create the code and UI.
Developing the application code and UI components. The Programmer
Analyst builds the code and UI components according to the functional
specifications and detailed design.
Other specific responsibilities in development include:
Working with the Systems Analyst to clarify and improve the design as
required. He or she may also prepare user documentation and will unit
test each piece of code to verify the basic functionality before passing it along
for more comprehensive testing. Throughout the project, the programmer analyst
consistently uses code management tools to avoid versioning problems.
Role Requirements
Problem solving and decision making
Learning agility
Client responsiveness
Project execution
Project analysis and planning
Technical Skills
Structured programming, design, and language(s) such as COBOL or C
Operating systems
Relational databases and data models (ex. DB2, Oracle or Access)
Source code management
Editing, compiling, and debugging tools
Creating user and technical documentation
Years of Relevant Experience Required: 0-4 years
Travel Required: None
COOL stands for COBOL Object-Oriented Language. It utilizes some of the
skills involved in both COBOL and C++ programming.
Again ANY HELP WOULD BE GREATLY APPRECIATED.

Answer 1

Actually the book thing is a great idea. I feel sorry
for you recent grads, when I graduated they were
putting English majors in programming postions.That explains so much of what I see! ;->
Seriously, I agree about the book. One important note is that phone interviews tend to run the gamut of perfunctory HR screenings ("can you spell SQL?", "What was your GPA?", "Does this guy seem to be able to communicate to other humans in the required language?") to fairly narrow, very deep technical screenings. I spend a lot of time giving the latter form.
Your best bet is to get comfortable with the kinds of questions you are likely to get (the book can help). Then consider all the questions that you hope they don't ask and decide (practice) how you are going to answer them when they do - and they often do. Don't get stunned when asked something unexpected. A simple "Hmm, I haven't really thought about that, but perhaps...." will go a long way. There are times when it is best to say "I don't know."
Don't try to bluff your way through unless you are sure that the person on the other end knows far less about the subject than you can successfully pretend to know. And be careful, some interviewers will go along with any bull they might hear to see where you take it... I know I do.
Most interviewers react badly to deceit and are probably looking at other candidates with similar level of skills to you - otherwise they probably wouldn't be calling you. Try to emphasize your abilities and demonstrate how you can easily fill any knowledge gaps you might have.
Don't try to fill lulls in conversation with information you don't really have. Nervous folks tend to chatter and get themselves into a hole, and interviewers are often taught to use this tactic to see how a candidate reacts. Just answer each question as completely as you feel is necessary and wait for the next question.
Chuck