Lead DevSecOps Engineer

Lead Dev Sec Ops  Engineer

This position will be onsite at a facility in Sterling, VA. This position requires an active U.S. national security clearance. To learn more about the security clearance process please access this link.

Lyntris is a defense technology company that connects sensing to action across the connected battlespace. Lyntris brings together the talents of Accelint and Vitesse teams under one mission, with each contributing deep expertise within their domain. Combining differentiated hardware, software and mission expertise, Lyntris helps customers sense threats, make sense of complex conditions and act with greater speed, precision and confidence in contested environments.

Lyntris supports U.S. and allied defense organizations across every branch - including Navy, Army, Air Force, Space Force and allied partners - spanning strategic, operational and tactical missions and every domain:
Space, Air, Land, Sea and Cyber. With more than 200 active defense programs, Lyntris works at every level of the mission, from national command authority to the tactical edge. Solutions are designed by operators who understand the mission, engineered for the conditions that degrade or defeat standard systems, and built on an open, modular architecture that integrates into existing programs without requiring them to start over.

Lyntris moves faster than the traditional defense cycle - with integrated design, build and test capabilities in-house - and delivers systems that sustain and endure long after initial fielding.

The Lead Dev Sec Ops  Engineer is a strategic and hands-on technical leader responsible for building and advancing the Dev Sec Ops  practices, infrastructure, automation, and integration capabilities that support complex DoD software systems. This role leads the design and execution of CI/CD pipelines, system integration testing, test automation, and secure, scalable deployment infrastructure while mentoring engineering teams and ensuring alignment with security and compliance requirements.

The Lead Dev Sec Ops  Engineer also drives reusable engineering practices, tooling, and deployment patterns that improve consistency, efficiency, and scalability across programs and the broader portfolio. This position supports the Beyond Line of Sight (BLOS) Engagement Controller and Manager (BECM) program and requires strong software integration engineering, test engineering, and Dev Sec Ops  experience to support integration, verification, automation, and documentation efforts in classified, highly regulated environments.

Work Environment:
This is a full-time on-site role in Sterling, VA, split between standard office space and SCIF work. Some flexibility in daily working hours is available, coordinated with program needs and facility access windows.

Duties & Responsibilities:

• Own system integration testing (SIT) across multiple internal subsystems and external systems, identifying issues related to interface contracts, data exchange, timing, usability, functionality, safety, and security
• Define and maintain SWIT and SIT test threads, cases, and steps, and drive traceability from requirements through verification evidence
• Lead integration events with external system owners and government stakeholders, including dry runs, formal test events, and site acceptance activities
• Triage integration defects to root cause across system boundaries and drive them to closure with the responsible team

• Design, build, and maintain test tooling as a first-class engineering product: simulators, stubs, message injectors, data generators, log analyzers, and results reporting
• Develop automated test suites and utilities, and keep them current as subsystems and external interfaces evolve
• Build and maintain automated regression capability integrated into CI/CD, so integration failures surface early rather than at test events
• Establish standard test reporting and evidence artifacts that satisfy both engineering and compliance consumers

• Design integration and test capabilities for reuse, so tooling, harnesses, pipeline templates, and deployment patterns built for BECM can be adopted by adjacent programs with minimal rework
• Identify duplicated effort across programs and consolidate it into shared, versioned, documented components
• Define and champion common standards for interface documentation, test structure, and environment configuration across the engineering organization
• Serve as a technical point of contact for other program teams adopting these capabilities

• Use container technologies to configure and deploy software to lab, integration, and customer site environments
• Build and maintain automation pipelines, artifact management, and environment provisioning for both connected and disconnected/classified enclaves
• Embed security and compliance controls into the pipeline rather than bolting them on at the end

• Collaborate with cross-functional teams to define, design, and implement new software and its verification approach
• Write and maintain…