Careers

DevOps and DevSecOps Engineer Jobs for Classified Environments

Build and run the accredited platforms that let mission AI ship into classified and disconnected environments.

DevOps and DevSecOps engineer jobs in defense build and run the pipelines and platforms that deliver software into accredited, classified, and disconnected environments, with security built into each step rather than added at the end.

By the numbers. BLS projects information security analyst employment to grow 21 percent from 2025 to 2035, with about 14,100 openings a year (BLS). Inside the department, GAO found that 3 of the 6 major business IT programs that reported using DevSecOps "did not use metrics and management tools required of these programs by DOD or did not provide evidence of their use" (GAO-25-107649, p. 36).

This page is for DevOps, platform, and security engineers deciding whether to work on defense and national security systems. It covers what the job is, where the department stands on DevSecOps, how classified systems get authorized, what the work pays nationally and in Kansas City, and what it looks like at Torch.AI.

What does a DevSecOps engineer do in defense?

The Department of War (DoW, formerly the Department of Defense) Cyber Workforce Framework defines a DevSecOps Specialist work role (code 627) that "selects/deploys/maintains the set of Continuous Integration/Continuous Deployment (CI/CD) tools and processes used by the development team and/or maintains the deployed software product and ensures observability and security across the lifecycle." Related roles include the Information Systems Security Manager (722), "responsible for the cybersecurity of a program, organization, system, or enclave," and the System Administrator (451) (DCWF Tool v5.3, Sept. 2026).

The best software is worthless to the mission if it cannot be deployed where the mission is. At Torch.AI, platform engineers make hard environments routine:

  • Accredited delivery across classification levels. CI/CD and infrastructure that meet the department's cloud impact levels (IL5, IL6) and carry software from unclassified through secret environments.
  • Edge deployment in DDIL conditions. Shipping and running systems that keep working when the network is denied, degraded, intermittent, or limited.
  • Compliance as code. Turning accreditation and continuous authorization requirements into automated, auditable controls instead of manual paperwork.
  • Observability where you cannot phone home. Telemetry and reliability for systems that have to be trusted without a live connection back.
How it works

From commit to an authorized, fielded system

DEVELOPER COMMITFIELDED, MONITORED CAPABILITYCOMMITCode mergedwith securitychecksBUILDPipeline buildsand scansartifactsASSESSControlsassessed underthe RMFAUTHORIZEGovernmentdecides toauthorizehuman decidesDEPLOYShipped toclassified oredge enclavesMONITORContinuousmonitoringafter fieldingSecurity evidence comes out of the pipeline, not a scramble at the end.

In classified environments the pipeline does double duty: it ships software and it produces the evidence the Risk Management Framework needs, so compliance becomes automated, auditable controls.

Under 32 CFR 117.18 the government makes the risk-based decision to authorize a classified contractor system; the engineer's job is to make that decision well supported.

Loops · respects reduced-motion · illustrative

Where is the department on DevSecOps adoption?

Committed, and early. In its 2025 assessment of major IT business programs, GAO reported that the department's CIO "is advancing DevSecOps as the preferred software delivery model to replace legacy waterfall practices" (p. 40). The same review found that "three of the six that reported using DevSecOps did not use metrics and management tools required of these programs by DOD or did not provide evidence of their use," and that CIO officials "acknowledged that the adoption of modern software approaches like Agile and DevSecOps may be in the early stages of implementation" (p. 36) (GAO-25-107649).

For an engineer, early is an opportunity: the practices are expected, and the people who can make them work in accredited environments are scarce.

How do classified systems get authorized?

DevSecOps in defense runs inside a security authorization process. A few rules shape the work:

Requirement What it means for a DevSecOps engineer Source
Contractors processing classified information on an information system appoint an Information Systems Security Manager with "technical competence commensurate with the complexity of the information system" Pipelines and platforms are built alongside a named security owner 32 CFR 117.18(c)
Classified contractor systems follow NIST SP 800-37 (Risk Management Framework), CNSS Instruction 1253, and NIST SP 800-53, and the government makes the "risk-based decision to authorize the system" Controls, evidence, and monitoring are engineering work, and the authorization decision belongs to the government 32 CFR 117.18(a), (e)
The RMF covers "control selection, implementation, and assessment; system and common control authorizations; and continuous monitoring" Continuous monitoring is part of the platform, not a one-time audit NIST SP 800-37 Rev. 2
DoD may only buy cloud services from providers with a DISA provisional authorization "at the level appropriate to the requirement" under the Cloud Computing SRG Platform choices are bounded by impact level DFARS 239.7602-1
Contractors keep government data "within the United States or outlying areas" unless the contracting officer approves otherwise Data residency is a design constraint DFARS 252.239-7010

The common thread is NIST's Secure Software Development Framework, "a core set of high-level secure software development practices" meant to be built into every life cycle (NIST SP 800-218).

Make hard deployments routine.

IL5 and IL6 delivery, air-gapped edge systems, and compliance as code. See where you would fit.

Accredited CI/CD.
Disconnected edge.
Continuous ATO.

See platform roles >

IL5 and IL6 delivery, air-gapped edge systems, and compliance as code. See where you would fit.

Accredited CI/CD.
Disconnected edge.
Continuous ATO.

What do DevOps and DevSecOps engineer jobs pay?

BLS has no separate code for DevOps engineers; the work sits inside these occupations. The table compares national medians with the Kansas City metro, where Torch.AI is headquartered.

Occupation (SOC) U.S. jobs U.S. median wage KC metro jobs KC median wage
Computer network architects (15-1241) 179,740 $134,050 1,620 $107,450
Information security analysts (15-1212) 190,650 $129,180 1,810 $104,010
Network and computer systems administrators (15-1244) 314,340 $99,130 2,760 $91,980

Source: BLS Occupational Employment and Wage Statistics, May 2025, national and Kansas City MO-KS MSA (28140). These are occupation-wide medians, not Torch.AI salaries.

  • Security-heavy roles grow fastest. BLS projects information security analysts to grow 21 percent and computer network architects 8 percent from 2025 to 2035; systems administrators are projected to decline 4 percent, though about 13,400 openings a year remain (BLS). The shift favors engineers who automate and secure platforms over those who only maintain them.
  • Kansas City over-indexes on these skills. Information security analysts are 35 percent more concentrated in the Kansas City metro than nationally, network architects 28 percent, and systems administrators 25 percent (location quotients 1.35, 1.28, and 1.25, BLS OEWS). For more on the local market, see Kansas City AI jobs.

What skills do DevSecOps engineers need for classified work?

  • CI/CD and infrastructure as code. Repeatable, auditable delivery is the foundation.
  • Risk Management Framework fluency. Knowing how controls are selected, implemented, assessed, and continuously monitored.
  • Air-gapped and disconnected operations. Moving artifacts, updates, and telemetry without assuming a connection.
  • Secure development practices. SSDF-style controls in the pipeline, including for AI model components.
  • Working with security owners. Partnering with the ISSM and assessors rather than handing compliance off.

Do DevSecOps engineer jobs require a security clearance?

Most work in classified environments does. Under 32 CFR 117.10, the government determines eligibility, and a contractor may request it only when classified access "is essential" to a contract. At Torch.AI, many roles require an active U.S. security clearance; others are open to clearable U.S. persons, with sponsorship for the right engineer. The step-by-step path is in Kansas City AI jobs.

What is it like to run platforms at Torch.AI?

Our environments are high-consequence, so the platform bar is high: deterministic deploys, least privilege by default, and systems that are trustworthy when disconnected. You own the path from commit to fielded capability in places most pipelines never reach. Torch.AI is headquartered in Leawood, Kansas, with engineering roles there and in the Washington, DC region (see current openings).

Is this you? You will likely do well here if you:

  • Treat a hard deployment environment as the interesting part, not the blocker.
  • Want to own reliability and security end to end, not hand them off.
  • Like making accreditation and compliance fast instead of painful.
  • Hold or can hold a U.S. security clearance.

This may not be for you if you only want greenfield cloud-native work with no constraints, you see security and compliance as someone else's job, or you would rather stay far from the mission the platform serves.

Related paths: AI Software Engineer, AI Data Engineer, and AI Technical Program Manager.

How do you apply for DevOps and DevSecOps jobs at Torch.AI?

Current openings, locations, and clearance requirements are listed at torch.ai/careers. Each listing states whether the role requires an active clearance or is open to clearable candidates.

Ship where most pipelines stop.

Own the path from commit to fielded capability in classified and disconnected environments.

End-to-end ownership.
Security by default.
Mission at the end.

View DevOps openings >

Own the path from commit to fielded capability in classified and disconnected environments.

End-to-end ownership.
Security by default.
Mission at the end.

Sources

See open roles