Head: Insurance Compliance

for intro paragraphs and general text,

for section headers,

• for list items. Must preserve all original content word-for-word, no additions, deletions, summarizing. Must not add any extra text. Must not use
  ,
  , CSS, etc. Must not add markdown fences. Just raw HTML. We need to parse the job description and output HTML accordingly. We have sections: Purpose Statement (maybe as heading?), Experience (minimum, ideal), Qualifications (Minimum), Qualifications (Ideal or Preferred), Key Performance Areas (maybe as heading?), then bullet points under each. Then Knowledge (Minimum, Ideal), Skills (list), Conditions of Employment (maybe paragraph), Capitec commitment (paragraph), How to Apply (numbered list? but instruction says use

  • for list items; but the How to Apply has numbered steps. Should we convert to
    • ? The rule: Use
      • for list items (duties, requirements, qualifications, skills). It doesn't explicitly say for How to Apply, but it's a list. Probably we should use
        • for that as well. However the content includes "1. To see what life at Capitec is all about and complete a short assessment, please click here!" etc. We need to preserve word-for-word, including numbers and punctuation. So we can output as
          • 1. To see what life at Capitec is all about and complete a short assessment, please click here!
          ... etc. But we need to use

          for section headers like "Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role". In this job description, we have headings: "Purpose Statement", "Experience", "Qualifications (Minimum)", "Qualifications (Ideal or Preferred)", "Key Performance Areas", "Knowledge", "Skills", "Conditions of Employment", "Capitec is committed...", "How to Apply". 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 each of those headings that appear. For headings that are not exactly those words but similar, we can still use

          maybe with the text as is. The rule: 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 "Purpose Statement"? Not listed, but it's a header. Could use

          Purpose Statement

          . Probably okay. We need to preserve all original content word-for-word. That includes bullet points and hyphens? The original text includes bullet points with hyphens. Should we keep the hyphens? The instruction says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. So we must keep the bullet dash and the text exactly as given. But we need to output HTML. How to represent bullet points? The original uses hyphens at start of each line. In HTML, we can output them as plain text within

          or

          • . The instruction says use
            • for list items (duties, requirements, qualifications, skills). So we should convert the bullet lines into
            • items. But we must preserve the content word-for-word, including the leading dash? The dash is part of the bullet marker, not part of the content? The original lines start with "- " then text. If we put that into
            • , we could include the dash as part of the li content, but that would add a dash that wasn't originally part of the text? Actually the dash is part of the original line; it's a bullet marker. The instruction says preserve ALL original content word-for-word. That includes the dash? The dash is not part of the textual content but part of the formatting. The content after dash is the text. The dash is a bullet marker, not part of the sentence. The instruction says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. So we should not alter the text. If we convert to
            • , we might need to keep the dash? But the dash is not part of the content; it's a marker. The content is the sentence after dash. The dash is part of the original line representation. If we remove it, we are removing a character. That might be considered removal. But the instruction says do not add, remove, summarise, or rephrase. Removing the dash might be considered removal. However the dash is not part of the actual sentence; it's a bullet marker. The content is the sentence. The instruction says preserve ALL original content word-for-word. That likely means we should keep the exact wording of each bullet, including the leading dash? The bullet lines are "- Complying with the fit and proper standards..." etc. If we output that as plain text inside
            • , we could include the dash and space? That would be adding a dash? Actually the dash is part of the original line; it's there. So we could output the dash as part of the li content, but then we would have "- Complying..." inside
            • . That would preserve the dash. But the dash is not part of the sentence; it's a bullet marker. The instruction didn't say we cannot include bullet markers. It says use
              • for list items. So we can output
              • - Complying with the fit and proper standards...
              . That would preserve the dash and the rest. That seems acceptable. But we must not add any extra text. So we should output exactly the same lines, but wrapped appropriately. We need to decide how to structure HTML. Potential structure:

              Purpose Statement

              - To be responsible for and promote an adequate level of compliance in Capitec’s Insurance business so that Capitec meets and complies with regulatory and statutory requirements.

              - Accountable for the strategic direction and operational effectiveness of the Compliance department within Capitec’s Insurance business.

              - To lead and manage the Compliance function, accountable for optimising performance through business planning, budgets, goals and metrics, people, standards, principles and processes.

              But the original has bullet points each on separate lines. Could we wrap each bullet as a separate

              ? The instruction says use

              for introductory paragraphs and general text. Use

              • for list items (duties, requirements, qualifications, skills). So maybe we should use
                • for the bullet items under sections like Experience, Qualifications, Key Performance Areas, Knowledge, Skills. For Purpose Statement, it's not a list? It is a list of bullet points? Actually Purpose Statement includes three bullet points. Those are duties? Could be considered list items. So we could use
                  • for each bullet under Purpose Statement as well. But the instruction says use
                    • for list items (duties, requirements, qualifications, skills). Purpose Statement is not explicitly listed, but it's a set of statements. Could treat them as list items. But maybe better to keep them as separate

                      lines? The instruction says use

                      for introductory paragraphs and general text. So we could treat the bullet points as general text? But they are bullet points. The instruction specifically says use

                      • for list items (duties, requirements, qualifications, skills). So we should use
                        • for those categories. For Purpose Statement, it's not a duty/requirement/qualification/skill, but it's a set of statements. Could just wrap each bullet as

                          maybe? But the instruction says use

                          • for list items (duties, requirements, qualifications, skills). It doesn't say we cannot use
                            • for other list items. But to be safe, we can use
                              • for all bullet points across the document. That would preserve content and use proper list semantics. But we also need to use

                                for section headers. So we can output:

                                Purpose Statement

                                • - To be responsible for and promote an adequate level of compliance in Capitec’s Insurance business so that Capitec meets and complies with regulatory and statutory requirements.
                                • - Accountable for the strategic direction and operational effectiveness of the Compliance department within Capitec’s Insurance business.
                                • - To lead and manage the Compliance function, accountable for optimising performance through business planning, budgets, goals and metrics, people, standards, principles and processes.
                                Then next section "Experience". Use

                                Experience

                                . Then maybe subheadings "Minimum:" and "Ideal:"? The original has "Minimum:" and "Ideal:" as labels. Should we treat them as headings? Could use

                                Minimum

                                and then list items? But the instruction says use

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

                                Experience

                                . Then we have bullet points under "Minimum:" and "Ideal:". Those are list items. So we can output:

                                Experience

                                Minimum

                                ? But we only can use

                                for section headers. The instruction only mentions

                                for section headers, not other heading levels. So we should not use

                                . So we could just treat "Minimum:" as part of the list? Or we could just output the bullet items under "Minimum:" as list items, maybe preceded by a label? The original has "- Minimum:" then bullet items? Actually the original shows: Experience Minimum: - Complying with the fit and proper standards contained in the Generally Accepted Compliance Practice (GACP) - 8-10 years’ proven experience in all matters related to legislative and regulatory requirements, in compliance management in the financial services industry, with exposure to insurance in at least 5 of the years Ideal: - More than 10 years’ experience leading all matters related to legislative and regulatory requirements within a similar industry - 7 years’ proven experience in compliance / risk management in the financial services/insurance industry - 7 years’ experience in managing a team of specialists within a similar environment - Proven experience in operating at a senior management level So there are labels "Minimum:" and "Ideal:" preceding bullet lists. Should we treat them as headings? Could use

                                Minimum

                                and

                                Ideal

                                maybe? But the instruction says use

                                for section headers like Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role. It doesn't mention "Minimum" or "Ideal". So maybe we should not add extra headings. We could just output the bullet items under "Experience" as list items, preserving the "Minimum:" and "Ideal:" labels as part of the text? But those labels are not part of the bullet content; they are labels preceding the bullet lists. The original includes them as separate lines. If we omit them, we are removing content. So we must preserve them. Could we output them as plain text paragraphs? For example:

                                Minimum:

                                • - Complying with the fit and proper standards...
                                ...

                                But that would add

                                Minimum:

                                which is a paragraph containing "Minimum:" exactly as in original. That preserves the label. That seems okay. But we need to preserve all original content word-for-word. So we must include "Minimum:" exactly as appears, including colon. So we can output

                                Minimum:

                                then the list items. That adds a

                                tag around "Minimum:" which is not in original but we are adding markup. The instruction says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. Adding a

                                tag is not part of the content; it's markup. That's allowed because we are formatting, not altering content. The content inside the tag must be exactly "Minimum:". That's fine. Thus we can structure each section with

                                SectionHeader

                                then maybe a

                                for the label if present, then

                                • for bullet items. But we must be careful not to add any extra text beyond what's in original. For example, the original has "Qualifications (Minimum)" and "Qualifications (Ideal or Preferred)". Should we output those as headings? The instruction says use

                                  for section headers like Qualifications. So we could output

                                  Qualifications (Minimum)

                                  and then the bullet items. But the original includes the parentheses and text. So we need to preserve that exactly. So we can output

                                  Qualifications (Minimum)

                                  . That includes the parentheses and text exactly. That is a header. That seems okay. Similarly for "Qualifications (Ideal or Preferred)" we can output

                                  Qualifications (Ideal or Preferred)

                                  . For "Key Performance Areas" maybe we output

                                  Key Performance Areas

                                  . For "Knowledge" we output

                                  Knowledge

                                  . For "Skills" we output

                                  Skills

                                  . For "Conditions of Employment" maybe we output

                                  Conditions of Employment

                                  then a paragraph. For "Capitec is committed..." maybe that's a paragraph, not a heading. Could just output

                                  Capitec is committed to diversity and, where feasible, all appointments will support the achievement of our employment equity goals.

                                  . For "How to Apply:" we have numbered list. We can output

                                  How to Apply

                                  then
                                  • 1. To see what life at Capitec is all about and complete a short assessment, please click here!
                                  ... etc. Now we must ensure we preserve all original content word-for-word. That includes punctuation, line breaks, etc. We need to replicate exactly the text as appears, but we can wrap in tags. We must not add any extra content. So we must not add any extra words, not even "Section:" etc. Now let's construct the HTML step by step. First, the job description starts with "Purpose Statement". Then bullet points. Then "Experience". Then "Minimum:" then bullet points, then "Ideal:" then bullet points. Then "Qualifications (Minimum)". Then bullet point. Then "Qualifications (Ideal or Preferred)". Then bullet point. Then "Key Performance Areas". Then bullet points (maybe multiple). Then "Knowledge". Then "Minimum:" then bullet points, then "Ideal:" then bullet points. Then "Skills". Then bullet points (maybe each bullet is a skill). Then "Conditions of Employment". Then a paragraph. Then "Capitec is committed..." paragraph. Then "How to Apply:". Then numbered list items. We need to preserve bullet points exactly as they appear, including hyphens and spaces. For list items, we will wrap each bullet line in
                                  • and include the hyphen and space as part of the content. That preserves the dash. But we must be careful: The bullet lines under "Key Performance Areas" start with "- Develop and execute the compliance strategy". That's a bullet. We'll output
                                  • - Develop and execute the compliance strategy
                                  . That includes the dash and space. Now we need to decide how to handle the "Minimum:" and "Ideal:" labels. They appear as separate lines before the bullet lists. Should we output them as separate

                                  elements? Yes, to preserve them exactly. So we can output

                                  Minimum:

                                  then the
                                  • items. But the original has "Minimum:" on its own line, then bullet items. So we can output

                                    Minimum:

                                    then
                                    ... list items ...
                                    . That preserves the label exactly. But the instruction says use
                                    • for list items (duties, requirements, qualifications, skills). It doesn't say we cannot have a

                                      for the label. So that's fine. Now we need to ensure we don't add any extra text. So we must not add any extra headings beyond

                                      for section headers. The section headers are the titles like "Purpose Statement", "Experience", "Qualifications (Minimum)", etc. So we will output

                                      Purpose Statement

                                      then the bullet list. Then

                                      Experience

                                      then

                                      Minimum:

                                      then the bullet list under Minimum, then

                                      Ideal:

                                      then bullet list under Ideal. Then

                                      Qualifications (Minimum)

                                      then bullet list. Then

                                      Qualifications (Ideal or Preferred)

                                      then bullet list. Then

                                      Key Performance Areas

                                      then bullet list items. Then

                                      Knowledge

                                      then

                                      Minimum:

                                      then bullet list, then

                                      Ideal:

                                      then bullet list. Then

                                      Skills

                                      then bullet list items. Then

                                      Conditions of Employment

                                      then paragraph. Then maybe a paragraph for "Capitec is committed..." (no heading). Then

                                      How to Apply

                                      then numbered list. Now we must ensure we preserve all original bullet content exactly, including punctuation and line breaks. We'll output each bullet as a separate
                                    • element. Now let's write the HTML. First line:

                                      Purpose Statement

                                      Then bullet items:
                                      • - To be responsible for and promote an adequate level of compliance in Capitec’s Insurance business so that Capitec meets and complies with regulatory and statutory requirements.
                                      • - Accountable for the strategic direction and operational effectiveness of the Compliance department within Capitec’s Insurance business.
                                      • - To lead and manage the Compliance function, accountable for optimising performance through business planning, budgets, goals and metrics, people, standards, principles and processes.
                                      But the instruction says use
                                      • for list items. It doesn