Technical Interview 4

[sughew]

Hi

I have an interview day soon and it will include a technical interview. The job role is automotive based.

Have any of you guys experienced an engineering technical interview? If so, could you give me some pointers on how to excel one, and possibly some examples.

Any tips will be appreciated
Cheers
Sughew

 

[GregLocock]

If you don't know the answer, say that you don't know, but you know how to find out (if you do).

Bring along photos or drawings or charts from something interesting that you've done, that you know well.

Don't be a smartypants, unless you really are the cleverest guy in the room. Even then, don't be a smartypants.

If you designed the spindle on a car, you designed the spindle on the car. You did not design the entire suspension. Don't exaggerate. If you did design the entire suspension bear in mind that there may well be someone in the room who has designed 5 suspensions, so be prepared for a long and tortuous examination of your design.

What sort of job is it, by the way? The requirements for a design/release engineer are very different to those for a development engineer, or a manufacturing engineer, or a screenhugger (CAE).

Speak clearly. Don't look at your interviewer's shoes, or your shoes. It's not about the shoes.


Cheers

Greg Locock

Please see FAQ731-376 for tips on how to make the best use of Eng-Tips.

 

[prohammy]

Sughew,

You have just got some excellent advice from Greg (definitely worth a star Greg)...

Just to add another little bit to it..Don't lie, you will be found out, maybe not in the interview, but certainly afterwards. The truth has never got anyone in trouble (in an interview) and certainly never lost anyone their chance of a job. It is a very valuable asset for anyone to have in their armoury.

Kevin Hammond

Mechanical Design Engineer
Derbyshire, UK

 

[sughew]

Thanks for the advice. The job is for a graduate position. I'm a little nervous.

Cheers
Sughew

 

[powerjunx]

sughew,
In my technical interview; it was a panel interview where number of PE throw questions and even demos. I'm really nervous to tell you frankly. But one thing to put in your mind be "tactful" whatever inquisitive person they are. But as above pointed..don't lie!

 

[kchayfie]

If its a technical interview for a graduate position, the chances are they won't be expecting you to have the answers but they will be looking at how you approach the problem. They will be looking for someone with the right mindset to be able to learn the job.

My advice would be to tell them what you are thinking. If there is a part of the problem that you don't understand or looks unfamiliar, ask for clarification. Show them that you can work your way through a problem. Show them that you have the ability to learn and the ability to recognise what you need to learn. Don't try to bluff because you'll risk looking like an arrogant know-it-all who knows nothing and its unlikely that will appeal to an employer.

 

[Heckler]

I've had a few technical interviews over my short 13 year career. Follow Greg's advice. If you over state you involvement in a project be prepared to be grilled. Unless you have prior automotive experience I would say the questions would be centered around "core" engineering fundamentals.

Heckler
Sr. Mechanical Engineer
SWx 2007 SP 2.0 & Pro/E 2001
XP Pro SP2.0 P4 3.6 GHz, 1GB RAM
NVIDIA Quadro FX 1400
o
_`\(,_
(_)/ (_)

(In reference to David Beckham) "He can't kick with his left foot, he can't tackle, he can't head the ball and he doesn't score many goals. Apart from that, he's all right." -- George Best

 

[STYMIEDPIPER]

As the other responses reiterated--do not lie or over sell your abilities.
At the last place of employment I past the technical interview with ease.

However, when I was at the job site, my immediate supervisor continually asked me "what is ...? and "what if ..? until he felt comfortable with my abilities.

The immediate supervisor wanted to ensure that the company made the right choice and that I was capable of handling various situations as they occur.
If I had overstated my capabilities during the interview I probably would have been in the 'dog house'.

 

[TStaples]

Sughew,

Many companies have adopted "Behavioral Based Interviewing" techniques. You may be asked questions about specific experieneces you have had, or situations that you have been in. They may or may not tell you in advance that this is what they are doing.

If asked those types of questions, then answer them with specific examples that relate to what was asked. DO NOT answer them generically with what you would do if you were in a situation. They want to drill down and see how you have previosuly handled issues or situations. It is predicated on the the idea that past behavior is the best indicator of future performance

Here are some of my favorite questions to ask engineering candidates (along with some explanations of why I ask them):

1) What is the most difficult technical challenge you have faced?

(This is a really good way to evaluate the scope of complexity that the candidate is capable of handling. If the answer is lame or shallow, I know the candidate is too. If the answer is deep and complex, I can drill down further with specific follow-ups to ensure I'm not getting smoke blown up my skirt.)

2) Tell me about a time when you had an impossible deadline. What was the situation, and how did you deal with it?

(This is a great way to tell how they handle pressure and deadlines. I'm looking for a person that knows how to re-write the rules, and leverage outside resources, to allow her/him to achieve a successful outcome. In 'Star Trek" parlance, I want to find out if the candidate knows how to reprogram the computer to allow for success in the no-win scenario.)

3) Tell me about your biggest technical failure.

(This is a deal breaker for me. If I get some comment like "I've never had a real technical failure.", then I know I can't trust the candidate to be honest with me, and/or the candidate has never really pushed her/himself in terms of design or projects. It doesn't matter which it is, both are unacceptable for an experienced engineer. Every really good engineer that I have known has had at least one zinger of a program or project where they had a major OOPS! I know every good engineer makes an error or two. I want to know how he/she handled it, and recovered from it. It gets down to the difference between a professional, and an amateur. Both make mistakes, but a PRO knows how to recover from them. Be honest with this type of question, and then describe how you made lemonade out of lemons.)

One other piece of advice based on the most bizarre interview I've ever had with a candidate: Don't refer to yourself in third person. I once interviewed a candidate whose first name was Hamesh. He answered my questions like this:

Question:
Tell me about a time when you dealt with an angry customer, either in person, or on the phone?

Answer:
"Hamesh would do this, and Hamesh would do that. Hamesh would do blah, blah, blah . . .." I have no earthly idea what he actually said, as I was in shock as to how he referred to himself. It was as if he was talking about someone who wasn't even in the room. I happened to have one of our directors sitting in on the interview with me. That candiate was recurring fodder for humorous dialog between us for several years! Bizarre! I cancelled his remaining interview appointments after me, and escorted him personally to the front lobby!

Good luck with your interview!



-Tony Staples

http://www.tscombustion.com

 

[powerjunx]

TStaples, that's great point! and question raised was really testing the "strenght and weakness" of a person.

 

[corus]

I think kchayfie's point about how you approach a problem is probably what they look for. Of course you get the smart alecs who want the precise answer they have written down, basically because they don't have much of a clue how to approach a problem themselves. In one techincal interview the questions I was sked were so basic I thought there must be a catch somewhere. Sadly the techincal ability of most folk is so low that such easy questions sorts out the riff-raff quite well. Greg's advice of not staring at the shoes is good advice. It clearly shows you've reached the position of begging mode. It doesn't work.

corus

 

[Romeosperson]

After the last round of interviews that I sat in on, I would highly recommend that you be prepared to sell yourself. It isn't always easy, but remember the interview is your only opportunity to sell yourself. Whatever you do, don't shy away from letting them know why you are right for the job. I actually had someone say, "I don't know" in response to our question, "Why should we hire you?"!

Good luck with the interview. It will be interesting to hear what the technical interview involve.