Application Security Support Specialist

for intro paragraphs and general text,

for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). Use

• for list items. No CSS classes, no inline styles, no
  s, no
  tags. Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. If text has no clear sections, just wrap paragraphs in

  tags. Return ONLY the HTML. No markdown fences, no explanation. We need to parse the given job description and extract sections. The raw text includes many

  tags with content. We need to output HTML with appropriate headings. We must keep all original content word-for-word. That includes the text inside tags, etc. We must not remove or rephrase. We can keep the tags? The rule says use

  for section headers. So we need to replace section headers like "Key Responsibilities", "Required Qualifications", etc. But we must preserve the original content word-for-word. The original content includes tags around headings. Should we keep the tags? The instruction: "Use

  for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". So we should use

  tags for those headings, not . But we must preserve all original content word-for-word. That includes the heading text. So we need to output the heading text inside

  but also preserve the original maybe? The original has Background / IRC Summary, Job Overview, Key Responsibilities, etc. We need to keep the content word-for-word, but we can wrap it in

  . The original includes tags around the heading text. Should we keep the tags? The instruction says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. So we cannot remove the tags; they are part of the original content. But we also need to use

  for section headers. Possibly we can replace with

  but that would be removing the tags, which is removal. However maybe we can keep the inside the

  ? The original heading is Key Responsibilities. If we output

  Key Responsibilities

  , we are removing the tags. That would be removing content (the tags). The instruction says do not remove any content. But the tags are formatting markup, not content. The "content" likely refers to the textual content, not markup. The instruction says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. So we must keep the same text, including the tags? The original text includes tags as part of the markup. If we output

  Key Responsibilities

  , we are altering the markup. That might be considered removal of the tags. But the instruction about HTML formatting says use

  for section headers. So we must output

  Key Responsibilities

  instead of Key Responsibilities. That is a change, but it's required by the formatting rules. The instruction about preserving content likely refers to the textual content, not the markup tags. So we can replace with

  . That is allowed. We must not add any extra content. So we need to output the entire job description as HTML, using

  for paragraphs,

  for headings,

  • for list items. We must preserve all original text word-for-word, including the tags? Actually we will not output tags; we will output

    headings. But the original text includes tags around headings; we will replace them with

    . That is a transformation, but it's required. The instruction says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". Replacing with

    is not preserving the original markup, but it's required by the formatting rules. I think it's acceptable because we are not altering the textual content; we are just changing the tag. The textual content "Key Responsibilities" remains unchanged. So it's okay. We must not add any extra commentary. So just output the HTML. Now let's parse the given job description: It starts with:

    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.

    Then there are empty

    etc. We can ignore empty paragraphs? They contain nothing, so we can output nothing for them. But we must preserve them? They are empty, so no content. Then

    Background / IRC Summary

    etc. We need to output HTML with

    for paragraphs and

    for headings. The headings are like "Background / IRC Summary", "Job Overview", "Key Responsibilities", "Access Management & Provisioning", "Access Governance & Compliance", "License Analysis & Optimization", "Reporting & Documentation", "Key Working Relationships", "Required Qualifications", "Preferred Qualifications", "Working Environment", "PROFESSIONAL STANDARDS". Also there are subheadings like "Access Management & Provisioning " inside a paragraph? Actually it's a paragraph with Access Management & Provisioning  then the list items. So we need to treat that as a heading? The instruction says use

    for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). So we should use

    for those headings. The heading "Access Management & Provisioning" is a subheader within the "Key Responsibilities" section. Should we output it as a heading? Probably yes, as a subheading. But the instruction only mentions using

    for section headers like those listed. It doesn't explicitly say to use

    for every heading. But we can treat any text as a heading and wrap in

    . However we must preserve all original content word-for-word. If we wrap "Access Management & Provisioning" in

    , we are altering the markup but preserving the text. That's okay. But we must not add extra headings that are not present. The original has Access Management & Provisioning  as a paragraph heading before the list. That is part of the content. We can output

    Access Management & Provisioning

    before the

    . That would be preserving the text. Similarly, "Access Governance & Compliance" and "License Analysis & Optimization" and "Reporting & Documentation" and "Key Working Relationships" and "Required Qualifications" and "Preferred Qualifications" and "Working Environment" and "PROFESSIONAL STANDARDS" are headings. We should output them as

    ...

    . But note that "PROFESSIONAL STANDARDS" is in all caps and preceded by . We'll output

    PROFESSIONAL STANDARDS

    . Now the content after that includes a paragraph about cookies: "Cookies: https://careers.rescue.org/us/en/cookiesettings" This is a paragraph with a link. We need to preserve it word-for-word. Should we output it as a paragraph? Yes, wrap in

    . The link includes HTML tags; we must preserve them exactly. The original includes .... That's part of the content. We must keep it exactly. So we output

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

    Now we need to output the entire job description as HTML. Let's reconstruct step by step. 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.

    We need to output that as

    ...content...

    . The style attribute should be removed? The rule says no inline styles. So we must not include style="text-align:left". So we need to output just

    ...content...

    without the style attribute. The content includes the same text but without the style attribute. The original includes the style attribute; we must preserve the content word-for-word, but the style attribute is part of the markup, not content. The instruction says no inline styles, so we must remove it. That is allowed. Thus we output

    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: The original uses & for ampersand? Actually it uses ' for apostrophe. We must preserve the HTML entities exactly as they appear. So we keep ' etc. Now after that there are empty
    etc. We can ignore them. Then

    Background / IRC Summary

    followed by a paragraph. So we need to output

    Background / IRC Summary

    then the paragraph content. The paragraph content is: "The International Rescue Committee responds to the world’s worst humanitarian crises and helps people to survive and rebuild their lives. Founded in 1933 at the request of Albert Einstein, the IRC offers lifesaving care and life-changing assistance to refugees forced to flee from war or disaster. At work today in over 40 countries and in 22 US cities, the IRC restores safety, dignity and hope to millions who are uprooted and struggling to endure. The IRC leads the way from harm to home." We must preserve that text exactly, including the apostrophe ’ (which is a typographic apostrophe). The original uses “world’s” with a curly apostrophe? Actually it's "world’s" with a right single quotation mark? The original text: "world’s worst humanitarian crises". That is a typographic apostrophe (U+2019). We must preserve it exactly. Also "life‑changing" includes a hyphen? It uses an en dash? Actually it's "life‑changing" with a non-breaking hyphen? The original shows "life‑changing" with a hyphen? It might be a non-breaking hyphen. We'll just copy as is. Now after that there is
    then

    Job Overview

    then a paragraph. So we output

    Job Overview

    then the paragraph content. Paragraph content: "The Application Security Support Specialist supports the Enterprise Applications & Systems team in the day-to-day management of user access, security role assignments, and license governance across Microsoft Dynamics 365 Finance & Operations (D365 F&O), Emburse expense management system and other related systems. Working closely with the Enterprise Applications & Systems team,  and country/office-level Integra Security Administrators (ISAs), this role is responsible for assigning and removing security roles, processing delegation of authority updates, maintaining journal approver configurations, and ensuring license allocations are accurate and optimized across IRC’s global operations." We must preserve the & etc. Then
    then
    then

    Key Responsibilities

    then a paragraph with Access Management & Provisioning  then list items. We need to output

    Key Responsibilities

    then the paragraph that contains the subheading? Actually the original has

    Key Responsibilities

    Access Management & Provisioning 

    ... list items ...

    Access Governance & Compliance

    In close coordination with Senior Adoption Coordinators:

    ... list items ...
    etc. We need to preserve the structure. The headings "Access Management & Provisioning" and "Access Governance & Compliance" are inside

    ...

    . We can output them as

    Access Management & Provisioning

    and

    Access Governance & Compliance

    . But they are not top-level section headers; they are subheadings within the responsibilities. The instruction says use

    for section headers (e.g. Responsibilities, Qualifications, Requirements...). It doesn't forbid using

    for subheadings. So we can use

    for those as well. But we must preserve the original content word-for-word. The original includes Access Management & Provisioning  as a paragraph. So we output

    Access Management & Provisioning

    then the following
    list items. However the original also has a paragraph after that containing the list items? Actually the list items are inside
    directly after the Access Management & Provisioning  paragraph. So we can output

    Access Management & Provisioning

    then the
    with
    • items. The
    • items contain

      tags inside them? The original has

    • Serve as a primary point of contact...

    etc. The instruction says use

    for introductory paragraphs and general text, and use

    • for list items (duties, requirements, qualifications, skills). So we should output
    • Serve as a primary point of contact for D365 F&O and Emburse access-related questions and issues from global staff.
    etc. But the original includes

    tags around the text inside each

    • . Should we keep the

      tags inside

    • ? The instruction says use

      for introductory paragraphs and general text, and use

      • for list items. It doesn't say to avoid

        inside

      • . But we can just output the text directly inside
      • without

        tags, because the content is a list item. The original includes

        tags around each list item text. That is part of the markup. If we remove them, we are removing content (the

        tags). But the instruction says preserve all original content word-for-word, but the

        tags are markup, not content. The textual content is the same. So we can output the text without the

        tags. However the instruction says "Use

        for introductory paragraphs and general text". List items are not paragraphs; they are list items. So we can output the text directly inside

      • . That would be fine. But we must preserve the content word-for-word, including the text inside the

        tags. So we can output the text exactly as it appears, but without the

        tags? That would be removing the

        tags, which is removal of markup. The instruction about preserving content likely refers to the textual content, not the markup. So it's okay. Thus we will output

      • Serve as a primary point of contact for D365 F&O and Emburse access-related questions and issues from global staff.
      etc. Now after the first list, there