Adobe Workfront Content Supply Chain Architect

We need to output only HTML fragment, no markdown fences. Must include sections only when posting has real specific content. Must use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections are present. The posting includes: - Intro about Accenture (company description) maybe "About the role"? Actually "We Are Accenture..." is company description. Could be "About the role"? The role description: "You Are A strategic and technically deep Adobe Workfront Content Supply Chain Architect..." That's role overview. So we could put that under

About the role

with paragraphs. - Responsibilities: The bullet list under "Work Platform Architecture & Design", "Workflow & Automation", "Stakeholder & Delivery Leadership", "Governance & Optimization". Those are responsibilities. So we can have

Responsibilities

with

• items. - Requirements: The "What You Need" bullet list of minimum experience etc. Those are requirements. So

  Requirements

  with list. - Qualifications: maybe "Bonus Points If You have ..." could be Qualifications or Skills. The instructions: Use headings for Qualifications, Skills, Benefits, Pay, Schedule. We have "Bonus Points If You have ..." which are preferred qualifications/skills. Could treat as Skills. Or Qualifications. We'll decide: The "Minimum of ..." are requirements. The "Bonus Points If You have ..." are preferred qualifications (skills). So we could have

  Skills

  for those bonus points. - Benefits: The posting mentions "Accenture offers a market competitive suite of benefits including medical, dental, vision, life, and long-term disability coverage, a 401(k) plan, bonus opportunities, paid holidays, and paid time off. See more information on our benefits here: U.S. Employee Benefits | Accenture". So we have benefits content. So

  Benefits

  with paragraph. - Pay: There's a table of salary ranges per location. That's pay info. So we need a Pay section. Must not include placeholder like "varies". The posting gives specific ranges per location. So we can include Pay section with maybe a
  listing each location and range. Or a

  describing. We'll output a

  • for each location. - Schedule: Not mentioned except "Travel may be required for this role. The amount of travel will vary from 0 to 100% depending on business need and client requirements". That's not schedule but travel. No schedule info like full-time, part-time, shift. So we should NOT create Schedule section because no specific schedule content. - Also there is "We anticipate this job posting will be posted until 11/06/2026." That's metadata; we can drop or put in short p. Probably drop as minor metadata. - Also "Compensation at Accenture varies depending on a wide array of factors..." That's generic; we already have Pay section with specific ranges; we could include a brief sentence about compensation varies but we have actual ranges; we can keep that as part of Pay section. - Also "Travel may be required..." could be part of Responsibilities or a separate note; but we can include under Responsibilities as a bullet maybe. But we already have responsibilities categories; we could add a bullet under Responsibilities about travel. However the instruction: "Prefer a few substantive sections over many thin ones." We'll keep responsibilities as is; we could add a note in responsibilities. - Also "Requesting an Accommodation" and EEO statements are boilerplate to remove. - Also "Role Location Annual Salary Range" heading then list of locations and ranges. That's pay. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay. We must not repeat job title as heading. The job title is "Adobe Workfront Content Supply Chain Architect". Not to be used as heading. We must output only HTML fragment, no /. Use

    for headings,

    for prose,

    • for lists. We need to preserve all substantive information; do not invent or summarize away detail. Must keep details like specific years of experience, specific tools, etc. Let's craft. About the role: combine the introductory sentences: "We Are Accenture is a global professional services company..." plus "You Are A strategic and technically deep Adobe Workfront Content Supply Chain Architect to design and optimize the end-to-end content lifecycle for our clients. This role sits at the intersection of marketing operations, creative production, and technology — owning the architectural vision for how content is planned, created, reviewed, approved, and activated at scale using Adobe's Content Supply Chain solution stack." We'll put that in

      maybe two paragraphs. Responsibilities: We'll list each major responsibility area as

    • with sub-bullets? The instruction: Use
      • for any list of duties/requirements/benefits. It didn't forbid nested lists, but we can keep simple: each responsibility area as a
      • with its description (maybe include internal semicolons). Could also break down each bullet inside as separate
      • but that may be too many. We'll keep each area as a
      • with the description. We need to include all details: For Work Platform Architecture & Design: list of tasks: "Architect the full content supply chain across Adobe Workfront, Adobe Experience Manager (AEM), Adobe GenStudio, Adobe Creative Cloud, and other leading marketing technology tools to ensure seamless handoffs at every stage of the content lifecycle", "Design Workfront object models, intake workflows, and routing logic that reflect real-world creative and marketing production processes", "Define the integration architecture connecting work management (Workfront) with downstream marketing technologies, including content production (Creative Cloud), asset management (AEM Assets), and activation platforms such as AEM Sites, Adobe Journey Optimizer, and similar tools", "Establish a scalable taxonomy, metadata framework, and asset governance model spanning the full Adobe ecosystem". We'll include those as separate sentences inside the
      • . Workflow & Automation: tasks: "Build and optimize end-to-end content workflows using Workfront Fusion, covering campaign intake, creative briefs, review cycles, approval gates, and content publishing", "Automate asset handoff and rendition generation between Workfront and AEM, reducing manual effort and accelerating time-to-market", "Design AI-assisted content workflows leveraging Adobe Firefly, GenStudio, and Adobe’s AI capabilities to support content velocity at scale". Stakeholder & Delivery Leadership: tasks: "Partner with marketing, brand, creative, legal, and technology teams to map current-state content operations and design future-state solutions", "Translate complex, cross-functional requirements into documented solution designs, integration maps, and phased delivery roadmaps", "Lead platform workshops, design sessions, and executive presentations to align stakeholders on architecture decisions", "Drive change management and enablement to ensure adoption across creative, marketing, and ops teams". Governance & Optimization: tasks: "Define and enforce configuration standards, naming conventions, and access control models across all connected platforms", "Conduct regular audits of content supply chain performance — identifying bottlenecks, rework loops, and opportunities for automation", "Establish KPIs and reporting frameworks to measure content throughput, cycle time, asset reuse rates, and campaign velocity", "Own the technical roadmap for the content supply chain platform, aligned to Adobe product releases and business growth", "Travel may be required for this role. The amount of travel will vary from 0 to 100% depending on business need and client requirements". We'll include travel note. Requirements: list each minimum experience bullet. We need to preserve exact phrasing? Not required but keep substance. List: - Minimum of 5 years of experience in marketing technology, creative operations, or content operations architecture - Minimum of 4 years of hands-on Adobe Workfront configuration and architecture experience at enterprise scale - Minimum of 3 years experience designing or implementing Adobe Content Supply Chain solutions (Workfront + AEM + Creative Cloud) - Minimum of 1 year experience/knowledge of Workfront Fusion for cross-platform automation and workflow orchestration - Minimum of 1 year experience integrating Workfront with creative tools (Adobe Creative Cloud, Frame.io) and downstream activation platforms - Bachelor’s Degree or equivalent (12 years) work experience (If an, Associate’s Degree with 6 years of work experience) We'll keep as is. Skills (Bonus Points): list: - Adobe certifications: Workfront Core Developer, Workfront Fusion, AEM Assets Developer, or Adobe Experience Platform - Hands-on experience with Adobe GenStudio for Performance Marketing or Adobe Firefly Services - Familiarity with content localization workflows and multi-market content operations - Strong understanding of DAM principles, metadata architecture, and asset lifecycle management within AEM Assets or equivalent - Understanding of REST APIs, JSON, and webhook-based integrations - Strong communication and facilitation skills with the ability to lead cross-functional design discussions We'll put as
        • . Benefits: paragraph: "Accenture offers a market competitive suite of benefits including medical, dental, vision, life, and long-term disability coverage, a 401(k) plan, bonus opportunities, paid holidays, and paid time off. See more information on our benefits here: U.S. Employee Benefits | Accenture." We need to preserve the link exactly as in original. The original link: U.S. Employee Benefits | Accenture We must keep that exactly. Pay: We need to list location and salary range. The original includes a heading "Role Location Annual Salary Range" then list lines like "California $94,400 to $266,300". We'll create
          • for each. List all locations and ranges: - California $94,400 to $266,300 - Colorado $94,400 to $230,000 - Connecticut $94,400 to $230,000 - District of Columbia $100,500 to $245,000 - Illinois $87,400 to $230,000 - Maine $80,400 to $196,000 - Maryland $94,400 to $230,000 - Massachusetts $94,400 to $245,000 - Minnesota $94,400 to $230,000 - New York $87,400 to $266,300 - New Jersey $100,500 to $266,300 - Ohio $87,400 to $213,000 - Virginia $87,400 to $245,000 - Washington $100,500 to $245,000 - New York City, NY - Albany, NY - Arlington, VA - Atlanta, GA - Austin, TX - Beaverton, OR - Bentonville, AR - Boston, MA - Carmel, IN - Charlotte, NC - Chicago, IL - Cincinnati