Need some help for interview (new graduate)

Feb 17, 2006 6 Replies

Hi,



There are several posts in this news group regarding this topic. I gained a lot from them, but still there are some questions or doubts which I want to clarify. Since I'm a new graduate, how much technically sound I should be. I have read this that final decision of you being hired by them is based on your interest shown in the company and the questions asked. One [interviewee] should know his basic E.E., but it is okay if he doesn't know every thing technical they ask you. Any thoughts on this?



If you are interviewed by several managers (say, five managers), how the final decision is made? Is it the majority vote or every one has to recommend you to get hired?



My interview is with Hamilton Sundstrand in Windsor Lock, CT. I would appreciate if you could give me some inside about the company. Any other tip for the interview will also be welcomed.



Many Thanks,



A

Be prepared to discuss, in detail, a technical program *you* have been concerned with.

Usually they'll decide among themselves which, if any, manager has the most suitable opening. If you've made a bad, or good, impression on any one it will come up in the discussion. If you're really good, they may even argue over who gets to make you an offer!

I entered "hamilton sunstrand" in Google and got lots of references.

Try:

formatting link
to start!

Good luck!

Small world; my son works there.

See inline:

"amad" wrote in message news: snipped-for-privacy@g14g2000cwa.googlegroups.com... : Hi, : : There are several posts in this news group regarding this topic. I : gained a lot from them, but still there are some questions or doubts : which I want to clarify. Since I'm a new graduate, how much technically : sound I should be.

The more you know, that you learned outside school, or as a result of it, the better, in general, but i'ts not a dealbreaker as a rule if that's all you have. You'll usually get a chance to talk about groups you belong to, hobbies, projects, etc, so only expand on the relevant ones. The rest are only of a passing interest to the interviewers. Any experience, no matter how small, might help, but again, not a dealbreaker most times. A lot depends on who/what they're looking for at that particular interview. An interview at the same place by the same interviewer/s might be entirely different 6 months from now. Or not. HR: Only wants to know about your education, interests, and how you feel about/know about the company most tiems. Dept heads: Like to talk details, might even have some schematics/graphs to talk over. Or not.

I have read this that final decision of you being : hired by them is based on your interest shown in the company and the : questions asked.

It's really based on how well they judge that you fit the pattern for the position they have open. Try to know as much as you can about that before you get there.

One [interviewee] should know his basic E.E., but it : is okay if he doesn't know every thing technical they ask you. Any : thoughts on this?

Again, it depends on so many things and just what they're looking for. If they need someone to hit the ground running and who has

5 year's experience in embedded software design for instance, that's probably not a new grad. But, you might still make the interview if they think you're a fast learner, they can afford the ttime to train, and on and on. It's very much variable. : : If you are interviewed by several managers (say, five managers), how : the final decision is made? Is it the majority vote or every one has to : recommend you to get hired?

Usually the final decision would be made by whoever runs or is in the department you applied for. Then the others become evaluators and make recommendations of their own. You might have HR, Quality, Purchasing, a VP, peer engineers, etc etc etc in on the interview, it's hard to say; everyone does it differently. The person with the opening will make the final decision though, in most cases. It's his budget and his rep on the line of you don't work out. There are so many possibilities it cannot be predicted in general. It'll only be actually known when you get there. ?When I was hiring, HR did the culling; rejected the truck drivers, bakers and carnival workers, and passed on to me the resumes that looked like it fit in my department (R&D). Then I'd do an interview. If it worked out well, the candidate would be asked back to meet again with me and a couple of my engineers plus a quality dept rep, and we'd go from there. All that said, I actually DID hire a truck-drive once that the HR person passed on. He turned out to be a very successful embedded SW designer for the next 7 years. He was only driving truck because he was out of work; HR missed that point but I didn't because I always insisted on seeing the resumes that were culled out, also, and I caught the situation. Youare NOT likely to know whether you were hired at the interview. Notification is usually done AFTER all the candidates have been reviewed and the best one chosen. It's possible they'll tell you no, you aren't going to get the job at the interview, but even that is rare. Unless I had several good candidates I never rejected anyone until someone had actually accepted the position. So, don't forget: You might get there and find out that YOU don't want to work there, too: It works both ways. Both parties have to be happy with the hiring and the only one watching out for you, is, well, you. : : My interview is with Hamilton Sundstrand in Windsor Lock, CT. I would : appreciate if you could give me some inside about the company. Any : other tip for the interview will also be welcomed.

Never lie. Never speak badly of anyone, including their competition or anything in the papers or press releases. Keep a positive spin as much as possible. Bragging a little bit doesn't hurt, but be truthful; braggards are quickly singled out. Nothign wrong with saying "No, I can't do that, but because I know ......... I'm sure I could pick it up very quickly; it'd be a great challenge!" Snoop around a bit before th einterview; watch people going into work and/or leaving at night. Try to dress accordingly for the interview; never overdress or underdress if you can help it. Mostly, remember, you are there to sell yourself to them, and they are there to sell themselves to you; both of you have to be compatible.

It was some years ago my son interviewd there, but it was a pretty standard interview if there is any such thing. He was straight out of college with a Master's and had a couple of pretty good projects under his belt, and it was all pretty straight forward.

Lots of luck!

Pop

: : Many Thanks, : : A :

Actually some interviewers will continue to ask technical questions UNTIL you don't know. The reason is two fold: first it shows how much you DO know, and second, it proves whether the person is able to admit they don't know something.

Being able to admit you don't know can be as important as not knowing to begin with. People who say they know something but don't are quite useless IMHO.

TTYL

I'll add to this, if you don't know, say so, and then tell how you would get the answer.

People who 'know stuff' are all over the place, people who know HOW to get answers are a good deal more rare.

I just left CT, have a buddy at HS.

-D

I want to thank you for replying back to my post - especially Pop! I have accepted a position with Hamilton Sundstrand and I look forward to joining them soon. Any ideas what to expect in my first year of employement? Is it true that new hires are almost slave workers? How can I be successfull at my job?

A

No, that's a sour grapes attitude from people unwilling to do what's required. There will be some seemingly low-grade things to do at first, as people get to know you and your personality and abilities, but it's "normal" in most cases. Of course, it depends on the boss and workers, so dont' alienate anyone until you know how things work.

Keep your eyes open, don't be afraid to be helpful, don't be afraid to learn, and if anyone seems to want to mentor for you, take it. Mentors are common in your line of work and can last for a lifteime if you should find a good one. Especially at first, don't criticize: Ask "why" instead. There might be a good reason for the seemingly bad way of doing something, or, you might just give someone an idea; you never know. Do whatever you can to support your own boss, your team/s, and the company. Think a lot and often. Observe. KNOW how things work. And you'll have the opportunity to go far. Just don't be too anxious or jump to conclusions, and know the atmosphere.

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required