Need Some Advice on My Job Perspective

[Ghros]

Hey everyone,

I'm a recent bachelor's graduate who just landed a job at a startup. Although I have a strong interest in and motivation to grow in the field, my hands-on experience in mechanical engineering is pretty minimal. Somehow, I’ve been hired as a mid-level design engineer. (During the interview, I was told this was a mid-level role. I managed to convey confidence and even somewhat outshined the interviewer by steering the conversation in my favor. I also presented a recommendation letter from my professor, which played a big role in landing the job.) I initially thought this was a manageable challenge, but after almost three months, the workload has become overwhelming. Developing a product that meets industrial standards—without the benefit of the typical gradual learning curve—has proven to be a major setback.

The Situation:

No Prior Experience: I’m completely new to the mechanical engineering practices expected in well-established product-based companies.

Solo Mechanical Responsibility: In our 4-member team, I’m solely responsible for the mechanical side. The other three team members are focused on electrical and software work and aren’t available to provide guidance.

High Expectations: Despite my lack of hands-on experience, the expectation is a final, well-working product without intermediate feedback or structured guidance.

Self-Learning Path: I’m already diving into self-learning and applying what I learn in real time, but I’m still unsure if I’m doing things the “right” way.

Questions for the Community:

Has anyone been in a similar situation? How did you manage the steep learning curve?

What resources (books, courses, mentors, online forums) would you recommend to quickly build a solid foundation?

How do I approach asking for more guidance from my team or supervisor without coming off as unprepared?

I’m really really passionate about this job and eager to contribute as much as my teammates. However, the pressure of performing at such a high level without proper mentoring is overwhelming. Any advice or insights would be greatly appreciated!

Thanks in advance!

 

[PeroK]

It's difficult to advise without knowing the specific circumstances. The startup might have been too ambitious. Perhaps the project is going to crash and burn in any case? Don't take the weight of the world upon your shoulders.

Who's responsible for the ultimate success of the project? You must be reporting to someone? Only raise issues that you absolutely cannot resolve by yourself.

Try to remain objective and realistic about what you can achieve. Set yourself achievable goals and try to learn as much as possible from the experience.

I'm not sure whether that helps. I suspect your situation is not uncommon.

 

[zoltrix]

in my opinion the future (or even the present) of mechanical engineering is mechatronics
because :
#1 all mechanical devices are fitted with electronic controllers
#2 complicated mechanical linkages have been replaced by simple electronic cams
#3 a sophisticated automation control theory is redundant for mechanical projects
in motion control you use PID controllers only
#4 the mechanical and the automation design must be seen as a whole rather than a matter of specialists

last I would suggest to purchase the book :
Control system design guide by George Ellis
fantastic book focused on motion control

 

[CrysPhys]

Hey everyone,

I'm a recent bachelor's graduate who just landed a job at a startup. Although I have a strong interest in and motivation to grow in the field, my hands-on experience in mechanical engineering is pretty minimal. Somehow, I’ve been hired as a mid-level design engineer. (During the interview, I was told this was a mid-level role. I managed to convey confidence and even somewhat outshined the interviewer by steering the conversation in my favor. I also presented a recommendation letter from my professor, which played a big role in landing the job.) I initially thought this was a manageable challenge, but after almost three months, the workload has become overwhelming. Developing a product that meets industrial standards—without the benefit of the typical gradual learning curve—has proven to be a major setback.

The Situation:

No Prior Experience: I’m completely new to the mechanical engineering practices expected in well-established product-based companies.

Solo Mechanical Responsibility: In our 4-member team, I’m solely responsible for the mechanical side. The other three team members are focused on electrical and software work and aren’t available to provide guidance.

High Expectations: Despite my lack of hands-on experience, the expectation is a final, well-working product without intermediate feedback or structured guidance.

Self-Learning Path: I’m already diving into self-learning and applying what I learn in real time, but I’m still unsure if I’m doing things the “right” way.

Questions for the Community:

Has anyone been in a similar situation? How did you manage the steep learning curve?

What resources (books, courses, mentors, online forums) would you recommend to quickly build a solid foundation?

How do I approach asking for more guidance from my team or supervisor without coming off as unprepared?

I’m really really passionate about this job and eager to contribute as much as my teammates. However, the pressure of performing at such a high level without proper mentoring is overwhelming. Any advice or insights would be greatly appreciated!

Thanks in advance!

* This company doesn't sound kosher. Why would they hire a kid straight out of school for a senior position?

* What about the other three team members (electrical and software)? Are they also newbies, or are they experienced?

* What are the backgrounds of your supervisor (and any other supervisors)? Are they engineers, business guys, or ...?

* If I understand you correctly, you are supposed to develop an actual product, correct? If so, this is not a scenario in which you can "fake it, until you make it". Especially if there are schedule and budget constraints, and you need to comply with industry standards..

* If you truly have no senior engineers to turn to for help, you may want to consider hunting for another job first, and then have a heart-to-heart talk with your supervisor. You're not going to learn what you need by reading books or watching videos on the Internet.

 

[CrysPhys]

in my opinion the future (or even the present) of mechanical engineering is mechatronics
because :
#1 all mechanical devices are fitted with electronic controllers
#2 complicated mechanical linkages have been replaced by simple electronic cams
#3 a sophisticated automation control theory is redundant for mechanical projects
in motion control you use PID controllers only
#4 the mechanical and the automation design must be seen as a whole rather than a matter of specialists

last I would suggest to purchase the book :
Control system design guide by George Ellis
fantastic book focused on motion control

And how does any of this help the OP in their present predicament?

 

[CrysPhys]

I suspect your situation is not uncommon

I find it bizarre. Almost like the plot of "The Producers."

 

[Choppy]

This sounds like a situation where the sooner you bring up your concerns with the team, the better. While it may feel good in the moment to project confidence and keep quiet, if the project comes crashing down later on everyone will wonder why you didn't say anything sooner. And that can have dire, career-altering consequences.
To the extent you can, identify the specific obstacles on the project you're working on and come up with a plan for addressing them. In general, people tend to be much more responsive to specific requests for help than they are to a vague list of concerns.

 

[marcusl]

First, it’s time to own up—not just to the team, but to your boss. The worst thing that can happen is to surprise everyone with failure at delivery time. Three months is already a long time.
As for worrying about sounding unprepared, get over it! You ARE unprepared, and the sooner your boss knows it the better. You can say you’re motivated and a fast learner, but admit that you’re over your head.

Second, ask your boss for help. He/she may be able to get you mentorship from someone else in the company, or hire someone senior, or get a part-time consultant. These are things you can suggest.

Third, study study study. Read to get the skills you need. Read regulations and standards manuals to learn the safety and other requirements you need to meet. These documents typically must be purchased (from UL, ANSI or wherever), so you’ll probably need to put through purchase reqs.

Hey everyone,

I'm a recent bachelor's graduate who just landed a job at a startup. Although I have a strong interest in and motivation to grow in the field, my hands-on experience in mechanical engineering is pretty minimal. Somehow, I’ve been hired as a mid-level design engineer. (During the interview, I was told this was a mid-level role. I managed to convey confidence and even somewhat outshined the interviewer by steering the conversation in my favor. I also presented a recommendation letter from my professor, which played a big role in landing the job.) I initially thought this was a manageable challenge, but after almost three months, the workload has become overwhelming. Developing a product that meets industrial standards—without the benefit of the typical gradual learning curve—has proven to be a major setback.

The Situation:

No Prior Experience: I’m completely new to the mechanical engineering practices expected in well-established product-based companies.

Solo Mechanical Responsibility: In our 4-member team, I’m solely responsible for the mechanical side. The other three team members are focused on electrical and software work and aren’t available to provide guidance.

High Expectations: Despite my lack of hands-on experience, the expectation is a final, well-working product without intermediate feedback or structured guidance.

Self-Learning Path: I’m already diving into self-learning and applying what I learn in real time, but I’m still unsure if I’m doing things the “right” way.

Questions for the Community:

Has anyone been in a similar situation? How did you manage the steep learning curve?

What resources (books, courses, mentors, online forums) would you recommend to quickly build a solid foundation?

How do I approach asking for more guidance from my team or supervisor without coming off as unprepared?

I’m really really passionate about this job and eager to contribute as much as my teammates. However, the pressure of performing at such a high level without proper mentoring is overwhelming. Any advice or insights would be greatly appreciated!

Thanks in advance!

First, it’s time to own up—not just to the team, but to your boss. The worst thing that can happen is to surprise everyone with failure at delivery time. Three months is already a long time.
As for worrying about sounding unprepared, get over it! You ARE unprepared, and the sooner your boss knows it the better. You can say you’re motivated and a fast learner but admit that you’re over your head.

Second, ask your boss for help. He/she may be able to get you mentorship from someone else in the company, or hire someone senior, or get a part-time consultant. These are things you can suggest.

Third, study study study. Read to get the skills you need. Read regulations and standards manuals to learn the safety and other requirements you need to meet. These documents typically must be purchased (from UL, ANSI or wherever), so you’ll probably need to put through purchase reqs.

Fourth, you might be able to get guidance through your professional societies, although this is more of a long shot. Most societies have clubs or forums for early career professionals and, sometimes, mentoring services.

To answer your other question, yes, I've been in jobs where I lacked the necessary skills, and I've used all four of the strategies listed above to some extent or other. Throughout a 45-year career, however, I never stretched the truth about my background and skills or overstated my qualifications. That's a lesson you've probably learned the hard way.

A final bit of advice is to take it in stride. You'll have a long career ahead of you and each step along the way is a learning experience (both good and bad). Good luck!

 

[Ivan Nikiforov]

Good afternoon! It seems to me that you were hired for a reason. Letters of recommendation are not given for nothing. The interviewers know their stuff too. You probably have wings, but you just haven't spread them yet. I can give you the following recommendations. 1) The success of any job lies in planning. Divide the task into stages, separate the main from the secondary. Determine the deadlines and resources for the implementation of each stage and strictly follow them. Be realistic about your capabilities at each stage. If necessary, feel free to ask for help. 2) Make the most of ready-made proven solutions. Create a library of ready-made solutions (parts, assemblies, structures). Try not to delve into the inventions. In large companies, 90% of the work is done using ready-made solutions. 3) Before starting work on the project, study the existing analogues and prototypes as fully as possible, so as not to reinvent the wheel.

Among the books, I can recommend the book "Theory of inventive problem Solving" by Altshuller.

 

[hutchphd]

To whom do you report? Have you been consulted on a schedule for your "deliverables" for the project? Did you agree to a schedule for these deliverables? Have you seen a Gantt chart for the effort?
If these items are foreign to you, then there may be many problems in the project, other than your own. It is time for honesty from everybody.

 

[CrysPhys]

It seems to me that you were hired for a reason.

Yes, but the question is, "What is the reason?" As I posted above, "Why would the company hire a newbie straight out of school for a critical position?" The reason could be they couldn't afford an experienced senior engineer. Or the manager is not competent. Or they could have some hidden agenda. Or ....

Letters of recommendation are not given for nothing.

The OP is a newbie straight out of school. So letters of recommendation can't address successful past performance in a scenario close to the one that the OP was hired into. Also, letters of recommendation are not always truthful (for various reasons).

The interviewers know their stuff too.

That's not necessarily a good assumption. Over the course of my career, I've dealt with some incompetent bosses who had been promoted into their slots for various reasons.

I once interviewed at a small startup tech company. Their chief technical officer and their chief intellectual property counsel were both impressed with me and wanted to hire me. But the two guys who held the real power were finance guys; and they nixed me. Turned out to be a blessing in disguise. I found out later that they had hired the husband of a former co-worker to fill the slot I had interviewed for. She told me the startup was a mess and folded less than a year after her husband had joined.

 

[PhysicsRelearner]

The advice you’ve received here is good and will help set expectations with your team (and perhaps some help / support).

There is a chance though that they will just come back with “we hired you to figure this stuff out”

In that case, I have two questions for you though. 1. How many hours are you working and 2. How many are you willing to work.

In other words, how motivated are you to grind your way up the experience curve. If this is something you want, you may need to work very hard. Early in my career, I spent many years working 80+hours a week. Sometimes you just need to get a couple of years of experience in half that time which means you double the hours.

Get in early, stay late. Do reading and learning in the evenings. Go on upwork and hire a mechanical engineer with the right industrial background from a low cost country and spend hours / weekends learning from them. Don’t share with them the work you are being paid to do, but there are a lot of more generalized questions and learning you can work with them on. One of the AI engines can be very helpful as well.

You have agency and can climb the mountain if you are willing to do what it takes if they don’t provide support. Or, you can find a new position somewhere more inline with your current capabilities / experience. I have no idea which is best for you - it’s your call!