Sr. Cybersecurity AI Engineer – Multiple Offices (Hybrid)

We need to output only HTML fragment, using

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. We need to preserve all substantive info. Let's parse posting: - Intro paragraph: "The AI Senior Security Engineer is responsible for establishing and operating the firm's AI security capability, combining hands-on technical assurance with governance, advisory, and enablement responsibilities. The role will help the business adopt AI safely while protecting sensitive information, reducing regulatory exposure, and maturing AI controls. This is a hybrid position and can be resident in Phoenix, AZ; Atlanta, GA; Minneapolis, MN; Seattle, WA; Charlotte, NC; Miami or Orlando, FL; or Dallas, TX, with an onsite expectation of once per month. Pursuant to Washington and Minneapolis regulations, the salary range is $162,700 to $179,000 annually and includes eligibility for performance-based bonuses. Factors which may affect starting pay within this range may include geography/market, skills, education, experience and other qualifications of the successful candidate. We offer generous compensation and benefits packages. For more information visit: https://www.littler.com/benefits/state-details." We need sections: About the role (maybe intro). Responsibilities (list). Requirements/Qualifications (maybe combine). Benefits (list). Pay (salary range). Schedule (hybrid, onsite once per month). Also maybe location? Not required heading. We must not create sections with filler. So we need to include sections that have content. We have: - About the role: we can put the intro paragraph (maybe trimmed) as

. - Responsibilities: list bullet points under headings: AI/ML security engineering and assurance, AI security governance and controls, AI governance, risk, and compliance, Innovation and enablement, Leadership and collaboration. Each with sub-bullets. We need to use

• for any list of duties/requirements/benefits. So we can have nested lists? Probably just top-level
  with
  • each duty. Could also have sublists but not required. We'll keep simple. - Requirements/Qualifications: The posting has "Qualifications" section with EDUCATION AND CERTIFICATIONS, Experience Required, Preferred Experience. Also "About Littler" is company description, not required for role. We might include "About Littler" as maybe not needed; but it's substantive but not about role. The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we should include company description? It's not a section heading we have; we could put under "About Littler" but we don't have a heading for that. The allowed headings are limited to those list; we cannot add other headings. So we need to fit company description somewhere maybe under "About the role"? But that's not appropriate. However we could include it as a

    after the responsibilities maybe under a generic heading? But we must only use those headings. Could we omit company description? The instruction says preserve ALL substantive information. So we need to include it somewhere. Perhaps we can include it under "About the role" as a paragraph describing the firm. But that might be mixing. However we could add a section "About Littler" but not allowed headings. The instruction: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples, not exclusive? It says "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. But we could still add other headings if needed? The instruction: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It might be okay to use other headings but they gave examples. Safer to stick to those. We need to include company description somewhere. Could put it under "About the role" as a paragraph after the role description. That would be okay: About the role includes both role and firm description. Might be acceptable. Alternatively we could add a section "About Littler" as

    About Littler

    but not in examples; risk. Better to follow examples: include About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. Skills maybe not present; we can omit if no specific skills list separate from qualifications. We have qualifications: education, certifications, experience required, preferred experience. We'll put under Requirements and Qualifications maybe combined? The instruction: we can have both Requirements and Qualifications sections if they have content. We have both. Thus:

    About the role

    ... intro + company description? We'll include intro paragraph and then maybe a short paragraph about Littler. But we need to preserve all substantive info: location, hybrid, onsite once per month, salary range, bonuses, factors affecting pay, benefits link, etc. We'll put location/hybrid/schedule under Schedule section. Pay section: salary range and bonus. Benefits section: list benefits. Responsibilities: list. Requirements: education and certifications. Qualifications: experience required and preferred experience. We must not repeat job title as heading. We must not include boilerplate like cookie/navigation/legal/EEO etc. Remove lines like "No recruiters – principals only." etc. Also remove "For more information visit: https://www.littler.com/benefits/state-details." maybe we keep as link? It's part of benefits? It's a link for benefits details; we can keep in Benefits section as a link. Also remove "For moreinformation about our firm visit: www.littler.com." etc. Remove "No recruiters –principals only." etc. Remove "Please note applications are only accepted through our careers page..." etc. Remove "This job posting is a general description..." etc. Remove "#BeYOUatLittler". Now craft HTML. We'll need to escape ampersand? Not needed. Let's write:

    About the role

    The AI Senior Security Engineer is responsible for establishing and operating the firm's AI security capability, combining hands-on technical assurance with governance, advisory, and enablement responsibilities. The role will help the business adopt AI safely while protecting sensitive information, reducing regulatory exposure, and maturing AI controls.

    Littler is the largest global employment and labor law practice in the world exclusively devoted to representing management. With more than 1,900 attorneys in over 100 offices worldwide, Littler serves as the single source solution provider to the global employer community. Consistently recognized in the industry as a leading and innovative law practice, Littler has been litigating, mediating and negotiating some of the most influential employment law cases and labor contracts on record for over 75 years. Littler’s unparalleled commitment to labor and employment law helps clients navigate a complex business world with nuanced legal issues—building better solutions for clients ’toughest challenges. With deep experience and resources that are local, everywhere, Littler is fully focused on its clients. With a diverse team of the brightest minds, Littler fosters a culture that celebrates original thinking. And with powerful proprietary technology, Littler disrupts the status quo—delivering bold, groundbreaking innovation that prepares employers not just for what’s happening today, but for what’s likely to happen tomorrow.

    Responsibilities

    • AI/ML security engineering and assurance
      • Maintain an inventory and threat model for AI systems, models, agents, and integrations.
      • Assess AI systems for prompt injection, model extraction, insecure outputs, excessive agency, and supply-chain risk.
      • Implement guardrails for AI access, integration, monitoring, logging, and output handling.
      • Embed secure MLOps / LLMOps practices across the AI lifecycle.
    • AI security governance and controls
      • Protect sensitive information used in prompts, embeddings, retrieval sources, logs, and third-party models.
      • Tune DLP, monitoring, and posture controls for AI channels.
      • Define standards for AI access, content handling, retention, logging, and acceptable use.
    • AI governance, risk, and compliance
      • Establish an AI governance model aligned to NIST AI RMF, ISO/IEC 42001, and applicable regulation.
      • Run AI risk reviews that balance business speed with control.
      • Produce AI control evidence for audit, compliance, and leadership reporting.
    • Innovation and enablement
      • Evaluate emerging AI security capabilities and recommend practical adoption.
      • Advise leadership on the AI security roadmap.
      • Create guidance and patterns that make safe AI use easier for business and engineering teams.
    • Leadership and collaboration
      • Serve as the firm's AI security subject-matter expert.
      • Partner with Legal, Privacy, Risk, Engineering, and business stakeholders.
      • Support response to AI-related incidents and control failures.

    Requirements

    • Bachelor’s degree or equivalent relevant experience
    • Core security certifications: CISSP, CISM, or CCSP.
    • AI/governance: ISO/IEC 42001 lead implementer/auditor or a recognized AI security / AI governance certification.
    • Cloud security certifications relevant to the firm's primary provider(s).

    Qualifications

    • Minimum 8+ years in cybersecurity, including minimum 3+ years focused on AI/ML security.
    • Hands-on experience securing AI/ML systems, including LLM, RAG, or agentic workflows.
    • Working knowledge of AI-specific threats and defenses.
    • Experience with AI platform security, lifecycle controls, cloud AI/ML services, and monitoring.
    • Ability to operate as a balanced hybrid: credible building controls and credible advising leadership.
    • Preferred: Software or ML engineering background and comfort reading/writing code (e.g., Python).
    • Preferred: Experience with AI red-teaming and adversarial testing.
    • Preferred: Familiarity with privacy-enhancing technologies and AI governance platforms.

    Benefits

    • Comprehensive health, dental and vision plan for employee, spouse/domestic partner and children.
    • Superior 401(k) plan.
    • Ample time off programs.
    • Mental health programs.
    • Family building and caregiving support.
    • Generous paid parental leave.
    • Life insurance.
    • Disability insurance.
    • Wellness program.
    • Flexible spending accounts.
    • Employee referral bonus program.
    • For more information visit: www.littler.com/benefits/state-details

    Pay

    Pursuant to Washington and Minneapolis regulations, the salary range is $162,700 to $179,000 annually and includes eligibility for performance-based bonuses. Factors which may affect starting pay within this range may include geography/market,