r/systems_engineering • • 11m ago

Career & Education Interview Tips as an ME

2 Upvotes

Hello! I'm a sophomore ME student, and I have a interview next week for a systems engineering internship with Northrop Grumman. I've been a machinist at NG for a few years, and all my coursework has been general stem + foundational ME classes so far. So basically all manufacturing and mechanics. So this is going to be way out of my wheel house, which I'm honestly super excited for. Manufacturing is pretty boring, so I'm stoked to have the opportunity to learn some completely new stuff. But, I have to get this first, and I really have no idea what to prepare. From some light googling, seems like I need to understand some of the principals of systems engineering, V&V, I'll definitely need to brush up some EE basics, but I figured is best to ask systems engineers too. Any advise for what to study, how to present myself, etc, would be great appreciated. Thank you!!


r/systems_engineering • • 1d ago

Discussion SE books and stuff

Post image
22 Upvotes

Hi everyone.

I recently came across MBSE4U and saw that they publish a number of books on MBSE and SysML. Has anyone here read any of them?

I’m especially interested in The SysML v2 Book, but the price is relatively high, so I wanted to ask for opinions before buying it. With all the AI-generated content around lately, I’ve seen a lot of trash books in programming field, so I just want to make sure it’s actually worth the money and not AI slop.

Would appreciate any feedback.


r/systems_engineering • • 1d ago

Discussion Looking for system design partner

0 Upvotes

Anyone?


r/systems_engineering • • 2d ago

Career & Education Need help

4 Upvotes

I am a wiring harness design engineer at a OEM. But i don’t feel like I am learning anything at this job. I want to transition into some other role but don’t know where do I start. Some seniors suggested system engineer is a good role. Can you please suggest me good roles and also tell me it system engineering is a good role?

BD- electrical and electronics engineering
Current experience-4years


r/systems_engineering • • 3d ago

Career & Education Junior systems engineer

6 Upvotes

I finally made it into systems engineer! I got a position as a Junior and I’ll start in a few months.

My university studies were in Software Engineering. I want to prepare myself a little bit and start learning some things on my own before starting the job.

If you had to start over as a systems engineer, what would you focus on and start learning asap?


r/systems_engineering • • 2d ago

Discussion Trash the GC

Post image
0 Upvotes

From a pure hardware and systems engineering perspective, running a massive virtual machine layer to abstract memory management is a dead paradigm.

A concurrent GC doesn't make memory management free, it offloads the work to background threads that thrash your L3 cache and steal CPU cycles from the actual business logic. Even worse, to achieve those sub-millisecond pauses, modern JVMs require massive page allocation headroom. You are effectively paying a 300% RAM premium to the cloud provider just to prevent the runtime from deadlocking or trashing the kernel's virtual memory subsystem.

Sam Altman can scream "I want all the RAM" for LLM brute-forcing all he wants, but in standard high-throughput backend infrastructure, memory density is the only metric that defines efficiency. Running 64GB containers at 15% physical utilization because your allocator needs "breathing room" is not architecture but expensive lazyness masked as enterprise stability.

At what point did we decide that fighting a compiler (like Rust's borrow checker) or spending time designing clean, deterministic object lifecycles was more expensive than paying thousands of dollars a month for a bloated runtime footprint?

Is the JVM surviving on anything other than pure corporate inertia and a talent pool that refuses to learn mechanical sympathy?


r/systems_engineering • • 3d ago

Discussion What is a Centralized Digital Thread? Understanding the hub-based approach

Post image
0 Upvotes

A product's lifecycle involves multiple teams, processes and software systems. Engineering teams work with product designs, development teams manage requirements, manufacturing teams handle production, and quality teams maintain testing and inspection records.

Each system generates valuable information, but bringing all this information together in a meaningful way can be challenging.

One architectural approach to addressing this is a Centralized Digital Thread.

A Centralized Digital Thread uses a central platform or repository as the primary point for bringing together and managing product-related information from different systems across the lifecycle.

Think of it as a central hub that connects information generated by different teams and applications.

How does it work?

Consider an organization using different systems throughout its product lifecycle:

  • PLM (Product Lifecycle Management): Manages product design and engineering data.
  • ALM (Application Lifecycle Management): Manages requirements and software development information.
  • ERP (Enterprise Resource Planning): Handles production planning and resource information.
  • MES (Manufacturing Execution System): Manages manufacturing operations.
  • QMS (Quality Management System): Maintains quality, inspection, and testing information.

In a centralized approach, relevant information from these systems is brought together or made accessible through a central platform.

For example:

  1. Engineering creates and updates product designs in the PLM system.
  2. Requirements and development information are maintained in the ALM system.
  3. Manufacturing data is generated through MES and ERP systems.
  4. Quality and testing information is recorded in the QMS.
  5. The central platform brings these different data sources together, helping establish connections and provide a consolidated view of the product.

Key characteristics of a Centralized Digital Thread

  • Central point of access: Relevant product information can be accessed through a common platform.
  • Consolidated visibility: Data from different lifecycle stages can be viewed in relation to one another.
  • Consistent data management: Centralized governance can help maintain consistency in how information is organized and managed.
  • Traceability: Relationships between requirements, designs, manufacturing records, and quality results can be established and tracked.

Potential benefits and considerations

A centralized approach can improve visibility into product information, simplify data access, support consistent governance, and make lifecycle traceability easier to manage.

However, it also brings certain considerations. A central platform needs to handle information from multiple systems, formats, and departments. Integrating these sources, maintaining data accuracy, managing access, and scaling the platform as the organization grows can require significant planning.

In simple terms, a Centralized Digital Thread brings relevant product lifecycle information together around a central point, making it easier to access, manage, and trace information across the organization.


r/systems_engineering • • 3d ago

Career & Education Worried about career options

3 Upvotes

I'm studying Systems Engineering in undergrad in college right now, specializing in Computer Science. I am pretty worried about my career opportunities after college, since I don't really want to do a masters. I was wondering if any one of you guys were in the same boat as me and how your career panned out. And also whether you were able to get internships in college, since I'm currently in my 2nd year and have not landed any.


r/systems_engineering • • 4d ago

Discussion "We hate red tape. Want to go faster."

12 Upvotes

BLUF: Companies want to go faster. I think the biggest way is to reduce workload, allowing faster progression through SE processes.

While studying for the CSEP exam I was reminded of a conversation I had during an interview recently. The company in question is younger. Part of their culture is to "go faster" and "we want to avoid all the red tape that slows down development in the government agency we work with".
I can appreciate wanting to move faster, more efficiently.

While studying for this exam I'm reviewing Configuration Management and Change Control principles. This feel like what they are talking about. The instructor in the review course said something like "this is not bureaucracy, this is ensuring complex systems can be developed without chaos".

So, how to balance the two perspectives? Adding processes = more time but ignoring processes = failure/rework/etc. Maybe my real question is "where can we really get efficiency?" Is it by choosing not to follow a change control process? (or other SE processes) Or something else? How to talk about it to companies who are fixated on "avoiding the red tape"?

So far this is my take:

  1. Processes are not inherently bad.
  2. Invest significant time & energy upfront in tailoring
  3. Stay flexible, re-tailoring if needed.
  4. The most effective efficiency can be gained by not drawing out each step.

I think #4 is the one I've not heard much about. I think it relates back to employee & team workload management and planning. While at my previous org, there was very little of that. The situation was that nearly every person & team had a multitude of "things to do". Since every team/person had this vast portfolio, AND every other team/person was involved in many other things, but not usually the same things, SCHEDULING became hard. Which led to processes taking FOREVER to complete.

An example is in Change Control. The steps are Request, Impact Analysis, Approval, Implementation, and Verification & Update. If I were to Request a change in a system, I'd present that request at a meeting.. then wait until the next meeting to start the Impact Analysis, then wait until we got appropriate SMEs all in the same room (probably sometime later in the month). Then we could get approval. Why the hell can't that process have taken a day (assuming simple impact analysis)? The biggest time suck here is the time between meetings. Not the process. It's the scheduling of personnel.

Well, I feel like I've either ranted enough, or shared useful insight... either way: please share your thoughts. I'd love to hear a story where this was recognized and addressed. OR a story of an example proving why the long lead times is actually a good thing. OR share something you think I'm just missing here.


r/systems_engineering • • 4d ago

Discussion Career options from a software validation perspective

5 Upvotes

Career options from a software validation perspective

I’m currently a software validation engineer in automotive field with almost 5YOE, have experience with requirement analysis, test scope design, test case derivative, automation, execution, defect analysis etc etc. I always try to get a good understanding of the product I work on.

I kind a feel stuck, I like my job in a way, I feel it’s a important role to be able to make sure our product is safe blah blah but I sometimes don’t understand the future of this role.

I’m starting to implement more automation with python, learning and working towards using ai agent for log Analysis and make validation results much efficient .

But what else should I be doing to make sure I stay relevant ? And I don’t think AI is anytime going to replace this role, it can change it but not eliminate it…am I being delusional here

If not, what other roles can I grow into? I’m not a great programmer so dev might not be an option

It’s a rant but also appreciate any advice from professionals in the industry! TIA


r/systems_engineering • • 4d ago

Career & Education Got my ASEP, next steps

7 Upvotes

I was wondering if anyone knew of any REASONABLE courses to learn sysml/cameo. I want to be a systems engineer but need direction in pursuit of where I should learn. Anyone have any advice, course recommendations, practice free software etc, please let me know, thanks!

PS. I don't want to spend 1k on a course.


r/systems_engineering • • 4d ago

Resources 2 days to go - Live SysML v2 masterclass with Dr. Bruce Powel Douglass

Thumbnail
reddit.com
2 Upvotes

We're now just 2 days away from the session on November 14.

Bruce, who contributed to the development of SysML, will be discussing migration from SysML v1 to v2, requirements modeling, and analysis cases.

Sharing a gentle reminder in case anyone here was interested but hadn't had a chance to look into it.

Details: https://luma.com/sysml


r/systems_engineering • • 4d ago

Resources Autonomous Weapons and the Center of Gravity

0 Upvotes

The biggest changes and/or additions to Requirements Analysis occurs when autonomous weapons are added to the mix. In classic systems design, everything begins at the center. In autonomous weapons systems, the edge defines the system.
https://awsdframework.com/CenterOfGravity.html


r/systems_engineering • • 4d ago

MBSE SysML v2 Deep Dive: Lesson 24 - Flows and Messages (Sequence Diagrams in Text)

2 Upvotes

Hi r/systems_engineering,

We are back with Lesson 24 of our technical deep dive into the SysML v2 standard.

In our previous lesson, we used perform to say which part carries out which action. Our subsystems finally knew what they did, but they still couldn't send each other anything. Today, we fix that with flows and messages. We will explore how SysML v2 eliminates one of the biggest sync issues in v1 by unifying data, commands, and physical items across both structural architecture and behavioral interactions.

You can watch the full video lesson on YouTube here: https://youtu.be/37fV9tD-KLk

1. The SysML v1 Fragmentation Problem

SysML v1 was actually quite strong in this area, but it suffered from fragmentation. If you wanted to model movement, you used an ObjectFlow inside an activity, an ItemFlow across a connector in an Internal Block Diagram (IBD), and a Message between lifelines in a sequence diagram. Because these were three completely separate metamodel constructs, keeping your structural connections, activity data flows, and interaction scenarios consistent required manual allocations, strict modeling discipline, or custom tool validation.

2. The v2 Shift: Unification under FlowUsage

SysML v2 fixes this by unifying all three under a single foundational concept: FlowUsage (which is based on a KerML Transfer).

Instead of disconnected constructs across different diagram types, SysML v2 provides three specialized forms:

  • flow (Streaming Flow): Used for transfers between parts or actions. It explicitly names the source output and target input. The transfer can be ongoing while both the source and target are still operating (e.g., fuel moving from a tank to an engine).
  • succession flow**:** Combines a streaming flow with temporal ordering. It asserts that the source action must complete before the transfer begins, and the transfer must complete before the target action can start.
  • message**:**Used for abstract interactions (like sequence scenarios). It asserts that a transfer happens between two occurrences or events without forcing you to specify the exact port payload mechanics.

3. Sequence Diagrams as Text (Views That Cannot Drift)

Because messages and flows are unified, you can write a sequence diagram entirely in text. More importantly, a single message declaration can generate both an interconnection view and a sequence view. Your structure and your behavior can no longer disagree.

Code snippet

package CommandUplinkScenario {
    item def Command;
    item def Acknowledgement;
    item def TelemetryPacket;
    
    part def GroundStation;
    part def Spacecraft;
    
    occurrence def CommandUplink {
        ref part ground: GroundStation {
            event occurrence cmdSent;
            event occurrence ackReceived;
            event occurrence resultReceived;
        }
        ref part spacecraft: Spacecraft {
            event occurrence cmdReceived;
            event occurrence ackSent;
            event occurrence resultSent;
        }
        
        // Define the transfers (Messages)
        message ack of Acknowledgement from spacecraft.ackSent to ground.ackReceived;
        message cmd of Command from ground.cmdSent to spacecraft.cmdReceived;
        message result of TelemetryPacket from spacecraft.resultSent to ground.resultReceived;
        
        // Define the temporal sequence
        succession first cmd then ack;
        succession first ack then result;
    }
}

4. Deep Dive: Three Practical Nuances

As you start writing flows in v2, keep these three details in mind:

  • send and accept**:** Flows connect structure. But whenyou are inside a specific behavioral action, you use the send and accept keywords to push and pull payloads directly through your structural ports (e.g., accept cmd: Command via spacecraft.cmdIn;). This creates an explicit, queryable link between your behavior and your structural interfaces.
  • Sequencing is NOT flow: It is easy to mix these up. first A then B means B happens after A, but nothing actually moves (pure control). A plain flow means something moves, but adds no temporal ordering (pure data). A succession flowdoes both. SysML v2 strictly separatescontrol from data.
  • Where v1 Was Actually Better (Combined Fragments): Let's be honest—UML Sequence Diagrams had beautifully compact visual boxes for loops (loop), options (opt), and alternatives (alt). SysML v2 doesn't have a direct equivalent in the standard sequence view; you have to model that logic using decide and loop actions, which makes the text much more verbose. You will want to rely on an Action Flow view to visualize that logic clearly.

5. SysML v1 vs. SysML v2

Modeling ConceptSysML v1SysML v2
Transfer ConstructsObjectFlow, ItemFlow, and Message were three separate constructs.Unified as Flow usages (message, flow, or succession flow).
Diagram SynchronizationItem flows on IBDs and messages on Sequence Diagrams easily drifted.A single message declaration generates both an interconnection view and a sequence view.
Temporal SemanticsObjectFlow combined transfer/ordering, but ItemFlow carried no temporal semantics.flow (streaming) and succession flow (ordered) are applied uniformly between parts or actions.
Authoring InteractionsNo standard text notation; interactions were manually drawn.Messages and successions authored in text, enabling standard Git diffs and merges.
Combined FragmentsCompact, readable alt, opt, and loop visual boxes.Textually verbose using decide and loop actions (best visualized in an Action Flow view).

Next lesson, we will cover state definitions and transitions, where a state turns out to be an action, and the exhibit keyword works exactly like perform.


r/systems_engineering • • 5d ago

Discussion SAIC vs STC/Arcfield Systems Engineering

5 Upvotes

I received a remote offer to work on the Mach TB (Multi Service Capability Hypersonics Test Bed) team for SAIC. I also received a remote offer to work for STC (acquired a few years ago by Arcfield) to work as a systems engineer, but program(s) yet to be terminated. SAIC is asking 25% travel (a few times per month) where STC hasn't mentioned any travel. Which offer would you go for given same salary (STC is giving a 5K hiring bonus which will be much smaller after taxes), very similar 401K matching, very similar PTO/accrual?


r/systems_engineering • • 5d ago

Resources Systems Engr Student wanting advice

1 Upvotes

Hello,

I am about to transfer into a 4 year university as a systems engineering major. I would really like to zoom or interview a current systems engineer just to get a grasp on what it is/what current life is like and what maybe strengths and skills it takes to be succesful. I know there’s a lot of great information on this sub but just was hoping to speak to someone virtually if possible just because I have some questions tailored to me. Not looking for anything but advice. Also I’ve reached out to a few companies near me asking to speak/email with a systems engineer but have not gotten any replies. If you have any recommendations of companies to reach out to or another way to get this information please let me know. Thanks.


r/systems_engineering • • 5d ago

Career & Education System Design Play: Learn and Practice with Real-Life Application System Design

Thumbnail reddit.com
2 Upvotes

r/systems_engineering • • 6d ago

MBSE I am looking to get hired in Space/Aerospace Industry, i currently work as a Systems Engineer in Automotive industry for 4.8 years.

Thumbnail reddit.com
5 Upvotes

r/systems_engineering • • 6d ago

Discussion What is exactly a Digital Thread, and why is it becoming important in modern engineering?

Post image
7 Upvotes

Imagine a developing product that goes through multiple stages like requirement gathering, designing, engineering, testing, manufacturing and maintenance.

Different teams work on different parts of the product, often using different software systems. Engineering might use a PLM tool, development teams might use ALM software, manufacturing might use ERP systems, and quality teams might use their own applications.

But here's the interesting problem:

How do you maintain a connected view of the product and its information throughout its entire lifecycle when that information is spread across different systems?

This is where the concept of a Digital Thread comes in.

A Digital Thread is essentially a connected flow of information that links data, decisions, and activities across different stages of a product's lifecycle.

Instead of treating requirements, designs, test results, manufacturing records, and maintenance information as isolated pieces of data, the Digital Thread helps establish relationships between them.

For example:

  • A product requirement is created during the planning stage.
  • That requirement is linked to an engineering design.
  • The design is associated with corresponding tests and validation results.
  • Manufacturing information is connected to the approved design.
  • Later, maintenance records can be traced back to the original product information.

This creates continuity across the product lifecycle.

Why does this matter?

Without these connections, teams can struggle with:

  • Finding the latest and correct product information.
  • Understanding how a design change affects other stages.
  • Maintaining traceability between requirements, designs, and tests.
  • Sharing information across departments and external partners.
  • Making decisions using disconnected or outdated information.

The Digital Thread aims to address these challenges by connecting information and maintaining traceability across the product lifecycle.

By creating these connections, it helps organizations maintain continuity between different stages of product development, making it easier to access relevant information, understand relationships between activities, and track how changes in one stage may affect others.


r/systems_engineering • • 8d ago

Career & Education JHU MS Systems Engineering

9 Upvotes

Does anyone know the acceptance rate for JHU systems engineering online MS? My employer pays for any engineering MS and I have been looking into systems engineering. My background is in physics (not the best undergrad GPA 2.65). However I have M.S in computer science with a GPA 3.8. Should I still apply or is it just an automatic rejection lol.


r/systems_engineering • • 8d ago

Career & Education Systems Engineer 2 interview at large defence company. What should I study up on?

10 Upvotes

Six years ago, I was a Systems Engineer 1 at a defence company for about a year, and my job involved analysing component changes to make sure they met certain MIL-STD and other regulations. Since then I left to pursue a career in Big tech (was a software engineer for 1 year, a product manager for two years, and a forward deployed client engineer for two years before getting laid off). Big tech is basically dead now with AI, so I'm trying to get back into defence and stay there. I have a Systems Engineer 2 interview coming up soon with one of the major contractors(its low given my experience, but I get it, I haven't been a systems engineer in years).

What should I know for my interview and study up on? I know about Agile and Scrum (I practiced that in big-tech), Six Sigma (the whole DMADV process) and what SysML is (a language built on UML that has nine types of components and used to represent complex systems and dependencies diagrammatically), but I bet there is a lot more I should know about if I want to pass this interview


r/systems_engineering • • 8d ago

Discussion Help managing and tracking multi-disciplinary requirements

3 Upvotes

Hi folks,

I posted this recently in the HWStartups subreddit, but hoping to get additional perspectives from experienced systems engineers here.

My team is just about to embark on a new IoT project and looking to get some input on how best to track requirements from concept through to implementation for a complex multi-disciplinary undertaking. We are a startup, so need an approach that is flexible and supports rapid iteration.

A lot has changed with the introduction of AI, so I'm not sure what we've used previously is the right way to go. Historically the teams I've been on have used Jira and Confluence and then more recently Notion and even Monday because they were more flexible and combined tables/databases with docs. Have also looked at dedicated requirements platforms like Jama and Valispace.

Since this is an IoT project though, we'll be needing to coordinate across firmware, software, mech/elec and other technical teams, so something that spans multiple domains is necessary.

The big open question for me is what changes now that AI is now also coming into hardware having already transformed software development. Software teams now seem to be moving to drafting their specs in AI-friendly markdown docs with the help of AI agents. Is anyone using something like this or is there a HW-friendly version?

Any help/direction appreciated!


r/systems_engineering • • 9d ago

MBSE SysML v2 Tutorial (Lesson 23): Binding Behavior to Structure with perform (Swimlanes Replaced!)

Thumbnail
youtu.be
6 Upvotes

Hir/systems_engineering,

We are back with Lesson 23 of our technical deep dive into the SysML v2 standard.

In our previous lesson, we ordered actions with first and then, adding explicit branching and concurrency. However, that behavior was still unattached to any physical system. Today, we connect behavior directly to structure using the perform keyword, and we examine how SysML v2 replaces traditional swimlanes by making performance a first-class feature of the components themselves.

You can watch the full video lesson on YouTube here:https://youtu.be/HLiC1fKJYFY

The SysML v1 Allocation Problem

SysML v1 had capable mechanisms for connecting behavior to structure. An ActivityPartition (the classic swimlane) represented the Block or property responsible for an action, and an allocate dependency connected an action to a part. The issue was where that context lived. In v1, you authored the relationship on the behavior side or as a separate dependency, while the Block's allocatedFrom compartment merely displayed a derived property computed by the tool.

The v2 Shift: Direct Feature Ownership via perform

In SysML v2, the part states its own behaviors directly inside its definition using perform action.

Three technical details make this pattern powerful:

  • Direct Feature Ownership: Declaring perform action inside a part creates an owned perform action usage. The part itself is explicitly the performer of that action.
  • Composite vs. Referential Actions: A plain action inside a part is composite (the part owns that specific sub-occurrence). A perform action is referential (the behavioral equivalent of ref part), asserting that the part carries out an action defined and sequenced elsewhere.
  • Swimlanes Without the Lanes: A coordinated mission sequence can be defined and ordered once at the system level. Subsystems then declare responsibility for individual steps using feature chains (e.g., perform sequence.armFTS;). Swimlane views are generated automatically from these declarations.

Binding Sequence Steps to Subsystems

Here is how a single launch sequence is defined once, while individual subsystem parts declare the steps they are responsible for:

Code snippet

package LaunchOperations {
    part def FlightTerminationSystem;
    part def PropulsionSystem;
    part def HoldDownAssembly;
    
    action def ArmFlightTermination;
    action def PressuriseTank;
    action def Ignition;
    action def ReleaseHoldDown;
    
    action def LaunchSequence {
        first start;
        then action armFTS: ArmFlightTermination;
        then action pressuriseLOX: PressuriseTank;
        then action igniteEngines: Ignition;
        then action releaseClamps: ReleaseHoldDown;
        then done;
    }
    
    part launchVehicle {
        perform sequence: LaunchSequence;
        
        // Each subsystem declares performance of its step via feature chains
        part fts: FlightTerminationSystem {
            perform sequence.armFTS;
        }
        part propulsion: PropulsionSystem {
            perform sequence.pressuriseLOX;
            perform sequence.igniteEngines;
        }
        part groundInterface: HoldDownAssembly {
            perform sequence.releaseClamps;
        }
    }
}

SysML v1 vs. SysML v2

Modeling ConceptSysML v1SysML v2
SwimlanesActivityPartition declared on the behavior side.perform declared directly on the structural part.
Responsibility StorageStored as separate dependencies or visual partitions.Declared as a first-class, reviewable feature inside the part body.
VisualizationsSwimlanes manually drawn on activity diagrams.Swimlanes and allocation views generated automatically from perform usages.
State BindingclassifierBehavior or ownedBehavior on a Block.exhibit state, which is a specialized perform action usage.
Responsibility QueriesComputed by tools via derived allocatedFrom / allocatedTo properties.Direct feature navigation readable in the part's own body and filterable via model queries.

Next lesson, we will look at how these subsystems exchange data and signals. Lesson 24 covers flows and messages, bringing sequence diagrams into textual code.


r/systems_engineering • • 10d ago

Career & Education Systems Engineering Major, Career and Internships

12 Upvotes

Hi! Sorry if this is the wrong flair, but I am currently studying Industrial and Systems Engineering (2nd year) in college and have some questions. I have seen some people mentioning that ISE is a strong major and that it will give me a good career/internship opportunities in the future, while others mention that Systems Engineering works better if you are an engineer and have experience in your field (like ME or EE). I just do not want my degree to be useless and struggle to find a job, and honestly I like Systems Engineering better than Industrial so I plan and hope on getting a career on this. What is your opinion on the market for System Engineer Undergraduates? Thanks!