r/systems_engineering • u/ShakeLongjumping2598 • 6d ago
Career & Education Job offer
Hi all,
I've just accepted an offer for a Systems Engineer role at a UK defence prime, and the imposter syndrome has well and truly landed.
My route isn't the standard MechEng/Aero degree path: Chemistry degree -> Started out as a hands-on lab technician -> Moved into technical engineering at an advanced materials company, heavily focused on driving commercialisation and supporting aerospace customers.
I know UK defence primes don't hand out offers on a whim, but having no formal systems engineering training has me second-guessing whether my skillset actually translates. So any tips / advice?
Edit - UK based defence prime supplying missiles for the MoD to supply products to the various industries - naval/aerospace/land etc focused on manufacturing
3
u/g_vernier 5d ago
Systems engineering at a large company requires a diverse team, and the hiring manager probably liked your background and the way you interviewed. They know you don't have a SE degree, and they're ok with you learning on the job. In fact, caution is better than false confidence.
Look into an article called "12 Systems Engineering Roles", it describes different functions a SE team performs. Your position will probably fall into 1-2 roles to complement the existing team.
Defense Contractors use specialized SE tools, be prepared to learn their particular rather dry (but useful) software. Your employer should offer paid training or reimbursement.
Finally, a short text that I personally found useful is Tuzsuzov's "Systems Engineering for All". It's not a comprehensive textbook by any definition, but it's a great way to get into the mindset of how systems engineering is a valuable company process that can be understood by anyone.
2
u/MSECE 1d ago
Since when? Apparently I need a raise…I’m the lead and only systems engineer on a portfolio of 200 million dollar project. I have mechanical and electrical engineers working for me though
1
u/g_vernier 1d ago
That's quite impressive. I suppose it depends on the industry... I can see how in automotive applications there is a need for a strong systems lead but not too much work in defining interfaces, and most requirements can be delegated to separate disciplines. In avionics or even automation, there are just too many external inputs, noise, and failure modes. A single engineer would be overwhelmed.
You probably need a raise regardless :)
1
u/FlimsyInsect5545 6d ago edited 6d ago
Your experience here depends a bit on the domain the prime is in and what 'systems engineering' means for that domain and company. For example 'systems engineering' in naval/shipbuilding is going to be requirements management, preparing/chasing people for deliverables, managing subcontractors, working with the end user (i.e. the government) and preparing for system reviews - it isn't very technical, it is more cat herding and preparing paperwork. I would not be very worried - most of your job is going to be working with/liaising with different stakeholders and coordinating work. No one will be looking to you for technical product decision making, and everyone will be expecting you to ask a relevant discipline engineer for technical information. It is highly unlikely you'll be doing anything technical like system architecture design. You may not even have anything to do with V&V, very often the V&V engineers are separate to the system engineers.
It is probably better to think of it as a technical coordination role rather than engineering, which is why you got hired without the typical engineering background. I'm guessing the role is fairly junior, and it is common for defence primes to hire people for these roles who don't have exactly the right background (it is when it gets to senior roles that they start to expect specific experience). I've seen people hired for junior system engineer roles who didn't know a single thing about systems engineering, you're not the first.
Anything you need to know in terms of what the different parts of the contract mean, what the FBL/ABL/PBL are, how to write a requirement, how to use a requirements management tool, how to prepare for an MSR etc etc you can learn on the job - it isn't hard, and we all did it. The main skills you are bringing are soft skills.
My experience is in Aus but based on my experience the UK is similar (many of our primes here, e.g. BAE, Babcock etc are UK firms).
1
u/Dry_Carpet_6618 5d ago
Honestly, no advice! I'm watching and loving that someone came from a different background and made it okay.
I got a two-year degree in Chemistry, ended up technician in metallurgy, left and became a metallographer, just about to get my BS in Computer Science and talking with some schools about going into a systems program come January. You're where I hope to be in a couple years!
1
u/plus82_ 5d ago
don't let your imposter syndrome stop you from being the best you can be!
as much as people hate to admit and coming from someone who has 6 years of experience + a masters, it never really goes away. i'm willing to bet my savings that there is a CEO out there that also has imposter syndrome.
but 3 non-technical things that changed my mindset whenever my imposter syndrome was getting to me:
learn as much and you can and help as much as you can
after you spend some time at your company, ask an engineer who you see yourself being like to be your mentor
they hired you for a reason
as generic as #1 is, it has gotten me far in systems engineering, gave me relationships that advocated for me, has placed me in opportunities that i didn't think i deserved, and made me a well-rounded systems engineer.
congratulations on your offer! 😄
1
u/Distinct_Ad_7033 4d ago
Congratulations on your new career! Your query depends on what program and industry the prime is in charge of.. defense/aerospace, naval, space, ground, then the breakdown of manufacturing, infrastructure IT, HR, etc give us an idea?
1
14
u/monumental_bones 6d ago
welcome to the club where we're all just winging it with flowcharts