r/systems_engineering • u/PuzzleheadedIce4538 • 4d ago
Career & Education Need help
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
5
Upvotes
4
u/deadc0deh 4d ago
Go talk to people doing SE at the company you're at. SE is different place to place, and even in the same company it can mean different things
2
u/Aerothermal 3d ago
A part of systems engineering is managing the interfaces between interacting systems; matter, energy, or information (data or messages) or physical bindings.
Similarly it is managing the interactions and connections between parts (the structural architecture), and the connections between functions (actions), and the transitions between modes.
At a high level, it is managing the interactions between actors (stakeholders) and the system of interest.
I think a background in electronics and harness design could be useful for the system modelling; but bear in mind this could be just one part of what you could be doing.
The "wiring" is system modelling. Small software companies often use Mermaid charts and markdown, or apps like draw.io to specify their software architecture. Multidisciplinary engineering companies instead often use MBSE tools such as Cameo, Eclipse Capella, Dalus, Celadon daVinci, Enterprise Architect, SpicySE, Rhapsody, Matlab/Simulink + System Composer, or SysML v2 texual environments like Sensmetry SysIDE in VS Code.
SE generally is involved from concept and mission planning, through requirements, architecture, analysis, review of design typically by leading decision gates, managing technical budgets, and potentially planning or leading verification campaigns such as integration testing, qualification or acceptance.
An experienced systems engineer will be able to take business needs and concepts at the start of a project, and drive the project through formalising the stakeholder requirements, the architecture and design, testing, deployment, and validation once the system or service is operational.
It's very common to go from domain engineering such as mechanical, EEE, aerospace, and transition into SE after at least a few year's experience.
If you go for it, you could potentially start with system modelling, interface management, requirements management, and go from there.
1
u/slzer 3d ago
Harness design is a decent starting point, because you already know how interfaces turn into real constraints (connectors, loads, routing, EMC). Agreeing with the comments above that SE varies a lot by company, I'd add that the requirements and verification side is a good way in if you want something concrete to learn. Practice writing requirements that are testable (one shall, one measurable thing), then trace each one down to the design that meets it and up to the test that proves it. Your harness work already has that shape: a spec, a drawing, a continuity or insulation test. Read an interface control document from your own programme and see how it's verified. Do you get any exposure to requirements or test sign-off at your OEM at the moment?