Workday Certified Financials/Studio Integration Consultant - Healthcare

We need to output HTML fragment with sections: About the role? The posting includes responsibilities, why join, who will be successful, travel, requirements, nice to have, compensation, benefits, location salary ranges, etc. We must use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. No Job ID etc. We must include a section only when posting has real specific content. So we need to decide which sections have content. We have responsibilities: list of duties. So we can have

Responsibilities

with

• items. We have "Why should I join the Accenture Workday team?" That could be "About the role" or maybe "About the team". But we have a heading "About the role" allowed. Could put that content there. We have "Who will be successful at Accenture?" That could be Skills or Qualifications. Could be "Qualifications" or "Skills". We have both headings allowed. We need to decide. We have "Travel may be required..." That's Schedule? Actually travel is not schedule; schedule could be work schedule. Not given. So we may omit Schedule section if no specific schedule info. We have "Here's what you need:" which includes requirements: certifications, experience, education. That's Requirements/Qualifications. We have "Nice to have:" which could be Skills. We have compensation info: "Compensation at Accenture varies..." plus salary ranges per location. That's Pay. We have benefits: "Accenture offers a market competitive suite of benefits..." that's Benefits. We have location salary ranges: that is part of Pay. We have "Requesting an Accommodation", EEO statements etc which we must remove as boilerplate. We must not include sections with filler like "commensurate with experience". Not present. Thus sections: About the role (why join), Responsibilities, Requirements (maybe Qualifications), Skills (nice to have), Benefits, Pay. We could combine Requirements and Qualifications into one section? The rules allow both headings but we should avoid thin sections. Could put all mandatory requirements under "Requirements". Nice to have under "Skills". That seems fine. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all bullet points from responsibilities, all points from why join, who will be successful, travel, requirements, nice to have, compensation, benefits, location salary ranges. We must not include boilerplate like EEO, accommodation request, etc. We need to format as HTML fragment only. Let's extract responsibilities list: - Lead the design of integrations from point to point systems as well as holistic interchange services rendering effective data quality and dependable exchanges of digital information - Identify, assess, and solve complex business problems for integrating the Workday cloud application with external applications across a wide array of Human Capital Management and Financial functional areas, where analysis of situations or data requires an in-depth evaluation of variable factors - Lead the design, build, and support testing of Workday integration code base including Studio, EIB and supporting 3rd party coding - Oversee integration delivery - Manage integration development process (may require interaction with global resources across multiple geographic locations) - Lead Discovery session with client for each domain specific integration - Deliver requirements and design documents to developers - Ensures timelines and quality of integration is met - Engages with 3rd party vendors as required - Closely follow the strategic direction set by leadership when establishing Workday project goals - Collaborate with client counterpart to successfully deliver on shared objectives - Responsible for timely identification and escalation of risks and development of alternative technical and functional approaches when necessary - Lead the identification of process improvements and changes to our methodology based on project experience That's a list. Now "Why should I join the Accenture Workday team?" bullet points: - Innovate every day. Be at the forefront of designing and delivering Workday solutions that push boundaries and create new opportunities for our clients. - Lead with the industry’s best. Join an industry-recognized global cloud leader with more than 2000 Workday certified professionals collaborating to drive enterprise-wide transformational projects on a global scale. - Accenture has worked with more than 600 clients to deliver Workday deployments to unlock the potential of their organizations. - Learn and grow continuously. Harness unmatched training and professional development to help you build and advance your Workday, consultative and delivery skills. With learning resources, interactive classroom courses, real-life client simulations and ongoing mentoring available when you need it, you’ll expand your thinking beyond the core Workday implementation. We could keep as paragraphs or list. Since it's prose, we can use

  for each bullet or combine into

  . The rule: Use
  • for any list of duties/requirements/benefits, and

    for prose. This is a list of reasons; could treat as list. But it's not duties/requirements/benefits; it's marketing. Could be prose. Safer to use

    for each sentence? Might be okay to use

    as it's a list. The rule says use
    • for any list of duties/requirements/benefits. It doesn't forbid using
      for other lists, but says use

      for prose. I'd treat as

      because it's a list of bullet points. However to be safe, we could use

      for each bullet. But that would be many

      tags. Either is fine. I'll use

      for clarity. Now "Who will be successful at Accenture?" bullet points: - It’s not just what you know or where you’ve been that propels success at Accenture: It’s who you are, fundamentally, as a person. - We prize diversity in backgrounds and perspectives. - Whatever your unique qualities, a few key traits should apply: - You’re passionate about technology and motivated to apply the latest technology trends. - You’re proactive and collaborative; a leader with effective communication skills. - You’re driven by new challenges and are motivated to improve. - You’re a creative problem solver with the flexibility to navigate uncertainty. - You’re focused on the future with a desire to develop inclusive, responsible and sustainable solutions to complex challenges. We could format as nested list. Now travel: "Travel may be required for this role. The amount of travel will vary from 0 to 100% depending on business need and client requirements." This is schedule? Not exactly schedule but could be under Schedule? The rule says Schedule section only if posting actually states them. It does state travel amount. Could treat as Schedule. But the allowed headings include Schedule. So we could create a Schedule section with that sentence. However the instruction: "Prefer a few substantive sections over many thin ones." Travel is a single sentence; maybe we could incorporate into About the role or Responsibilities? But it's not about role. Could be under "About the role" as additional info. But we already have About the role for why join. Might be better to make a Schedule section with that sentence. It's substantive enough. Now requirements: "Here's what you need:" list: - Workday Studio Certified - Minimum of 2 years of experience in Workday Financials (FINs) implementations - Minimum of 2 years of integration tools including Studio, EIB, Core Connectors, and Document Transformation experience - Minimum of 2 years experience with REST/SOAP web services and API-based integrations - Bachelor's degree or equivalent (minimum 12 years work experience). If Associate’s Degree must have equivalent minimum 6 year work experience. We'll put as
      . Now nice to have: - Knowledge of Health Industry - Strong understanding of Workday Financial data model including FDM, Subledger Accounting, and Customer/Supplier objects - Ability to support E2E testing, defect triage, and resolution with minimal ramp-up time - Strong communication skills for vendor and client-facing interaction Now compensation: "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/09/2026." Then location salary ranges list. We need to include all that. The posting until date is maybe not substantive? It's a date; could be considered metadata but it's substantive. We'll include as a

      maybe. 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 as

      or

      . It's a list of benefits; could be
      . But rule: use
      • for any list of duties/requirements/benefits. So we should use
        for benefits. Now we must not include boilerplate like EEO, accommodation request, etc. So we will omit those sections. Now we need to decide headings: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule (travel). Could also include Qualifications but we have Requirements covering mandatory qualifications; Skills covering nice to have. That seems fine. We must not repeat job title as heading. Not needed. Now produce HTML fragment. We'll wrap sections in maybe? Not required but okay. The instruction didn't forbid. Just output HTML fragment. We'll produce:

        About the role

        • ... each bullet

        Responsibilities

        ...

        Requirements

        ...

        Skills

        ...

        Benefits

        ...

        Pay

        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/09/2026.

        ... location salary ranges

        Schedule

        Travel may be required for this role. The amount of travel will vary from 0 to 100% depending on business need and client requirements.

        Check that we didn't miss any substantive info: The "Why should I join..." we put under About the role as list. Good. The "Who will be successful..." we put under Skills? Actually that's more about traits; could be under Skills as well. But we already have Skills for nice to have technical. Could we put those traits under Skills as well? Might mix. Better to have a separate section for "Who will be successful" but we don't have a heading for that. Could use "Qualifications" for those traits? But Qualifications is more about mandatory qualifications. However we could put them under "Skills" as they are skills/traits. But we already have Skills for nice to have technical. Could combine? Might be thin. Alternative: Use "Requirements" for mandatory, "Skills" for nice to have technical and also include the success traits? Might be okay. But we have "Who will be successful at Accenture?" which is a list of traits. Could be placed under "Skills" as well, but it's not technical skills. However the rule doesn't restrict Skills to technical; it's just a heading we can use. So we can include both nice to have technical and success traits under Skills. That would make Skills section substantive. Thus we can have Skills section containing both nice to have technical and the success traits. Let's list them: