Technical Integrator

About the role

The Technical Integrator acts as the bridge between engineering and complex defense customer operations, enabling progress when navigating bureaucracy matters. Success in this role depends on operating effectively within program office, lab, ship, or submarine environments and driving integration timelines forward.

Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.

Key facts

What you'll do

Acceptance criteria are validated by confirming software behavior against requirements during scheduled lab time and standing up the necessary test environments. Stakeholder understanding is built by clarifying performance thresholds, interface specifications, and operational constraints into actions the engineering team can execute. Technical credibility is demonstrated when Spear AI is represented at integration events, demos, and working groups. Blockers and integration risks are identified early, and solutions are proposed before issues escalate to program-level problems. Outcomes, open items, and decisions are documented in real time so work does not fall through gaps.

Requirements

Experience operating in or alongside DoD program environments such as a program office, defense lab, ship, or submarine is required. The ability to hold informed conversations with software engineers is necessary, even without writing code. Clear written and verbal communication ensures emails are answered and briefings are understood by stakeholders. Organization and relentless follow-through are used to track open items to closure. Capability to locate the right person in unfamiliar organizations and build relationships quickly is essential. An active Secret clearance is required, with TS/SCI as a strong advantage. Familiarity with LM ARCI lab environments or AN/BYG-1 and submarine C4ISR pipelines is advantageous but not mandatory.

Nice to have

A Navy background in submarine sonar, fire control, or C4ISR ratings is valued. Direct experience with NUWC Newport, NAVSEA, or PEO IWS organizations is viewed as an advantage. Familiarity with message bus architectures such as Redpanda or Kafka in defense contexts supports the role. Basic ability to read code in Rust, C, or Protocol Buffers allows for asking informed questions about implementation details.

Practical notes

This role requires comfort with defense bureaucracy and the ability to navigate complex integration schedules. Work directly influences fleet modernization outcomes for the organization. General defense technology context centers on message-driven architectures and legacy sensor system replacement. Typical interview steps

Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.

Good to know

Technical Integrators operate effectively within defense bureaucracies and own integration timelines. The work connects engineering teams to program-level stakeholders and affects modernization outcomes. Relevant tools include message-driven architectures and legacy sensor system replacement pipelines. Clear communication and follow-through are central to success in this role. This role operates within a defense technology environment focused on integrating new Rust-based systems with existing infrastructure.