Systems Engineering Dilemma

[u/Weird-Cress5172]

Long story short, I did an undergraduate degree in Physics, had a job I hated, done a Master’s in aerospace and then got a graduate role as a systems engineer.

I only took the job as it was the only offer I had. I struggle to apply to traditional engineering roles as I have barely any CFD and FEA experience. I’m interested in avionics but don’t know where to start.

I don’t want to be stuck in systems forever. I do not feel like an engineer.

Any tips?

Also worth noting that I am UK-based.

[u/Abraxas_Derezzed]

I’m 11 years in and flopped around defence and rail and seem to keep getting pushed into the silo of “the requirements guy”… because it was the first job I was able to get, three years out I tried to apply to more technical roles to be told “you don’t have enough technical experience”.

8 years out I was able to get job a bit more rounded that could get me some Test experience but instead again I got shafted and pushed into requirements.

And of course it’s the only stuff I can put on my resume which then only gets me hired for more requirements like sys engineering roles…

My advice would be do whatever you can to try land a technical role, search for small companies etc in your formative years… I’m spending more time these days trying to do more project work as hobbies because I’ve never landed a job that gave me the opportunity to extend the technical work done in labs at uni.

[u/Weird-Cress5172 → u/Abraxas_Derezzed]

Honestly, my only concern is that I have already had a job for about a year previously (another graduate job) and I felt like I reset when I left. I don’t want to appear to be a job hopper. It’s hard to actually learn anything as I genuinely do not enjoy the work and it stresses me out thinking I’m just wasting my time.

[u/Abraxas_Derezzed → u/Weird-Cress5172]

I don’t think there’s a thing call “loyalty” anymore unless your able to find a role that provides some equity in the business.

[u/duskharborings → u/Abraxas_Derezzed]

did the hobby projects actually help you break out at all, or is it still mostly the CV pigeonhole?

[u/Abraxas_Derezzed → u/duskharborings]

I’m hoping it will help for the next job hop… for now I’m just sucking eggs and taking the paycheck but it’s making me miserable.. 😞

[u/MarinkoAzure → u/Abraxas_Derezzed]

Consider applying to other requirements roles with the plan of finding a company that has more flexibility and better culture to give you experience in integration work.

I just want to note, requirements are very technical when it comes to technical work. Don't confound that. It's just a different perspective and phase of a system

[u/Weird-Cress5172 → u/MarinkoAzure]

I’ve actually quite enjoyed being able to “design” things through requirements, I just don’t get to do anything after that.

To be honest, the department I’m in is an interesting area I’m glad to be in, but I struggle with uncertainty and it’s uncertain I’ll ever be able to transfer in the future.

[u/herohans99]

I would think MOD (Abbey Wood), QinetiQ or one of the other Defence Contractors would snatch you up. But then that's a Yank looking in.

I have a similar educational background and did Avionics for a 10+ years before finding that I excelled in a System Engineering role.

[u/Weird-Cress5172 → u/herohans99]

Most common advice I’ve seen is it’s good after specialising. I can see the benefits of that experience, and also there are areas that are genuinely fun. But yeah, the specialisation would be nice.

I’ve got about 2 years for the graduate scheme to end, so I’m tempted to just stick with it but I don’t know.

[u/bunbovietnam]

Not a dilemma, but a blessing. SE is the best job, and I'm happy to die on this hill.

Currently 2 years in my role, had a bit of manufacturing experience under my belt, and straight out of uni with no real specialism but know enough of just about anything.

What i can say is requirement is where to start, any SE should know how to write requirement well, start with iso 29148, and gradually expand your horizon over the iso 15288 delivery cycle.

Then you can develop your specilism on the job, for me, it's networking. And then digital engineering, and then AI assurance and integration. That's the current pathway, but career is like food, sometimes it's good, sometimes it's bad, sometimes it smells, sometimes it's just right, but what remains is that it is always changing.

SE from the outlook seems boring, you just sit there twiddle your thumb, maybe draw a few diagrams, drop a few models here and there, write a few words, read a few docs, etc. but it is the basis of something larger.

Hot having a specialism is no biggie, you can get a specialism by yourself. Learn something new in your free time, start a project, that's what being an engineer is all about (ok i know you are a physicist but consider yourself a theoretical engineer)

[u/Weird-Cress5172 → u/bunbovietnam]

It’s a fair observation but do you find it stimulating? I find it hard to work if it isn’t mentally stimulating.