Re-Tooling TBL

For several years TBL was a blog where I wrote about a wide variety of topics. Those postings are still in the Blog Archive and many are about professional development for engineers. I am now transitioning TBL to be a place where my current and former students can find information related to job searches.

Monday, February 4, 2008

Advice to a New Engineer

The following exchanges took place. I would be interested in any further comments.

FORMER STUDENT:

I have some frustrations at work that I don't know how to address in aprofessional/tactful manner, and I am hoping that you may have someadvice on how to approach the subject.I am aware that I am a young, entry level engineer and with that havepositive aspects as well as drawbacks. I have been working at thisfacility for about 8 months now, and I have yet to do, or at least whatI consider to do, anything really engineering related.

Once I finished some of the general training, which included 3 months of shift work, Ihave been working on an OSHA required program that is severely lackingat this location. I know that this program is very important to get inshape and implemented, but I feel as if I am sacrificing being able to work on projects/designs here. I have brought these concerns to my direct supervisor/mentor, which is the Plant Engineer, to no real success. The last time that this was discussed was at my 6 month review. No one has a problem with my job performance, but I do.

Within this company engineers move around the country or even overseas quite often.When a new engineer is hired out of college, two years is generally how long the stay is at the first location. At this rate, I am concerned about falling behind my peers. I am worried that I won't be competitivefor the next position as a process engineer at the next unknown location. As the pressure is on to get the before mentioned program into place by corporate, it is as though the real reason I was hired, to be an engineer, is falling to the far wayside. I really don't know how to broach this subject with my superiors and getthe desired outcome-being trained on and then allowed to work onprojects. If you have any suggestions on how to do this from your experience outin the field, please feel free to relay that to me. I am actually quite lost on how to proceed from this situation. Thank you in advance for any help that is given.

RON:

Great to hear from you! I hope I can offer a fresh perspective for you. Let me start by asking you a question. When will the OSHA project be completed?

FORMER STUDENT:

As I have come to understand it, this project is not a destination but a journey. But I think the ultimate timeline is to get all of the pieces into place by June. There is tons of documentation that needs to be in place prior to using the program to the full potential. And after it is in place, it still needs to be managed.

RON:

I have spent a long time contemplating this. Here is my advice: You should embrace the task you have. Do it to the best of your ability and even better. Have the project be a smashing success. This will put you ahead of your peers who are doing design. It certainly won't put you behind.

In anything, capable people produce results. I believe your best bet is to show you are a capable person.The other option is much less pretty. If you kind of force your hand and in a sense complain that you aren't being challenged or aren't doing real engineering, then the tagline that will follow you is that you area complainer or a trouble maker.

I would much rather have the reputation of being the person who can succeed than the person who complains.Then if after a year and a half, if you have still not been put in the type of work that you want to be doing, start looking for other work. I hope this helps.

FORMER STUDENT:

Thank you for earnest response. I do like the point that you made about having a reputation of being a person who will get the job done, and done well rather than being a complainer. Thank you once again for taking the time to consider what I have asked.

3 comments:

Anonymous said...

A couple thoughts come to mind.

One is that someday in the future, you'll find that your experience and perspective from your OSHA project will have at least an indirect bearing on a "real" engineering project.

Another is, it sounds like you've been entrusted with an important project and have been allowed to work fairly independently on it. It sounds like your success or failure will be visible at the corporate level.

Compare that work to a "real" engineer who is doing technical work, but it's the repetitive "grunt work" under the direct supervision of a senior engineer. They have no chance to make an impression to upper levels of management. They will have limited experience in developing proper documentation. They also have no chance to hone and demonstrate project management skills.

Stick it out, learn what you can. Concentrate on developing your skills in managing your time and your project. Learn how to work with other departments. When your OSHA project is finally done, you will likely find that your peers are the ones who have fallen behind in their career development.

--Rich

Unknown said...

I agree fully with Ron and Rich. I know first hand that these types of programs are very important. The "higher ups" keep a very close eye on them because these are the programs that make the company as well as upper management look good. When I first arrived at McChord AFB, I was given a broke down repair and reclamation program. I did well in handling this program, so I was given two more programs that were in disrepair. A hazmat program and a program similar to OSHA for the Air Force. At first I felt the same way. I felt like I was doing a tedious job for no good reason and the paperwork was horrible (I was an aircraft mechanic by trade so paperwork sucked). However, I hate to do bad at anything so I repaired the programs and added more to them. In 2005 our unit won the AF Outstanding Unit Award and it was in part to the repaired programs. I received an award from my commander and a recommendation on my EPR. So my advice is to stick it out. The best way for you to get recognized is to make your company and your upper management look good.

Jake

Anonymous said...

One thing it took me awhile to realize is that we go to school for years, basically to design things. There's a lot more things that engineers are capable of doing. Ron has had a blog entry in the past that discusses this issue. Don't believe all you were educated for is design. You can do well at other things. You were educated/trained to think, not just how to design.

Like Ron said, if it's really not for you, move on, but only after you've given it a chance and done the best you can.

Maybe one other "tough love" bit of advice would be to ask more questions during job interviews next time. What you will be doing, day to day, in 5 years, in 10 years, etc.

Good luck!

-Caleb C.