Adobe Workfront Consultant/Architect

We need to output HTML fragment with sections: About the role? The posting includes description of company, role responsibilities, requirements, qualifications, benefits, pay, schedule? Travel mentioned. We need to include sections only if real specific content. We must not repeat job title as heading. No Job ID. Remove boilerplate: EEO, legal, accommodation request, etc. Also remove navigation, cookie, etc. Keep substantive info: company description, role description (pre-sales support, solution leadership, internal capability enablement, etc.), responsibilities list, requirements (minimum experience, education, bonus points), compensation (range by location), benefits (list), travel note maybe schedule? Travel may be required, amount varies 0-100% depending on business need. That's schedule? Could be under Schedule? But schedule not defined; travel is not schedule. Could include a "Travel" section? Not in allowed headings list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Travel not allowed; maybe we can incorporate travel note under Responsibilities or About the role. Probably under Responsibilities. We need to use

for section headings. Use

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

  for prose. We must preserve all substantive information, not invent or summarize away detail. So we need to include all details from posting that are substantive: company description paragraph, role description paragraphs, bullet list of responsibilities (the many items), requirements (minimum experience, education), bonus points (Adobe certification, experience leading multi-platform Adobe solutions, experience configuring integrations using Workfront Fusion), compensation (range by location), benefits (medical, dental, vision, life, long-term disability, 401(k), bonus opportunities, paid holidays, paid time off), maybe also note about compensation varying etc. Travel note maybe under Responsibilities. We must not include boilerplate: EEO, accommodation request, equal opportunity statement, legal notices, etc. Also remove duplicated lines. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. Company description: "We Are Accenture is a global professional services company with leading capabilities in digital, cloud and security. Combining unmatched experience and specialized skills across more than 40 industries, we offer Strategy and Consulting, Interactive, Technology and Operations services—all powered by the world’s largest network of Advanced Technology and Intelligent Operations centers. Over 500,000 people deliver on the promise of technology and human ingenuity every day, serving clients in more than 120 countries. We embrace the power of change to create value and shared success for our clients, people, shareholders, partners and communities. Visit us at www.accenture.com." We can keep that as prose

  . Role description: "You Are We're looking for a senior Adobe Workfront expert to join our team in a solution consulting and architecture role to help clients adopt the Adobe Marketing Cloud and support large-scale business transformations. This is a combined pre-sales and solution leadership role requiring deep technical platform expertise, strong commercial acumen, and proven experience leading complex, multi-stakeholder programs." We can combine into

  . Then responsibilities list: many bullet-like sentences. Let's list them as

  • each. Responsibilities: - Pre-sales Support – Working closely with our growth, alliances, and client service teams to help accelerate the sales process and onboard clients. This will include defining marketing technology strategies & solutions, roadmaps, and budgets; as well as writing proposals and SoWs. - Solution Leadership – Working with our clients in an advisory capacity to help them define solutions and accelerate delivery as a product owner, or work in support of a client product owner, on large-scale implementations and transformation programs. - Internal Capability Enablement – Working with our internal teams to help accelerate practice growth through knowledge sharing, service definition, training, and partner certification. - Organizing and facilitating discovery and requirement capture workshops with senior client stakeholders. - Writing Business Requirement Documents (BRDs), Epics, and Stories. - Defining functional and technical solution architecture and working with project managers to shape the overall delivery approach. - Owning business objectives and requirements during delivery, and coordinating dependencies and priorities across multiple teams. - Leading and supporting new Workfront implementations, from discovery through deployment, as well as assessments of existing implementations with roadmaps for future development. - Contributing to large-scale programs that extend beyond Workfront or marketing technologies — including data platforms, analytics, experience platforms, and creative/production services. - Overseeing acceptance testing and driving issue resolution to completion. - Supporting business change including process engineering, role definition, workflow automation, and skills transfer. - Working with strategy and planning teams to define marketing activation use cases that leverage solution capabilities and best practices. - Supporting new business qualification to ensure focus on the right types of opportunities. - Providing pre-sales support for growth and client service teams, including proposal writing, pitch delivery, and statements of work. - 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 can include travel note as last li. Requirements: Minimum of 3 years of experience as a Workfront System Administrator or in a consultancy Workfront delivery role; Minimum of 2 years of experience with Workfront implementation and project optimization; Minimum of 1 years experience showcasing the ability to lead discovery and requirements workshops with cross-functional stakeholders; Bachelor’s Degree or equivalent (12 years) work experience (If an, Associate’s Degree with 6 years of work experience). We'll keep as prose or list? It's a list of requirements; we can use
    • . Qualifications? The posting has "Bonus Points If You have..." maybe treat as Qualifications or Skills. Could be under Qualifications or Skills. We'll create a section "Qualifications" for bonus points? Or "Skills". The allowed headings include Qualifications, Skills. We'll put bonus points under Qualifications. Bonus points list: - Adobe Experience Cloud certification in one or more of the following: Workfront, Adobe Campaign, Adobe Experience Platform, Adobe Marketo, or Adobe Analytics - 1+ years of experience leading multi-platform Adobe solutions as a product owner, technical client service lead, or solution consultant - 1+ years of experience configuring integrations and automations using Workfront Fusion We'll put under Qualifications. Pay: Compensation at Accenture varies depending on a wide array of factors... As required by local law, Accenture provides a reasonable range of compensation for roles that may be hired as set forth below. We anticipate this job posting will be posted until 11/06/2026. Then list of location salary ranges. We need to include that as Pay section. Should we include the posting end date? It's substantive; we can include in Pay section as note. We'll create

      Pay

      then

      Compensation at Accenture varies depending on a wide array of factors, which may include but are not limited to the specific office location, role, skill set, and level of experience. As required by local law, Accenture provides a reasonable range of compensation for roles that may be hired as set forth below. We anticipate this job posting will be posted until 11/06/2026.

      then maybe a
      with each location and range. But the instruction: Use
      • for any list of duties/requirements/benefits. For Pay, it's a list of location ranges; could treat as list. We'll use
        • . Benefits: "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'll put Benefits section with
          • each benefit. Schedule: Not explicitly given besides travel note. Could omit Schedule section because no specific schedule info. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Travel is not schedule; we can omit Schedule. Now ensure we don't include boilerplate: Remove EEO, accommodation request, legal notices, etc. Also remove duplicated lines like "Visit us at ..." we kept. Now produce HTML. We need to ensure proper escaping of inner quotes? The HTML fragment will contain tags with attributes containing quotes; we need to ensure they are properly quoted. The original had messy data-cmp-data-layer with nested quotes; we can simplify? We must preserve the link but can we keep as is? The original had data-cmp-data-layer="{"jobdetail-1e0b7e5710-Job Description-item0":{"analytics-link-name":"www.accenture.com","analytics-link-type":"engagement","xdm:linkURL":"http://www.accenture.com/","analytics-engagement":"true"}}" which includes double quotes inside double quotes; that's invalid HTML. But we must output as given? Probably we should keep the link as is but we need to escape inner quotes or change to single quotes? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The link is substantive; we need to keep it. However the malformed quotes may break HTML but we must output as given? Usually we would keep the attribute value with double quotes and escape inner quotes with " or use single quotes for outer. But we cannot change the substantive information? Changing quoting could be considered altering but still same link. Safer to keep as is but ensure valid HTML by using single quotes for outer attribute and keep inner double quotes. Eg: data-cmp-data-layer='{"jobdetail-1e0b7e5710-Job Description-item0":{"analytics-link-name":"www.accenture.com","analytics-link-type":"engagement","xdm:linkURL":"http://www.accenture.com/","analytics-engagement":"true"}}'. That preserves content but changes quoting style. Is that allowed? It's still same information; not inventing or summarizing. I think it's acceptable. We'll do that for all tags. Now craft HTML. Let's write:

            About the role

            We Are Accenture is a global professional services company with leading capabilities in digital, cloud and security. Combining unmatched experience and specialized skills across more than 40 industries, we offer Strategy and Consulting, Interactive, Technology and Operations services—all powered by the world’s largest network of Advanced Technology and Intelligent Operations centers. Over 500,000 people deliver on the promise of technology and human ingenuity every day, serving clients in more than 120 countries. We embrace the power of change to create value and shared success for our clients, people, shareholders, partners and communities. Visit us at www.accenture.com.

            You Are We're looking for a senior Adobe Workfront expert to join our team in a solution consulting and architecture role to help clients adopt the Adobe Marketing Cloud and support large-scale business transformations. This is a combined pre-sales and solution