Find what governs the problem.
I start with first principles: what is fundamental here? Energy, physical size, power, or another controlling constraint? Identify that driver before choosing an approach.
I’m Alex Ford. This archive follows the systems I’ve worked on, the teams I’ve led, and what I’ve learned along the way.
A personal professional archive · August 2017 to present

The archive begins in August 2017, at the transition from graduate research into industry. Each chapter records the questions, teams and capabilities that shaped what came next.
Exact appointment dates and titles from the June 2026 CV, kept distinct from the location-based career chapters.
Selected projects, told through the problems, decisions, and people behind them. Open a source to trace the public record.
Principles developed through hands-on engineering, technical reviews, and leading teams. The aim is rigorous work and helping people succeed.
My role as a leader is to help the team succeed. I set reasonable deadlines and hold work products to a high standard. When someone needs an explanation, hands-on help, or top cover, I provide it.
As a technical authority, I enjoy getting close to the engineering. The highest moments of managing an organization, though, came from watching other engineers grow and succeed.
I start with first principles: what is fundamental here? Energy, physical size, power, or another controlling constraint? Identify that driver before choosing an approach.
Inconsistencies suggest that a work product needs more rigor. A lack of clarity can mean the underlying reasoning is not yet well understood. I prefer to work through those issues with the engineer.
Growth assignments should stretch engineers, and some struggle is expected. Good leadership builds the support around them instead of leaving them set up for failure.
My ideal team is full of capable engineers who know things I do not and challenge my thinking. Technical authority does not remove the need to keep learning.
“Every week. I’m always learning.”
I hope to help shape ground-based radar strategy across the enterprise, drawing on innovations from space, airborne, and other disciplines. That starts with relationships among technical experts, followed by collaborative technology roadmaps.
Recognition for technical invention and professional contributions. Each award is placed alongside the work it represents, where that connection is documented.
Additional honors and nominations from the professional years.
Follow the places behind the projects: career bases, missions, campuses and conferences. This is the same interactive Life Map that powers my personal atlas, here focused on work.
Having trouble viewing the embedded map? Open it directly in a new tab ↗
Conferences, panels, research papers, invited talks, and organizing roles are connected to the work presented. Authorship does not automatically mean attendance.
Journal articles and technical conference papers published after August 2017. Links point to publisher records or the public bibliography, not personal licensed PDFs.
Research affiliations held alongside professional work, without introducing a separate geographic career chapter.
Sources and revisions matter. Press links often move; original URLs, surviving official pages and contemporary coverage are preserved without inventing archive captures.
More program histories, public artifacts, photographs and memories will follow as each can be corroborated.