AI Security Engineer

We need to output only HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Keep substantive info. We need to parse the posting. Key parts: - Title: Protect Enterprise Innovation as Our Next AI Security Engineer! (not used as heading) - About Us: description of Trimble. - What Makes This Role Great: description of role. - Key Exciting Responsibilities: bullet list. - Essential Skills & Experience: bullet list. - Bonus Points For: bullet list. - Logistics: Location: Westminster, CO, Hybrid Travel Requirement: 10% - Why You'll Love Working With Us: description. - Compensation: details with range. - Benefits: description. - How to Apply etc: remove. We need sections: About the role (maybe "About the role" corresponds to "What Makes This Role Great"? Or "About Us"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. We have: - About the role: could be "What Makes This Role Great" plus maybe "About Us"? But "About Us" is company description, not role. Probably "About the role" should contain description of role and company context. We'll combine "What Makes This Role Great" and maybe "About Us" as role context? But "About Us" is company overview; could be part of "About the role". We'll include both. - Responsibilities: from "Key Exciting Responsibilities". - Requirements: maybe from "Essential Skills & Experience" (these are requirements). Could also include "Bonus Points For" as "Qualifications" or "Skills". We need to decide. We have sections: Requirements, Qualifications, Skills. Could split: Requirements = essential skills & experience; Qualifications = bonus points; Skills = maybe specific technical skills list? But we can combine. We must not create sections with filler. So we need actual content. Pay: we have compensation range. Schedule: we have location and travel requirement; schedule maybe not explicit; but we have "Hybrid" and travel 10%; maybe schedule not given. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. We have Pay (compensation range). Benefits: we have benefits description. Schedule: we have location and travel requirement but not schedule like full-time, part-time, shift. The posting mentions "full time schedule" in compensation description. So we could include Schedule: full-time (maybe mention). But we need to see if posting explicitly states schedule: "This compensation range is based on a full time schedule." That implies full-time. So we can include Schedule section with "Full-time". That's specific enough. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to ensure we don't repeat content unnecessarily. Let's extract content. About the role: combine "What Makes This Role Great" and maybe "About Us"? But "About Us" is company description. Could be part of About the role. We'll include both paragraphs. What Makes This Role Great: "In this high-impact senior individual contributor role, you will serve as the dedicated AI security expert across the enterprise, bridging Agentic AI, Cyber Security, and AI Governance. You will have full ownership to design adversarial attack scenarios, secure agentic systems, and develop secure-by-default reference architectures that directly protect next-generation enterprise technology." About Us (Trimble description): two paragraphs: first about Trimble being industrial technology company transforming way world works, delivering solutions enabling customers to thrive, connecting digital and physical worlds, helping increase productivity, quality, safety, sustainability. Second paragraph: Corporate Trimble is a global technology company connecting physical and digital worlds, transforming ways work gets done, relentless innovation in precise positioning, modeling and data analytics, enabling essential industries including construction, geospatial and transportation, helping customers build/maintain infrastructure, design and construct buildings, optimize global supply chains or map the world, at forefront driving productivity and progress. Also mention website. We'll keep that. Responsibilities: list from "Key Exciting Responsibilities": - Assess and secure AI agents, tool integrations, and agentic workflows while evaluating permission scoping, action-chain risk, and non-human identity frameworks. - Design and execute advanced adversarial attack scenarios including prompt injection, jailbreaking, insecure output handling, and data leakage across retrieval pipelines. - Partner with AI engineers to establish automated security guardrails, vector store access controls, and output filtering policies across model lifecycles. - Audit AI Ops pipelines, vet third-party AI supply chain components, and lead model risk assessments prior to production deployment. - Develop enterprise AI security standards and train cross-functional AppSec, SecOps, and GRC teams on AI-specific attack classes and threat mitigations. Requirements: from "Essential Skills & Experience": - 5+ years of security engineering or application security experience with demonstrated technical depth in operational AI attack classes. - Hands-on proficiency with Python, MLOps tooling, AI frameworks (PyTorch, TensorFlow), and agent protocols (MCP). - Practical experience executing AI red-teaming using open-source tools such as PyRIT, Garak, or Promptfoo. - Solid background in cloud security architecture across AWS, Azure, or GCP and containerized environment security. - Strong working knowledge of OWASP Top 10 for LLMs, OWASP agentic threat guidance, and NIST AI RMF standards. Qualifications: from "Bonus Points For": - Experience with commercial AI security platforms, shadow AI discovery tools, or applied MITRE ATLAS tactics. - Awareness of international AI governance frameworks, including ISO/IEC 42001 and the EU AI Act. - Contributions to open-source AI security tools, published security research, CVEs, or industry conference speaking engagements. - Relevant certifications such as OSCP, OSCE, AWS Security Specialty, or GIAC cloud security tracks. Skills: maybe we can list specific technical skills: Python, MLOps, PyTorch, TensorFlow, MCP, PyRIT, Garak, Promptfoo, AWS, Azure, GCP, container security, OWASP LLM, OWASP agentic, NIST AI RMF. But we already have those in Requirements. Could create Skills section summarizing technical proficiencies. However we must not repeat content unnecessarily; but we can still have Skills with a concise list. The instruction: Prefer a few substantive sections over many thin ones. Might be okay to have Skills as a subset. But we already have Requirements and Qualifications; Skills could be redundant. Maybe we can omit Skills if not needed. But we need to include sections only when posting has real specific content. We have content for Skills (specific technical proficiencies). Could include. But we must not create sections with filler. So we can include Skills with bullet list of specific skills: Python, MLOps tooling, PyTorch, TensorFlow, MCP, PyRIT, Garak, Promptfoo, AWS, Azure, GCP, container security, OWASP Top 10 for LLMs, OWASP agentic threat guidance, NIST AI RMF. Benefits: from "Benefits:" paragraph: "Trimble offers comprehensive core benefits that include Medical, Dental, Vision, Life, Disability, Time off plans and retirement plans. Most of our businesses also offer tax savings plans for health, dependent care and commuter expenses as well as Paid Parental Leave and Employee Stock Purchase Plan." Pay: from compensation: "Hiring Range $115,600.00–$158,900.00 Pay Rate Type Salary Bonus Eligible? Yes Commission Eligible? No". Also note "This compensation range is based on a full time schedule." We'll include Pay with that range and note bonus eligible. Schedule: from "This compensation range is based on a full time schedule." Also location hybrid travel 10% maybe not schedule. We'll put Schedule: Full-time (based on full-time schedule). Could also mention hybrid location? But schedule section is for schedule, not location. We'll just put Full-time. We must not include location in Schedule; location could be part of About the role or maybe we drop. The instruction: do not put Job ID/requisition numbers as headings — fold minor metadata into a short

or drop it. Location is minor metadata; we could fold into a short

under About the role or maybe drop. But we have location info: Westminster, CO, Hybrid Travel Requirement: 10%. Could include as a short paragraph under About the role or maybe under a separate "Logistics" but we don't have heading for that. Since we must not create extra headings unless needed, we could include location in About the role paragraph. Thus About the role will include company description, role description, and location/hybrid/travel. Now produce HTML fragment with

headings and

• for lists,

  for prose. We must not include markdown code fences. Let's craft. Structure:

  About the role

  Trimble is an industrial technology company transforming the way the world works by delivering solutions that enable our customers to thrive. We create technologies that connect the digital and physical worlds, helping our customers increase productivity, quality, safety, and sustainability. From purpose-built products to enterprise-level solutions, our technology empowers professionals in construction, geospatial, government, transportation, and more. Corporate Trimble is a global technology company that connects the physical and digital worlds, transforming the ways work gets done. With relentless innovation in precise positioning, modeling and data analytics, Trimble enables essential industries including construction, geospatial and transportation. Whether it's helping customers build and maintain infrastructure, design and construct buildings, optimize global supply chains or map the world, Trimble is at the forefront, driving productivity and progress. For more information about Trimble (Nasdaq:TRMB), visit: www.trimble.com.

  In this high-impact senior individual contributor role, you will serve as the dedicated AI security expert across the enterprise, bridging Agentic AI, Cyber Security, and AI Governance. You will have full ownership to design adversarial attack scenarios, secure agentic systems, and develop secure-by-default reference architectures that directly protect next-generation enterprise technology.

  Location: Westminster, CO (Hybrid) with approximately 10% travel.

  Responsibilities

  • Assess and secure AI agents, tool integrations, and agentic workflows while evaluating permission scoping, action-chain risk, and non-human identity frameworks.
  • Design and execute advanced adversarial attack scenarios including prompt injection, jailbreaking, insecure output handling, and data leakage across retrieval pipelines.
  • Partner with AI engineers to establish automated security guardrails, vector store access controls, and output filtering policies across model lifecycles.
  • Audit AI Ops pipelines, vet third-party AI supply chain components, and lead model risk assessments prior to production deployment.
  • Develop enterprise AI security standards and train cross-functional AppSec, SecOps, and GRC teams on AI-specific attack classes and threat mitigations.

  Requirements

  • 5+ years of security engineering or application security experience with demonstrated technical depth in operational AI attack classes.
  • Hands-on proficiency with Python, MLOps tooling, AI frameworks (PyTorch, TensorFlow), and agent protocols (MCP).
  • Practical experience executing AI red-teaming using open-source tools such as PyRIT, Garak, or Promptfoo.
  • Solid background in cloud security architecture across AWS, Azure, or GCP and containerized environment security.
  • Strong working knowledge of