Cloud Engineer II

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, maybe Preferred Qualifications? The instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Include a section only when posting has real, specific content. So we need sections: About the role, Responsibilities, Requirements, Preferred Qualifications? The posting includes "Preferred Qualifications Azure or GCP experience would be advantageous." That's a specific content, so we can include a section maybe "Preferred Qualifications". Also there is "Grade 12 National Certificate / Vocational A relevant tertiary qualification in Information Technology - Computer Science Clear criminal and credit record". That's part of Requirements. Also there is "This role offers: Complex multi-account and multi-region cloud architecture. High-impact networking and cloud infrastructure challenges. A strong engineering culture. Collaboration with skilled technical teams. Continuous learning and growth. The opportunity to help build foundational infrastructure that matters". That could be considered Benefits? It's more like role offers. Could be considered "Benefits" or maybe "What we offer". The instructions list Benefits as possible heading. Since there is content about what the role offers, we could put that under Benefits. However we need to ensure we don't create sections with filler like "commensurate with experience". This is substantive. So we can include Benefits section. Also there is no explicit Pay or Schedule, so we omit those. We must not repeat job title as heading. No Job ID. We need to preserve all substantive information. So we need to include all bullet points etc. We need to use

• for any list of duties/requirements/benefits, and

  for prose. We need to parse the text. Let's extract sections: About the role: paragraph(s) after "About the Role". It says: "At Capitec, we design, deploy and maintain resilient, scalable, cost-effective and high-performing cloud-native solutions that support our ambition to become the best bank in the world." That's it. Responsibilities: big block after "Responsibilities". Contains multiple paragraphs and a list after "This includes:" with bullet-like items. We need to turn duties into

  • . Also there are prose paragraphs before the list. We need to preserve all info. Let's break responsibilities text: "This role sits at the point where our cloud platform meets the network it runs on. We are looking for a Cloud Engineer II with a strong networking foundation—someone who understands traditional networking, cloud networking, security and complex infrastructure environments. You will join our Cloud Core Engineering team, the specialist group responsible for the foundational cloud infrastructure that the rest of the organisation builds on. The team manages the core AWS platform and networking layer, supporting systems used by millions of clients every day. The role has no direct reports, so the focus is on technical depth, engineering excellence and hands-on contribution." Then: "You will design and deploy cloud solutions in line with information security and governance frameworks, regulatory requirements, high availability principles, scalability and capacity planning. This includes:" then list items: - Creating detailed planning and implementation documentation. - Documenting designs, specifications and operational procedures. - Preparing handover documentation. - Carrying out complex deployments. - Liaising with stakeholders to plan and deliver work. - Supporting knowledge transfer to operational and support teams. Then: "You will help ensure our infrastructure remains secure, stable, cost-effective and reliable." then list: - Automating deployments and testing. - Following standard operating procedures and documentation requirements. - Maintaining compliance with internal, industry and regulatory security standards. - Managing configuration standards for new deployments. - Tracking costs, usage, constraints and risks. - Supporting monitoring, alerting and availability. - Providing third-level support for critical infrastructure issues. Then: "You will work closely with internal teams, clients, suppliers and partners, contributing technical expertise and helping teams make strong engineering decisions." then list: - Influencing technical decisions. - Supporting collaboration across teams. - Contributing knowledge on cloud engineering trends and best practices. - Helping cloud engineering resources align to business workload. Then: "You will play an active role in improving how we work." then list: - Coaching and being coached. - Building your technical knowledge in ways that benefit the business. - Suggesting process, coding and automation improvements. - Contributing to Communities of Practice. - Keeping the knowledge base and engineering procedures current. Thus responsibilities consist of multiple prose paragraphs and lists. We can combine them into a single
    maybe? But better to keep prose paragraphs separate and then lists. We need to use

    for prose,

    • for any list of duties/requirements/benefits. Thus we will output:

      About the role

      At Capitec, we design, deploy and maintain resilient, scalable, cost-effective and high-performing cloud-native solutions that support our ambition to become the best bank in the world.

      Responsibilities

      This role sits at the point where our cloud platform meets the network it runs on. We are looking for a Cloud Engineer II with a strong networking foundation—someone who understands traditional networking, cloud networking, security and complex infrastructure environments. You will join our Cloud Core Engineering team, the specialist group responsible for the foundational cloud infrastructure that the rest of the organisation builds on. The team manages the core AWS platform and networking layer, supporting systems used by millions of clients every day. The role has no direct reports, so the focus is on technical depth, engineering excellence and hands-on contribution.

      You will design and deploy cloud solutions in line with information security and governance frameworks, regulatory requirements, high availability principles, scalability and capacity planning. This includes:

      • Creating detailed planning and implementation documentation.
      • Documenting designs, specifications and operational procedures.
      • Preparing handover documentation.
      • Carrying out complex deployments.
      • Liaising with stakeholders to plan and deliver work.
      • Supporting knowledge transfer to operational and support teams.

      You will help ensure our infrastructure remains secure, stable, cost-effective and reliable.

      • Automating deployments and testing.
      • Following standard operating procedures and documentation requirements.
      • Maintaining compliance with internal, industry and regulatory security standards.
      • Managing configuration standards for new deployments.
      • Tracking costs, usage, constraints and risks.
      • Supporting monitoring, alerting and availability.
      • Providing third-level support for critical infrastructure issues.

      You will work closely with internal teams, clients, suppliers and partners, contributing technical expertise and helping teams make strong engineering decisions.

      • Influencing technical decisions.
      • Supporting collaboration across teams.
      • Contributing knowledge on cloud engineering trends and best practices.
      • Helping cloud engineering resources align to business workload.

      You will play an active role in improving how we work.

      • Coaching and being coached.
      • Building your technical knowledge in ways that benefit the business.
      • Suggesting process, coding and automation improvements.
      • Contributing to Communities of Practice.
      • Keeping the knowledge base and engineering procedures current.
      Now Requirements: after "Requirements". The text: "We are looking for real, demonstrable depth in networking, including:" then list items. Then later: "A deep understanding of cloud computing concepts and technologies." etc. Then "Hands-on experience designing, deploying and managing solutions on AWS." etc. Then "Working knowledge of CI/CD tooling and DevOps practices." etc. Then "Scripting and provisioning experience with tools such as: Terraform Ansible CloudFormation Equivalent infrastructure automation tools". Then "3+ years’ experience in cloud computing, ideally across more than one platform." Then "This is a technical role with real impact." etc. Then "You will work on infrastructure that supports multiple engineering teams and services used by millions of clients. Your decisions will influence how teams connect, scale and secure their services." Then "This role offers: Complex multi-account and multi-region cloud architecture. High-impact networking and cloud infrastructure challenges. A strong engineering culture. Collaboration with skilled technical teams. Continuous learning and growth. The opportunity to help build foundational infrastructure that matters". Then "Grade 12 National Certificate / Vocational A relevant tertiary qualification in Information Technology - Computer Science Clear criminal and credit record". Then "Preferred Qualifications Azure or GCP experience would be advantageous." We need to separate Requirements section (maybe includes the bullet list and also the prose about impact etc). The "This role offers:" could be Benefits. The qualifications (Grade 12 etc) also part of Requirements. Preferred Qualifications separate. Thus we will have sections: Requirements, Benefits, Preferred Qualifications. We must not create sections with filler. All have content. Now parse Requirements content. First paragraph: "We are looking for real, demonstrable depth in networking, including:" then list: - Strong knowledge of networking protocols, network architecture and network security. - Practical experience with public and hybrid cloud networking. - Understanding of how traditional network design principles translate into cloud environments. - Hands-on experience with authentication and authorisation protocols such as: LDAP Kerberos Active Directory OAuth 2.0 OpenID Connect SAML - The ability to troubleshoot connectivity issues from first principles. - Experience working with complex networking environments, ideally including: Routing Switching Firewalls VPNs VPCs Transit Gateways Direct Connect / DX Hybrid connectivity Network segmentation Network security controls That's a list. Then after that: "A deep understanding of cloud computing concepts and technologies." (maybe a sentence). Then "Hands-on experience designing, deploying and managing solutions on AWS." Then "Cloud-native solution design using APIs, containers, Kubernetes and service mesh." Then "Experience introducing cloud technology into an environment from scratch." Then "Design and troubleshooting experience on AWS." Then "Experience developing and supporting infrastructure for microservices-based architectures." Then "Working knowledge of CI/CD tooling and DevOps practices." Then "Comfort with virtualisation technologies such as VMware, Docker and Kubernetes." Then "Scripting and provisioning experience with tools such as: Terraform Ansible CloudFormation Equivalent infrastructure automation tools". Then "3+ years’ experience in cloud computing, ideally across more than one platform." Then "This is a technical role with real impact." Then "You will work on infrastructure that supports multiple engineering teams and services used by millions of clients. Your decisions will influence how teams connect, scale and secure their services." Then after that we have "This role offers:" which we will treat as Benefits. Then "Grade 12 National Certificate / Vocational A relevant tertiary qualification in Information Technology - Computer Science Clear criminal and credit record". This is also part of Requirements (maybe as qualifications). We'll include as a paragraph or list. Thus Requirements section will have multiple paragraphs and lists. We need to decide how to split into prose and lists. We'll treat the initial bullet list as
      . Then each subsequent sentence could be its own

      or we could group similar items into lists. But the instruction: Use

      • for any list of duties/requirements/benefits, and

        for prose. So any list of requirements should be

        . The items like "Strong knowledge of networking protocols..." is a list. The later items like "A deep understanding of cloud computing concepts and technologies." could be considered a list item as well (they are requirements). So we could combine all requirement items into a single list. However some are sentences like "This is a technical role with real impact." That's more prose. But we could still treat as list? Might be odd. Better to separate: list for concrete skill requirements, prose for descriptive statements. Thus we will create a list for the bullet items after "including:" and also for the subsequent bullet-like items (cloud concepts, AWS experience, etc). We'll make a list for those as well. Let's extract all requirement items: From first block: - Strong knowledge of networking protocols, network architecture and network security