Enterprise AI Administrator

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. Remove boilerplate, EEO, etc. Also remove Job ID etc. Need to preserve all substantive info. Let's parse the posting. First part is fluff about Celsius brands etc. That's not needed? It's part of description but not a section. Should we include as "About the role"? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to create sections based on content. We have: - Intro paragraph about Celsius and the role: "Celsius is seeking an Enterprise AI Administrator to manage the operational, governance, and compliance requirements of our enterprise artificial intelligence ecosystem. This role will oversee the use of platforms such as Microsoft Copilot, OpenAI, and Anthropic Claude, along with the models, agents, plugins, connectors, add-ons, and integrations used across the organization." - Then description: "The Enterprise AI Administrator will serve as a central point of coordination among IT, Information Security, Compliance, Legal, Privacy, Internal Audit, and business stakeholders. This person will monitor platform usage, access, licensing, model availability, costs, risks, and policy compliance while helping the organization adopt AI responsibly and effectively." - Then "The ideal candidate combines hands-on AI platform experience with a practical understanding of governance, risk management, and basic SOX audit principles. This person should follow developments in the AI industry closely and be comfortable translating emerging capabilities and risks into appropriate enterprise controls." That could be "About the role" or "Responsibilities"? Actually responsibilities are listed later. We have a "Requirements" bullet list: - Bachelor's degree in Information Technology, Computer Science, Information Systems, Cybersecurity, Business, Risk Management, or a related field - or equivalent professional experience - 3 to 5 years of experience in enterprise technology administration, SaaS platform administration, AI operations, IT governance, security, compliance, or a related field - Experience administering or governing one or more platforms such as Microsoft Copilot, OpenAI or ChatGPT Enterprise, Anthropic Claude, or comparable technologies - Working knowledge of identity and access management, role-based access controls, licensing, usage monitoring, reporting, and change management - Basic understanding of SOX compliance and audit concepts, including access reviews, segregation of duties, evidence retention, control testing, and issue remediation - Experience documenting processes, controls, risk decisions, approvals, and technical configurations - Ability to evaluate technical capabilities and risks and communicate them clearly to both technical and nontechnical audiences - Sound judgment when handling confidential information and sensitive compliance matter Then "Responsibilities" list: - AI Platform Administration and Monitoring (with subpoints) - AI Governance and Policy (subpoints) - AI Intake and Risk Assessment (subpoints) - Compliance, Controls, and Audit Support (subpoints) - AI Industry and Vendor Management (maybe just heading? Actually after that there is a line "AI Industry and Vendor Management" then benefits.) We need to capture each bullet as

under appropriate

. The subpoints are indented; we can treat each line as a list item. We also have "Benefits" section: list of benefits. - Comprehensive medical, dental, and vision benefits - Long- and short-term disability - Life insurance - 10 vacation days per year (subject to accrual policy) - 11 company-paid holidays - 401(k) with company match - Identity theft and legal services Then "Pay": The base pay range for this position is for a successful candidate within the state listed. The successful candidate's actual pay will be based on multiple factors, such as work location, job-related knowledge, skills, qualifications, and experience. Celsius is a total rewards company. This position may be eligible for other compensation, including bonuses and Restricted Stock Units (subject to company plans). That's vague but still mentions pay range etc. It says "The base pay range for this position is for a successful candidate within the state listed." Not specific numbers. According to instruction: do NOT include Pay section unless posting actually states them. It does state base pay range exists but not actual numbers. It says "The base pay range for this position is for a successful candidate within the state listed." That's still stating there is a base pay range, albeit not giving numbers. Is that considered "real, specific content"? It says not to include heading if content is filler/placeholder like "commensurate with experience", "not specified", "N/A", "varies", "TBD". This is similar to "within the state listed" which is vague but not exactly placeholder. Might be considered not specific enough. Safer to omit Pay section because no concrete numbers. Schedule: Not mentioned. So omit. Qualifications and Skills: The posting has Requirements (which could be considered Qualifications). There's no separate Skills section besides maybe within Requirements. We could treat Requirements as Qualifications. The instruction includes Qualifications as a possible heading. We could output Requirements under

Requirements

. Or we could split into Qualifications and Skills. But we have no explicit Skills list. Better to use Requirements heading. We also need About the role section: we can combine the introductory paragraphs into About the role. Thus sections: About the role, Requirements, Responsibilities, Benefits. Check if any other sections like "Qualifications" separate? Not needed. Now we need to strip boilerplate: EEO, accommodation, etc. Also remove the fluffy brand intro at top? That's not part of role description but could be considered About the role? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." The brand intro is not metadata; it's marketing fluff. Should we keep? It says "Preserve ALL substantive information; do NOT invent or summarize away detail." The brand intro is not substantive to the job; it's marketing. Might be considered boilerplate? Not exactly legal/EEO but still not job-specific. I'd drop it to keep focused. Thus About the role paragraph: start from "Celsius is seeking an Enterprise AI Administrator..." etc. Let's craft HTML. We'll output:

About the role

Celsius is seeking an Enterprise AI Administrator to manage the operational, governance, and compliance requirements of our enterprise artificial intelligence ecosystem. This role will oversee the use of platforms such as Microsoft Copilot, OpenAI, and Anthropic Claude, along with the models, agents, plugins, connectors, add-ons, and integrations used across the organization. The Enterprise AI Administrator will serve as a central point of coordination among IT, Information Security, Compliance, Legal, Privacy, Internal Audit, and business stakeholders. This person will monitor platform usage, access, licensing, model availability, costs, risks, and policy compliance while helping the organization adopt AI responsibly and effectively. The ideal candidate combines hands-on AI platform experience with a practical understanding of governance, risk management, and basic SOX audit principles. This person should follow developments in the AI industry closely and be comfortable translating emerging capabilities and risks into appropriate enterprise controls.

Then Requirements:

Requirements

• Bachelor's degree in Information Technology, Computer Science, Information Systems, Cybersecurity, Business, Risk Management, or a related field - or equivalent professional experience
• 3 to 5 years of experience in enterprise technology administration, SaaS platform administration, AI operations, IT governance, security, compliance, or a related field
• Experience administering or governing one or more platforms such as Microsoft Copilot, OpenAI or ChatGPT Enterprise, Anthropic Claude, or comparable technologies
• Working knowledge of identity and access management, role-based access controls, licensing, usage monitoring, reporting, and change management
• Basic understanding of SOX compliance and audit concepts, including access reviews, segregation of duties, evidence retention, control testing, and issue remediation
• Experience documenting processes, controls, risk decisions, approvals, and technical configurations
• Ability to evaluate technical capabilities and risks and communicate them clearly to both technical and nontechnical audiences
• Sound judgment when handling confidential information and sensitive compliance matter
Responsibilities: We need to capture subpoints. We have headings: AI Platform Administration and Monitoring, AI Governance and Policy, AI Intake and Risk Assessment, Compliance, Controls, and Audit Support, AI Industry and Vendor Management. We can either make each heading as

inside responsibilities? But instruction only says use

for section headings. Could embed headings as or just include as part of list items? Probably better to keep as list items with the heading as part of the item text. But we could also make subheadings using

though not instructed. Safer to keep as list items with the heading bolded via . However instruction didn't forbid other tags. It only said use

for section headings,

• for any list,

  for prose. It didn't forbid other tags like . We'll keep simple: each responsibility as a list item, with the heading as part of the item. Thus:

  Responsibilities

  • AI Platform Administration and Monitoring
    • Administer the organization's approved enterprise AI platforms, including Microsoft Copilot products, OpenAI services, Anthropic Claude, and future AI technologies
    • Manage user access, roles, licenses, configurations, approved models, integrations, and platform settings
    • Monitor usage, adoption, costs, capacity, and activity across enterprise AI platforms
    • Identify unusual usage patterns, unauthorized tools, inactive licenses, excessive consumption, and potential policy violations
    • Maintain dashboards and recurring reports covering adoption, cost, risk, compliance, and operational performance
    • Track model releases, feature changes, service updates, deprecations, and vendor roadmap developments
    • Maintain an accurate inventory of approved AI platforms, models, agents, integrations, plugins, and associated business owners
  • AI Governance and Policy
    • Own the operational administration and periodic review of the company's AI Policy and related standards, procedures, and guidance
    • Partner with Legal, Compliance, Privacy, Information Security, Internal Audit, and business leadership to keep AI governance requirements current
    • Translate policy requirements into practical administrative controls, approval workflows, documentation standards, and monitoring procedures
    • Communicate policy changes and provide guidance to employees, managers, developers, and business teams
    • Monitor adherence to the AI Policy and ensure identified issues are documented and addressed
    • Manage AI policy exceptions, including business justification, risk review, approvals, expiration dates, and compensating controls
  • AI Intake and Risk Assessment
    • Manage the intake process for proposed AI models, agents, plugins, add-ons, connectors, integrations, and new use cases
    • Gather and validate requirements such as business purpose, ownership, data classification, intended users, expected benefits, cost, and technical dependencies
    • Coordinate reviews with Information Security, Legal, Privacy, Compliance, Architecture, Records Management, Procurement, and other stakeholders
    • Assess proposed solutions for risks involving confidential data, personal information, intellectual property, data retention, model outputs, third-party access, human oversight, and regulatory obligations
    • Determine whether proposed capabilities affect financially significant processes or systems subject to SOX controls
  • Compliance, Controls, and Audit Support
    • ... (the text after that heading is cut