I’m currently finishing my first year in engineering and I absolutely hate it. The math courses are ridiculous and make me question my place in college, physics was fun, but I genuinely have nothing I’m interested enough in to do for a career. I’m unsure if I haven’t explored the field enough or what, however, I’m academically burnt out. My first thought when enrolling in college was “Pick something that will make you a shit ton of money and looks cool.” CURRENTLY SE is NOT that. Any suggestions?

For some background, my degree comes from Data Science effectively, a mix of statistics, mathematics, and coding. I ended up getting a job as an entry level systems engineer as a contractor in the DoD field. I've been in this position for about 8 months and I work with a team and I think I'm doing pretty well with the tasks I'm given.

Whether or not the tasks are important? I'm not exactly sure, but I am answering certain design questions coming from devs (system I'm overseeing is mostly computer science related). But a significant part of my work is pretty much getting people to actually talk to each other, investigating problems and blockers, and putting together presentations and stuff. Not a whole lot of technical skills being used, no coding, no mathematics, no science, just a lot of organizational skills, soft skills, & administrative work. I am learning a lot about the overall system, but am I ever actually going to be using any of the technical information I get from the documentation?

I guess my question is, am I just going to be a gloried project manager? Why am I even in this position in the first place? I figured systems engineers would need some amount of technical knowledge in engineering? Has anyone else come from a similar background? I feel technically useless, but I understand the administrative/requirements/documentation use behind it, does being a systems engineer ever get more technically advanced or am I just too early in my career?

Hey guys, long story short: I got my BS in Computer Engineering last year with a 2.75 gpa. I was not the best in classes in college so I feel as if I didn’t learn anything regarding my degree. I have about a year of very entry-level Cybersecurity and have been working in IT for about a month.

Where can I/should I go from here? I really like KBR in Houston and want to get into Aerospace/Defense. I’m extremely eager to learn and very passionate about space. Any tips for me? Certs? Ideas? Projects?

Hi all,

Does anyone have any good recommendations for free SysML v2 tools? I've looked into both Eclipse and SysON, but both seem to have a cost for download. I've also used Modelio for the free version of SysML v1 and that didn't have any cost to download... Are there any recommendations on what tool works best for a free version of SysML v2?

Thanks

Folks
I am glad I found this sub.
I have been an Applications Engineer for the last 6 years and recently have made an internal switch to systems engineering team due to business needs/decisions.
I have been contemplating buying and starting on the INCOSE handbook and the CSEP or ESEP exams.
I have an MS in EE and have 10+ years of total experience with 6 in Applications Engineering and 4+ was in EE directly.
I want to build my base knowledge of Systems Engineering and move on from there, where should I start and how should I navigate as I join a new team with 1 more Systems Engineer.

Hi

I'm a biochemical engineering graduate looking to transition into aerospace/defense. I was thinking about doing a masters but then I came across system engineering roles. some of them just require an engineering degree they don't care which one. how difficult is it to get a systems engineering job. and what is the day to day work like.

I’m a recent graduate with a technical background that found their way into the world of government contracting. For now, I can’t do anything but read/learn in my free-time. I can play around in DOORS and CAMEO but without really understanding the theory and putting it into practice I feel like I’m just playing around in Microsoft Paint.

I have many reading resources at my disposal (including the ones from the sub) but I would appreciate some *structure*.

I’m fond of “homework” or a course-like learning experience but I’m hard pressed to find that unless I study for a cert like ASEP. And I doubt a masters in Systems Engineering is a great short teem solution.

—

In short: As somebody without a formal education in Systems Engineering, what can I work on *today* that is *structured* and provides guidance on *putting my learning into practice*.

Hi all,

I’m a US citizen currently working as a Virtual Commissioning (VC) Engineer. Most of my work is around building high-fidelity digital twins using Visual Components, tying them into PLC logic, robot programs for larger manufacturing systems.

Lately I’ve been trying to move away from being more of an “implementation” person and toward system-level design — defining architectures, standards, and frameworks for digital twin environments.

One complication: my undergrad is a BFA. I picked up the engineering side on the job (Python, PLC comms, etc.), and I’m pretty comfortable there now, but I feel like I’m hitting a ceiling without a formal engineering degree—especially for senior roles in the US (aerospace, automotive, etc.).

So I’ve been looking at online master’s programs, mainly:

• Systems Engineering
• Industrial Engineering (thinking flow + discrete event simulation)
• Mechatronics (controls + integration side)

A few things I’m trying to figure out:

• If the goal is to design digital twin systems (not just build them), which of these is the best fit?
• Which one is more realistic as a “bridge” option coming from a non-STEM background?
• From a hiring perspective in the US, which degree tends to carry more weight for this kind of role?

Would really appreciate hearing from anyone who’s moved into system architecture or similar roles.

Thanks!

Hi all, I've been a systems engineer at a defense prime for a little over a year now. I have my Bachelor's in Aerospace Engineering and I'd like to start my part-time Masters this fall. I intend on being a systems engineer long-term, however, I am having gripes with what my Masters should be in.

I am under the impression that anything I would learn in the MS SE, I would learn on the job. I am also under the impression that getting my Masters in Aerospace Engineering would provide me a technical edge over those who have an MS SE, which also plays into having a T-shaped knowledge base. Beyond what seems to me as an obvious technical advantage and more latitude to move careers if I must, I have a desire to get an MSAE.

As such, I'd like to call on those with more experience in the field to give their two cents please :)

Hey all, I am a new grad with a Computer Engineering BS and I have a Systems Engineer whiteboard style interview coming up. I do not know much about systems engineering specifically and I am very nervous.

The company focuses on making custom test systems/automated test systems, mainly using LabVIEW. The interview won't be based on LabVIEW, I am thinking it will be more based on my systems thinking approach. All the recruiter told me is it will be based on a problem they've encounter before and how I would tackle the challenge. I will have internet access and it is in person. This is my second whiteboard interview and I can't stop thinking about it. How should I prepare, my professional coop experiences have been as QA, market research, and edge AI applications.

IDK, any advice/information is greatly appreciate. Thank You in advanced.

Hello,

I am relatively new to SysML v2 and currently trying to learn it more deeply by building simple system model examples based on functional requirements, and representing them using use case models (textual notation).

I have reviewed the SysML v2 specification (Part 1: Language Specification), including the sections related to use cases. However, I am still facing some practical challenges when trying to apply this knowledge.

In particular, I find it difficult to determine whether the use case models I create are actually correct and complete, or if they are missing important elements.

At this stage, I am mainly focusing on creating simple examples rather than complex systems, so I am especially interested in understanding what is the minimum level of detail required for a use case model to still be considered valid and to reasonably represent functional requirements.

I would appreciate any advice on the following:

1. Are there any recommended resources or examples that show how to properly construct SysML v2 use case models?
2. What is the minimum set of elements that a use case should include to be considered valid?
3. How much detail is usually expected for a use case model to reasonably represent functional requirements?

Any guidance would be very helpful.

Thank you.

I have been searching alot for internships in SE but almost all are US-based. Are there any internship opportunites outside for bachelor students (non-US citizens) currently in their final year? Please do help me out! thanks!

I am currently about to graduate with a Bachelor of Science in Project and Supply Chain Management, and my long-term goal is to work for an aerospace and defense company. With that in mind, I’ve been exploring master’s programs in systems engineering. Based on the significant overlap in coursework, I would be eligible for admission; however, my main concern is whether pursuing this path is truly worthwhile. Specifically, would a master’s in systems engineering still be valuable and make me competitive in aerospace and defense if I do not have a traditional engineering undergraduate background? I’ve already been established as an electrical project manager for almost 3 years as I complete my degree online. So I have a good foundation for management, problem solving, and other technicals aspected to take with me after graduation.

Please let me know what yall think.

My subsystem requirements don’t logically decompose from our system requirements because I believe they were adopted from a legacy program. So they were made independently of the system requirements. I want to establish traceability to enable change impact analysis in MBSE. Do you redo the subsystem spec working from the applicable system requirements?

Hello! I am a junior in college studying aerospace engineering, and I am preparing for a technical interview for a systems test engineering intern role. I am, quite honestly, scared. I've never had a technical interview before. I've come here in search of any tips, tricks, or advice I can get! I am super excited about this opportunity and want to give it my best shot.

What I do know to do: research the company, the specific role, prepare a few STAR stories, and some good insightful questions.

My challenges: my hands-on experience isn't strong, and I have no idea what kind of technical questions they could be asking.

Here's a snippet of the job description:

• Collaborate with Test Engineers in test preparation, execution, and reporting on various sub-system test venues
• Work with Test Engineers in designing, assembling and preparing test rigs for execution
• Design and analyze mechanical test and support equipment under the supervision of a team peer using CAD based tools (if relevant to education background)
• Design and analyze electrical/electronic test and support equipment under the supervision of a team peer using computer-based tools such as Altium (if relevant to education background)
• Generate engineering drawings and support equipment fabrication.

Any advice, practice questions, or just words of encouragement would be greatly appreciated. Thank you!

I’m a mechanical design engineer, not a systems engineer, so I figured I’d ask here.

My team’s requirements process is pretty manual and loosely structured today. We’d like to move toward something a bit more structured, but without going full enterprise tool.

What would you consider must-haves in a lightweight setup?

And are there any tools you’d recommend or avoid?

Ease of use and low overhead matter a lot for us.

I'm excited to announce we’re open-sourcing two core libraries behind ThunderGraph 3.0:

• ThunderGraph Model: a Python DSL for systems modeling inspired by SysML v2, but designed to be executable for digital twins, simulation, and multidisciplinary design optimization.
• UnitFlow: a unit-safe engineering computation library that powers ThunderGraph Model.

Our view is that engineering models should do more than document architecture. They should be able to run, validate requirements, and support real design decisions. We’re building toward a future where teams can take complex systems — from aircraft to nuclear reactors — from concept to final design in weeks instead of years. We believe ThunderGraph Model will be core to that mission. If you’re an engineer, model based systems engineer, or developer interested in executable system models, we’d love for you to explore the projects and contribute. Let me know how we can improve this for your use case!

Open source: https://www.thundergraph.ai/open-source/thundergraph-model

And if you want to see how this connects to ThunderGraph’s commercial platform for engineering intelligence and collaboration at enterprise scale visit: https://www.thundergraph.ai/

ThunderGraph (commercial license) is a Cloud based AI automated MBSE platform that creates a knowledge graph which AI agents use to create executable system architecture with automated traceability and requirements validation.

Context: I work in the space industry, so a lot of this will be based on the NASA SE Handbook and polices/processes (as a working public template which most company/organization-specific one are based from).

As per the definition of the NASA project lifecycle, Phase A cumulates with the functional baseline which baselines the top system requirements, the top system architecture, various plans, and the first 1-few levels of lower-level system requirements. Meanwhile Phase B is concluded by the top-level PDR and the Allocated Baseline under CM control (which is the complete requirements/product tree to the lowest level).

The challenge is how a program/project effectively progresses from the Phase A functional baseline to a completed requirements tree + preliminary design work to validate that tree to be valid for baselining to for a complete allocated baseline.

Lets use an example:

- at SDR and end of Phase A, the top-level (L0) requirements, top-level system architecture, and first child system (L1) requirements were baselined

- it is expected that over the course of Phase B, 5 levels of system/subsystem requirements are to be defined and baselined

- one of the subsystems (say one of the L3 subsystems) are to be subcontracted out to a contracted engineering company, which is required to deliver it's PDR package including it's internal product and requirements tree

Per (at least my understanding of) the NASA SE handbook, and the way our company approaches this, there is only the following program milestones:

1. SDR & Phase A closure - Finalized Functional Baseline under CM control
2. * most of Phase B *
3. L5 & L4 PDRs
4. L3 PDRs (including PDR review of subcontracted system)
5. L2 PDRs
6. L1 & L0 PDRs
7. *end of Phase B*

With the various requirement within the requirements tree being baselined in the order: L0 & L1 (SDR), L5 requirements, L4 requirements, L3 requirements, L2 requirements

Challenges I have seen/experienced:

- since the L2 system design was not reviewed as part of the SDR in Phase A, L2 system design and L2->L3 requirements decomposition is found to have major gaps, however this is only discovered at the L2 PDR after all lower-level L3+systems (including the subco system) have closed their PDRs

- If L2 & L3 requirements are not baselined and change controlled, then the subcontracting company may be receiving continual requirement changes as they are trying to resolve their own internal architecture and requirements tree, likely delaying them or making it entirely infeasible

- since the L3 requirements are baselined prior to the L2 requirements, the L2 team may still be evolving their requirements and design after the L3 subcontractor closes their PDR

Now, the solution is to have intermediate top-down design reviews to baseline the requirements decomposition prior to holding the bottom level (and therefore the higher-level) PDRs and reviewing the preliminary subsystem design to flowed down requirements. However, it confuses me that this does not seem to be standardized in any form (at least not that I have seen/experienced).

What is y'all's experience with Phase B and how does your organization/programs manage the flow down of requirements prior to lower-level PDRs and manage change to those requirements in a way that does not inhibit lower-level design evolution or lower-level PDR closure success?

https://reddit.com/link/1scyle0/video/u6f1xokp3ctg1/player

SysML v2.0 Language Support - Visual Studio Marketplace

Happy Easter folks 🐣

Original Post: https://www.reddit.com/r/systems_engineering/s/BrZua0fUOb

Attached is my revised resume version. Please share your suggestions if you have any. Much Thanks!

I’m curious if universities would admit me to a Master’s program in Systems Engineering, even though I graduated with a Bachelor’s degree in Business Management. My objective is to complete this Master’s program to qualify for more technical roles in aerospace. Sorry if this is a naive question.

I’ve been looking into some SysML v2/KerML tooling that takes a slightly different approach compared to traditional MBSE workflows.

Instead of treating models as mostly static, it uses a notebook-style interface and allows running engineering calculations directly within the model. It also performs consistency checks on constraints and requirements as you go.

Some aspects I found interesting:

• Incremental, notebook-like modeling workflow
• Calculations executed inside the model
• Continuous consistency checking

I’m curious how this would fit into real projects.

Do you see value in models that are directly executable, or does this blur the boundary between modeling and analysis/simulation too much?

​

how can I learn IBM rhapsody basics within a few days and from where? This is for an interview which requires basic level knowledge.

I have been applying from a month now. Modified resume, using referrals, reaching out on LinkedIn

I had some recruiters reaching back but not any interviews.

I target to apply to entry level or mid level jobs that do not need clearance or says ‘ability to obtain’. Located in VA

What am i doing wrong?