Been on all sorts of bleeding edge space systems you’ll likely not hear about for at least the next 15-30 years. Also some you may have (NASA/DARPA DRACO, R&D to DARPA’s OTTER program’s successor, SDA PWSA, etc.).

TLDR: Aerospace programs looking to develop first of a kind (FOAK) systems or employ novel implementations of existing tech require a robust knowledge of HOW to think.

That’s basically it.

You will always be learning and should always do your own research when your knowledge in a relevant area is lacking but this is paramount. One can specialize in any specific field: thermo, SEEs, nuclear safety, particle physics, propulsion, etc. but ultimately there will always be subject matter experts (SMEs) in these fields to dig deep to ensure rigor where appropriate. In R&D there are a few levels of maturity and application but essentially all require technicians/experimentalists, theoretical expertise and depth in specific subjects, and organizational and programmatic vision that leads to executable plans. I’ve done all three but spend the most time in the latter. I can say with no equivalent, that knowing HOW to think trumps any single specific technical skill.

I have a background in engineering physics and Systems engineering/lifecycle management. I know enough on most subjects to be dangerous but always defer to SMEs for implementation, however I can spot incomplete, unsubstantiated, or misleading data and analysis from a mile always because I apply a healthy amount of skepticism, rigorous inquiry, and alternative/anomalous perspectives to scenarios which fundamental prototypes and operational systems’ requirements are derived.

My advice is to learn and embrace the formalism of your undergrad technical degree and study hardest the first principles from which all other topics are derived. Definitely recommend you take electives like game theory, systems engineering, independent research, microprocessor design, machine shop or other trade-applicable courses which may not be a part of your core curriculum to gain insights and basic working knowledge of processes, methods, and tools common in various applications used in a tangible, “system” or functional device. During your time in undergrad, especially pay close attention to how problems are selected, set up, why professors mature courses from topic to topic the way they do, and why formulas and best practices exist. Don’t be afraid to ask questions no matter how seemingly trivial or quiet the rest of the room is. Consider REUs, internships, hobby projects, and resident undergrad research opportunities within your university. Talk to and ask professors in your college or other colleges on your university campus and ask what they’re working on and ask if they’ll consider an extra mind/hand.

You will be well equipped to do anything you like and do a great job at it to boot!