> Markdown version of [/jobs/ext/2653483-technical-integrator](https://www.wearedevelopers.com/jobs/ext/2653483-technical-integrator). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Technical Integrator - **Company:** Spear AI - **Location:** Manassas, VA, United States - **Contract:** Permanent contract - **Skills:** Artificial Intelligence, Protocol Buffers, Message Oriented Middleware, Software Construction, C4ISR, Navsea, Apache Kafka - **Published:** August 9, 2026 - **Apply:** https://www.indeed.com/viewjob?jk=df35ca7b3ffcf568 ## About the Role * Experience operating in or alongside DoD program environments - a program office, a defense lab, a ship, or a submarine all count. * Enough technical fluency to hold an informed conversation with software engineers: you don't need to write code, but you need to understand what's being built and why it matters. * Strong written and verbal communication - you write emails that get read and responded to, and you can brief a room without losing people. * Organized and relentless about follow-through - you track open items, own them, and close them. * Comfortable finding the right person in an unfamiliar organization and building relationships quickly. * Active Secret clearance required; TS/SCI a strong plus. * Familiarity with the LM ARCI lab environment or AN/BYG-1 / submarine C4ISR integration pipelines is a significant advantage, but not required. Nice to have * Navy background in submarine sonar, fire control, or C4ISR (STS, FT, ET ratings or equivalent officer designators). * Direct experience with NUWC Newport, NAVSEA, or PEO IWS organizations. * Familiarity with modern message bus architectures (Redpanda, Kafka) in a defense context. * Exposure to Rust, C, or Protocol Buffers - enough to read code and ask informed questions. ## Description Spear AI is modernizing legacy submarine sensor systems - replacing decades-old C code with cloud-native, Rust-based pipelines backed by a modern messaging solution. We're good at building software. What we need is someone who excels at driving results within a complex defense customer environment. The Technical Integrator is the connective tissue between our engineering team and the customer. You secure access, coordinate test times, identify the right POC, ensure forms are filed, and validate our software against real requirements before it matters. This is a "get things done" role as much as a technical one - the person who knows which door to knock on and isn't afraid to knock on it. We care more about your ability to operate in this environment than your years of experience. If you've navigated DoD bureaucracy, worked alongside engineers, and made integration timelines move - whether that was in a lab, a program office, or a submarine - we want to hear from you. What you'll do * Navigate customer bureaucracy - track down forms, approval chains, and the right POC so engineers stay heads-down on code. * Own test coordination: schedule lab time, stand up environments, and confirm software behavior against acceptance criteria. * Surface, clarify, and document requirements - performance thresholds, interface specs, operational constraints - in terms that the engineering team can act on. * Maintain a living map of stakeholder contacts and escalation paths within the customer organization. * Represent Spear AI at integration events, demos, and working groups with technical credibility. * Identify blockers and integration risks early and propose solutions before they become program-level problems. * Document outcomes, open items, and decisions in real time so nothing falls through the cracks. ## Related Videos - [How to Benchmark Your Apache Kafka](https://www.wearedevelopers.com/videos/76-how-to-benchmark-your-apache-kafka) - [Hacking AI at the Edge of the Indian Ocean](https://www.wearedevelopers.com/videos/100177-hacking-ai-at-the-edge-of-the-indian-ocean) - [Let's Get Started With Apache Kafka® for Python Developers](https://www.wearedevelopers.com/videos/565-let-s-get-started-with-apache-kafka-for-python-developers) - [The Software Engineer 2030: From Coder To AI Orchestrator? - Patrick Schnell](https://www.wearedevelopers.com/videos/1825-the-software-engineer-2030-from-coder-to-ai-orchestrator-patrick-schnell) - [The AI-Native Engineering Org: What’s Real, What’s Hype, What’s Next](https://www.wearedevelopers.com/videos/100004-the-ai-native-engineering-org-what-s-real-what-s-hype-what-s-next) - [Tips, Techniques, and Common Pitfalls Debugging Kafka](https://www.wearedevelopers.com/videos/838-tips-techniques-and-common-pitfalls-debugging-kafka) ## Related Articles - [How We Built a Worry-Free System That Runs for 10+ Years – And What We’d Do Again](https://www.wearedevelopers.com/magazine/751-how-we-built-a-worry-free-system-that-runs-for-10-years-and-what-we-d-do-again) - [Dev Digest 134 - Where pixels sing?](https://www.wearedevelopers.com/magazine/477-dev-digest-134-where-pixels-sing) - [Dev Digest 132 - Binging WADFlix?](https://www.wearedevelopers.com/magazine/473-dev-digest-132-binging-wadflix) - [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline) - [Dev Digest 137 - AI'm not sure about this](https://www.wearedevelopers.com/magazine/485-dev-digest-137-ai-m-not-sure-about-this) - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers)