The DC experience confirmed the direction: build defense systems with enough technical depth to matter and enough institutional fluency to move through the rooms where those systems are funded, fielded, challenged, and governed.
Five days of institutional exposure across defense, policy, intelligence, humanitarian law, and graduate national security pathways.
The major lesson was specificity. “Interested in defense” is not a direction. Power and communications systems, GPS-denied navigation, mission-assured communications, TT&C, resilient infrastructure, and the ability to brief those systems to non-technical decision-makers - that is a direction.
Questions with intelligence, policy, and defense leaders repeatedly returned to degraded navigation, contested communications, and the capability gaps that open when systems lose trusted PNT.
CNAS and Capitol Hill reinforced the same lesson: engineers who can explain technical risk, operational consequence, and budget relevance become far more useful than engineers who only build.
The week produced concrete research pathways for ARMS through problems discussed around SOCOM, CENTCOM, defense contractors, and service innovation pipelines.
Walked the Pentagon, then engaged CNAS researchers on technology competition with China, AUKUS quantum PNT, defense industrial base constraints, airpower, and GPS-denied navigation. The takeaway: technical systems only matter when they can survive the acquisition, integration, and operational environment around them.
Discussed weapons reviews, autonomous systems, meaningful human control, NDAA pathways, HASC relationships, and the link between technical military capability and diplomatic leverage. The lesson: defense engineering does not operate outside law and policy - it is shaped by them.
Engaged LTG (Ret.) Robert Ashley Jr. on JSOC mission failure modes when navigation and communications systems degrade, capability gaps the engineering community underestimates, and what a student defense engineering organization should build toward.
Georgetown SSP clarified a long-range academic path: Technology and Security as a natural bridge for an EE student working on defense hardware, strategic context, and national security institutions.
That is the career direction now: technical depth in power, communications, embedded systems, and navigation - paired with enough national security fluency to understand what the system has to do, who it has to serve, and what happens when it fails.