Skip to main content

Lead Software Engineer/Technical Program Manager

Posted 11 days ago

odyssey systemsColorado Springs (CO)

SENIORITY

Lead

Apply (opens in a new tab)

About the role

Lead Software Engineer / Technical Program Manager We are seeking a Lead Software Engineer / Technical Program Manager to own both the technical architecture and program execution of the Multimode Threat Engagement Simulation Platform — a standalone, high-performance desktop application for defense mission planning. This is a dual-charter role: you are the technical authority for the software stack and the program manager accountable to the government customer for schedule, cost, and delivered capability. What sets this role apart from a traditional software lead is the breadth of sensor and phenomenology domain knowledge required. The platform integrates physics-based models spanning RF/radar detection, electro-optical and infrared sensor performance and multi-sensor fusion into a single coherent mission analysis tool. You will work directly with RF and EO/IR engineers to translate their models into the software — which means you need enough domain fluency to review their work, design the right APIs, make informed trade-off decisions, and present results credibly to government customers who are subject matter experts in these disciplines.*Contingent upon contract award*Responsibilities Technical Leadership Own the end-to-end software architecture: Julia-based computation backend (trajectory simulation, orbital mechanics, Monte Carlo analysis, surrogate ML inference), React/TypeScript frontend with CesiumJS 3D geospatial visualization, and Electron desktop shell targeting Windows and LinuxMake and document architecture decisions: data flow between physics backend and frontend, API contracts, mission data schema, CZML generation for Cesium time-dynamic animation, and cross-platform build pipeline (GitHub Actions, electron-builder, PackageCompiler.jl) Lead technical design reviews; review and approve all major pull requests; maintain code quality, test coverage, and documentation standards across the team Define performance requirements and validate that the computation backend meets them: Monte Carlo throughput, surrogate model inference latency (

Before you apply

Applying takes about a minute. These four things decide how fast it moves after that.

Your profile is current

It's what we read first. Occupations, seniority and locations matter more than a long history.

Two examples you can talk through

Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.

A number in mind

What you're on now and what would make you move. We negotiate better when we know both.

Your notice period

Employers plan around it, and it's the question that stalls offers most often.

Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.

More like this