Skip to content
DAT

Sr AI Engineer (Emerging AI)

Seattle, Washington, United States; Seattle, WAUnited States
Senior
POSTED 12 OCT
Apply Ask
Role
28 days opentrue age
Posted 12 Oct
Pay
$185k–$211kno pay posted
Market p25–p75
$185k–$211k
Seattle · n=24 · 365d to 6 Nov
CompanyDAT →
36open roles
Opened · 30d
+0
Closed · 30d
−0
4d of snapshots · 30d window
Market
1,501open · Senior ML / AI
Opened · 7d
+987% of open
All ml / ai
6,613open
All tracked boards · live 10 Nov · n=1,501
AWS

About DAT

DAT Freight & Analytics is an award-winning employer of choice and a next-generation SaaS technology company that has been at the leading edge of freight and logistics innovation for nearly five decades. Founded in 1978, DAT operates the largest freight marketplace in North America — processing 250 million+ load posts annually and maintaining one of the largest repositories of freight market transaction data in the world. On a defined path to $1 billion in revenue, DAT deploys a suite of software solutions, machine learning models, and intelligent automation tools that help brokers, carriers, and shippers price freight accurately, source capacity, reduce risk, and operate more efficiently. With nearly 700 teammates across offices in Denver, CO; Portland, OR; Seattle, WA; Springfield, MO; Toronto, ON; and Bangalore, India, DAT combines the credibility of a multi-decade market leader with the drive of a company that is not done disrupting the industry it helped build. For more information, visit www.DAT.com

Job Application Deadline: 11/30/2026

The Opportunity

As a Sr AI Engineer, you're an integral part of the team who will build and own the platform that power our agentic solutions at DAT. Freight is an uncertain business, and the models we ship reduce that uncertainty: rate forecasts, load-to-truck matching, document extraction, fraud signals, and the agentic workflows our brokers and carriers use to move freight faster. None of that reaches a customer without a platform that makes training, serving, evaluating, and monitoring models routine instead of heroic.

You'll help build the platform, from the model gateway and inference layer through feature and vector storage, evaluation harnesses, production observability, agentic framework (A2A) all on a spine based on secure access and utilization. This is a highly visible role for an engineer who wants their work multiplied across every AI team in the company.

What You'll Do

  • Build and Ship: Write production code for the agentic services and platform components that power DAT's agentic mesh. This powers the systems our product and engineering counterparts build from.
  • Deliver Against Specification: Build an approved specification which includes the problem, the non-goals, the non-functional budget, the trust boundary it crosses and deliver working software against it. Flag drift between what was asked for and what you were given before you write the first line, not after.
  • Own Your Tests: Write the test suite for what you build including unit, integration, and evals from the specification itself, not from your own implementation, so a green suite means the requirement is met, not that the code agrees with itself. Your tests and observability are what raise, or cap, the repository's autonomy ceiling.
  • Build Agentic Systems: Build and operate agents, tools, and multi-agent workflows on DAT's agent mesh which includes tool-calling, retrieval, memory, and orchestration that run inside the entitlements resolved for the request and never reach past them.
  • AI Infrastructure on AWS: Build and operate production AI infrastructure on AWS — Bedrock,Agent Runtime Core, Strands, Lambda, S3, etc
  • Design: You don't own the architecture, but you do own designs built from the premise. Bring informed pushback to decisions made by the team, flag what won't hold up in production, and show up to the conversation with an opinion, not just an implementation.
  • Author Designs: Write the high-level design (HLD) for what you build. The design, the tradeoffs you made, and why so the next engineer, and the next team, can pick it up without you in the room.
  • Review for Fidelity: Review AI-generated and human-written changes for the systems you own, holding the line on fidelity to the spec rather than on formatting, which is already settled by code.
  • Respond to Incidents: Carry on-call for the services you build, investigate and resolve incidents in your own systems, and turn root cause into a fix rather than a postmortem slide.
Source · DATFirst seen 7 NovOriginal ↗