Job description

Job Title: Lead Software Engineer Location: Remote + Travel (2 weeks per Quarter) Security Clearance: Top-Secret Eligible We question. We listen. We adapt. Be honest. Be pragmatic. Omni Federal , founded in 2017 and headquartered in Washington, DC, is a highly specialized software solutions provider with a robust presence in key locations across the United States, including Boston, MA, Colorado Springs, CO, San Antonio, TX, and St. Louis, MO. Born out of the Department of Defense's software factory ecosystem, Omni has rapidly distinguished itself by delivering both mission-critical and enterprise solutions that enhance the technological capabilities of the federal government. With a focus on areas such as Command and Control, Cybersecurity, Space, Geospatial, and Modeling & Simulation, Omni leverages cutting-edge commercial technology tailored to government objectives, improving mission performance and delivering transformative outcomes for the Department of Defense (DoD), Intelligence Community (IC), and their end-users. The company's innovative approach is backed by its Omni Labs and SBIR Innovation centers, where they develop advanced platforms and tools in data mesh, secure connectivity, and intelligent automation. Why Omni? • Environment of Autonomy • Innovative Commercial Approach • People over process Omni Federal is building A2D2, an AI-assisted course-of-action generation capability for the Department of the Air Force battle management. The Lead Software Engineer owns the technical direction of A2D2’s data and services layer and leads developers across several component teams in a shared monorepo. The core of the role is steady, deliberate system evolution: architecture that changes in small steps the team can follow, decisions written down and defensible, and outcomes that improve release over release. The lead is the technical voice to operators and the government customer. They are expected to learn the C2 mission personally and teach it to the team Required: Mission and Domain • Delivered software for operational C2 or battle management systems, with direct exposure to air battle management, BMC2, or equivalent mission threads. Prior operator or battle manager service also qualifies. • Speaks C2 fluently: can explain the kill chain, the air tasking cycle, and how a COA moves from planning to execution to a developer and to an operator. • Understands mission tempo: what latency an operator can tolerate, what must stay deterministic, and what degradation is acceptable under load. • Familiarity with JADC2/CJADC2 or ABMS program context and the data-sharing problems they are chartered to solve. Required: Technical Skills • 7+ years of overall technical experience • Designed and operated event-driven pipelines over Redis Streams, Kafka, or NATS with explicit backpressure, replay, and delivery-semantic guarantees. • Engineered entity resolution and enrichment workflows reconciling records across heterogeneous upstream sources with provenance and confidence scoring carried end to end. • Operated Redis as stream transport, RPC substrate, and cache with deliberate failure, reconnection, and idempotency handling. • Delivered software against operational C2 or battle management systems, with direct exposure to air battle management, BMC2, or equivalent mission threads. • Worked fluently with tactical data links and C2 message standards — Link 16 / MIL-STD-6016, VMF, JREAP, Cursor on Target, or OMS/UCI — including parsing, normalization, and emission. • Engineered track management, correlation, and fusion logic feeding a common operating picture, including handling conflicting and stale reports from multiple sensor sources. • Designed data systems for DIL environments — disconnected, intermittent, and limited-bandwidth — where the network is an assumption that fails routinely. • Implemented store-and-forward and delta-synchronization patterns with explicit conflict resolution on reconnect, rather than last-write-wins. • Engineered bulk mission-data offload and reconciliation workflows: ingesting an airborne system’s accumulated state on return to a connected installation and merging it against the authoritative record. Required: Leadership Skills • Set technical direction for a multi-engineer team and evolved a production architecture incrementally. Can describe a large rewrite they chose to stage or decline, and why. • Writes architecture decision records and deployment documentation as first-class deliverables. • Briefs technical tradeoffs directly to government customers and operators in their terms. • Uses AI coding tools productively while owning every design decision and being able to defend it. Nice to have: • ISR and defense mission data domains: link analysis, course-of-action modeling, track and entity fusion. • Geospatial data handling. • Abstracted model backends behind a stable interface so the same mission capability runs under either tier without a forked codebase. • Directed technical design and code review across multiple component teams inside a shared monorepo. • Experience with Platform One, Big Bang, or Iron Bank distribution patterns for accredited on-prem delivery. • Delivered analytical and batch processing at scale using Polars, pandas, PyArrow, Parquet, and DuckDB over columnar stores. • Published architecture and deployment documentation as a first-class deliverable alongside code. Our team is always hungry for more – more knowledge, more problem solving, more growth, more innovation, and, ultimately, customer success. This hunger and hustle fuel our determination to excel in everything we do. It’s not just about meeting established goals; it’s about exceeding them. We take immense pride in applying our expertise in cutting-edge technologies and our ability to adapt to emerging trends directly to the users in the field, as our nation’s protectors deserve nothing less. Omni Federal is an equal opportunity and affirmative action employer. Omni Federal is committed to administering all employment and personnel actions on the basis of merit and free of discrimination based on race, color, religion, sex, sexual orientation, gender identity, national origin, protected veteran status, or status as an individual with a disability. Consistent with this commitment, we are dedicated to the employment and advancement of qualified minorities, women, individuals with disabilities, protected veterans, persons of all ethnic backgrounds and religions according to their abilities

Requirements

Must-haves

Job Title: Lead Software Engineer
Location: Remote + Travel (2 weeks per Quarter)
Security Clearance: Top-Secret Eligible
We question. We listen. We adapt.
Be honest. Be pragmatic.
Environment of Autonomy
Innovative Commercial Approach
People over process
Required: Mission and Domain
Delivered software for operational C2 or battle management systems, with direct exposure to air battle management, BMC2, or equivalent mission threads. Prior operator or battle manager service also qualifies.
Speaks C2 fluently: can explain the kill chain, the air tasking cycle, and how a COA moves from planning to execution to a developer and to an operator.
Understands mission tempo: what latency an operator can tolerate, what must stay deterministic, and what degradation is acceptable under load.
Familiarity with JADC2/CJADC2 or ABMS program context and the data-sharing problems they are chartered to solve.
Required: Technical Skills
7+ years of overall technical experience
Designed and operated event-driven pipelines over Redis Streams, Kafka, or NATS with explicit backpressure, replay, and delivery-semantic guarantees.
Engineered entity resolution and enrichment workflows reconciling records across heterogeneous upstream sources with provenance and confidence scoring carried end to end.

Nice-to-haves

ISR and defense mission data domains: link analysis, course-of-action modeling, track and entity fusion.
Geospatial data handling.
Abstracted model backends behind a stable interface so the same mission capability runs under either tier without a forked codebase.
Directed technical design and code review across multiple component teams inside a shared monorepo.
Experience with Platform One, Big Bang, or Iron Bank distribution patterns for accredited on-prem delivery.
Delivered analytical and batch processing at scale using Polars, pandas, PyArrow, Parquet, and DuckDB over columnar stores.
Published architecture and deployment documentation as a first-class deliverable alongside code.

Application prep

Use the role’s language and application details while tailoring your materials.

Keywords to mirror

Platform: agile-ats
Effort: medium