VIEW: [ C4SIR System Payload ]

Mission-critical leadership roles

My leadership developing mission-critical systems emerged during a time of rapid technological change. My early role in the Pioneer UAV program — one of the first operational UAV systems fielded by the U.S. military — kicked off a run spanning nearly two decades in systems integration applying innovations in RF systems, applied digital signal processing (DSP), and information systems design.

After Pioneer, I was drawn into direction-finding and DSP-based systems, and was soon drafted into a department manager role at a commercial hardware company — effectively becoming a chief engineer in all but title. I led a multi-product portfolio through successive iterations of development, and as the company prepared for acquisition, I was promoted to Technical Director, responsible for managing its intellectual property and research and development portfolio. These proved to be key assets in achieving a favorable sale price.

I made a deliberate decision to pivot as Y2K arrived. In 1999, I left hardware behind to join a dot-com startup — convinced that the internet, not RF-centric military systems, represented the future of innovation.

That startup ultimately failed, but the reinvention was real. I returned to the national security domain with hard-won experience in distributed information systems, and was recruited as chief engineer for a global mission management architecture program. Shortly afterward, I was offered — and accepted — a leadership bonus to join a multi-platform C4ISR light aircraft integration project as their chief engineer.

The attached C4ISR Platform Proposal excerpt illustrates my systems integration experience, as I resumed my deliberate reinvention. I anticipated that the market for applications like C4ISR platforms would force career choices unfavorable to my own lifestyle and family, so I had returned to graduate school — toward emerging trends in information retrieval, applied graph theory, and large-scale analytics using models like MapReduce. The time had come to make the final jump as the integration project was working through the tail its five platform deliveries.

  • I was offered — and accepted — a leadership bonus to join a multi-platform C4ISR light aircraft integration program as chief engineer. The project delivered five airborne platforms integrating sensors, mission computing, and communications in a high-stakes, politically sensitive environment.

    From the outset, the program demanded not just system design and integration, but sustained field operations, including multi-month flight testing, platform calibration, and live mission simulation. These efforts involved:

    • Coordinating 24/7 test ranges and airfield operations

    • Managing a cross-disciplinary team across hardware, RF, and software domains

    • Leading the reduction of high-volume telemetry and signal data

    • Enforcing rigorous test and validation procedures to gain acceptance across multiple stakeholder groups

    The customer often operated in a “we’ll know it when we see it” mode, which required my team to maintain agility while preserving system integrity and traceability. Translating informal expectations into testable outcomes became a core part of the leadership challenge.

    Outcome: The team delivered five fully verified platforms. As the program neared completion, I resumed my deliberate pivot toward data-centric systems — focusing on signal extraction, graph modeling, and large-scale analytics using MapReduce, drawn directly from the data these platforms were built to collect.

  • I served as chief engineer for a mission management architecture demonstrator intended to reimagine global operations center workflows. I led the completion of a formal DODAF architectural baseline and built an integrated demonstration environment using:

    • ESRI ArcGIS

    • OLAP and reporting frameworks

    • BEA WebLogic middleware

    • Early BPMN-based visualization

    • Virtual workstations and projection displays

    I worked directly with stakeholders across multiple agencies to ensure system realism, scope control, and architectural integrity.

    Impact: The demonstrator seeded follow-on systems, and the architecture informed future global enterprise processes.

  • At Watkins-Johnson, a company known for advanced RF and SIGINT systems, I rose into senior technical leadership as Technical Director, managing the intersection of research and development, intellectual property strategy, and product portfolio direction.

    My responsibilities included:

    • Overseeing technology transfer from prototype to fielded product

    • Managing and documenting intellectual property critical to company valuation

    • Coordinating R&D project selection and funding

    I was part of the executive technical team during the company’s transition and eventual acquisition, where the value of our IP and roadmap was a key part of negotiations. This experience gave me deep insight into how engineering leadership shapes strategic outcomes, not just product outcomes.

  • As a systems engineer on the Pioneer UAV program in the late 1980s, I contributed to one of the first operational UAV deployments in U.S. military history. I played multiple roles over the life of the program, including serving as an automatic landing control systems engineer — supporting critical flight control capabilities at a time when autonomous UAV operations were still emerging.

    My work spanned system integration, test readiness, and field deployment, including:

    • At-sea trials and flight operations from the USS Iowa, USS New Jersey, and USS Missouri

    • Desert flight testing in harsh environmental conditions

    • Operational engineering support for Navy and Marine Corps deployment teams

    Pioneer made history during the First Gulf War as the first U.S. UAV used in combat, providing real-time reconnaissance, targeting support, and contributing to enemy surrenders — proving the battlefield value of unmanned systems.

    This experience shaped my approach to engineering leadership

    • Platform integration must be grounded in field operability and mission context

    • Control systems must work reliably under real-world constraints, not just in simulation

    • Success depends on blending systems thinking with an understanding of operational tempo

    Pioneer remains a formative experience — both technically and professionally — anchoring my early career in real-world mission-critical delivery.