Staff PlatformOps Engineer (Emerging AI)
DAT Freight & Analytics · Seattle, WA · 1 mo ago
HybridFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes "About DAT" (company description) then "The Opportunity", "What You'll Do", "The Skills And Experience You'll Bring", "We'd be Extra Excited if You Have", "Why DAT?" plus salary range for Washington-based candidates.
We must not repeat job title as heading. Use for section headings. Use
for section headings. Use - for any list of duties/requirements/benefits, and
for prose. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Job Application Deadline: 10/31/2026"? That's metadata; we can fold minor metadata into a short
or drop it. Probably we can include a short paragraph with deadline? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include a short
for deadline.
We must include sections only when posting has real specific content. So we need sections: About the role? Actually "About DAT" is company overview, not role. Could be "About the role"? Not present. Could use "About DAT" as a section? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not strict list; we can use appropriate headings like "About DAT", "The Opportunity", "What You'll Do", "Skills and Experience", "Preferred Qualifications", "Why DAT?", "Pay". We need to include Pay section only if posting actually states them. It does: salary range for Washington-based candidates: $198,000 - $246,000 + target bonus. So we can include a Pay section.
Benefits: The posting lists many benefits under "Why DAT?" includes medical, dental, vision, etc. So we can create a Benefits section with list.
Schedule: Not mentioned; we should not create Schedule section.
We must not include filler like "commensurate with experience". Not present.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from sections.
We need to format lists appropriately.
Let's extract content:
Company description (About DAT): Paragraph about DAT, award-winning employer, SaaS, founded 1978, largest freight marketplace, 250M+ load posts, repo of data, path to $1B revenue, suite of software solutions, ML models, intelligent automation, helps brokers etc. Offices locations, nearly 700 teammates, etc. Also "For more information, visit www.DAT.com". That's a link; we can keep as plain text? Probably keep as is.
Job Application Deadline: 10/31/2026 - we can put in a short p.
The Opportunity: paragraph describing role.
What You'll Do: list of bullet points (each starts with bold heading like "Platform Ownership:", etc). We need to convert each bullet into
- with the content. The bullet headings are bold; we can keep them as strong or just text.
The Skills And Experience You'll Bring: list of numbered items (1., 2., etc). We'll convert to
- .
We'd be Extra Excited if You Have: list of bullet points (starting with "Experience with model fine-tuning..." etc). Convert to
- .
Why DAT?: paragraph describing award-winning employer, hybrid work environment, values, etc. Then list of benefits: Medical, Dental, Vision, Life, and AD&D insurance, Parental Leave, Flexible Vacation Time (FVT), additional 10 holidays, 401k matching, Employee Stock Purchase Plan, Short- and Long-term disability sick leave, Flexible Spending Accounts, Health Savings Accounts, Employee Assistance Program, Additional programs - Employee Referral, Internal Recognition, and Wellness, Free TriMet transit pass (Beaverton Office), Competitive salary and benefits package, Work on impactful projects..., Collaborative and supportive team culture, Opportunity to make a real difference..., Employee Resource Groups.
We need to extract benefits list. Also note that "Competitive salary and benefits package" is a bit generic; but we can include.
Pay section: salary range for Washington-based candidates: $198,000.00 - $246,000.00 + target bonus. Also note that DAT considers factors etc. We can include that as prose.
We must not include EEO boilerplate etc. So remove the long EEO paragraph at end.
Also remove duplicated lines? Not seeing duplicates.
Now construct HTML.
We'll start with a
for deadline maybe.
Then
About DAT
... company description ...
Then The Opportunity
...
Then What You'll Do
with each bullet.
Then Skills and Experience
with each bullet.
Then Preferred Qualifications
(or "We'd be Extra Excited if You Have") .
Then Why DAT?
... intro paragraph about award-winning employer, hybrid work environment, values...
then maybe Benefits
list.
Then Pay
... salary range ...
We must not repeat job title as heading.
Check that we didn't include any boilerplate.
Let's craft.
Need to ensure we preserve all substantive information: include all details from each bullet.
Let's list bullets for What You'll Do:
- Platform Ownership: Design, build, and operate the shared services that engineers and business users use to ship models: a model gateway for LLM access, inference endpoints for real-time and batch scoring, feature storage, vector search, and a common SDK.
- Technical Leadership: Lead architecture for large-scale AI systems, write the design documents, and drive alignment across Product, and Engineering and Business users on how models get built and shipped at DAT.
- Cloud Architecture: Architect and run scalable, reliable AI infrastructure on AWS, including Bedrock, SageMaker, EKS, Redpanda, MSK (Kafka), Lambda, and S3, all defined in Pulumi.
- Evaluation and Quality: Build the offline and online evaluation systems that tell us whether a model or prompt change is an improvement, including regression suites, LLM-as-judge pipelines, A/B and shadow testing, and drift detection.
- Cost and Performance: Own inference cost and latency as first-class metrics. Right-size GPU and serverless capacity, tune batching, caching, and quantization, and give teams clear visibility into what their workloads cost.
- Safety and Governance: Implement guardrails, prompt and output logging, PII handling, access controls, and model and dataset lineage so AI systems meet our security and customer data commitments.
- Best Practices: Drive the adoption of modern software development practices across AI work, including automated testing, code reviews, CI/CD pipelines, and infrastructure-as-code.
- Mentorship: Mentor engineers and data scientists on production ML and distributed systems, and raise the operational bar of every team that builds on the platform.
- Incident Management: Lead the response and resolution for complex production incidents involving AI services, perform root cause analysis, and implement preventative measures.
Now Skills And Experience You'll Bring (list):
1. 10+ years of experience in software engineering, including significant time as a senior or staff engineer owning production infrastructure that other engineering teams depend on.
2. 4+ years building and operating machine learning or AI platforms, with models you've taken from notebook to production traffic and then kept healthy.
3. Strong development language skills ideally using TypeScript/Node.js, Java, or Go, with the software engineering discipline to build libraries other teams adopt willingly.
4. Extensive AWS experience with production systems, ideally including EKS/Kubernetes, Lambda, Redpanda, MSK/Kafka, S3, and Secrets Manager, plus infrastructure-as-code with Pulumi, Terraform or similar.
5. Hands-on experience serving models at scale: containerized inference, GPU scheduling, autoscaling, batching, and the tradeoffs between real-time, streaming, and batch scoring.
6. Practical experience with LLM systems in production, including retrieval-augmented generation, vector databases, prompt and context management, tool-calling or agent frameworks, and managed model APIs such as Amazon Bedrock.
7. Proven experience building evaluation and monitoring for models, not just services: offline eval sets, online metrics, drift and data quality checks, and a clear definition of what "regression" means for a model.
8. Strong background in event-driven and distributed systems using Redpanda, AWS MSK or Kafka.
9. Fluency with observability and on-call health, designing dashboards, APM traces, logs, and alerts, defining SLOs, and using these tools to drive down incident frequency and MTTR.
10. Experience establishing and raising engineering standards for a team: PR and testing guidelines, deployment validation checklists, model release criteria, and post-incident review practices.
11. Demonstrated technical leadership: leading cross-team designs in ambiguous problem spaces, writing clear system design documents and operations runbooks, and driving alignment across Engineering, Product, and Operations.
12. Proven mentoring track record, especially helping engineers and data scientists grow in system design, observability, and operational excellence.
13. Excellent communication skills, with the ability to explain trade-offs and system behavior clearly to engineers, product managers, and non-technical stakeholders.
Now Preferred Qualifications (We'd be Extra Excited if You Have):
- Experience with model fine-tuning, distillation, or parameter-efficient training, and a clear point of view on when it beats prompting.
- Background in marketplace, pricing, forecasting, or document extraction problems.
- Freight, logistics, or supply chain domain experience.
Now Why DAT? paragraph: "DAT is an award winning employer of choice. For starters, we have a hybrid work environment, but we also know what makes a great workplace. We have a time-tested and resolute set of operating values predicated on integrity, mutual respect, open communication, and executing with excellence. These values inform our strategic vision as much as any one of our products does. We’ve been an employer of choice in the Portland metropolitan area for four decades, and within one year of opening our Denver office, DAT was #26 on Built In Colorado’s 100 Best Places to Work In Colorado."
Then benefits list: Let's extract each benefit item:
- Medical, Dental, Vision, Life, and AD&D insurance
- Parental Leave
- Flexible Vacation Time (FVT)
- An additional 10 holidays of paid time off per calendar year
- 401k matching (immediately vested)
- Employee Stock Purchase Plan
- Short- and Long-term disability sick leave
- Flexible Spending Accounts
- Health Savings Accounts
- Employee Assistance Program
- Additional programs - Employee Referral, Internal Recognition, and Wellness
- Free TriMet transit pass (Beaverton Office)
- Competitive salary and benefits package
- Work on impactful projects in a cutting-edge environment
- Collaborative and supportive team culture
- Opportunity to make a real difference in the trucking industry
- Employee Resource Groups
We should keep them as list items.
Now Pay section: "For Washington-based candidates, in compliance with the Washington State Pay Transparency Law, the salary range for this role is $198,000.00 - $246,000.00 + target bonus. DAT considers factors such as scope and responsibilities of the position, candidate's work experience, education and training, core skills, internal equity, and market and business elements when extending an offer."
We can include that as prose.
Now we need to ensure we didn't include any boilerplate like EEO etc. Remove that.
Now produce HTML.
We'll start with a
for prose. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Job Application Deadline: 10/31/2026"? That's metadata; we can fold minor metadata into a short
or drop it. Probably we can include a short paragraph with deadline? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include a short
for deadline. We must include sections only when posting has real specific content. So we need sections: About the role? Actually "About DAT" is company overview, not role. Could be "About the role"? Not present. Could use "About DAT" as a section? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not strict list; we can use appropriate headings like "About DAT", "The Opportunity", "What You'll Do", "Skills and Experience", "Preferred Qualifications", "Why DAT?", "Pay". We need to include Pay section only if posting actually states them. It does: salary range for Washington-based candidates: $198,000 - $246,000 + target bonus. So we can include a Pay section. Benefits: The posting lists many benefits under "Why DAT?" includes medical, dental, vision, etc. So we can create a Benefits section with list. Schedule: Not mentioned; we should not create Schedule section. We must not include filler like "commensurate with experience". Not present. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from sections. We need to format lists appropriately. Let's extract content: Company description (About DAT): Paragraph about DAT, award-winning employer, SaaS, founded 1978, largest freight marketplace, 250M+ load posts, repo of data, path to $1B revenue, suite of software solutions, ML models, intelligent automation, helps brokers etc. Offices locations, nearly 700 teammates, etc. Also "For more information, visit www.DAT.com". That's a link; we can keep as plain text? Probably keep as is. Job Application Deadline: 10/31/2026 - we can put in a short p. The Opportunity: paragraph describing role. What You'll Do: list of bullet points (each starts with bold heading like "Platform Ownership:", etc). We need to convert each bullet into
for deadline maybe. Then
About DAT
... company description ...
ThenThe Opportunity
...
ThenWhat You'll Do
- with each bullet.
Then
Skills and Experience
- with each bullet.
Then
Preferred Qualifications
(or "We'd be Extra Excited if You Have")- .
Then
Why DAT?
... intro paragraph about award-winning employer, hybrid work environment, values...
then maybeBenefits
- list.
Then
Pay
... salary range ...
We must not repeat job title as heading. Check that we didn't include any boilerplate. Let's craft. Need to ensure we preserve all substantive information: include all details from each bullet. Let's list bullets for What You'll Do: - Platform Ownership: Design, build, and operate the shared services that engineers and business users use to ship models: a model gateway for LLM access, inference endpoints for real-time and batch scoring, feature storage, vector search, and a common SDK. - Technical Leadership: Lead architecture for large-scale AI systems, write the design documents, and drive alignment across Product, and Engineering and Business users on how models get built and shipped at DAT. - Cloud Architecture: Architect and run scalable, reliable AI infrastructure on AWS, including Bedrock, SageMaker, EKS, Redpanda, MSK (Kafka), Lambda, and S3, all defined in Pulumi. - Evaluation and Quality: Build the offline and online evaluation systems that tell us whether a model or prompt change is an improvement, including regression suites, LLM-as-judge pipelines, A/B and shadow testing, and drift detection. - Cost and Performance: Own inference cost and latency as first-class metrics. Right-size GPU and serverless capacity, tune batching, caching, and quantization, and give teams clear visibility into what their workloads cost. - Safety and Governance: Implement guardrails, prompt and output logging, PII handling, access controls, and model and dataset lineage so AI systems meet our security and customer data commitments. - Best Practices: Drive the adoption of modern software development practices across AI work, including automated testing, code reviews, CI/CD pipelines, and infrastructure-as-code. - Mentorship: Mentor engineers and data scientists on production ML and distributed systems, and raise the operational bar of every team that builds on the platform. - Incident Management: Lead the response and resolution for complex production incidents involving AI services, perform root cause analysis, and implement preventative measures. Now Skills And Experience You'll Bring (list): 1. 10+ years of experience in software engineering, including significant time as a senior or staff engineer owning production infrastructure that other engineering teams depend on. 2. 4+ years building and operating machine learning or AI platforms, with models you've taken from notebook to production traffic and then kept healthy. 3. Strong development language skills ideally using TypeScript/Node.js, Java, or Go, with the software engineering discipline to build libraries other teams adopt willingly. 4. Extensive AWS experience with production systems, ideally including EKS/Kubernetes, Lambda, Redpanda, MSK/Kafka, S3, and Secrets Manager, plus infrastructure-as-code with Pulumi, Terraform or similar. 5. Hands-on experience serving models at scale: containerized inference, GPU scheduling, autoscaling, batching, and the tradeoffs between real-time, streaming, and batch scoring. 6. Practical experience with LLM systems in production, including retrieval-augmented generation, vector databases, prompt and context management, tool-calling or agent frameworks, and managed model APIs such as Amazon Bedrock. 7. Proven experience building evaluation and monitoring for models, not just services: offline eval sets, online metrics, drift and data quality checks, and a clear definition of what "regression" means for a model. 8. Strong background in event-driven and distributed systems using Redpanda, AWS MSK or Kafka. 9. Fluency with observability and on-call health, designing dashboards, APM traces, logs, and alerts, defining SLOs, and using these tools to drive down incident frequency and MTTR. 10. Experience establishing and raising engineering standards for a team: PR and testing guidelines, deployment validation checklists, model release criteria, and post-incident review practices. 11. Demonstrated technical leadership: leading cross-team designs in ambiguous problem spaces, writing clear system design documents and operations runbooks, and driving alignment across Engineering, Product, and Operations. 12. Proven mentoring track record, especially helping engineers and data scientists grow in system design, observability, and operational excellence. 13. Excellent communication skills, with the ability to explain trade-offs and system behavior clearly to engineers, product managers, and non-technical stakeholders. Now Preferred Qualifications (We'd be Extra Excited if You Have): - Experience with model fine-tuning, distillation, or parameter-efficient training, and a clear point of view on when it beats prompting. - Background in marketplace, pricing, forecasting, or document extraction problems. - Freight, logistics, or supply chain domain experience. Now Why DAT? paragraph: "DAT is an award winning employer of choice. For starters, we have a hybrid work environment, but we also know what makes a great workplace. We have a time-tested and resolute set of operating values predicated on integrity, mutual respect, open communication, and executing with excellence. These values inform our strategic vision as much as any one of our products does. We’ve been an employer of choice in the Portland metropolitan area for four decades, and within one year of opening our Denver office, DAT was #26 on Built In Colorado’s 100 Best Places to Work In Colorado." Then benefits list: Let's extract each benefit item: - Medical, Dental, Vision, Life, and AD&D insurance - Parental Leave - Flexible Vacation Time (FVT) - An additional 10 holidays of paid time off per calendar year - 401k matching (immediately vested) - Employee Stock Purchase Plan - Short- and Long-term disability sick leave - Flexible Spending Accounts - Health Savings Accounts - Employee Assistance Program - Additional programs - Employee Referral, Internal Recognition, and Wellness - Free TriMet transit pass (Beaverton Office) - Competitive salary and benefits package - Work on impactful projects in a cutting-edge environment - Collaborative and supportive team culture - Opportunity to make a real difference in the trucking industry - Employee Resource Groups We should keep them as list items. Now Pay section: "For Washington-based candidates, in compliance with the Washington State Pay Transparency Law, the salary range for this role is $198,000.00 - $246,000.00 + target bonus. DAT considers factors such as scope and responsibilities of the position, candidate's work experience, education and training, core skills, internal equity, and market and business elements when extending an offer." We can include that as prose. Now we need to ensure we didn't include any boilerplate like EEO etc. Remove that. Now produce HTML. We'll start with a