Associate Director - Workfront

We need to output HTML fragment with sections: About the role? Actually the posting includes description about Bounteous (company overview) maybe as About the role? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. We need to include sections only when posting has real specific content. So we need to parse. Content: - Intro paragraph about Bounteous (company description). Could be "About the role" or maybe "About the company". The instruction says use headings like About the role, Responsibilities, etc. We can use "About the role" for the description of the role? But we have a description of the company and role. Could treat as "About the role". We'll include that paragraph. - Responsibilities: list of bullet points under "Key Responsibilities". We'll put each as

. - Desired Skills And Experience: list of bullet points. Could be "Skills" or "Requirements". The instruction includes Skills, Requirements, Qualifications. We'll decide: "Skills" for desired skills and experience. Also there is "Information Security Responsibilities" which could be part of Responsibilities or separate? It's a separate bullet list about security responsibilities. Could be included under Responsibilities as additional items, or we could create a separate section like "Information Security". But instruction only lists certain headings; we can add others? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those examples. Safer to stick to those. So we can merge security responsibilities into Responsibilities. - Pay: "$105,000 - $130,000 a year". So we need a Pay section. - Benefits: Not mentioned explicitly. No benefits listed. So we should not create Benefits section. - Schedule: Not mentioned. No schedule. - Qualifications: Could be certifications etc. But we have "Workfront Core Developer certification or equivalent." That's a qualification. Could be under Qualifications. But we also have skills list. We could separate: Requirements (experience, certification) and Skills (communication, etc). However instruction says prefer few substantive sections over many thin ones. So we might combine into Skills and maybe Requirements. Let's think. We have: - 6+ years of experience in Adobe Workfront development and implementation. (experience requirement) - Strong understanding of Workfront design and system integrations using Workfront Fusion, connectors, and APIs. - Workfront Core Developer certification or equivalent. - Proven ability to develop and implement automation for workflow optimization. - Exceptional troubleshooting skills with experience in resolving configuration issues. - Excellent communication and problem-solving skills, with a talent for driving user adoption through effective training and support. - Ability to manage multiple projects simultaneously and prioritize tasks efficiently. - Ability to work in a fast-paced and collaborative environment. These are a mix of experience, certification, skills. Could be under "Requirements" (experience, certification) and "Skills" (soft skills). But to avoid many thin sections, we could have one "Requirements and Skills" section. However instruction says use headings like Requirements, Qualifications, Skills. We could have "Requirements" for experience and certification, and "Skills" for the rest. That's two sections, still okay. But we also have "Information Security Responsibilities" which we can include under Responsibilities. Thus sections: - About the role (company overview + role description) - Responsibilities (list of responsibilities + security responsibilities) - Requirements (experience + certification) - Skills (list of skills) - Pay (salary range) We must not include Benefits or Schedule. We must preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO, scam warning, navigation, cookie, etc. Also must not include "We invite you to stay connected..." etc. Also must not include "Bounteous is proud to be an equal opportunity employer." etc. Also must not include the AI tools note. Also must not include the subscription line. Also must not include the "#BI-Remote" maybe? That's metadata; we can drop. We need to output only HTML fragment, no /, no markdown fences. Let's craft. First, About the role: combine the introductory paragraph(s) about Bounteous and the role description? The posting starts: "Bounteous is a global AI Services firm where agentic engineering and human experience converge to deliver transformative business outcomes for the enterprise. We help organizations design, build, and scale AI-driven products, platforms, and processes. With more than 5,000 team members worldwide, Bounteous delivers AI that sticks, powering adoption and outcomes that move organizations from experimentation to true transformation. Bounteous is backed by New Mountain Capital, a New York-based growth-oriented investment firm that emphasizes business building." Then "Job Title: Associate Director - Workfront Location: USA Mode of Work: Remote Type of Job: Fulltime". We should not repeat job title as heading, but we can include location, mode, type as maybe a short paragraph? The instruction says do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include location, mode, type in a short paragraph after About the role maybe. But we should not repeat the job title as a heading; we can still mention it in prose? Probably okay to include location etc in a paragraph. Thus About the role section:

About the role

then

containing the company description and maybe location etc. But we must not repeat the job title as a heading; we can still mention it in the paragraph if needed. However the instruction says "Do NOT repeat the job title as a heading (the page already shows it)". So we can mention it in paragraph if we want, but better to avoid duplication. We'll just include the company overview and maybe note that it's remote full-time. Let's craft:

Bounteous is a global AI Services firm where agentic engineering and human experience converge to deliver transformative business outcomes for the enterprise. We help organizations design, build, and scale AI-driven products, platforms, and processes. With more than 5,000 team members worldwide, Bounteous delivers AI that sticks, powering adoption and outcomes that move organizations from experimentation to true transformation. Bounteous is backed by New Mountain Capital, a New York‑based growth‑oriented investment firm that emphasizes business building. This role is a full‑time, remote position based in the USA.

That covers location, mode, type. Now Responsibilities: list from "Key Responsibilities" plus the Information Security Responsibilities bullet points. Key Responsibilities bullet points: - Develop and configure Adobe Workfront solutions tailored to client needs, implementing best practices in project management and process automation to enhance operational efficiency. - Configure and customize Workfront, including dashboards, reports, templates, and workflows to optimize client operations. - Complete detailed Workfront architecture and configuration documentation for inclusion in client design documents, largely in collaboration with a business process expert/lead. - Implement automation rules processes within Fusion to streamline key functions, including project management and resource allocation. - Participate in discovery sessions and stakeholder interviews to identify business requirements and process improvement opportunities. - Identify enhancements and new functionalities that can benefit client instances. - Troubleshoot and resolve configuration-related issues, ensuring system performance and reliability. - Regularly update knowledge on Workfront best practices and updates to recommend and implement enhancements. - Provide comprehensive quality assurance for all configurations and implementations. - Work with clients and internal teams to develop and deliver training on Workfront solutions to promote effective usage. - Act as a liaison between technical and business teams, ensuring clear communication and alignment. - Provide ongoing technical support within the scope of the product to ensure client success. Information Security Responsibilities bullet points: - Promote and enforce awareness of key information security practices, including acceptable use of information assets, malware protection, and password security protocols - Identify, assess, and report security risks, focusing on how these risks impact the confidentiality, integrity, and availability of information assets - Understand and evaluate how data is stored, processed, or transmitted, ensuring compliance with data privacy and protection standards (GDPR, CCPA, etc.) - Ensure data protection measures are integrated throughout the information lifecycle to safeguard sensitive information We'll combine them into one

under Responsibilities. Now Requirements: we need to capture experience and certification. - 6+ years of experience in Adobe Workfront development and implementation. - Workfront Core Developer certification or equivalent. Also maybe "Strong understanding of Workfront design and system integrations using Workfront Fusion, connectors, and APIs." Could be considered a requirement as well. But we could put that under Skills. However it's a technical understanding; could be requirement. Let's decide: We'll put experience, certification, and understanding of Workfront design and system integrations as Requirements. The rest as Skills. Thus Requirements list: - 6+ years of experience in Adobe Workfront development and implementation. - Strong understanding of Workfront design and system integrations using Workfront Fusion, connectors, and APIs. - Workfront Core Developer certification or equivalent. Now Skills list: - Proven ability to develop and implement automation for workflow optimization. - Exceptional troubleshooting skills with experience in resolving configuration issues. - Excellent communication and problem-solving skills, with a talent for driving user adoption through effective training and support. - Ability to manage multiple projects simultaneously and prioritize tasks efficiently. - Ability to work in a fast-paced and collaborative environment. Now Pay:

Pay

$105,000 - $130,000 a year

We must not include Benefits or Schedule. Now ensure we preserve all substantive information: Did we miss any? Let's review original: - Intro paragraph about Bounteous (we captured) - Job Title etc (we captured location/mode/type) - Key Responsibilities (we captured) - Information Security Responsibilities (we captured) - Desired Skills And Experience (we split into Requirements and Skills) - Pay (we captured) - The rest: "We invite you to stay connected..." etc (boilerplate, drop) - Equal opportunity employer (drop) - Visa sponsorship (drop) - #BI-Remote (drop) - AI tools note (drop) - Contact for data processing (drop) All substantive info preserved. Now output HTML fragment. We need to use

for section headings. Use

• for any list. Use

  for prose. We'll produce:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Skills

  • ...
  ...

  Pay

  $105,000 - $130,000 a year

  Make sure no extra whitespace issues. Let's craft the About the role paragraph precisely. Paragraph: "Bounteous is a global AI Services firm where agentic engineering and human experience converge to deliver transformative business outcomes for the enterprise. We help organizations design, build, and scale AI-driven products, platforms, and processes. With more than 5,000 team members worldwide, Bounteous delivers AI that sticks, powering adoption and outcomes that move organizations from experimentation to true transformation. Bounteous is backed by New Mountain Capital, a New York‑based growth‑oriented investment firm that emphasizes business building. This role is a full‑time, remote position based in the USA." Make sure to use proper hyphen? Use  ? Not needed. Now Responsibilities list items: need to copy exactly as given, preserving punctuation. Let's list them: 1. Develop and configure Adobe Workfront solutions tailored to client needs,