Senior Experience Designer | Product & Conversation Design

We need to output HTML fragment with sections: About the role? The posting includes intro about Accenture Song, description of role, responsibilities (The Work), Basic Qualifications, Nice to Haves, Compensation (salary ranges), Benefits (Accenture offers a market competitive suite...), Travel, Location (Primary residency within 90 minutes...). Also maybe "Pay" section if salary ranges present. "Schedule" not present. "Benefits" present. "Skills" maybe not separate; we can include under Qualifications? But we need to follow rules: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Include a section only when posting has real, specific content. So we need to decide which sections to include. We have: - About the role: we have introductory paragraph describing Accenture Song and role description. Could be "About the role". We'll put that as

About the role

with

content. - Responsibilities: "The Work" list of duties. We'll make

Responsibilities

with

• each bullet. - Requirements / Qualifications: Basic Qualifications and Nice to Haves. Could combine into Requirements? The spec says we can have Requirements, Qualifications, Skills. We need to avoid thin sections. Perhaps we make

  Qualifications

  with Basic Qualifications list, and maybe another

  Nice to have

  ? But they said prefer few substantive sections over many thin ones. Could combine Basic and Nice into one Qualifications section with two sub-lists? But we must use
  • for any list. Could have two
    under same heading. That's okay. - Benefits: we have description of benefits. So

    Benefits

    with

    maybe plus link. - Pay: we have salary ranges per location. That's specific. So

    Pay

    with maybe a
    of location ranges or a

    with table? We'll just list as

    • each location range. - Location: we have "Primary residency within 90 minutes of an approved Accenture office" plus list of many cities. That's location info. Could be under "Location" heading but not in list of allowed headings? Allowed headings include About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Location not listed but we could treat as part of About the role or maybe we can add a heading? The instruction: "Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive. But they say "include a section ONLY when the posting has real, specific content for it". It doesn't forbid other headings, but to be safe we could incorporate location into About the role or Pay? Probably better to have a "Location" section as it's specific. However they didn't list Location as example but didn't forbid. I'd include Location as

      Location

      with

      and maybe

      of cities. - Travel: "Travel: As required for client support." That's specific but minimal. Could be included under About the role or maybe a short

      . Since it's not a list, we can just include a

      under About the role or a separate thin section. Better to incorporate into About the role. - Also there is "Compensation at Accenture varies..." which is generic; we already have Pay section with ranges; we can ignore the generic sentence. - Also there is "We anticipate this job posting will be posted until 10/30/2026." That's boilerplate? Might be considered metadata; we can drop. - Also there is "See more information on our benefits here:" link; we can include that in Benefits section. - Also there is "Requesting an Accommodation" etc. That's EEO boilerplate; remove. - Also there is "Equal Employment Opportunity Statement" etc; remove. - Also there is "Other Employment Statements" etc; remove. - Also there is "Accenture is an EEO and Affirmative Action Employer..." remove. Thus final HTML will have sections: About the role, Responsibilities, Qualifications, Benefits, Pay, Location. Possibly Skills? Not needed. We need to preserve all substantive information. Ensure we don't lose any bullet points. Let's extract content. Intro paragraph: "We Are Accenture Song—a new breed of agency that’s all about the Experience. For us, customer experience is not an add-on; it’s foundational to who we are and how we empower our clients. As the world’s largest, most disruptive agency, we drive lasting growth for clients by helping them design, build, and run meaningful experiences that make people’s lives better, more productive, and more meaningful. We do this in three ways: by transforming organizations through standout products and services; by building and delivering award-winning campaigns so brands can engage and communicate creatively with customers at scale; and by using our top-notch skills to pilot, integrate, scale, and run the platforms that underpin the world’s greatest experiences. Visit us here to learn more about what makes us the Experience Agency: www.accenture.com/song The digital economy has caused a massive increase in the amount and importance of digital content. Digital content and the customer experience it fuels are, together, a vital expression of a brand’s voice and purpose. We help leading brands create and deliver the right content for the right customer at the right time for immersive, relevant experiences. We offer an end-to-end approach to the content lifecycle and cut through the complexity for improved speed to market and relevance, at scale. Our unique tools and services organize, store, and optimize content, including taxonomy, rights and asset management, analytics, and quality assurance." Then "You Are As an Experience Designer within Accenture Song’s Service Creative practice, you will shape how people interact with next‑generation, AI‑powered customer service products. This role blends strong foundations in UI/UX and product design with emerging work in GenAI and agentic AI, focusing on screen‑based and conversational experiences that feel intuitive, trustworthy, and human. You will work within a cross‑disciplinary team of service designers, product designers, conversation designers, AI engineers, and CX strategists to design end‑to‑end customer experiences that operate at enterprise scale and deliver measurable impact." We can combine these into About the role paragraph(s). We'll keep the link. Now Responsibilities (The Work) bullets: - Own end‑to‑end UX and product design for AI‑powered customer service solutions, from discovery and research through wireframes, high‑fidelity prototypes, and design system contributions - Design screen‑based interfaces for chat experiences, agent dashboards, escalation workflows, and self‑service tools across web and mobile platforms - Translate complex AI behaviors (e.g., confidence states, reasoning steps, agentic actions) into clear, transparent, and controllable user experiences - Partner closely with product managers, AI/NLP engineers, and CX strategists to align design intent with system behavior and business requirements - Plan and conduct usability testing, synthesize qualitative and quantitative insights, and iterate designs based on evidence - Contribute to AI‑native design systems, including accessibility‑compliant UI patterns, fallback and error states, and human‑in‑the‑loop interactions - Collaborate with service and conversation designers to ensure screen‑based and conversational touchpoints form a cohesive, end‑to‑end customer journey - Advocate for inclusive, accessible design across all experiences, including AI‑generated content and interactions - Travel: As required for client support. We could keep Travel as separate bullet or incorporate into About the role. We'll keep as bullet under Responsibilities. Now Basic Qualifications list: - 3+ years of professional experience delivering UI/UX or product design for screen‑based digital products (web and/or mobile) - 1+ years experience designing conversational or AI‑driven experiences, such as chatbots, virtual agents, or voice interfaces - 2+ years of ownership of at least 2–3 end‑to‑end product or service design initiatives, from discovery through high‑fidelity execution - 2+ years of advanced, hands‑on experience using Figma for production work, including components, variants, auto‑layout, and interactive prototyping across multiple shipped experiences - 2+ years of demonstrated experience collaborating with 3 or more cross‑functional roles (e.g., product, engineering, AI/NLP, CX, research) within agile or iterative delivery environments Nice to Haves list: - Experience designing conversational or AI‑driven experiences, such as chatbots, virtual agents, or voice interfaces (duplicate of basic? but it's nice to have) - Familiarity with GenAI or LLM‑powered product surfaces, including trust, transparency, and human‑in‑the‑loop design patterns - Exposure to CX platforms, enterprise SaaS, or customer service ecosystems - Applied knowledge of WCAG 2.1 AA accessibility standards across both UI and AI‑generated content - Prior experience working in consulting, studio, or multi‑client environments - Bachelor’s degree in design, human‑computer interaction, cognitive science, or a related field We can combine under Qualifications heading with two subheadings? But we must use

      for section headings only; we could have

      Qualifications

      then

      Basic Qualifications:

      ... then

      Nice to have:

      ... That's acceptable. Now 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 that in Benefits section. Pay: Salary ranges per location. We'll list each location with range. We have many locations: list includes states with ranges and then many cities. The posting includes both state ranges and then a long list of cities (maybe for each state?). Actually they list state ranges then a list of cities (maybe all locations where those ranges apply?). The safest is to include the state ranges as given, and also list the cities (maybe as additional info). We'll include both: a
      with each state range, then another
      for cities (maybe just note "Locations include: ..."). We'll preserve all. Location: "Primary residency within 90 minutes of an approved Accenture Office". Also list of many cities (the same list). Actually the list of cities appears after the state ranges; maybe it's the list of approved offices. So we can treat Location section with that sentence and then list of cities. Thus we may have overlapping location info between Pay and Location. To avoid duplication, we could put city list under Location