First day jitters 4

[mecheng2008]

Hi, I am a recently graduated mechanical engineer. I am about to start a new job working for a company that designs/fabricates equipment for various industries: timber, meat, quarrying etc. I have a few questions regarding the big first day, and for that matter the first few months. Maybe some of the more experienced members of this forum can give me a few hints.

What do you think I should spend the first couple of weeks doing? Aside from locating the break room, getting lost, figuring out why my computer won’t go, getting lost again, talking to the guys etc, and trying to work out what it is that we actually do?

If any of you employ graduate engineers or have them working for you, what could a new graduate do to show they were enthusiastic, hard working, keen to get established in the company etc?

I’m sure this topic has been discussed to death, but I thought I’d ask anyway and brace myself for the wave of “this topic has already been discussed!” posts. To those who do take the time to respond – Next rounds on me!

 

[KENAT]

Similar has been posted before, take a look (the search function doesn't work too well so you may just have to scroll thorough the last year or so's worth of posts).

Ask questions, note the answers in a log book or similar so you don't have to ask again. Also, as much as possible, think through the problem, do some research before asking the question. I prefer to be asked "I was thinking of doing it like this, do you agree" than "how do I do this" though sometimes the latter is appropriate.

KENAT, probably the least qualified checker you'll ever meet...

 

[jistre]

You're going to spend the first few weeks familiarizing yourself with your new company, its products, and its clients. There's likely going to be a mountain of documentation on everything, so when you're not directly tasked to do something, I'd make it a point to be reading these things until you get a good knowledge of what exactly it is you and your company make and do and can speak intelligently with other members of your group about both topics and be understood. Then you'll be comfortable enough with the product to go to your boss and say "Hey Boss, wingding number 2 on widget A looks like it could be improved. I've got some free time. Mind if I take a crack at it?"

Also, I wouldn't worry about getting thrown into the deep end, although I would at some point in my mind be prepared for it. At larger companies, and depending on your supervisor, your initial tasks will likely be things you can't screw up too badly and you'll be watched closely to prevent uh-ohs. However, I was lucky enough to end up at a small company as the only kid with an engineering degree and told, "We would like you to design a new product from the ground up. Go." The point of this is that if an idiot like me can pull it off, anyone can.

Oh yeah, this topic has already been discussed!!

Sorry. Couldn't resist. In all seriousitude, you're going to want to learn as much about everything as quickly as you can to show your boss that you're on the ball. Your boss has been budgeted X number of training hours to get you up to speed. If you're able to come in under that number of hours, you will have both saved him some overhead costs on his budget and proven that you're swifter than they thought you'd be. That's a good way to make him more comfortable with giving you a little bit of extra leash to run around on since you've proven you're such a capable learner.

 

[ash9144]

Get to know the old timers at your new place. Be careful and make sure to identify the ones that actually work and understand how things work and avoid the ones just waiting to retire.

When you find a knowledgeable well experienced craftsman, get to know him and get to know what he knows. No matter how cranky (or anti engineer) these individuals come across they are full of priceless knowledge and will be eager to teach someone willing to learn.

 

[Jack808]

I agree with KENAT; don't be afraid to ask questions and write things down. You may have a really good memory, but you don't want to be caught off guard when you're asked about something you realize you had forgot. I have been working at a company where the boss changes his mind every five minutes and assigns everything from paying car insurance bills to modeling the entire working system. His policy is to load people with tasks "until they scream" so I write everything down and stay on top of it.

My second bit of advice is to keep "brilliant" ideas to yourself for a little while; let them stew. If you have what you think is a great idea, it may be, but you may also need to understand things better. I wrote down all of my "brilliant" ideas the first couple of weeks. When I came back to them after a few months, some of them were ridiculous, but others are now being implemented. It's sometimes hard to gage the value of an idea until you really understand things.

Best of luck!

 

[MechEng2005]

First thing I'd recommend is getting to know those you'll be working with and determining who to ask when you have questions. Also, try to be active in getting things setup with human resources. I think that making sure everything is in-order is a good way to show that this position is important and you aren't just "showing up" until something better comes along.

Try and find out if the company has any standards or common products, and research them. Look at the drawings and determine what each component is there for, why it's located where it is, why it's bolted versus welded on, etc. You can also get information from this such as if it's standard procedure to use lock washers and things like that. The person checking your work may not really notice that you included them, but they would surely notice if they had to add them all in.

That's all I can think of at the moment. Congrats on the graduation and good luck in the job. Nice name too!

- MechEng2005

 

[macmet]

A few people have pointed out how it's important to get to know the older timers and techs. This is very true and keep in mind that just because they may not have an 'engineering degree' doesn't mean they don't know what they're talking about. Experience counts for a lot and the old timers will often know more than the 'engineers' in the office.

I am not sure what your job is, but chances are you'll need their knowledge more often than your knowledge of third year calc.

 

[MadMango]

Make friends with the front desk person, someone in IT and in HR. Try to attempt to go to lunch with various groups of co-workers, spread yourself around. You don't want to fall into clique to discover it was the wrong one. You're investigating your co-workers (don't make it obvious), keep "visits" short so you don't eat up all their time or yours.

Get a log book, write everything down that you can. No one expects you to memorize everything the first day/week/month, but they also don't want to tell you the same things over and over.

As a first job, you're probably going to get stuck processing Engineering Change Orders. Don't be afraid to walk out into the production floor (if you have one) and talk with the workers there. Try to determine if changes are design or process related.

As a first job, you're probably going to get stuck doing a project that has been pawned-off to various people for various reasons. Do it in stride.

If you don't have a feel for the company culture, wear a tie your first day. You'll be able to tell pretty quickly if you should take it off before lunch. It's easier to dress-down at work than it is to dress-up if needed.

"Art without engineering is dreaming; Engineering without art is calculating."

Have you read faq731-376 to make the best use of Eng-Tips Forums?

 

[Gymmeh]

Congrads on finishing and getting a job right out.

Ask your boss for (or find) a good mentor (they don’t even need to be an engineer to help you)!

One thing to keep in the back of your mind which is not thought anywhere in school is office politics and personalities. Most engineers just want to do their job but unfortunately, there are politics in the offices, and understanding them to some extent will help you C.Y.A. (cover you’re a$$) and with a little luck they can even help you.

Best of Luck

 

[electricpete]

I have seen in the past brand new engineers that seem too eager to show off their knowledge and don't quite realize how much they have to learn.

I am impressed by a new engineer that hits the ground running with a focus on learning, tackling problems and getting the job done. If you have that focus rather than a focus on impressing people, then people will be impressed.

=====================================
Eng-tips forums: The best place on the web for engineering discussions.

 

[csd72]

Ask lots of questions, the earlier the better. Make a list of these questions when you have no-one to ask.

But make note of the answers and try to make sure that you dont ask the same questions twice!