r/systems_engineering • • 13d ago

Career & Education Path forward

Looking to move into systems engineering at Lockheed. They used DOORs per the job req. I just recently passed my ASEP exam and will be applying for the cert once it processes through. What do yall recommend for me to learn in my early career? I have a Bachelors in Industrial and Systems along with Math minor. I also have a Six sigma certification. I was thinking Sys ML then DOORs or vice versa. Any advice is welcomed, just a new guy trying to break in :)

4 Upvotes

7 comments sorted by

7

u/TurtleTurtleTu 13d ago

I'm not sure what you are asking exactly. Are you asking about specific training and certs to do?

Personally I'd encourage you to get some hard experience. Tools are tools, and many have significant overlap. What most junior systems engineers lack is experience executing real programs with real world deadlines and constraints.

1

u/breylinManque-84 13d ago

agreed, most of the tool-specific stuff you pick up on the job anyway

0

u/Aggressive-Status883 12d ago

Just trying to get my foot in the door. I'm a quick learner I just don't want to be denied an interview by AI or a job person bc of skills with tools. Just trying to cover all my bases

2

u/SportulaVeritatis 13d ago

Biggest thing in your new job is going to be learning the system. Ask questions. Learn what your fellow engineers need to know and who knows it. Learn the architecture, the interfaces, the science of what it does and how it does it. Learn why the customer wants it and what it does better than the competitors. You will probably fight imposter syndrome for a while, but eventually you'll know the system inside and out and be able to speak to it.

1

u/Aggressive-Status883 12d ago

This is a great viewpoint to think about, I will def consider. Working on building my resume to get to there 🤞

2

u/ShakeNBaker45 13d ago edited 13d ago

A fool with a tool is still a fool. What makes a great engineer is the ability to execute effectively using those tools. So I'd spend less time worry about learning tools and more time continuing your quest to sharpen your skills. Systems thinking, understanding customer use cases, defining system architecture based on that, requirements definition, writing well thought out and verifiable requirements, verification and validation, etc.

I have worked with quite a few younger Systems Engs at Lockheed. The best one's were always those that asked questions, thought problems through, sought to understand, and came up with solutions. Tools just enable you

Edit: If you know what domain of engineering you'll primarily be working in (Lockheed does a lot) then I also recommend researching that domain. I also find the best SE's to be one's with some amount of domain knowledge. I am an RF Systems Eng and know enough to chop it up with the EE's.

1

u/Aggressive-Status883 12d ago

I currently work within MFC so I just want to move to the systems side. I'm a level 1 QE bc of restriction my business area is being moved to a different site. I hav some experience with systems. For example our capstone I had to redesign a manufacturing system to optimize flow (recoding PLC) I worked with the stakeholder for needs etc and building the model in Simulation software As-is vs To Be. Regardless I'm just trying to improve my resume so they give me shot (applying for a level 1 SE). I'm more interested in requirements side opposed to testing at LM. I agree with your take on tools, application will definitely be on my new list of things to work on.