HR Systems Analyst (Security & Integrations)

for paragraphs,

for section headers,

• for list items. No CSS classes, no inline styles, no
  , no
  . Must preserve all original content word-for-word, no addition, removal, summarizing, rephrasing. Must remove any HTML tags that are not allowed? The input includes many HTML tags with styles etc. We need to convert to allowed tags while preserving text content exactly. We must not add or remove any text. So we need to extract the plain text content from the given HTML, preserving it exactly, then wrap in appropriate tags. We must not add any extra text like explanations. Just output HTML. We need to identify sections: Intro paragraph(s) before "Job Overview/Summary:" etc. Then headers: Job Overview/Summary, Key Responsibilities, Key Working Relationships, Job Requirements, Preferred Additional Qualifications, Working Environment, Professional Standards, Cookies, maybe #LI-1. We need to use

  for each section header. The header text includes the bold/underline tags etc. We must preserve the exact text of the header (including the colon?). The original header text: "Job Overview/Summary:" So the text is "Job Overview/Summary:" (including colon). We need to keep that exactly. So

  Job Overview/Summary:

  . Similarly for others. We need to convert list items: each

• ...

etc. We need to output
• with the text inside (preserving any inner tags? The inner

  tags should be removed? We must preserve text word-for-word, but we cannot keep

  inside

• because that would be extra tags not allowed? The rules: Use
  • for list items. It doesn't forbid having

    inside

  • , but likely they expect just text inside
  • . However we must preserve all original content word-for-word; if we strip the

    tags we are removing tags, which is altering content. But the instruction says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. That likely refers to the textual content, not the markup. Since we are converting to HTML, we are allowed to change tags as long as the textual content remains same. So we can drop the inner

    tags. Also need to handle & etc. The original text includes HTML entities like &. We must preserve them as they appear? The original content includes "Workday's". That's an apostrophe encoded as '. We must keep that exactly. So we should not decode them. Keep as is. Also there are some stray
    tags and   etc. We must preserve them? The rules say no
    tags. So we must not output
    . But we need to preserve the content; the
    tags are not content, they are formatting. Likely we can drop them. Also there are spaces like " ". That's a non-breaking space entity. We should keep it as is? It's part of content. We'll keep the entity. We must not add any extra text like explanation. Let's extract the textual content sections. I'll parse manually. Start with first

    ... The International Rescue Committee (IRC) responds ...

    Then there are two empty
    (empty). We can ignore them as they have no content. Then

    Job Overview/Summary:

    Then paragraph:

    The HR Systems Analyst (Security & Integrations) owns the functional design, build, and maintenance of Workday's integration layer and security configuration in support of all Workday users. This role is responsible for designing, testing, and hardening integrations between Workday and downstream systems, and for configuring Workday's security groups and policies in line with IRC's data classification standard. The role also builds rule-based automation for high-volume, structured P&C processes, and escalates complex, cross-functional design decisions to the Global HR Systems Product Manager.

    Then

    This position requires hands-on experience with Workday integration tools (EIB, Core Connectors, Studio, and ideally Orchestrate) and a working understanding of Workday's security framework.
     

    Note there is a
    and a non-breaking space after. We'll drop the
    and keep the space? The space entity maybe we keep as a space? We'll just keep the text before the
    and ignore the
    and the   maybe as a space? But to preserve content word-for-word, we might need to keep the   entity. However we cannot include
    tags. We could keep the   as is, and omit the
    . That would change the content slightly (removing
    ). But the instruction says no
    tags. So we must omit them. The   is not a tag, it's an entity; we can keep it. Thus after that paragraph we have the text: "This position requires hands-on experience with Workday integration tools (EIB, Core Connectors, Studio, and ideally Orchestrate) and a working understanding of Workday's security framework." followed by a space? Actually there is a
      (space). We'll keep the   as a space? We'll just keep the entity   maybe. But we can't guarantee. Safer to keep the   as is, and omit the
    . So output: "This position requires hands-on experience with Workday integration tools (EIB, Core Connectors, Studio, and ideally Orchestrate) and a working understanding of Workday's security framework. " (note the space after? Actually the   is a non-breaking space; we keep it.) Then next header:

    Key Responsibilities:

    Then
    with list items each containing

    ...

    . We'll output each as
    • with the inner text. We need to preserve inner text exactly, including any entities like & etc. Let's extract each list item text. Item1: "

      Design, build, test, and maintain Workday integrations using EIB, Core Connectors, Studio, and Orchestrate to connect Workday with payroll, benefits providers, and other third-party systems

      " Item2: "

      Own the functional design process for Workday security and integrations, escalating complex cross-functional decisions to the Global HR Systems Product Manager

      " Item3: "

      Configure and maintain Workday security groups, business process security policies, and domain security policies aligned to IRC's data classification standard

      " Item4: "

      Build and maintain rule-based automation for high-volume, structured processes (bulk data loads, account provisioning, permissions, location and hierarchy setup) using Orchestrate and EIBs.

      " Item5: "

      Proactively monitor integration health, troubleshoot failures, and resolve root-cause issues ahead of ticket escalation

      " Item6: "

      Test and validate integrations and security configurations during Workday releases and functional area changes

      " Item7: "

      Gather requirements from HR and non-HR partners; map data elements as needed

      " Item8: "

      Collaborate with HRIS colleagues, Payroll, Finance, and IT to identify opportunities for process improvement and efficiency within IRC's current Workday usage, including cross-functional considerations

      " Item9: "

      Produce reporting and dashboards related to integration performance and security compliance

      " Item10: "

      Perform other special projects as needed
       

      " Note item10 has a
      and   after text. We'll keep the   entity and omit
      . So text: "Perform other special projects as needed& nbsp;"? Actually it's "Perform other special projects as needed
       ". We'll output: "Perform other special projects as needed " (keeping the entity). Ensure no extra spaces. Now after the ul, we have header:

      Key Working Relationships:

      Then paragraphs:

      Position Reports to: Global HR Systems Product Manager

      Position directly supervises: n/a

      Indirect Reporting: n/a

      Internal: Human Resources, Payroll, Finance, IT, Information Security

      External: Workday, Cornerstone, ADP, and other third-party vendors
       

      Again last paragraph has
       . We'll keep   and omit
      . Then header:

      Job Requirements:

      Then ul with list items each

      ...

      . Need to extract each. Item1: "

      Bachelor's degree or equivalent with 4+ years of professional experience managing data sharing/integrations between enterprise software applications

      " Note "4+" is "4+". Keep entity. Item2: "

      Hands-on experience building and maintaining Workday integrations using EIB, Core Connectors, and Workday Studio; working knowledge of Workday Orchestrate a strong plus

      " Item3: "

      Working understanding of Workday's security framework: security groups, domain and business process security policies

      " Item4: "

      Working knowledge of data security/classification frameworks (e.g., GDPR or equivalent)

      " Item5: "

      Experience working with large datasets, in-depth understanding of data relationships, and data cleansing practices

      " Item6: "

      Intermediate understanding of relational database concepts

      " Item7: "

      Exceptional problem-solving skills with attention to detail, excellent time management, organizational skills, and ability to prioritize work

      " Item8: "

      Self-motivated with the ability to work both independently and in a team environment

      " Item9: "

      Excellent customer service, communication (written and verbal), and cross-group collaboration skills required

      " Item10: "

      Flexibility in daily schedule, and ability to understand and react quickly to changing priorities

      " Item11: "

      Experience working in a globally distributed environment a plus

      " Item12: "

      Experience working with a helpdesk ticketing system a plus
       

      " Again last item has
       . Then header:

      Preferred Additional Qualifications

      Note original: "Preferred Additional Qualifications" (no colon). We'll keep exactly that. Then ul with list items: Item1: "

      Workday Pro certification in Integrations or Security a strong plus

      " Item2: "

      Experience with an international nonprofit in the delivery of systems across varying IT infrastructure and low/intermittent bandwidth scenarios

      " Item3: "

      Experience with data migration and systems integration projects
       

      " Again last has
       . Then header:

      Working Environment:

      Then paragraph:

      Standard office work environment with the ability to work a hybrid office/remote schedule.

      Then

       

      (just a non-breaking space). We'll keep that as a paragraph containing   maybe. Then header:

      Professional Standards:

      Note there is a space after colon before closing . The text: "Professional Standards: " includes a space after colon. We'll keep exactly. Then paragraph:

      All International Rescue Committee workers must adhere to the core values and principles outlined in IRC Way - Standards for Professional Conduct. Our Standards are Integrity, Service, Equality and Accountability. In accordance with these values, the IRC operates and enforces policies on Safeguarding, Conflicts of Interest, Fiscal Integrity, and Reporting Wrongdoing and Protection from Retaliation. IRC is committed to take all necessary preventive measures and create an environment where people feel safe, and to take all necessary actions and corrective measures when harm occurs. IRC builds teams of professionals who promote critical reflection, power sharing, debate, and objectivity to deliver the best possible services to our clients.

      Then
      then

      Cookies: https://careers.rescue.org/us/en/cookiesettings

      Then
      then

      #LI-1

      We need to preserve the link text etc. But we cannot keep tags? The rules didn't forbid . They only said use

      for paragraphs,

      for section headers,

      • for list items. No CSS classes, no inline styles, no
        , no
        . It didn't forbid or . However they said use

        for introductory paragraphs and general text. It didn't say we cannot use other tags like . But to be safe, we could keep as is, but we must strip inline styles and classes. The tags have target="_blank" and href, that's okay. The inside has style attribute, which is inline style - not allowed. So we must remove the tags but keep the text inside. Also we must remove the style attribute from ? The has target="_blank" and href only, no style. That's fine. The has style attribute, we must drop it but keep its text. Thus for the link we output: IRC Way - Standards for Professional Conduct Similarly for Safeguarding link. Also the Cookies link: https://careers.rescue.org/us/en/cookiesettings We must also preserve the text "#LI-1" inside a paragraph. We also need to handle the empty paragraph with just   after Working Environment. We'll output

         

        (preserving the entity). That's okay. Now we need to ensure we don't add any extra text. We'll output exactly the sections in order. Let's construct. Start with introductory paragraph(s): The first

        with the IRC description. Then there were two empty paragraphs; we can ignore them as they have no content. So we output that paragraph as

        ...

        . Then header

        Job Overview/Summary:

        Then paragraph(s) after that: there are two paragraphs: first the overview paragraph, second the experience requirement paragraph (with  ). We'll output each as

        ...

        . Ensure we keep the   entity. Then header

        Key Responsibilities:

        Then

        with each
        • containing the text (without inner

          ). We'll need to preserve line breaks? Not needed. Then header

          Key Working Relationships:

          Then paragraphs for each line. Then header

          Job Requirements:

          Then
          with list items. Then header

          Preferred Additional Qualifications

          Then
          . Then header

          Working Environment:

          Then paragraph: Standard office work environment... Then paragraph:   (non-breaking space) Then header

          Professional Standards:

          Then paragraph with the long text (including links with stripped spans). Then paragraph: Cookies: ... Then paragraph: #LI-1 Now we need to ensure we keep all original text exactly, including spaces and punctuation. Let's extract each piece precisely. I'll copy the text from the input, removing tags. First paragraph: "The International Rescue Committee (IRC) responds to the world's worst humanitarian crises, helping to restore health, safety, education, economic wellbeing, and power to people devastated by conflict and disaster. Founded in 1933 at the call of Albert Einstein, the IRC is one of the world's largest international humanitarian non-governmental organizations (INGO), at work in more than 40 countries and 29 U.S. cities helping people to survive, reclaim control of their future and strengthen their communities. A force for humanity, IRC employees deliver lasting impact by restoring safety, dignity and hope to millions. If you're a solutions-driven, passionate change-maker, come join us in positively impacting the lives of millions of people world-wide for a better future." Note there is an apostrophe encoded as '. We'll keep that. Second paragraph after header: "The HR Systems Analyst (Security & Integrations) owns the functional design, build, and maintenance of Workday's integration layer and security configuration in support of all Workday users. This role is responsible for designing, testing, and hardening integrations between Workday and downstream systems, and for configuring Workday's security groups and policies in line with IRC's data classification standard. The role also builds rule-based automation for high-volume, structured P&C processes, and escalates complex, cross-functional design decisions to the Global HR Systems Product Manager." Note there is & and ' etc. Third paragraph: "This position requires hands-on experience with Workday integration tools (EIB, Core Connectors, Studio, and