> Markdown version of [/jobs/ext/2144205-ai-platform-engineer](https://www.wearedevelopers.com/jobs/ext/2144205-ai-platform-engineer). 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).

---

# AI Platform Engineer

- **Company:** Forterra
- **Location:** Arlington, VA, United States
- **Experience:** Experienced
- **Salary:** $125,000.0 - $145,000.0
- **Contract:** Permanent contract
- **Skills:** Application Programming Interfaces (APIs), Data Analysis, Systems Engineering, Code Review, Continuous Integration, Linux, Middleware, Issue Tracking Systems, Python (Programming Language), Machine Learning, OAuth, Open Source Technology, OpenID, Role-Based Access Control, Requirements Management, Security Assertion Markup Language (SAML), Software Construction, Software Engineering, Dynamic Routing, Chatbots, Large Language Models, Multi-Agent Systems, Model Validation, Data Layers, AI Platforms, Software Version Control
- **Published:** August 20, 2026
- **Apply:** https://www.disabledperson.com/jobs/74391405-ai-platform-engineer

## About the Role

3+ years building software systems, with meaningful recent depth in LLM-based or agentic systemsDemonstrated fluency with modern agent architecture: tool/function calling, MCP or an equivalent tool protocol, context management, retrieval, multi-agent orchestration, and hooks or middleware for policy enforcementPractical judgment about model selection and cost/latency/quality tradeoffs, and a habit of tracking the frontier rather than relying on last year's assumptionsExperience evaluating AI system quality with rigorExperience with analysis of unstructured dataExperience running non-interactive workloads in production: CI pipelines, scheduled jobs, or event-driven triggersStrong Python intuition plus comfort in shell, CI, and Linux service operationExperience building and maintaining production applicationsWorking understanding of enterprise identity and authorization (OAuth2/OIDC/SAML, tokens, scopes, least privilege)Excellent written AND oral communication, Strong background in statistics and/or classic machine learning AND deep learningExperience fine tuning LLMs on codebases and enterprise data (DPO, QLoRA, GRPO)Contributions to open source agent harnessesKnowledge-graph, ontology, or retrieval architecture work across heterogeneous unstructured enterprise dataExperience developing metrics and measuring productivity of software engineeringExperience running an internal developer platform or enablement function: adoption metrics, contributor onboarding, deprecationBackground in systems engineering, safety engineering, or verification & validationExperience with AI systems in a regulated, classified, or export-controlled environment - CUI, ITAR, NIST 800-171, FedRAMP/GovCloudExperience designing human-in-the-loop review gates for automated systemsPublished, blogged, spoken, or contributed open source on agent evaluation methodologyFamiliarity with robotics, autonomy, or safety-critical software development

## Description

About ForterraAt Forterra, we are unleashing autonomy at scale to transform the battlefield. Our mission is to build the foundational platforms that enable an intelligent ecosystem to coordinate, adapt, and execute with speed and precision even in the uncertainty and disruption of modern conflict. In an era marked by rapid technological change and evolving threats, we design for flexibility, survivability, and operational dominance.

Forterra delivers weapons, sensors, and battlefield effects through integrated autonomous networks reaching operational areas faster, safer, and without placing human lives at risk. Our systems operate with distributed control, dynamic routing, and real-time responsiveness, enabling sustained advantage across complex mission environments.

About the role

Forterra runs its engineering on agentic systems, not chatbots. Requirements, safety analysis, test generation, code review, and validation are increasingly performed by fleets of agents operating against Forterra's real systems of record.

This role builds and owns that substrate: the agent definitions, skills, MCP servers, guardrails, and evaluation harnesses that determine whether hundreds of engineers get leverage or just burn tokens.

The hard part is not wiring an API. It is judgment, such as knowing which problems should be handed to an agent, which should stay deterministic, when to use a classical data analysis method, and how to prove an agent's output is trustworthy.

You will work across the entire company: systems engineering, safety, software, product, IT, cybersecurity, and executive level leadership. Almost none of it sits inside your reporting line. Influence and growth directly come from performance and earned credibility. You will have direct visibility to chief executive leadership.

What you'll do
Design agentic systems, not promptsAuthor agent definitions and context as engineered artifacts, with explicit role separation, tool allowlists, model selection, and hard behavioral limits.Design multi-agent architectures where roles are adversarial and reliable by construction.Build skills with disciplined triggering, progressive disclosure, and non-overlapping ownership boundaries - so capability scales without the context window collapsing.Orchestrate work across multiple model vendors, harnesses, and agent runtimes.Make and defend the call on whether a problem warrants an agent at all. Know when a deterministic script or webhook is the correct answer, and how to engineer away from an agent left polling in a loop.Make agents part of the engineering infrastructureDesign how agents get invoked across the full range of trigger patterns - a developer working interactively at a terminal, a nightly scheduled run, an event-driven trigger like CI, and long-running unattended
work. Know the failure modes for each, and ship the result as shared, versioned engineering infrastructure rather than one-off scripts.Define the autonomy gradient explicitly: which agents are permitted to act, and which may only propose.Engineer unattended agents for the absence of a human: bounded scope, idempotent reruns, deliberate fail-open versus fail-closed decisions, cost and runtime caps, structured verdicts, and ephemeral scoped credentials that keep them auditable.Design the human-facing side of autonomous work: how an agent escalates when it is genuinely blocked, how and when it asks for a human in the loop, and how a fleet of concurrent agent sessions stays observable to the humans accountable for them.Prove agent output is trustworthyDesign defensible evaluations of AI tooling: controlled A/B trials, ablation studies, blinded LLM judges, contamination and leakage controls, reported uncertainty, and honest null results.Build validation harnesses that
distinguish genuine signal from hollow green. Instrument your own systems against complexity drift: measure whether each added skill, agent, or tool is actually pulling its weight in quality, cost, and turns.Build the guardrailsDesign structural controls for agents operating near controlled information: layered redaction, egress filtering, enforcement at the data layer rather than the prompt layer.Anticipate cross-boundary failure modes unique to agents.Connect agents to the enterpriseBuild and operate the connective tissue between agent tooling and Forterra's infrastructure & processes: requirements management, issue tracking, documentation, source control, diagramming, and unstructured data.Own enterprise identity integration end-to-end, including federated and government-cloud authentication, and specify precisely what changes IT needs to make.Run these as real production services with real uptime expectations, including incident response and root-cause write-ups.Drive
adoptionTurn tribal knowledge into onboarding paths, curricula, setup automation, and self-diagnosing tooling that lets an engineer's own agent fix its broken configuration.Teach transferable technique rather than button-clicking, including curriculum for non-software audiences - systems engineering, safety, program management, design, business operations - and design yourself out of delivery so training scales past you.Maintain the platform other engineers contribute to: review their work, set and hold the standards for acceptable agent patterns, grow the contributor base, and convert user pain into prioritized organizational demand.


## Related Videos

- [Keeping applications secure by evolving OAuth 2.0 and OpenID Connect](https://www.wearedevelopers.com/videos/100152-keeping-applications-secure-by-evolving-oauth-2-0-and-openid-connect)
- [Docker network without Docker](https://www.wearedevelopers.com/videos/1418-docker-network-without-docker)
- [Agentic employees in world's most downloaded FinTech app](https://www.wearedevelopers.com/videos/100123-agentic-employees-in-world-s-most-downloaded-fintech-app)
- [Get started with securing your cloud-native Java microservices applications](https://www.wearedevelopers.com/videos/123-get-started-with-securing-your-cloud-native-java-microservices-applications)
- [Delay the AI Overlords: How OAuth and OpenFGA Can Keep Your AI Agents from Going Rogue](https://www.wearedevelopers.com/videos/1637-delay-the-ai-overlords-how-oauth-and-openfga-can-keep-your-ai-agents-from-going-rogue)
- [Docker exec without Docker](https://www.wearedevelopers.com/videos/1094-docker-exec-without-docker)

## Related Articles

- [How to Become an AI Engineer](https://www.wearedevelopers.com/magazine/331-how-to-become-an-ai-engineer)
- [From Prototype to Production: Build AI Agents with This Free 4-Course Learning Path](https://www.wearedevelopers.com/magazine/655-from-prototype-to-production-build-ai-agents-with-this-free-4-course-learning-path)
- [What is Agentic Programming and Why Should Developers Care?](https://www.wearedevelopers.com/magazine/625-what-is-agentic-programming-and-why-should-developers-care)
- [Dev Digest 137 - AI'm not sure about this](https://www.wearedevelopers.com/magazine/485-dev-digest-137-ai-m-not-sure-about-this)
- [MLOps And AI Driven Development](https://www.wearedevelopers.com/magazine/82-mlops-and-ai-driven-development)
- [Graph and AI Trends 2026: Why Is AI Running but Not Yet Delivering?](https://www.wearedevelopers.com/magazine/680-graph-and-ai-trends-2026-why-is-ai-running-but-not-yet-delivering)