This page is under construction
One of the key systems engineering learning experiences, as an objective of Systems 490, is to learn to compete as a systems engineer: it is to learn how to get an SE job done when almost everything up front suggests it can't be done: not enough time, not enough experience, and more questions without answers, as well as inadiquate guidance and decisions by those who should provide them. That is the real world for systems engineers.
A valuable response in any interview for a systems engineering
position is to be able to report, with experience: "I can get things
done when all would suggest that it couldn't be done. " " I know how to
prioritize, capitalize, and keep going in spite of otherwise
insurmountable odds." "I know hot to identify ranges and options in
the absense of clear guidance. " "I know how to abstract specifics
into generic problems, that are then tractable in the context of generic
(system) solutions." "I know how to satisfy constraints with the
best that can be done, rather than complain or justify why I failed."
"I know how to complete and win contracts for systems."
I am a Systems Engineer.