Careers
Build the models and reasoning that turn fused mission data into understanding the customer can trust and trace.

AI and machine learning engineer jobs in defense build, evaluate, and field models that turn mission data into decisions people can trace, usually for employers whose work requires a U.S. security clearance or the ability to obtain one.
By the numbers. BLS projects U.S. employment of data scientists to grow 35 percent from 2025 to 2035, and of computer and information research scientists to grow 22 percent, citing demand for artificial intelligence (BLS Occupational Outlook Handbook). The median annual wage for computer and information research scientists was $140,300 in May 2025 (BLS).
This page is for engineers deciding whether to point their machine learning career at defense and national security. It covers what the work is, how it differs from commercial ML, what the jobs pay nationally and in Kansas City, how clearances work, and what the work looks like at Torch.AI.
The Department of War (DoW, formerly the Department of Defense) has its own definition. Its Cyber Workforce Framework includes a Data/AI workforce element, and within it an AI/ML Specialist work role (code 623) that "designs, develops, and modifies AI applications, tools, and/or other solutions to enable successful accomplishment of mission objectives" (DoW Cyber Workforce Framework, DCWF Tool v5.3, Sept. 2026). The same element defines an AI Test and Evaluation Specialist role (672) that tests AI "to ensure they are developed to be and remain robust, resilient, responsible, secure, and trustworthy."
In practice, the job is less about training the largest model and more about making a model's output usable for a decision with consequences. At Torch.AI that means building:
The algorithms are the same. The constraints are not. The comparison below is Torch.AI's view, anchored to the public standards that shape defense AI.
| Dimension | Typical commercial ML | Defense and national security ML |
|---|---|---|
| Data | Mostly first-party, consistent formats | Fragmented across many systems, mixed formats and classification levels |
| What "good" means | Engagement, conversion, accuracy on a benchmark | A decision a person can defend, with the evidence behind it |
| Explainability | Often optional | Expected: the DoW's AI principles call for "transparent and auditable methodologies, data sources, and design procedure and documentation" |
| Human role | Automation where possible | Humans stay in command of consequential decisions |
| Where it runs | Public cloud, always connected | Classified enclaves and disconnected or degraded networks at the edge |
| Ownership | Vendor-owned models and pipelines | Increasingly government-owned systems the customer can inspect |
Two public frameworks explain most of the right-hand column. The National Institute of Standards and Technology lists the characteristics of trustworthy AI as "valid and reliable, safe, secure and resilient, accountable and transparent, explainable and interpretable, privacy-enhanced, and fair with harmful bias managed," and treats valid and reliable as "a necessary condition of trustworthiness" (NIST AI RMF 1.0, p. 12). The department's five AI Ethical Principles (2020) require AI to be responsible, equitable, traceable, reliable, and governable, including "the ability to disengage or deactivate deployed systems that demonstrate unintended behavior" (DoW release).
The department's 2023 Data, Analytics, and AI Adoption Strategy rests on an "AI Hierarchy of Needs" that starts with "quality data, governance, insightful analytics and metrics, assurance and responsible AI," and one of its stated goals is to "expand digital talent management" (DoW release, Nov. 2, 2023). Data quality comes first in that hierarchy, which is why so much defense ML work is data and evaluation work.
There is no federal occupation code for "machine learning engineer." The Bureau of Labor Statistics counts the work inside a few existing occupations, so the honest answer is a range across them. The table compares the national median 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 and information research scientists (15-1221) | 37,200 | $140,300 | 120 | $104,670 |
| Software developers (15-1252) | 1,687,890 | $135,980 | 12,160 | $124,990 |
| Data scientists (15-2051) | 262,440 | $120,230 | 1,260 | $99,870 |
| Computer occupations, all other (15-1299) | 435,370 | $116,580 | 3,900 | $105,470 |
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.
What the numbers say:
The fundamentals are the same as anywhere: Python, statistics, model training and evaluation, and data engineering. Defense work raises the weight on a few others.
Many do, and the rules are set by federal regulation rather than the employer. Under 32 CFR 117.10, the government (the cognizant security agency) determines eligibility, a contractor may only request it when classified access "is essential" to a contract, and requests "will not be used to establish a cache of cleared employees." A contractor can start the process before your first day once it has made a written offer and you have accepted it in writing (117.10(f)).
That is why job listings say "active clearance required" for some roles and "clearable" for others. 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 full step-by-step path is in how to get a cleared AI job without a clearance.
Torch.AI builds reasoning infrastructure for defense and national security: software that fuses data from many separate systems into conclusions a mission team can trace back to sources, in systems the customer owns. AI/ML here is not demos. It is reasoning that has to be right, explainable, and fast enough to matter when a decision is on the line.
Torch.AI was founded in Kansas City and 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:
This may not be for you if you want to chase benchmark numbers in a sandbox, you are indifferent to explainability and provenance, or you would rather stay far from how the model gets used.
Related paths: AI Software Engineer, AI Data Engineer, and DevOps and Platform Engineer.
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. Tell us what kind of reasoning you want to build and why it matters to you.