Audit Department.Information Systems Audit Manager

,

,

• . They don't mention . Since the original content uses tables for structured data, I think I should keep them as tables since they're part of the original content structure. Actually, looking at the rules again: "Use
  • for list items (duties, requirements, qualifications, skills)". This suggests that qualifications should be in a list format rather than a table. But the original content has tables for qualifications. Hmm. The rule says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". So I should keep the table structure as is, since it's part of the original content. But wait, the rules also say "Use
    • for list items (duties, requirements, qualifications, skills)". This could mean I should convert the qualification tables into lists. But that would change the structure. I think the safest approach is to keep the tables as they are, since they're part of the original content and the rules don't explicitly forbid tables. The rules focus on

      ,

      ,

      • for specific purposes, but don't prohibit tables. Actually, re-reading: "If text has no clear sections, just wrap paragraphs in

        tags". And the rules about lists are for "list items (duties, requirements, qualifications, skills)". The qualifications ARE listed in a table format. I think keeping the tables is fine since they preserve the original content. Let me also note: the text mentions "[1]" and "[2]" footnotes which are reference numbers. These seem like formatting artifacts. The rule says "Stray numbers or formatting artifacts" should be removed. But these are reference markers [1], [2] that appear in the Need Type column. Are these "stray numbers"? They seem to be footnote references. I'll keep them since they're part of the original content structure, but actually the rule says to remove "Stray numbers or formatting artifacts". Hmm, but these are part of the table content (Need Type column shows RQ, ES, AA). The [1] and [2] are footnote links. I think I should keep them as they're part of the original content. Actually wait, looking more carefully at the instruction: "REMOVE all of the following: ... Stray numbers or formatting artifacts". The [1] and [2] are reference numbers that appear as superscript links. These could be considered formatting artifacts. But they're part of the original content. I'll keep them since they're integral to the table structure. Hmm, but actually the Need Type values (RQ, ES, AA) are the actual data. The [1] and [2] are just footnote references. I think I should keep the Need Type values but could remove the footnote links. Actually, the rule says "Preserve ALL original content word-for-word", so I should keep everything. Let me reconsider. The instruction says to REMOVE "Stray numbers or formatting artifacts". The [1] and [2] are reference numbers/links. But they're part of the original content. I think the safest interpretation is to keep them since they're part of the original text structure. Actually, I'll keep them. The instruction to remove stray numbers is probably more about things like page numbers, dates, etc. that are clearly not part of the job content. Reference numbers in footnotes are part of the document structure. Now, regarding the empty paragraphs ( ): The rules say to use

        for paragraphs. Empty paragraphs with   should probably be removed or kept as empty

        tags. Since the rule says "Preserve ALL original content word-for-word", I'll keep them as empty

        tags. Actually, an empty

        tag might not make sense. Let me think... The original has `

         

        ` which is an empty paragraph. I'll convert these to `

         

        ` or just remove them. Since the rule says preserve all content, I'll keep them as `

         

        `. Wait, but the rule says "No
        tags". An empty

        is different from a
        . An empty

        is fine. Let me also consider: should I convert the qualification tables to lists? The rule says "Use

        • for list items (duties, requirements, qualifications, skills)". This suggests qualifications should be in a list. But the original has tables. The rule also says "Preserve ALL original content word-for-word". I think the intent is that if the original content is in a list format, convert it to
          • . If it's in a table, keep it as a table. The rule about using
            • is for when you need to present list items, not necessarily to convert everything to lists. Actually, re-reading more carefully: "Use
              • for list items (duties, requirements, qualifications, skills)". This is telling me HOW to format list items. It doesn't say to convert tables to lists. The original content already has tables for qualifications, so I should keep them as tables. OK, let me finalize my output. I'll keep the tables as they are, preserving all content. One more thing: the Experience Area 4 row seems to be cut off in the input ("border-style: none so"). I'll complete it based on context - it should say "Core Banking Technology and other Bank applications functionalities" with some minimum years. Looking at the pattern, it likely has a minimum number of years too. But since the text is cut off, I'll just include what's available. Actually, the text ends abruptly with "border-style: none so" which is clearly incomplete. I should probably just include what I can reasonably infer. But the rule says "Preserve ALL original content word-for-word". Since the content is cut off, I'll include what's there and note the incomplete nature. Actually, looking at the pattern of the table, each row has: Detail | Minimum No of Years | Need Type. For Experience Area 4, the Detail is "Core Banking Technology and other Bank applications functionalities" and the minimum years would follow the pattern. But since the text is cut off, I'll just include what's available. Let me write the final HTML now. Actually, I realize I should double-check: the rules say "Return ONLY the HTML. No markdown fences, no explanation, no preamble." So I should just output the HTML directly. Also, regarding the empty paragraphs - I think I should keep them as `

                 

                ` to preserve the original structure, or I could omit them. The rule says "Preserve ALL original content word-for-word", so I'll keep them. Wait, actually, looking at the empty paragraphs again: `

                 

                `. These are empty paragraphs used as spacing. In HTML, an empty

                is valid. I'll keep them as `

                 

                `. Hmm, but actually, should I keep the `style` attributes? The rules say "No CSS classes, no inline styles". So I need to remove all style attributes. The `style="text-align: justify;"` should be removed. The `style="font-family: Arial, sans-serif;"` should be removed. Etc. So my output should have NO style attributes anywhere. Just clean semantic HTML. Let me also handle the `

                ` and `

  ` elements. The figure wrapper isn't needed, and the class attribute should be removed. I'll just use `` directly. For the `
  ` lists that wrap the section headers, I should convert them to `

  ` headers directly. Let me draft the final HTML: ```html

  KEY RESPONSIBILITIES

  • Consistently document relevant facts and information that support the work performed and conclusions drawn in individual audit engagement reports and audit issues tracking.
  • Designing and building small automation solutions and queries for use by Internal Audit.
  • Develop audit tests and evaluation programs, execute the audit assignments, ensuring quality and report on the audit results with appropriate recommendations for corrective measures to be undertaken in areas of weaknesses.
  • Lead audits of specific target areas identified from the overall risk assessment in consultation with the Head of Audit, to ensure quality audit approach in in accordance with professional standards, achievement of set audit objectives and completion within agreed schedule.
  • Identify and analyze level of threat and potential risk to the Bank IS assets risk and threats which may translate into losses, in both assurance audit engagements or advisory as may be assigned.
  • Implement continuous audits more leveraging on automated Audit Tools
  • Assist the Bank in incorporating best practice standards / policies in the management of it's IT/IS resources. E.g. COBIT and other IT related ISOs.
  • Participate in the Annual Risk Assessments leading to the compilation of the Risk Based Annual Audit Plan
  • Support the Head of Internal Audit and the team in meeting Board, Senior Management, regulatory, and other key stakeholders reporting requirements.
  • Supervise, coach, mentor and develop IS Audit staff in line with the succession plan of the department.

   

  Academic & Professional

   

  Particulars	Detail	Specific Field or Qualification	Need Type
  Education	Bachelor's degree	Computer Science/Information Technology	RQ
  Professional Qualifications	CISA/CISM	CISA/CISM	RQ
  Masters Degree	Masters Degree	Business Administration/MSC IT	AA

   

  Experience

   

  Various position as detailed below	5 years
  Experience Area 1 (IT Data Analysis and Management experience)	3
  Experience Area 2 (Information Systems Audit)	5
  Experience Area 3 (Use of Automated data analysis tools)	3
  Experience Area 4 (Core Banking Technology and other Bank applications functionalities)

  ``` Wait, I need to reconsider the Experience Area 4 row. The original text is cut off. Let me look at what's there: ``` Experience Area 4 (Core Banking Technology and other Bank applications functionalities