Cyber Security Engineer

for intro paragraphs and general text,

for section headers,

• for list items. 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 headings beyond h4. Use h4 for section headers like Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role. The job description includes sections: "Experience", "Ideal", "Knowledge", "Qualifications", "Technical capabilities", "Conditions of Employment". Also there is introductory paragraph "Join a specialised Data Security team" and then description paragraphs. We need to structure accordingly. We must preserve all original content word-for-word. So we must include exactly the same text, including bullet points and line breaks? We need to output HTML only. Use

  for paragraphs and general text. Use

  for section headers. Use

  • for list items. We need to decide which parts are headings. The raw text includes "Experience", "Ideal", "Knowledge", "Qualifications", "Technical capabilities", "Conditions of Employment". Also there is "Minimum:" and "Ideal:" lines preceding bullet lists. Those are part of the text; we can treat them as part of paragraph? Probably we should make them headings? 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 can use

    Experience

    etc. But the text includes "Experience" as a heading? Actually the raw text shows "Experience" then "Minimum:" etc. So we can treat "Experience" as a section header and wrap in

    . Then under that we have bullet lists with "Minimum:" and "Ideal:" maybe as subheadings? But we need to preserve all original content word-for-word. So we cannot change "Minimum:" to something else; we must keep it as part of the text. But we can embed it within a

    or

    • . The bullet points are preceded by hyphens. We need to output them as
    • items. The bullet list items include "Minimum:" line? Actually the bullet list items are: - 3-5 years of experience in security engineering or a related technical role. - Proven experience building, implementing, managing security solutions. - Experience across cloud, DevOps, infrastructure or software engineering environments - Exposure to CI/CD tools (e.g. GitLab, GitHub) and automation practices - Working knowledge of cloud platforms (AWS preferred, Azure/GCP advantageous) - Hands-on experience with security tools and technologies, Proficiency in automation. Then "Ideal:" line appears as a heading? Actually after that there is "Ideal:" then "Experience" bullet? Wait the raw text: Experience Minimum: - 3-5 years of experience in security engineering or a related technical role. - Proven experience building, implementing, managing security solutions. - Experience across cloud, DevOps, infrastructure or software engineering environments - Exposure to CI/CD tools (e.g. GitLab, GitHub) and automation practices - Working knowledge of cloud platforms (AWS preferred, Azure/GCP advantageous) - Hands-on experience with security tools and technologies, Proficiency in automation. Ideal: - Experience in cloud platforms is highly desirable. - 2-3 years DevOps experience. So "Ideal:" is a label, then bullet items. So we need to preserve "Ideal:" as part of the text. How to format? Could be a

      "Ideal:" then list items? But we need to preserve word-for-word. So we could have a

      "Ideal:" then

      items. But the instruction says use
      • for list items (duties, requirements, qualifications, skills). So we can have a

        "Ideal:" then

        items. But "Ideal:" is not a list item; it's a label. Could be part of a paragraph preceding the list. But we need to preserve it exactly. So maybe we can have a

        "Ideal:" then a

        with
        • items. That would preserve "Ideal:" as separate text before the list. That seems okay. Similarly "Knowledge" appears as a heading? The raw text shows "Knowledge" then "Minimum:" etc. So we can treat "Knowledge" as a section header

          Knowledge

          . Then under that we have "Minimum:" and bullet items, then "Ideal:" and bullet items. But we need to preserve "Minimum:" and "Ideal:" labels. So we can have

          Minimum:

          then
          items. But "Minimum:" is not a list item; it's a label. Could be part of a paragraph. But we need to preserve it exactly. So we could have

          Minimum:

          then
          items. That would preserve the colon and spacing? The original has "Minimum:" on its own line, then bullet items. So we could output

          Minimum:

          then
          ... items ...
          . That would preserve the "Minimum:" text as a paragraph. Then the bullet items as
          • items. But the instruction says use
            • for list items (duties, requirements, qualifications, skills). So bullet items should be in
            • . The label "Minimum:" is not a list item; it's a label. So we can keep it as a separate

              Minimum:

              . That preserves it. Similarly "Qualifications" appears as a heading? The raw text shows "Qualifications" then "Minimum:" then bullet items, then "Ideal or Preferred:" then bullet items. So we can treat "Qualifications" as a section header

              Qualifications

              . Then

              Minimum:

              then
              items. Then

              Ideal or Preferred:

              then
              items. But "Ideal or Preferred:" includes "Ideal or Preferred:" exactly as in original? The original says "Ideal or Preferred:" then bullet items. So we need to preserve that exact phrase. So we can output

              Ideal or Preferred:

              then
              items. Then "Technical capabilities" appears as a heading? The raw text shows "Technical capabilities" then bullet list of capabilities. So we can output

              Technical capabilities

              then
              items. Then "Conditions of Employment" appears as a heading? The raw text shows "Conditions of Employment" then bullet item. So we can output

              Conditions of Employment

              then

              Clear criminal and credit record

              maybe as a paragraph (since it's not a list? Actually it's a bullet item? The original shows "Conditions of Employment" then "- Clear criminal and credit record". That's a bullet item. So we could output
              • Clear criminal and credit record
              . But the instruction says use
              • for list items (duties, requirements, qualifications, skills). So we can put it in a
                • ...">
                . That would be fine. Now the introductory paragraph: "Join a specialised Data Security team" then a blank line then "To implement, support and manage Cyber Security solutions..." etc. That's a paragraph. So we can wrap that in

                Join a specialised Data Security team

                then

                To implement, support and manage Cyber Security solutions to protect systems, networks, users and data from cyber threats, assist in safeguarding Capitec’s digital assets and ensuring the confidentiality, integrity and availability of information.

                then maybe another paragraph: "To design, build, implement, support and collaborate with Cyber Security colleagues and Capitec teams, participating in engineering and contributing to the delivery success of projects, based on specifications, while adhering to established standards." That's another paragraph. We need to preserve all original content word-for-word. So we must include exactly those sentences. Also we must preserve the line breaks? Not needed; we just output HTML. We must not add any extra commentary. So output only the HTML. Now we need to decide the order of sections. The raw text order: - "Join a specialised Data Security team" (intro) - Then description paragraphs (two paragraphs) - Then "Experience" heading - Then "Minimum:" bullet list - Then "Ideal:" bullet list - Then "Knowledge" heading - Then "Minimum:" bullet list - Then "Ideal:" bullet list - Then "Qualifications" heading - Then "Minimum:" bullet list - Then "Ideal or Preferred:" bullet list - Then "Technical capabilities" heading - Then bullet list of technical capabilities - Then "Conditions of Employment" heading - Then bullet item But also there are some headings like "Experience", "Knowledge", "Qualifications", "Technical capabilities", "Conditions of Employment". 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 can use

                Experience

                ,

                Knowledge

                ,

                Qualifications

                ,

                Technical capabilities

                ,

                Conditions of Employment

                . That matches. Now we need to preserve "Minimum:" and "Ideal:" labels. They are not headings; they are part of the text. So we can output them as

                Minimum:

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

                Minimum:

                then
                ... items ...
                . That preserves the colon and line break? The colon is part of the text. So

                Minimum:

                will output "Minimum:" as a paragraph. That's fine. But the bullet items themselves start with hyphens. In HTML, we need to output
                • item text without the hyphen? The bullet hyphen is part of the original text? The raw text shows "- 3-5 years of experience..." So the hyphen is part of the list marker, not part of the content. The instruction says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. Should we include the hyphen? The hyphen is part of the formatting, but it's not part of the content? It is part of the list marker. The instruction says preserve ALL original content word-for-word. That includes the hyphen? Probably yes, but we are using
                • to represent list items; we should not include the hyphen because it's not part of the content; it's just a marker. However, the instruction says "preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". Including the hyphen would be adding a character? Actually the hyphen is part of the original line; but if we output
                • 3-5 years of experience in security engineering or a related technical role.
                , we are removing the hyphen. That would be removing content. But the hyphen is not part of the content; it's a bullet marker. The instruction says "preserve ALL original content word-for-word". The content includes the bullet points text; the hyphen is not part of the text content, it's just a marker. Usually we would not include the hyphen in the output. But to be safe, we could include the hyphen as part of the
                • text? That would be adding a hyphen that wasn't originally part of the content? The original line starts with "- ". The hyphen and space are part of the line. If we output
                • - 3-5 years ...
                that would include the hyphen and space. But that would be adding a hyphen before the content, which is not present in the original content (the content after the hyphen). The original content after the hyphen is "3-5 years of experience...". So we should output that content without the hyphen. So it's okay. Thus we will output
                • 3-5 years of experience in security engineering or a related technical role.
                etc. Now we need to preserve the bullet items exactly as they appear, including punctuation, parentheses, etc. So we must copy them exactly. Now we need to output the HTML. Let's construct step by step. First paragraph: "Join a specialised Data Security team" HTML:

                Join a specialised Data Security team

                Second paragraph: "To implement, support and manage Cyber Security solutions to protect systems, networks, users and data from cyber threats, assist in safeguarding Capitec’s digital assets and ensuring the confidentiality, integrity and availability of information." HTML:

                To implement, support and manage Cyber Security solutions to protect systems, networks, users and data from cyber threats, assist in safeguarding Capitec’s digital assets and ensuring the confidentiality, integrity and availability of information.

                Third paragraph: "To design, build, implement, support and collaborate with Cyber Security colleagues and Capitec teams, participating in engineering and contributing to the delivery success of projects, based on specifications, while adhering to established standards." HTML:

                To design, build, implement, support and collaborate with Cyber Security colleagues and Capitec teams, participating in engineering and contributing to the delivery success of projects, based on specifications, while adhering to established standards.

                Now section header "Experience". Use

                Experience

                Then "Minimum:" label. We'll output

                Minimum:

                then
                items. Bullet items under Minimum: - 3-5 years of experience in security engineering or a related technical role. - Proven experience building, implementing, managing security solutions. - Experience across cloud, DevOps, infrastructure or software engineering environments - Exposure to CI/CD tools (e.g. GitLab, GitHub) and automation practices - Working knowledge of cloud platforms (AWS preferred, Azure/GCP advantageous) - Hands-on experience with security tools and technologies, Proficiency in automation. We need to output each as
                • ... item ...
                . Preserve punctuation exactly. Now "Ideal:" label. Output

                Ideal:

                then
                items. Bullet items: - Experience in cloud platforms is highly desirable. - 2-3 years DevOps experience. Now section header "Knowledge". Use

                Knowledge

                Then "Minimum:" label again. Output

                Minimum:

                then
                items. Bullet items: - Basic understanding of at least one high-level programming language (GoLang / .net / Java / python) - Advanced scripting skills in at least one interpreted language (Bash/PowerShell) - Design and deployment of highly available, enterprise-scale Cloud infrastructure - Advance knowledge of infrastructure concepts, technologies and patterns - Supporting and enhancing build and release processes through automation Now "Ideal:" label. Output

                Ideal:

                then
                items. Bullet items: - Previous experience in a DevOps role and incorporating security controls in the build process. - Experience in engineering data and/or security log pipelines using Big Data technologies such as Spark, Kafka, Hadoop, Storm, etc. - Demonstrated experience in designing, implementing, and managing data security solutions for structured and unstructured data. - Understanding of modern software engineering patterns, including those used in highly scalable, distributed, and resilient systems. - Experience working with cross-functional teams and providing data security guidance to developers and IT staff. - Familiarity with regulatory requirements and industry standards related to data protection. Now section header "Qualifications". Use

                Qualifications

                Then "Minimum:" label. Output

                Minimum:

                then
                items. Bullet items: - A relevant tertiary qualification in AWS Foundation or Cloud Computing Now "Ideal or Preferred:" label. Output

                Ideal or Preferred:

                then
                items. Bullet items: - Bachelor's Degree in Information Technology or Engineering – OtherRelevant certifications such as CISSP, CISM, CISA, or other security-related certifications.AWS Data/Security certification Note: The original text: "Ideal or Preferred: Bachelor's Degree in Information Technology or Engineering – OtherRelevant certifications such as CISSP, CISM, CISA, or other security-related certifications.AWS Data/Security certification" There is no bullet marker? Actually the original shows "Ideal or Preferred:" then "Bachelor's Degree in Information Technology or Engineering – OtherRelevant certifications such as CISSP, CISM, CISA, or other security-related certifications.AWS Data/Security certification". It seems they omitted bullet markers; it's just a paragraph? Actually the raw text shows: Qualifications Minimum: A relevant tertiary qualification in AWS Foundation or Cloud Computing Ideal or Preferred: Bachelor's Degree in Information Technology or Engineering – OtherRelevant certifications such as CISSP, CISM, CISA, or other security-related certifications.AWS Data/Security certification So "Ideal or Preferred:" is a label, then the text is not bullet list but a paragraph that includes multiple sentences separated by periods. It includes "Bachelor's Degree in Information Technology or Engineering – OtherRelevant certifications such as CISSP, CISM, CISA, or other security-related certifications.AWS Data/Security certification". There's no bullet marker. So we need to preserve that exact text as a paragraph. So we should output

                Ideal or Preferred:

                then

                Bachelor's Degree in Information Technology or Engineering – OtherRelevant certifications such as CISSP, CISM, CISA, or other security-related certifications.AWS Data/Security certification

                . But the instruction says use
                • for list items (duties, requirements, qualifications, skills). This is not a list item; it's a paragraph. So we can output it as a paragraph

                  ...

                  . That preserves the text exactly. Now "Technical capabilities" heading. Use

                  Technical capabilities

                  Then bullet list of technical capabilities: - Cloud security principles - Data protection (encryption, masking, DLP) - Access control and identity management - Scripting (e.g. Bash, PowerShell, Python