I hope someone in this group can give some special advice -

[hedgehog]

I have a son, recent graduate, computer science engineer, who is looking for work. You know the joke, about how you can tell an extroverted engineer because he stares at your shoes? Well, he's pretty much of an introvert. He also is such a good fit for coding that he has no comprehension that most people can't even understand what he does, let alone do it.

I've practiced some job interview type questions with him, and he tends to stop and ponder the question. So - what advice for getting him to speak up in job interviews?

[Lisa D]

1. Rehearse, rehearse, rehearse.

Keep looking for job interview questions and put 15 to 20 of them together. Have him write out the answer to each question, then during the rehearsal interviews, let him refer to his answers if needed.

This will give him confidence and even if he is asked different questions, he'll be able to plug in part of the answers.

Here are some basics (that you may already have):

What are you strengths?
What are your weaknesses?
How would you handle a disagreement with an coworker or manager?
Tell me about a conflict you've had in the past and how you dealt with it.
Where do you see yourself in five years?
Tell me about a time you made a mistake and how you resolved it?
Tell me about yourself (this can be a tough one--keep it short and positive

The next step would be to have someone else interview him--and mix up the questions. The more he practices his interview techniques, the more comfortable he'll be when it's time for the real thing.

Good luck!

[tk2kewl]

2. Have some solid coding examples along with unit tests

It amazes me how few software engineering candidates I have interviewed really understand how to write and test code well.

If he can explain his approach I couldn't care less about being charmed.

[hedgehog]

3. That's an interesting comment - he planned on taking some examples with him to interviews,

but I'd never heard of doing that. If you can add anything to your comment, I'd appreciate it.

[tk2kewl]

4. the examples should reflect an understanding of object oriented design and polymorphism

unit tests are critical. he should be able to talk about why and be familiar with the concept of test-first development.

As far as I am concerned anyway, these abilities are far more important than answers to general questions like what are your strengths.

Another thing that drives me bats is when someone shows up without extra copies of the resume. He can distribute a copy of his resume and his sample code as part of his introduction - it will show that he is prepared.

[MannyGoldstein]

5. Develop a list of things he's excited to talk about

Projects, classes... anything relevant.

An excited candidate is a good candidate. If he can work the things he's excited about into his conversations, it will help.

Also, research companies before sending resumes and before interviewing, and find things that are interesting to discuss.

[tk2kewl]

6. I agree with manny

that is why i say bring some examples of solid work and be prepared to steer the conversation towards that.

[sir pball]

7. Ask Slashdot

Their group expertise would be more useful in answering this question IMO, and it's just the kind of thing they'd probably jump on.

http://ask.slashdot.org/

[StanGr]

8. PM me. I've been on both sides of the desk.