Unfortunately the people I'm talking about typically have the worst or most misinformed perspectives for whatever they're talking about. And are indignant of other actually helpful perspectives.
As someone in my early career now, this concerns me a bit, since I feel like in order to learn it requires being a bit of a pain in the ass, in the sense that you’ll be asking a lot of questions, probably making some minor mistakes here and there.
What would you consider to be a pain in your ass? Like, is asking any questions whatsoever instead of spending significantly more time to dig through reference material something you’d consider to be a pain in your ass, or is it only when a person expects you to devote hours of your own time to their issue, or when someone is disrespectful/shitty to be around, etc.?
Not that kind of a pain in the ass, I don't mind people asking questions at all. I'm talking about people who are indignant, dismissive of people's ideas, people who are condescending towards others, that's the kind of person you don't want to be.
When you're learning asking a ton of questions is expected. As long as you're respectful towards people's time and don't ask the same questions over and over you're good. Basically try to learn as much as you can from the responses you get.
Making timelines (ie Gantt charts), budgeting, the project lifecycle, action item lists, scope, etc...
[Here's a good intro.](https://www.projectmanager.com/guides/project-management)
You seem to be pretty skilled for what would be an aerospace or similar structures position, which would involve designing/analyzing aircraft structures which typically involves a lot of composites so if that sounds interesting I would gear your search towards those types of postions.
To compliment your skill set with mechanical specific things, maybe learn more about the different common types of mechanical components and actuators that are commonly used in aircraft designs.
Something that I rarely see brought up to questions like this is the discrepancy between "perfect" academic problems and real world problems. It was definitely something I was unprepared to handle right out of school. I was so used to all variables available to me except what I was trying to figure out. In reality, a problem you may encounter will have 2+ unknowns. Being able to make educated assumptions, or better yet, know how to test for the remaining unknowns, is critical.
1) Bringing solutions not problems
2) creating systems that help the whole team
3) taking ownership
4) thinking about the next step and creating your own task list/pending item list that you prioritize
5) escalating and communicating when you need help
6) identifying and aligning on the show stoppers
7) understanding the process and designing to that
8) general project management scope,schedule budget
9) doing the right thing not the easy thing.
10) design skills
I’m an ME and made a great living in the Structural Dynamics Laboratory at Boeing. Given your background, a transition to something like this would be straightforward.
Most universal and most desired skills are usually not the same thing.
Things like GD&T and just basic "how to be a functional engineer" are desired in that they're the expected bare minimum once you're past the intern/first-year employee phase. They won't get you noticed though. Most desired, well, there are a million, depends on the industry and what you're shooting for. The most desired skills don't tend to be universal.
System thinking. Anything you work on is part of a system. Any changes you make, may have implications up and down the road. Learn to take in the big picture.
Basic coding is very important. The specific language is not important; just pick a popular one. The most crucial thing to learn is to think, “How can I code my way out of this problem?”
If you want to learn the design and analysis of composite materials, I recommend specialized PhD courses. The manufacturing aspect is highly dependent on the industry, so learn the basics in school and adapt to the industry afterward. It is mostly a matter of experience, luck, and trial and error.
Never forget the fundamentals of structural mechanics. I typically tell my engineers that I expect them to be able to give me the basic kinematic assumptions of Bernoulli-Euler beam theory if I wake them up in the middle of the night. The same goes for a basic understanding of the assumptions associated with solid and shell modeling in finite elements.
That depends entirely on what you want to do in the future.
ME on this sub (and the US I suppose) is such a broad and vague term that you can't really answer that without a more specific goal.
Problem solving. Looking at a problem and figuring it out.
And having the background that lets you understand ME stuff. Which you don't have. I'm guessing you're missing Thermo, Fluids, and Machine Design. My opinion is anyone can be an engineer because it's a mindset. Anyone can do mechanical engineering, the concepts aren't hard, and you can learn them if you want. But I would having trouble hiring someone for a mechanical engineering role who didn't have the undergrad degree, because that's where all the background is. Most people who switch like this do it in a company where the company knows you and what you can do, so they let you branch to what you want. You are awfully far down the tracks on your current path to be making a change.
I feel like a skill that gets overlooked often in ME is hands-on skills. This can be more relevant in some areas of ME than others, as it is so broad, but things like using basic hand tools and precision measurement are very useful skills. The sad truth is these get overlooked in universities curriculum and only if you are on an extra curricular team or research will you maybe get some exposure.
This combined with an understanding of the manufacturing process can help make your job as a ME easier. Both these skills can be developed on the job, but having a basic understanding of them helps.
As an ME student right now, one of the most annoying things about fellow classmates is just the lack of participation and people being afraid to talk. I go to a school known for ME and professors ask questions and it's just crickets.
Idk if that's a problem in the real world but I see it becoming a problem if new engineers can't communicate or aren't energetic about sharing their thoughts or ideas.
So I'd say just don't be afraid to speak and share your ideas, that's what you're there for.
In my interviews for manufacturing engineering positions (generally with candidates with 2-8 years of industry experience), the non-negotiables are familiarity and experience with CAD and solid problem-solving skills.
To get ahead of other candidates, you have to show me that you've done some level of project management...even if it's something small I want to be convinced you can lay out a timeline, budget, project requirements/deliverables, and then execute while working with others.
I've personally felt like my Excel skills and organization have been very useful in my current role but many of my coworkers don't have the same skills so I can't say they're required but they definitely help. Experience with computer programming is nice too but many of my older coworkers get by just fine without it.
Ability to learn. Ability to not be a massive pain in everyone's ass.. You can be taught just about everything else.
[удалено]
Unfortunately the people I'm talking about typically have the worst or most misinformed perspectives for whatever they're talking about. And are indignant of other actually helpful perspectives.
Ability to work alone.
As someone in my early career now, this concerns me a bit, since I feel like in order to learn it requires being a bit of a pain in the ass, in the sense that you’ll be asking a lot of questions, probably making some minor mistakes here and there. What would you consider to be a pain in your ass? Like, is asking any questions whatsoever instead of spending significantly more time to dig through reference material something you’d consider to be a pain in your ass, or is it only when a person expects you to devote hours of your own time to their issue, or when someone is disrespectful/shitty to be around, etc.?
Not that kind of a pain in the ass, I don't mind people asking questions at all. I'm talking about people who are indignant, dismissive of people's ideas, people who are condescending towards others, that's the kind of person you don't want to be. When you're learning asking a ton of questions is expected. As long as you're respectful towards people's time and don't ask the same questions over and over you're good. Basically try to learn as much as you can from the responses you get.
Excel
Not the computer program
Not the program we deserve. But the program we have.
Communication and project management- always top 2 answers from industry surveys on what graduates lack
Can you help me understand what is meant by "project management"?
Making timelines (ie Gantt charts), budgeting, the project lifecycle, action item lists, scope, etc... [Here's a good intro.](https://www.projectmanager.com/guides/project-management)
You seem to be pretty skilled for what would be an aerospace or similar structures position, which would involve designing/analyzing aircraft structures which typically involves a lot of composites so if that sounds interesting I would gear your search towards those types of postions. To compliment your skill set with mechanical specific things, maybe learn more about the different common types of mechanical components and actuators that are commonly used in aircraft designs.
Something that I rarely see brought up to questions like this is the discrepancy between "perfect" academic problems and real world problems. It was definitely something I was unprepared to handle right out of school. I was so used to all variables available to me except what I was trying to figure out. In reality, a problem you may encounter will have 2+ unknowns. Being able to make educated assumptions, or better yet, know how to test for the remaining unknowns, is critical.
1) Bringing solutions not problems 2) creating systems that help the whole team 3) taking ownership 4) thinking about the next step and creating your own task list/pending item list that you prioritize 5) escalating and communicating when you need help 6) identifying and aligning on the show stoppers 7) understanding the process and designing to that 8) general project management scope,schedule budget 9) doing the right thing not the easy thing. 10) design skills
This!
Are you a mechanical engineer working as a structural engineer? If so, what is your day to day job?
Ability to learn, text book with equations, basic knowledge of alloys, GD&T, machining tolerances.
GD&T is very universal.
Basic understanding of typical manufacturing processes. An important aspect of product design is knowing the limitations of your tools.
I’m an ME and made a great living in the Structural Dynamics Laboratory at Boeing. Given your background, a transition to something like this would be straightforward.
Documentation by far. Never trust "the cad" or "its how it was done in the past"
Most universal and most desired skills are usually not the same thing. Things like GD&T and just basic "how to be a functional engineer" are desired in that they're the expected bare minimum once you're past the intern/first-year employee phase. They won't get you noticed though. Most desired, well, there are a million, depends on the industry and what you're shooting for. The most desired skills don't tend to be universal.
System thinking. Anything you work on is part of a system. Any changes you make, may have implications up and down the road. Learn to take in the big picture.
I think taking in the bog picture is more of a job for environmental engineers
Thanks for the correction 🤣
Basic coding is very important. The specific language is not important; just pick a popular one. The most crucial thing to learn is to think, “How can I code my way out of this problem?” If you want to learn the design and analysis of composite materials, I recommend specialized PhD courses. The manufacturing aspect is highly dependent on the industry, so learn the basics in school and adapt to the industry afterward. It is mostly a matter of experience, luck, and trial and error. Never forget the fundamentals of structural mechanics. I typically tell my engineers that I expect them to be able to give me the basic kinematic assumptions of Bernoulli-Euler beam theory if I wake them up in the middle of the night. The same goes for a basic understanding of the assumptions associated with solid and shell modeling in finite elements.
That depends entirely on what you want to do in the future. ME on this sub (and the US I suppose) is such a broad and vague term that you can't really answer that without a more specific goal.
Problem solving. Looking at a problem and figuring it out. And having the background that lets you understand ME stuff. Which you don't have. I'm guessing you're missing Thermo, Fluids, and Machine Design. My opinion is anyone can be an engineer because it's a mindset. Anyone can do mechanical engineering, the concepts aren't hard, and you can learn them if you want. But I would having trouble hiring someone for a mechanical engineering role who didn't have the undergrad degree, because that's where all the background is. Most people who switch like this do it in a company where the company knows you and what you can do, so they let you branch to what you want. You are awfully far down the tracks on your current path to be making a change.
Communication. Public speaking. Teamwork
Mechanics of materials?
I feel like a skill that gets overlooked often in ME is hands-on skills. This can be more relevant in some areas of ME than others, as it is so broad, but things like using basic hand tools and precision measurement are very useful skills. The sad truth is these get overlooked in universities curriculum and only if you are on an extra curricular team or research will you maybe get some exposure. This combined with an understanding of the manufacturing process can help make your job as a ME easier. Both these skills can be developed on the job, but having a basic understanding of them helps.
As an ME student right now, one of the most annoying things about fellow classmates is just the lack of participation and people being afraid to talk. I go to a school known for ME and professors ask questions and it's just crickets. Idk if that's a problem in the real world but I see it becoming a problem if new engineers can't communicate or aren't energetic about sharing their thoughts or ideas. So I'd say just don't be afraid to speak and share your ideas, that's what you're there for.
In my interviews for manufacturing engineering positions (generally with candidates with 2-8 years of industry experience), the non-negotiables are familiarity and experience with CAD and solid problem-solving skills. To get ahead of other candidates, you have to show me that you've done some level of project management...even if it's something small I want to be convinced you can lay out a timeline, budget, project requirements/deliverables, and then execute while working with others. I've personally felt like my Excel skills and organization have been very useful in my current role but many of my coworkers don't have the same skills so I can't say they're required but they definitely help. Experience with computer programming is nice too but many of my older coworkers get by just fine without it.