AI Security Engineer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, etc. Preserve all substantive info. Include a section only when posting has real specific content. Avoid filler like "commensurate with experience". Pay and Schedule sections only if posting actually states them. The posting includes compensation range and benefits. It also mentions location and travel requirement, but schedule? Not explicit schedule (full-time). It says "This compensation range is based on a full time schedule." So schedule could be full-time. Should we include Schedule section? It says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states compensation range and benefits, and mentions full time schedule. So we can include Pay, Benefits, Schedule sections. However we need to ensure we don't include filler like "not specified". The schedule is full time (implied). We can include a

  stating full-time schedule. We need to extract substantive content: - About Us: description of Trimble. Could be placed under About the role? Actually "About Us" is company description. Could be part of About the role? The instruction: use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have: - "What Makes This Role Great": description of role impact. Could be About the role. - "Key Exciting Responsibilities": list of responsibilities. - "Essential Skills & Experience": list of skills/experience. - "Bonus Points For": additional qualifications. - "Logistics": location, travel requirement. - "Why You'll Love Working With Us": company culture, impact. Could be part of About the role or separate? But we only have allowed headings; we could incorporate into About the role or maybe Skills? Better to put under About the role (company culture). However we also have "About Us" earlier. Could combine. - Compensation and Benefits: separate sections. - Schedule: full-time. We need to avoid boilerplate: EEO, equal opportunity, scam warning, application instructions, privacy notices, etc. Remove "How to Apply", "Application Deadline", EEO statements, etc. We must preserve all substantive information. So we need to keep details like responsibilities list, skills, bonus points, location, travel, compensation range, benefits description, etc. We must not invent or summarize away detail. So we need to keep each bullet. We need to format lists with

  • . For prose, use

    . We must not repeat job title as heading. The job title is "AI Security Engineer". Not to be used as heading. We must not include Job ID/requisition numbers. We must output only HTML fragment. Let's extract content: About Us / What Makes This Role Great / Why You'll Love Working With Us: - 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. - At Trimble, we're not just a company that "does good"—we are a team dedicated to making a tangible, positive Real-World Impact. We build innovative solutions designed to solve the world's most critical challenges. From construction sites to transportation hubs, our work tangibly improves how people live, build, move, and grow. You'll work on projects that truly matter: Our purpose-driven culture means you'll be helping to build and deliver solutions that make work faster, safer, and more sustainable for millions of people worldwide. Our impact is tangible, from connected machines that save fuel to data-driven insights that reduce waste. Collaborate with like-minded people: Our strong internal culture is a "hidden gem." You will work with a collaborative, supportive team that shares your purpose and fosters a genuine sense of belonging. We're a company of "visionary pragmatists" who think boldly and build things that work. Be an owner: Trimble thrives on individuals who take initiative and embrace ownership. You'll find an entrepreneurial spirit where success is often "self-authored," empowering proactive "doers." We can combine these into About the role section (maybe also include company description). We'll produce a few paragraphs. Responsibilities list: - 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. These are bullet points. 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. 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. Logistics: - Location: Westminster, CO, Hybrid - Travel Requirement: 10% We could put location and travel under a section? Not in allowed headings. Could incorporate into About the role or maybe a separate "Logistics" not allowed. Since only allowed headings are those, we might put location/travel in a

    under About the role or maybe under Requirements? But better to include in About the role as additional info. Compensation: - Hiring Range $115,600.00–$158,900.00 - Pay Rate Type Salary - Bonus Eligible? Yes - Commission Eligible? No We need to present Pay section with this info. Should we include "Pay Rate Type Salary", "Bonus Eligible? Yes", "Commission Eligible? No". Use

    • maybe. Benefits: - 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. - If this position is identified above as commission- or bonus-eligible, the terms of the commission plan or discretionary bonus plan for which you are eligible will be provided following the employee start date. We can keep that. Schedule: - This compensation range is based on a full time schedule. Thus schedule: full-time. We need to avoid filler like "not specified". We have actual info. Now produce HTML:

      About the role

      ... paragraphs ...

      Responsibilities

      • ...
      ...

      Requirements

      maybe we combine Essential Skills & Experience and Bonus Points For into Requirements? But we have separate headings: Requirements, Qualifications, Skills. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these headings. We have Essential Skills & Experience (could be Requirements or Skills). Bonus Points For could be Qualifications. We could also have a Skills section for technical proficiencies. Let's decide: - Requirements: mandatory experience (5+ years, proficiency, etc.) - Qualifications: bonus points (additional desirable qualifications) - Skills: maybe list specific technical skills (Python, MLOps, AI frameworks, cloud security, OWASP, NIST). But we already have those in Requirements. Could split. Better to follow typical job posting: Requirements = mandatory, Qualifications = preferred, Skills = maybe technical skills. But we can allocate: Requirements: 5+ years security engineering/app sec, hands-on proficiency with Python, MLOps tooling, AI frameworks (PyTorch, TensorFlow), agent protocols (MCP), practical experience executing AI red-teaming using open-source tools, solid background in cloud security architecture across AWS, Azure, GCP and containerized environment security, strong working knowledge of OWASP Top 10 for LLMs, OWASP agentic threat guidance, NIST AI RMF standards. Qualifications: Bonus points: experience with commercial AI security platforms, shadow AI discovery tools, applied MITRE ATLAS tactics; awareness of international AI governance frameworks (ISO/IEC 42001, EU AI Act); contributions to open-source AI security tools, published research, CVEs, speaking engagements; relevant certifications (OSCP, OSCE, AWS Security Specialty, GIAC cloud security tracks). Skills: maybe we could list the specific technical skills again? But that would duplicate. Could instead put under Skills: Python, MLOps tooling, PyTorch, TensorFlow, MCP, AI red-teaming tools (PyRIT, Garak, Promptfoo), cloud security (AWS, Azure, GCP), container security, OWASP LLM, OWASP agentic, NIST AI RMF. However that duplicates Requirements. But we can keep Requirements as experience, Skills as technical proficiencies. Let's do that. Thus: Requirements: experience bullets (5+ years, etc.) maybe without listing specific tools? But we need to preserve all substantive info. So we need to include the tools etc. Could put them under Skills. Thus: Requirements: 5+ years of security engineering or application security experience with demonstrated technical depth in operational AI attack classes. Skills: 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