3 answers
Fabrizio
Student
Lynwood, California
2
Questions
Asked
1263 views
What is the average day of a mechanical engineer?
I want to explore my options as to what type of engineering field I would like to pursue. #mechanical-engineering
Login to comment
3 answers
Spruce Cox
Retired Aerospace Engineer and Rocket Scientist
76
Answers
Updated
Spruce’s Answer
Hey Fabrizio,
Although my degree is ME, I worked most of my career as an aerospace System Engineer (SE) in a large aerospace company. Think of the job of an SE as part of the Chief Engineer’s office in the sense that we kept track of program level requirements and status of all the major subsystems in meeting those requirements. Even though we did not have individual responsibility for specific hardware or software items (MEs and EEs did), we got to learn about all major hardware and software items and how they interfaced with each other to make the whole system work. The SE group on a large program can have many different responsibilities, this is usually the largest one.
I was a lead engineer working with up to 30 (but usually 5-10) other SEs. Almost always, we spent approximately half our time sitting and talking with different engineering disciplines on the program to facilitate agreements between different groups whenever any of their hardware or software touched or interacted (i.e. interfaced) with hardware or software from any other group. The other half of our time was spent in meetings with those and other groups resolving issues of higher risk or cost, and describing and controlling all agreements with signed documents. Of course, we also had regular status briefings with management and customers. We followed a strict set of controlled processes in conducting our activities and producing our preliminary and final products.
The MEs I worked with spent most of their time at their desks designing their parts using 3-D design software. They probably spent the equivalent of two hours per day coordinating with the different groups that gave them, for the parts they were designing: loads, environments, max weight, shape or volume requirements, and interface requirements. Once the smaller parts were designed their drawings were put together into subsystem integrated drawings, then system integrated drawings, and finally into a single integrated drawing, all stored online in the design software tools. For large aerospace projects at least, this process was repeated at least twice, once with “preliminary loads” and once with “final loads”. Design is truly an iterative process especially in high-tech, complicated aerospace projects such as airplanes, rockets, or spacecraft.
The key to a job like this is to enjoy what you’re doing. Yes, some of the schooling is pretty tough, but if you’re part of a group designing F-35s or manned rockets to Mars or commercial aircraft communications systems, the people flying those machines need to know that they’re built right, and you will have been a part of that. Good luck in selecting your flavor of engineering, and have fun!
Although my degree is ME, I worked most of my career as an aerospace System Engineer (SE) in a large aerospace company. Think of the job of an SE as part of the Chief Engineer’s office in the sense that we kept track of program level requirements and status of all the major subsystems in meeting those requirements. Even though we did not have individual responsibility for specific hardware or software items (MEs and EEs did), we got to learn about all major hardware and software items and how they interfaced with each other to make the whole system work. The SE group on a large program can have many different responsibilities, this is usually the largest one.
I was a lead engineer working with up to 30 (but usually 5-10) other SEs. Almost always, we spent approximately half our time sitting and talking with different engineering disciplines on the program to facilitate agreements between different groups whenever any of their hardware or software touched or interacted (i.e. interfaced) with hardware or software from any other group. The other half of our time was spent in meetings with those and other groups resolving issues of higher risk or cost, and describing and controlling all agreements with signed documents. Of course, we also had regular status briefings with management and customers. We followed a strict set of controlled processes in conducting our activities and producing our preliminary and final products.
The MEs I worked with spent most of their time at their desks designing their parts using 3-D design software. They probably spent the equivalent of two hours per day coordinating with the different groups that gave them, for the parts they were designing: loads, environments, max weight, shape or volume requirements, and interface requirements. Once the smaller parts were designed their drawings were put together into subsystem integrated drawings, then system integrated drawings, and finally into a single integrated drawing, all stored online in the design software tools. For large aerospace projects at least, this process was repeated at least twice, once with “preliminary loads” and once with “final loads”. Design is truly an iterative process especially in high-tech, complicated aerospace projects such as airplanes, rockets, or spacecraft.
The key to a job like this is to enjoy what you’re doing. Yes, some of the schooling is pretty tough, but if you’re part of a group designing F-35s or manned rockets to Mars or commercial aircraft communications systems, the people flying those machines need to know that they’re built right, and you will have been a part of that. Good luck in selecting your flavor of engineering, and have fun!
Kevin Garrett
2
Answers
Updated
Kevin’s Answer
I think one of the "fun" things about most engineering positions is that they are not a consistent, 9-5, same-stuff-different-day roles. The project cycles, especially in areas like design where schedules can be fluid based on success of initial concepts, often come in waves... so while you may be working CAD for 8 hours a day for 2 months straight, the following 2 months may be 0 CAD. Sometimes the 60-hours weeks are followed by 30-hour weeks... so it really takes the right kind of person who can put the pedal to the metal when needed, but can also fill downtime with side projects, organization tasks, and long-term/low-profile stuff.
Obviously all jobs, roles, and companies won't be the same, but I often tell people that for a mechanical design engineer, every day is different sometimes. One of the reasons they pay us the big bucks is that these aren't boiler-plate roles with clear definitions, and they typically have a lot of potential for good folks to go above and beyond, both for themselves and the company. But most of us would take that over a position that pays the same but just has you pushing the same button over and over every day.
Obviously all jobs, roles, and companies won't be the same, but I often tell people that for a mechanical design engineer, every day is different sometimes. One of the reasons they pay us the big bucks is that these aren't boiler-plate roles with clear definitions, and they typically have a lot of potential for good folks to go above and beyond, both for themselves and the company. But most of us would take that over a position that pays the same but just has you pushing the same button over and over every day.
Suresh C
Tech Support at Dell
5
Answers
Bengaluru, Karnataka, India
Updated
Suresh’s Answer
8 to 10 hours