ICM Consultant / Manager

We need to output only HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Preserve all substantive info; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless posting actually states them. Prefer a few substantive sections over many thin ones. We need to parse the posting for substantive content. Let's extract main content: - Intro: "We Are Accenture Song accelerates growth and value for our clients through sustained customer relevance. Our capabilities span ideation to execution: growth, product and experience design; technology and experience platforms; creative, media and marketing strategy; and campaign, content and channel orchestration. With strong client relationships and deep industry expertise, we help our clients operate at the speed of life through the unlimited potential of imagination, technology, and intelligence. Visit us at: www.accenture.com/song." That's about the company; could be "About the role"? Actually "About the role" is typical heading for description of role. But we have "You Are An experienced professional..." etc. That's more like qualifications. There's also "The Work As a Consultant, Song Sales & Commerce Sales Performance Management, you will apply your expertise..." That's responsibilities. We need to decide sections: maybe "About the role" (company overview), "Responsibilities" (the work), "Qualifications" (job qualifications), "Skills" (bonus points?), "Benefits" (benefits info), "Pay" (compensation range). Also maybe "Schedule"? Not present. We must not create sections with placeholder/filler. We have actual content for each. We need to ensure we don't include boilerplate like EEO, accommodation request, etc. Remove those. Also remove duplicated lines. We need to preserve all substantive info: company description, role description, qualifications, bonus points, benefits, compensation ranges per location, maybe also mention "We anticipate this job posting will be posted until 11/01/2026." That's maybe not substantive? It's a date; could be considered metadata but not required? It's not boilerplate; it's a posting end date. Might be considered minor metadata; we could fold into a short

  or drop it. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So posting end date is minor metadata; we could drop it or include in a short p. Probably drop. Also "Compensation at Accenture varies depending on a wide array of factors..." then "As required by local law, Accenture provides a reasonable range of compensation for roles that may be hired as set forth below." Then list of location salary ranges. That's substantive pay info. 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" That's substantive. Now we need to avoid duplication: The intro includes "Visit us at: www.accenture.com/song." That's a link; we can keep as part of About the role. Now we need to produce HTML fragment only, no /, no markdown fences. We need to use

  for section headings. Use

  • for any list of duties/requirements/benefits, and

    for prose. We need to decide what goes into lists. Responsibilities: The Work As a Consultant... includes bullet-like sentences? It's a paragraph. Could be prose. Qualifications: "Here’s what you’ll need:" then bullet list? Actually it's a paragraph with multiple sentences: "3+ years of Sales Performance Management domain experience leading sales transformations specifically focused on sales planning and incentive compensation management. A strong understanding of the Financial Services, Technology, Healthcare and/or Life Sciences industries including market trends and challenges and the regulatory environment, along with experience on topic areas such as sales territory planning, sales capacity planning, quota planning, incentive compensation management, seller enablement, and sales operations operating model design leveraging leading sales performance management platforms such as Anaplan or Varicent, is required. 2+ years of experience in management or technology consulting, with broad experience in engagement management, business development, and leading complex projects / programs." We could turn each sentence into

  • items under a
    . That would be a list of requirements. Bonus Points: "Bonus Points If You have excellent communication..." etc. That's a list of bonus qualifications; could be a
    under Skills or maybe separate "Skills" section. We need to decide sections: Perhaps "About the role" (company overview), "Responsibilities" (the work), "Qualifications" (required experience), "Skills" (bonus points), "Benefits", "Pay". Avoid thin sections; but we have enough content. We must not repeat job title as heading. So no heading for the job title. We must not include Job ID/requisition numbers; none visible. We must remove boilerplate: EEO, accommodation request, equal opportunity statement, etc. Also remove "Requesting an Accommodation" etc. Also remove "Equal Employment Opportunity Statement", "Other Employment Statements", etc. Also remove duplicated lines: there may be duplicate sentences? Not obvious. Now produce HTML. Let's draft:

    About the role

    We Are Accenture Song accelerates growth and value for our clients through sustained customer relevance. Our capabilities span ideation to execution: growth, product and experience design; technology and experience platforms; creative, media and marketing strategy; and campaign, content and channel orchestration. With strong client relationships and deep industry expertise, we help our clients operate at the speed of life through the unlimited potential of imagination, technology, and intelligence. Visit us at: www.accenture.com/song.

    But we need to preserve the link attributes exactly as in original? The original includes a lot of data attributes. We should keep them as they are, but we need to ensure proper quoting inside HTML. The original had nested quotes with double quotes inside the attribute value; they used data-cmp-data-layer="{"jobdetail-1e0b7e5710-Job Description-item0":{"analytics-link-name":"www.accenture.com/song","analytics-link-type":"engagement","xdm:linkURL":"http://www.accenture.com/song","analytics-engagement":"true"}}". That's problematic because the attribute value contains double quotes. In HTML, you need to escape them or use single quotes. The original likely used double quotes around the whole attribute and escaped inner quotes? Actually they wrote: data-cmp-data-layer="{"jobdetail-1e0b7e5710-Job Description-item0":{"analytics-link-name":"www.accenture.com/song","analytics-link-type":"engagement","xdm:linkURL":"http://www.accenture.com/song","analytics-engagement":"true"}}". That's invalid HTML because the attribute value starts with a double quote, then immediately another double quote for the JSON key. In real HTML they'd use single quotes for the attribute or escape. But we must preserve ALL substantive information; we cannot change the meaning. However we can keep as is; the output will be invalid but maybe acceptable? Usually they'd expect we keep the exact string. We'll keep it as is, but we need to ensure we don't break the HTML fragment. Since we are outputting HTML, we need to make sure attribute values are properly quoted. We could change outer quotes to single quotes to avoid conflict, but that changes the attribute value? It changes the quoting style but not the content. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Changing quoting style is not substantive; it's syntactic. Probably acceptable. Safer to use single quotes for the attribute. Thus: www.accenture.com/song We'll do similar for other links. Now Responsibilities:

    Responsibilities

    As a Consultant, Song Sales & Commerce Sales Performance Management, you will apply your expertise in sales planning and incentive compensation management on Anaplan and/or Varicent to transform front office sales strategies and solutions to help clients achieve top line growth and profitability objectives.

    That's the only responsibility paragraph. Qualifications:

    Qualifications

    • 3+ years of Sales Performance Management domain experience leading sales transformations specifically focused on sales planning and incentive compensation management.
    • A strong understanding of the Financial Services, Technology, Healthcare and/or Life Sciences industries including market trends and challenges and the regulatory environment, along with experience on topic areas such as sales territory planning, sales capacity planning, quota planning, incentive compensation management, seller enablement, and sales operations operating model design leveraging leading sales performance management platforms such as Anaplan or Varicent.
    • 2+ years of experience in management or technology consulting, with broad experience in engagement management, business development, and leading complex projects / programs.
    Now Skills (bonus points):

    Skills

    • Excellent communication (written and spoken) and interpersonal skills, including compelling story telling skills for an executive audience and the ability to interact with diverse stakeholders.
    • Strong client executive relationship development and management skills.
    • Experience in delivering CRM, CPQ, Lead to Order, Sales Transformation implementations.
    • Experience working with onshore and offshore delivery teams.
    • Bring an existing network of relationships within the Financial Services, Technology, Healthcare and/or Life Sciences industry from past work experiences.
    • Familiar with AI, GenAI, or other emerging technologies.
    Now Benefits:

    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: