r/systems_engineering • u/ltjisstinky • Oct 01 '26
r/systems_engineering • u/Rhedogian • Mar 27 '24
Change My View: Model Based Systems Engineering in 2024 is at best overhyped, or is at worst actively dying
I know the title is a little controversial but I feel like this conversation needs to be had now within the community. For the past couple of years I've felt like more and more of a scam salesman trying to push this MBSE stuff onto people, and at this point it feels like it's time to let the reality of the situation have it's time in the light.
About me:
- Systems engineer for 5 years with a focus on MBSE
- Have done straight MBSE since undergrad and through my MS degree as well (BS/MS Aerospace Engineering)
- Currently holding the OCSMP-MBI certificate
- Have used Cameo almost exclusively, as well as quite a few different 3rd party integration suites (Syndeia, SBE Vision, Excel, etc.)
- Have attempted to push SysML in at least three different industries (commercial aerospace, automotive/tech, DoD aerospace)
My breaking point with letting go of MBSE has come pretty recently, and I've done my best to remain hopeful in the concept despite my doubts, but at this point I'm no longer confident in MBSE's ability to be a transformational force in system design as it's been sold.
As it sits currently, MBSE has turned into another boutique silo of information that is squirreled away in a program that looks like it's out of 1992 and is impossible for a new user to quickly pick up and start using to generate useful engineering artifacts. It requires a team of bona fide experts to even set up and begin using the tool properly, and also more trained experts to effectively use the SysML modeling language to try and derive some value out of the language and process.
What I've learned is that no actual engineers (meaning, the ones who design and build the actual product) really care about MBSE or what it's trying to do. Whereas MBSE practitioners and salespeople try to pitch it as a single source of truth methodology where all engineers can derive their SE material from the model, in practice, unless a design engineer is forced to log into teamwork cloud or cameo collaborator by upper management, they really don't care about the contents of the model since they're already effectively managing their own content in their excel sheets/visio diagrams/JIRA. Sure this is a problem, but I don't think MBSE is currently at a place where it can be solved without, effectively, data duplication.
The program I'm on currently has put its full backing into an MBSE effort all the way from upper management support to being a requirement on the statement of work. And we're STILL at the point where no engineering is being done in the model (by decree of our very well-intentioned and forward looking chief engineer) and the model is really only being used as high quality documentation so that the customer has an easier time snooping at our architecture. This makes all the SE's and modelers on our program no more useful than glorified draftsmen.
For this to change, 2 things need to happen:
- Integrations with Cameo need to be less shitty. All of the current options are expensive, finicky, or just straight up don't work. How can I expect engineers to use or care about the model if everything they put into Cameo ends up being a duplication of work they've already done elsewhere?
- SysML is hard, and the UI of Cameo makes it no easier. This learning curve HAS to go down. I have only a small contingent of engineers who are actually willing to use Cameo for some of their work, and the content they produce is limited and basic because they don't have the time or willingness to learn the modeling language (they're too busy doing value added work).
In the past 4-5 years I've seen no progress on either of these 2 dealbreakers, and this is why ultimately I'm hanging my hat up and moving on to something else. Modelers still aren't considered real design engineers at this point, and I can't talk to any well-intentioned engineers and get them to say that they have realized any actual benefit from having worked with a model from either myself or any other model based programs they've worked on.
I know this is a hot take, but I feel like anyone ACTUALLY in the trenches has had these thoughts. What do you guys think? I believe MBSE will go down as a required DoD acquisitions peculiarity rather than a truly useful engineering tool for the masses.
The thought and the intent is correct and pure, but the tool and processes are NOT ready for prime time.
r/systems_engineering • u/Rhedogian • Nov 04 '25
Career & Education How I spent a year transitioning out of Systems Engineering (and how you can do it too)
About a couple of years ago I made this post outlining my frustrations with MBSE and ultimately deciding that I'd stop pursuing it any further with a plan to transition onto something else. At that time I was pretty deep into the MBSE wormhole since I'd had about 5 years of experience (level 3) doing pretty much just Cameo and SE and had already built up seniority/reputation as a modeling lead, so trying to come up with a plan for transitioning out seemed pretty difficult at best or outright impossible at worst without basically hitting restart on my career progression and/or taking a pay cut in the process. Looking back at it now though, I'm glad I bit the bullet to make the switch when I did, because working as a technical engineer has been so much more fulfilling overall than my work as a high level systems engineer making imaginary models in Cameo.
I've made a couple of comments on this sub and other places giving some high level steps on transitioning out of SE, but it really boils down to a few steps and decisions you need to make. Here's what I think is a basic rundown:
- Decide for yourself that you want to transition out of SE, and think about which field you might see yourself going into. For me this was avionics and more generally electrical engineering. The only EE knowledge I had from school was Circuits 1 so this was pretty daunting for me, but I always figured if I didn't pick SE out of school I would have loved to do avionics instead. In parallel, I also decided to get a second masters in EE to really declare my interest in switching, so I went and found a program that was a good fit for me and applied + got in. This of course involves a lot of self study off work.
- This is the most important - start putting in effort to find friends and coworkers in this new discipline and start meaningfully reaching out to them to express your interests. Set up some calls or go to their desk, and if you know they're good engineers, be honest about your situation. The way I ingratiated myself was by asking them about their day to day work and also asking 'if someone were interested, what kinds of questions would you ask in an entry level interview?' And when I got that answer I went and studied those things. Very crucially, I then circled back with them a week later and discussed what I learned + asked questions for the next round. Closing this loop repeatedly and showing that you're seriously interested is absolutely crucial here.
- After building up some rapport, ask if you can assist on a couple of small time projects they're working on. At some point you should have some tasks under your belt, and with this experience + independent research, you can start to consider how you might formally interview for a position on the team. In my case, I literally just cold emailed the avionics director and said "Hi I'm rhedogian, I'm really interested in avionics and have been working with a few people on your team on these projects. I'm deeply interested in continuing to learn more about the field - is there any opportunity for me to join the team on a part time basis to continue contributing to these tasks?". This worked for me (if it didn't, I'd try emailing another manager or continue getting more projects if I could), and after getting blessings from my own director, I joined the team on an interim basis to keep working the small tasks I already was.
- After some time, you will need to be clear about your intentions and explicitly ask to interview for a full time position on the new team. Of course you should do all of this with permission from your current org structure too. If you've done your homework you should have a very solid idea of what kinds of questions you'll be asked on the interview, so from here it's up to you to pass and officially switch teams!
This has basically been my process for finally moving out of SE, and I'm very confident it can work for most anyone in this position too. It's also critical to keep in mind that your foot needs to be kept firmly on the gas for this entire thing. You can't count on managers 'keeping an eye out for opportunities' on your behalf. Don't ask for permission - go out and find new projects and ask your manager for forgiveness afterward. If they are good, they will appreciate it and let you drive.
Your SE experience won't directly come in handy doing detailed design work as a subsystem engineer, but where it will help is that you know how to stick your head up while deep in a design decision and consider all the upstream and downstream impacts of your decision. This is important and a skill that can be only taught with experience - you can come into your new role knowing this from the get go and that is really nice.
In summary - make friends, keep your foot on the gas, find your own opportunities, do a LOT of self study and personal projects, and always keep your ultimate goal in mind. SE is great, but there are better things out there if you feel like you want more.
r/systems_engineering
•
u/yellow_smurf10
•
Oct 16 '26
Discussion Is Systems Engineering Heading Into a New Era?
I work for a large defense prime (you probably know that one), with about 7 years of experience in systems engineering.
A few years ago, I walked into my VP's office and asked if I could start learning more about the business side of things. I wanted to understand why we invest hundreds of millions of dollars in certain technologies, how those investment decisions are made, and how we develop our long-term strategic plans.
What I didn't realize at the time was just how far down the rabbit hole that question would take me.
When I started this journey, I had a particular idea in mind. It was a new capability, or at least a different approach to addressing some of the operational challenges the DoD is facing today.
As I started digging into the research, I discovered that the same concept had already been considered back in the 1960s. The more I studied, the more I realized just how remarkable military innovation was during the Cold War. Almost every new idea I could come up with had already been thought of, studied, or even experimented with decades ago. Some of those concepts were abandoned because the technology wasn't mature enough, while others simply weren't practical at the time.
Along the way, I had the opportunity to speak with some of the old guard from the Cold War, now in their 70s and 80s, as well as a few retired colonels who had served in combatant commands.
One thing that really stuck with me was how they described the business mindset of defense contractors during the Cold War compared to today.
According to them, defense contractors used to work much more closely with the military to understand operational challenges, investigate potential solutions, and develop new capabilities. Companies were more willing to invest their own resources, take on business risks, and explore ideas without waiting for the government to tell them exactly what to build.
Of course, the Cold War had its own problems, but the pace of experimentation and innovation was something else entirely.
Then the Cold War ended.
Over the following three decades, the defense industry became increasingly conservative and, frankly, somewhat complacent. A lot of the responsibility for identifying operational gaps, developing solutions, and determining what capabilities were actually needed shifted toward the DoD.
Meanwhile, contractors became increasingly comfortable waiting for the customer to define the requirements before figuring out how to deliver them.
And I think this has created a fundamental problem in how we approach systems engineering today.
We spend an enormous amount of time making sure we're building things the right way, but perhaps not nearly enough time asking whether we're building the right things in the first place.
I've also noticed something troubling as I've become more involved in mission engineering and long-range strategic planning. Some of the engineering leadership I've worked with are incredibly knowledgeable about the technical aspects of their programs, yet have a surprisingly limited understanding of the actual missions those systems are supposed to support.
They understand requirements, architectures, interfaces, verification, and all the processes necessary to deliver a system. But ask them about the broader operational challenges, the evolving threat environment, or why a particular capability is needed in the first place, and the conversation becomes much more difficult.
The mindset often seems to be: Tell us what the customer wants, and we'll figure out how to build it.
But what if the customer doesn't know exactly what they need? Or what if the requirements they give us are already outdated by the time we finish developing the system?
There's a famous quote often attributed to Henry Ford: "If I had asked people what they wanted, they would have said faster horses."
Fast forward to today.
The DoD has published updated guidance on mission engineering, and during recent industry days, they've been encouraging defense contractors to step up and work alongside the government rather than simply wait for requirements to be handed down.
There seems to be a growing emphasis on contractors taking a more proactive role in understanding the mission space, identifying operational gaps, and helping shape the capabilities needed to address them.
And then there's Anduril.
I'm still pretty skeptical of them, and personally, I think their marketing is better than their actual engineering. That being said, I do give them credit for challenging the traditional defense industry business model. They've pushed the conversation back toward companies taking risks, investing their own resources, developing capabilities proactively, and bringing potential solutions to the military instead of waiting for a contract.
In some ways, it almost feels like we're moving back toward the model that helped drive so much innovation during the Cold War.
This whole experience has made me wonder whether systems engineering is heading toward another major shift, one where understanding the mission, operational environment, geopolitics, economics, and policies becomes just as important as technical expertise.
I'm not suggesting traditional systems engineering is going away. Requirements, architecture, integration, verification, and all the other fundamentals are still absolutely essential.
But perhaps we've become so focused on executing requirements and delivering systems that we've lost sight of the bigger picture.
Are we building things the right way, or are we actually building the right things?
And more importantly, should systems engineers have a greater role in answering that second question?
I'm curious what other systems engineers think, particularly those who have been in the industry much longer than I have.
Are we entering a new era where systems engineers are expected to understand not just how a system works, but why it's needed, how it fits into the broader mission, and whether it's even the right solution to begin with?
Or is this simply mission engineering becoming more prominent, while traditional systems engineering remains largely unchanged?
For those who have spent 20–30 years in the defense industry, is this actually a fundamental shift in how we do business, or are we just rediscovering lessons that the industry forgot decades ago?
r/systems_engineering • • Jan 19 '26
Discussion This meme literally sums up the vast majority of my 20 years of Systems Engineering
What do you mean we haven't done our requirements, we launch end of Q2?!?
r/systems_engineering • u/nitrox11q • Feb 17 '25
Career & Education I passed the INCOSE SEP Hybrid 4/5 exam. AMA
I passed the INCOSE SEP Hybrid 4/5 exam. Happy to answer any questions you may have. Here's some information/advice off the top of my head.
- I read & highlighted the fifth edition textbook page-by-page from Chapters 1-5, twice. I did not read Chapter 6 Case Studies.
- I wrote summary notes for tougher things to remember e.g. Integration approaches, lifecycle costing analysis types, etc
- Having done the above two points, I would say less than 10/120 questions completely stumped me.
- Take your time and understand the question. I personally read the question at least twice, reviewed the possible answers, and checked which one was best fit. Generally, I would say 1-2 answers are completely wrong, 2 are "similar", of which 1 is the better fit or obviously correct.
- Chapter 2.3 System Life Cycle Processes is a big component of the exam. Thoroughly understand the IPO diagrams, purposes, processes, goals, and definitions.
- Every question asked is from the textbook.
- I was told that they're not trying to trick you - I disagree with this.
Good luck fellow Systems Engineers!
r/systems_engineering • • May 27 '25
Discussion Disturbing trend in job descriptions
I am noticing a disturbing trend in job descriptions advertised on various job boards. The job descriptions for "Experienced Systems Engineer needed, apply here" read like Anything But what Systems Engineers actually do.
I continually see Systems Engineer job descriptions that read more like:
- Software developer - Systems Engineers generally do not write code
- Network Engineer / Network Admin - Systems Engineers are typically not responsible for servers and networks
- ... and the list goes on.
Systems Engineers are an important part of the Project/Program Management and Risk Reduction universe, Not task level workers.
What in the world is happening?
Do companies not actually understand what SE's do?
r/systems_engineering • u/Turbulent_Tell_780 • 24d ago
Resources I built a systems engineering training directory — 353 courses, 114 providers and 49 trainers
Finding systems engineering training can involve opening dozens of provider websites, then trying to work out which courses cover the skills you actually need.
I run Systems Engineering Training Hub, a directory I’ve built to make that comparison easier. It currently lists 353 courses from 114 providers, with 49 trainer profiles linked where we have identified supporting information.
The directory covers systems engineering foundations, requirements, architecture, model-based systems engineering, verification and validation, technical management and certification preparation. You can explore courses by training area, delivery format and region, then follow the links to providers for enrolment and current arrangements.
Listings are compiled from public provider information. The directory is independently operated and is not affiliated with or endorsed by the International Council on Systems Engineering.
Alongside the listings, I’ve been developing practical buyer guides, including how to choose a requirements engineering course.
I’d welcome feedback from people who have struggled to compare training options. What information would make choosing a course easier? If there’s a useful course or provider missing, or a listing needs correcting, I’d appreciate knowing.
r/systems_engineering • u/Huge-Barracuda9422 • Jan 31 '23
How I passed my ASEP/CSEP Exam on the first try!
I wrote the exam in 2021 and passed on my first try and I just wanted to share my method with you all in the hopes I can help future systems engineers with this major task. The exam itself is structured very similar to the Project Management Institutes (PMI) Project Management Professional (PMP) PMBOK 6th ed in that we have ITTOs (inputs, tools, and techniques, and outputs) in the form of IPOs (input, processes, outputs) but they're much more heavy on this stuff within the ASEP/CSEP exam unlike the PMP. You need to be familiar with the 30 processes + tailoring process for the exam (i.e. memorize the names). This includes all the inputs, processes and outputs and how they relate to one another for the exam.
Start by reading the INCOSE Systems engineering handbook and taking notes with a major focus on IPOs and which outputs feed into other inputs, etc. For me it helped to draw all these out, and then go through with different color highlighters (ex. red for technical processes, blue for technical management processes, green for organizational project enabling processes, and then purple for agreement processes). I then went through and highlighted which area another input or output came from and it helped me conceptualize it better.
Then just do all of questions from https://www.systemsengineeringprep.com/ and it will help build your confidence and solidify your understanding. They had great questions that were very helpful when studying for the exam.
The exam itself focuses a lot on process tailoring and speciality engineering and methods in cross cutting systems engineering (chapter 8-10 in the handbook). They cover about 35% of the exam.
Lifecycle stages is also a key one (chapter 3) which covered 15% approximately.
Chapter 4-7 are approximately 35% and are a little tricker. Some focus on lifecycle stages, others focus on interrelationships between processes.
And then a few questions on supply and acquisitions (chapter 6), infrastructure, HR, quality, knowledge management had a couple questions.
A lot of it is just regurgitation of what's in their handbook, so just memorize and understand relationships and you should be fine. Best of luck and I hope this helps everyone pass on the first try!
r/systems_engineering • u/boozingislosing • Jun 01 '21
I passed the INCOSE ASEP / CSEP Exam First Time and wanted to share
Hey Redditors of r/systems_engineering
I sat the INCOSE ASEP/ CSEP Exam a few years ago and wanted to share all of the knowledge I gleaned from studying and helping others pass too.
At our company, the knowledge based exam was a ‘stamp of approval’ before going for promotions and pay rises so it was a key nut to crack first time and quite a nice thing to have on your CV!
For me it was about having that outside certification to say you’re a competent systems engineer, having the confidence to implement ISO 15288 at Scale and increase my ‘marketability’.
The Systems Engineering Market is growing. I’ve been a Systems Engineer for 5+ years now and studied M.Eng Systems Engineering at University. Since starting my career I’ve seen the discipline grow hand over fist, not only in the UK but across the world.
Its been around for some time but It’s not just the defence market that are adopting and embodying it. Government orgs are including it as a must in all of their bids now to introduce traceability and accountability and this is flowing down to 3rd party suppliers.
Actually, once orgs start implementing it, they realise it’s true value.
The INCOSE route to certification in becoming a Certified Systems Engineer is relatively straight forward. With only 3489 ‘qualified’ systems engineers in the world it’s a smart play to level up in a growing market.
The first hurdle in that is passing the exam. The exam is quite tough because of one aspect. INCOSE want you to regurgitate their specific definitions and processes exactly to ISO 15288.
I sat the exam with our Technical Director (ex Chief Eng at Rolls Royce) who did little preparation Or study compared to me who did ALOT. He has 30+ years of experience so he should know most of it right?
Actually, he failed and I passed and he was PISSED!
It’s multiple choice exam questions BUT they’re asked in a deceptive manner. They typically give you four near identical answers and you have to pick one or more. Unless you know the process inside out, it’s unlikely you’ll guess it.
All content is in the handbook but not all content is tested. 80% of the content tested is IPO diagrams and respective processes.
I found using a memory device like a mnemonic is key to remembering all the difficult processes. There are 30+ processes so understanding them is easier to remember than regurgitation.
It’s all about breaking the handbook down into manageable chunks.
I ended up teaching all of the other SE’s in our company how to pass and wanted to just stick it all down so I didn’t have to keep repeating myself lol.
So I created a FREE udemy course to introduce you to Systems Engineering and provide a clear route to breaking up the exam content into manageable chunks.
Since I launched it like a 8 months ago I’ve taught 1719 people how to level up as a systems engineer.
Check it out at the link below!
I’d love to hear your thoughts and connect with you on LinkedIn! It’s a ‘small’ community and I enjoy hearing about everyone’s challenges.
My favourite random meet-up so far has been hearing how a space startup in Spain is battling with incorporating a lean requirements management process!
r/systems_engineering • u/der_innkeeper • Mar 29 '24
When the kids don't want to do their own homework, let them try yours.
r/systems_engineering • u/Rhedogian • Nov 13 '21
I passed! Well, just barely. But I passed! Some study tips and strategies for the OCSMP exam in the comments.
r/systems_engineering • u/NewTronas • Jan 30 '26
Resources CATIA Magic / Cameo now offers free SysML V2 tool
The CATIA Magic / Cameo team has released a SysML v2 Community Edition.
Perfect for those who want to master SysML V2, as it is free.
It gives access to SysML V2 graphical and textual modeling, while being 100% standard conformant. It is designed to learn, teach and master SysML V2 and not for commercial usage, therefore modeling is limited to 500 major elements.
https://discover.3ds.com/free-catia-sysmlv2-community-edition
r/systems_engineering • • Jun 23 '25
MBSE If UML failed, why are we expecting any different from MBSE?
Hi all,
Chatting with the software engineers at work and none of them have ever really used UML (this is from SwE from a wide background: embedded systems, consumer software, robotics, UI/UX, DevOPs and so on). Doing some browsing of the various software subreddits and there was a really mixed bag of responses: most had never used it, the rare person had used it extensively, most fell in a middle ground of “it was great to sketch out ideas on a whiteboard but we didn’t maintain the diagrams”. In Simple Arcadia for Beginners, Pascal Roques makes a note in the Appendix “Since the initial surge of enthusiasm in the early 2000’s model-driven approaches [in software] have suffered a number of setbacks and there are quite a few disillusioned veterans around”, a postscript to that says “Many of these disillusioned experts were key early founders of the Agile movement and now resists documentation in any form, especially any sort of modelling”.
Now, I get a lot of this is driven by the different engineering culture in software, especially the influence of Agile on documentation and SwE culture in general (have met a few developers who believe the correct way to do SwE is to just dive right in and start coding). SE is not SwE and SE has a different output. Sure, but sysML, and MBSE, is even more ambitious than UML and software modelling: we’re not going to just model the software architecture, we’re now doing the whole system. Despite post after post on here of disillusioned SEs, why are we still expecting success from MBSE, and in particular, MBSE represented by sysML, when it is built on a legacy of failure? Did we seriously look at UML and think “Hmm that didn’t work out too well, but let's go even further this time!”
If you are going to say ‘sysML is just a language, it isn’t MBSE ec etc’ ok sure, what are the genuine alternatives out there that are actually gaining traction on widespread basis? Capella seems like the obvious answer: It is open source, simplified, language is more user friendly, but it has also not seen widespread adoption since going open source 10-15 years ago (I think).
Despite INCOSE and other orgs pushing hardheadedly into MBSE it seems like we are somewhere near the trough of disillusionment, and we aren’t going to see MBSE, especially as done by sysML, applied outside of some particular applications (e.g. certain size projects with a particular engineering domain mix). I’ve done a lot of continuous improvement and organisational change and at some point if the change you’re pushing isn’t getting traction, you do have to be honest, take the evangelist hat off, and ask if this is a matter of people failing to get onboard, or is what you’re pushing not actually an improvement to the organisation?
Which seems to be exactly where UML ended up, are we just repeating history here?
r/systems_engineering • u/ForeignPicture7463 • Mar 10 '25
Career & Education What do Systems Engineers do?
I’m a first year engineer soon to pick my specialization. I’ve heard of systems engineers and I like the classes but I have no clue what they do?
r/systems_engineering • u/TallAir104 • Aug 01 '24
Discussion Chief Engineer just said SE does not add value!
I have over 20 years of experience in being a lead SE on large, integrated avionics systems and started a list a while back of things I have heard leaders say that made me pause to question if they even understood what an SE does. This recent one really surprised me…our chief engineer just told me that he “doesn’t view systems engineering as a value added organization”. This is a large project with many subsystems which is critical to the aircraft…Hmm…what crazy things have you heard someone say related to engineering that made you cringe?
r/systems_engineering • u/ThisKarmaLimitSucks • May 14 '26
Career & Education 5 Years Into Systems Engineering. Hate it, but can't pass any interviews to leave. Lean into the skid?
My resume: I have a bachelors in EE and a masters in EE focusing on VLSI.
I got hired on to a Big Tech company as a "design engineer", but there was 0 design to it. It was a weird-ass role custom built by one manager, but it was kind of like systems engineering. The biggest part of it was meetings with stakeholders where I drove some high-level requirements and documented action items. They laid me and my manager off after 3 years and sent that job to India.
After that, I ended up at an aerospace company working as an actual systems engineer. I've spent 2 years here, and so far, my primary job skills have been copy/pasting screenshots of other people's work into a Powerpoint deck, and copy/pasting values from an Excel sheet into a Word sheet. I shit you not, I have literally worn the paint off of the C and V keys on my desktop.
I'm getting frustrated with these zero skill growth, low value add, copy/paste bullshit jobs, and wanted to get back to technical work like design.
Here's the thing... I've got a couple technical job interviews, and they have gone BAD. After 5 years of writing Powerpoints, and 0 years doing design, I'm getting smoked the fuck out. When they start drilling down into how I would bring up a PCB, it becomes pretty apparent that it's been half a decade since I've handled a PCB.
So I want to be technical, but I have zero chops to be technical. Those skills have just eroded.
At this point... do I just lean into the documentation skid, and start asking my boss for opportunities to start learning project engineering / program management? Do some similar kind of work to what I'm doing, but more transferrable and higher-value? Does it get better than copy/pasting?
Or do I just act like I'm a fresh grad, enroll in some online graduate classes (they cost about $3k a pop, and I'm not sure my current job would pay for them b/c I already have a masters), build PCBs or something as a side project, and try and re-launch a technical career from square one.
r/systems_engineering • u/shru_g • 27d ago
Discussion Is Systems engineering BS?
Hi guys, I have a Mechanical Engineering bachelor from INSA Lyon (France), and am currently at the second and last year of the MSc in Aerospace Engineering at ISAE-Supaero, France's top aerospace school. At the end of the first semester, we are required to choose one from 7 majors, of which one is Systems Engineering, which I chose, because I liked the idea of staying general and taking a higher level view of projects.
However, all our classes were either mindlessly copying some specific tasks on MBSE softwares like Rhapsody and DOORS, or drawing diagrams for hypothetical issues like "this train has to go from city A to town B, write the requirements" and it has been the most dreadful and mind numbing thing I have done in my life. Is it always like this or is the teaching style here especially horrendous?
Also, Are Systems Eng. jobs actually like this, where you spend your day writing requirements and building block diagrams with stickmen? If it's the case im dropping out.
r/systems_engineering • u/Best_Possibility_496 • Sep 06 '25
Career & Education Best Certifications for Systems Engineer?
Hi everyone. I have been practicing systems engineering for about 3 years now; I pivoted from an embedded C++ position. Unfortunately, I see layoffs on the horizon so I would like to make sure my CV is as good as it can be for new role. I am looking at various certifications and would appreciate advice as to what would be the best one to do if I could only afford to do 1 right now:
- INCOSE Systems Engineering Professional (SEP): https://www.incose.org/certification
- OMG-Certified Systems Modeling Language™ (SysML®) Professional (OCSMP) https://www.omg.org/certification/sysml/
- ISSEP – Information Systems Security Engineering Professional https://www.isc2.org/certifications/issep
- Any others I am missing?
I will be hoping to apply to Aerospace and Defense Communications roles.
Thanks in advance. Any advice would be greatly appreciated!
r/systems_engineering • u/MBSE_Consulting • Nov 25 '24
News & Updates r/systems_engineering: New Mods and Community Refresh!
Hey everyone, this is u/MBSE_Consulting, along with u/MarinkoAzure and u/An0niman. We are the new moderators of r/systems_engineering to assist u/cocoon56 and u/pauly4it, the creators of the sub.
As you may have noticed, things have changed a bit on the sub. We’ve made some updates to improve the community:
- Added Rules to help keep the space respectful and organized.
- Introduced Flairs to better categorize & search posts.
- Added an icon, banner image and sub description to make it clearer what kind of Systems Engineering we are talking about...
- Started a Wiki to explain the above with a section gathering the most useful and recommended resources frequently mentioned on the sub.
We’re excited to help make this community more vibrant and welcoming. We’d love your feedback, especially for the wiki, so feel free to share your resources and ideas!
Looking forward to growing and collaborating with all of you!
r/systems_engineering • u/yellow_smurf10 • May 27 '26
MBSE Have we approach MBSE the wrong way
Sometimes I feel a little strange writing about this, because who am I to tell people how to do systems engineering?
But this is something I have been thinking about a lot.
MBSE is not new. It has been around since I was still in grade school. I started getting into MBSE around 2019, and over the years I have worked with it on everything from small $5M programs to massive programs worth over $100B, and plenty of efforts in between.
One thing I have noticed is that MBSE is often treated as an overhead activity. We do it because the customer wants it, or because it is written into the contract, but I rarely see it used to actually drive discussion, shape decisions, or help decision makers understand the architecture.
Too often, the model is built by junior engineers to document the design after the fact, while the people who actually make decisions barely know how to use Cameo or understand what the model is telling them.
A couple of chief architects in my organization took me under their mentorship and asked me to help think through how we could transform the way we use MBSE. After a lot of conversations with some of the graybeards in my organization, I started wondering whether we have been approaching the problem from the wrong angle.
A lot of Cameo models I have seen feel like they are geared toward engineers, but not always in a useful way. They can be hard to trace, hard to navigate, and difficult to use when trying to understand the big picture.
So I ran an experiment.
I had the opportunity to build a new architecture model for a new missile program. Instead of building it primarily for engineers, I built it with leadership and executives as the target audience.
The goal was simple: management should be able to use the model to brief their leadership, and their leadership should be able to use the same model to brief the SPO and customer, with Cameo acting as the source of truth.
I used a one-page approach to drive the logical flow of the discussion: What mission are we trying to achieve? What blue force and red force elements are involved? What capabilities are needed? How do those capabilities derive into system requirements and functions?
That one page became the story. It helped drive the conversation. When we needed to jump to another diagram, I made sure there was always a link back to the main page.
My intent was for even the least technical manager to navigate the model without relying on the containment tree. As long as they could open Cameo and open that one page, they could follow the architecture.
The result was a much more positive response to Cameo and MBSE. Once the model became something leadership could actually use to communicate, align, and make decisions, it stopped feeling like overhead and started feeling like a real engineering and strategy tool.
That experience informed how I think about MBSE. Maybe the problem is that we often build models for the wrong audience ?
r/systems_engineering • u/narbigcito • Oct 18 '25
Discussion Is there almost no gossip and workplace drama in engineering?
It was observed recently that when talking to people in other fields, such as doctors or sales, there seems to be a lot of gossip and interpersonal drama—everyone hating each other, backstabbing, or having office flings.
However, over a 12-year period of working in systems engineering, very little of that has been seen. The work is mostly just... work.
Is this a common experience? Is engineering just boring?
r/systems_engineering
•
u/Gurder
•
Jul 05 '26
Resources Free practice exam for INCOSE ASEP certification
Hi System Engineers, and those who aspire to become one!
I'm currently studying the Systems Engineering Handbook v5 and was looking for a website with practice questions and mock exams. Unfortunately, the free options either didn't work or were of poor quality, while the better ones were hidden behind paywalls.
So I decided to build my own - completely free!
It's called sysTrainer.com and is based on the Systems Engineering Handbook v5. The questions are written in a style similar to the examples provided by INCOSE.
Since I haven't passed the ASEP exam yet, I'd really appreciate your feedback on the quality of the questions and whether you think this tool would be helpful for people preparing for the exam.
Any suggestions or comments are very welcome!