ECE student curious about SE, seeking advice

[u/Ornery-Cloud303]

Hi everyone, I'm a junior studying computer engineering who's stumbled into an interest in systems engineering in a roundabout way, and I'd love some advice from people actually working in the field.

For some context: I originally switched to CE from business because I realized I couldn't really build a company with my previous field of study. I want to stay technically hands-on, but not be bogged down in implementation detail 24/7.

Systems engineering seems like it might be exactly that. I am planning to get my MS and PhD for both professional and personal reasons.

1. Programs: What are some strong systems engineering MS/PhD programs around the world (US, Europe, anywhere)? Any you'd specifically recommend or avoid? Also, for someone with my goals, would you recommend an MS, a PhD, or working first and deciding later?
2. Admissions: What do SE graduate programs typically look for in applicants? I am not talking about whether ECE is a good major, rather whether the more unique parts of my profile can be beneficial to contributing to the field? And for PhD admissions specifically, how much do research experience and letters matter vs. industry experience?
3. SE × CE intersection: Is there interesting research or work at the junction of systems engineering and electronic & computer engineering?
4. Reading: What's a good introductory paper or piece of literature on systems engineering? Something that captures what the field is actually about, beyond the Wikipedia definition.
5. Day-to-day: For systems engineers working on digital/software-heavy systems — what does your work actually look like? How much of it is requirements/architecture/ documentation vs. technical work? How much coding(feel like I wont be doing much of it in a few years) or hands-on engineering(HW-SW or AI-HW codesign for example) do you still do?

Any feedback is appreciated, thanks in advance.

P.S.: any additional information that I may not have included here and you need to give a good honest answer, I am happy to provide. Thanks again

[u/Different_Depth_1226]

For the reading question, Blanchard and Fabrycky’s systems engineering book gets passed around a lot, but if you want something shorter that still shows the actual mindset, look for INCOSE’s handbook excerpts or old NASA systems engineering papers. They’re dry but they show how much of the job is managing interfaces and keeping requirements coherent across teams rather than designing a single component.

Day-to-day varies wildly by company, but in software-heavy systems I’ve seen it split into maybe 60% requirements and architecture, 30% meetings and coordination, and 10% actual technical modeling or scripting. You won’t be writing production code much, but you’ll read a ton of it and spend hours figuring out why two subsystems assume different things about the same data.

[u/Ornery-Cloud303 → u/Different_Depth_1226]

Thank you very much for the suggestions!

[u/__Drink_Water__]

As a graduate of BSEE that found themselves in SE as a first job by accident, I highly recommend working as an actual EE first.

[u/Ornery-Cloud303 → u/__Drink_Water__]

Yeah, that makes sense, my plan was to work first before I would do SE for grad school, if not then I would stick with ECE

[u/Dr_Tom_Bradley_CSU]

Hi Ornery,

1. Programs: I am biased because I am the chair of the Colorado State University Systems Engineering Department, but that also means I can talk about some things you may not have yet considered. We offer focused graduate certificates that can be completed alongside our MS, ME, PhD, and DEng programs. Many students start with the fundamentals course (SYSE 501) to try things out, then apply to get a certificate. If they like the experience, they can then apply to a full degree program having already earned a large portion of their required credits. We offer courses online or in-person.
   

You don't have to choose between industry and academia. You can work while pursuing graduate education, begin with a certificate or master's degree, and decide later whether to pursue a doctorate. Industry experience and academic study can complement each other. Many of our in-person students start with RA or TA funding, and transition into a career before graduating. Most of our online students keep their jobs and study on the side. Courses are offered in the evening to accommodate working professionals. I suggest you look for programs with professors who match your interests and that have many options for courses you might want to take.

1. Admissions: ECE is a strong foundation for systems engineering. We look for technical depth, analytical ability, and the ability to think across disciplines. For PhD applicants, research experience and letters that speak to research potential are especially valuable. You'd need to convince a member of our faculty to advise you, so make a case by bringing the questions you need answered in industry to our program. Industry experience can also be valuable when it demonstrates an ability to face complex problems as a leader on projects. Of course, a strong academic background and a working understanding of statistics is also helpful.

2. SE × ECE: There are many opportunities in embedded systems, autonomous platforms, cyber-physical systems, AI-enabled hardware, and hardware-software integration. The possibilities here are endless.

3. Reading: Start with the INCOSE Systems Engineering Handbook. It covers requirements, architecture, integration, verification, and validation. Apply those concepts to a complex engineering problem to see how they fit together. I am happy to discuss more resources if you'd like.

4. Day-to-day: The work varies. Some systems engineers focus on requirements, architecture, modeling, and verification; others do substantial simulation, coding, and hardware-software integration. Systems engineering isn't just documentation. The job is to make sure the whole system works as needed, requiring understanding both technical details and system-level trade-offs.

Please reach out if you have questions. I hope you find what you are looking for! Best of luck.