OM Bank - Senior Business Analyst

,

,

• . No
  , no
  , no CSS, no inline styles, no extra tags like , , etc. Must preserve original content word-for-word. So we need to extract sections and format accordingly. We need to identify section headers: "Job Description", "KEY RESULT AREAS", "ROLE REQUIREMENTS", "Skills", "Competencies", "Education", "Closing Date", etc. Use

  for section headers. We must preserve all original text exactly, including line breaks? We can wrap paragraphs in

  . Must not add or remove content. So we need to output the same text but wrapped appropriately. We need to remove any stray tags like

  etc. But we must preserve the text inside. The instruction: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". So we cannot change wording, but we can wrap in tags. However we must not keep the original HTML tags like

  etc. We can just output the text content inside

  . The original content includes those tags? The raw text includes HTML tags. Should we keep them? The instruction says preserve ALL original content word-for-word. That includes the HTML tags? Probably yes, but we are to format as clean semantic HTML using only allowed tags. So we need to output the content without the original styling tags, but the textual content must be exactly as in original (including line breaks?). The original includes a lot of HTML tags and styling. We need to extract the textual content and wrap appropriately. Thus we should output something like:

  Job Description

  We are seeking an experienced Senior Business Analyst to join our team. The ideal candidate will have a proven Retail Banking track record and will be responsible for analyzing and documenting business requirements, designing solutions, and ensuring the successful implementation of banking systems and processes. Strong Salesforce knowledge/experience, ideally in a Retail Banking environment is required. The candidate will work in cross-functional Waterfall/Agile teams, including product owners, developers, testers, project managers, and other stakeholders (e.g. Risk) to identify customer and business needs, and translate them into requirements expressed as Use Stories, to ultimately deliver compelling Customer Experiences.

  KEY RESULT AREAS

  • Collaborate with Product Owners and other stakeholders to identify and document business requirements for banking systems and processes
  • Work with product owners and development teams to design and develop solutions that meet customer needs
  • Analyze and translate business requirements into artefacts that define and express the requirements, including:
  • User Stories
  • Acceptance Criteria (Gherkin)
  • Business Processes
  • Business Rules
  • Wireframes
  • Data Requirements
  • Run Refinement sessions
  • Proactively manage project timelines, and deliverables
  • Conduct user acceptance testing and ensure that systems and processes are performing as expected
  • Communicate with stakeholders to provide updates on status and ensure alignment with business goals and objectives
  • Identify opportunities for process improvements and propose solutions to increase efficiency and effectiveness

  ... and so on. We must preserve the exact wording, including punctuation and line breaks? We can keep line breaks within

  maybe not needed. Use

• items as they appear. The original list items are split across many
• with nested etc. We need to extract the text inside each
• exactly as appears, but without extra tags. The original
• content includes extra and   etc. We need to preserve the text exactly as appears, but we can strip the extra tags. However that would be removing tags, which is allowed? The instruction: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". Removing tags might be considered removing content? The tags are not part of the textual content; they are markup. The textual content is the words inside. So we can output the textual content exactly as appears, but we must not alter words. So we can output the text inside the
• exactly as is, including any extra spaces? The original
• includes Collaborate with  Product Owners and other  stakeholders to  identify and document business requirements for banking systems and processes 

. The actual visible text is "Collaborate with Product Owners and other stakeholders to identify and document business requirements for banking systems and processes". There are extra   and tags. We need to preserve the words exactly, but we can output just that sentence. That would be a removal of tags but not removal of words. That should be okay. Thus we need to produce clean HTML with

headers and

• list items. Use

  for paragraphs. We need to include sections: "Skills", "Competencies", "Education", "Closing Date", maybe "The Old Mutual Story!" etc. We must not add any extra commentary. Let's parse the raw text: - There's a heading "Let's Write Africa's Story Together!" but that's maybe not a job title? It's part of intro. Probably we keep it as paragraph. - Then "Old Mutual is a firm believer..." etc. - Then "Job Description" bold. - Then the job description paragraph. - Then "KEY RESULT AREAS" bold. - Then a long list of duties each in

• . - Then "ROLE REQUIREMENTS" bold. - Then sub sections: "Domain Expertise", "Work Experience", "Skills and Qualifications", etc. - Then "Skills" bold. - Then a list of skills separated by commas? Actually it's a paragraph of skills separated by commas. - Then "Competencies" bold. - Then a list of competency names each preceded by
  maybe empty. Actually they are
  tags with nothing. But they are not content. So we can ignore. - Then "Education" bold. - Then "Closing Date" bold with date. - Then a paragraph with italic bold about appointment. - Then "The Old Mutual Story!" italic bold. We need to output clean HTML using only

  ,

  ,

  • . So we can have multiple

    sections. We need to include all content exactly as appears, but we can break into paragraphs. Let's construct: First paragraph: "Let's Write Africa's Story Together!" (but we need to preserve the original text, which includes the HTML entity '. Should we output the entity or the actual apostrophe? The instruction: preserve word-for-word. So we must keep the entity as is: "Let's Write Africa's Story Together!". Probably keep it exactly. Then "Old Mutual is a firm believer in the African opportunity and our diverse talent reflects this." (the text inside ). So we output that as a paragraph. Then maybe blank paragraphs are just empty; we can ignore. Then "Job Description" -> we need a header

    Job Description

    . Then the following paragraph: "We are seeking an experienced Senior Business Analyst to join our team. The ideal candidate will have a proven Retail Banking track record and will be responsible for analyzing and documenting business requirements, designing solutions, and ensuring the successful implementation of banking systems and processes. Strong Salesforce knowledge/experience, ideally in a Retail Banking environment is required. The candidate will work in cross-functional Waterfall/Agile teams, including product owners, developers, testers, project managers, and other stakeholders (e.g. Risk) to identify customer and business needs, and translate them into requirements expressed as Use Stories, to ultimately deliver compelling Customer Experiences." Then blank paragraphs. Then "KEY RESULT AREAS" ->

    KEY RESULT AREAS

    Then the list items. We need to output each as

    ...text...

    . The text for each item is the visible sentence(s). Let's extract each bullet text exactly as appears (including any trailing spaces?). We'll copy the text inside each

    after stripping tags. List items (from original): 1. "Collaborate with Product Owners and other stakeholders to identify and document business requirements for banking systems and processes" 2. "Work with product owners and development teams to design and develop solutions that meet customer needs" 3. "Analyze and translate business requirements into artefacts that define and express the requirements, including:" 4. "User Stories" 5. "Acceptance Criteria (Gherkin)" 6. "Business Processes" 7. "Business Rules" 8. "Wireframes" 9. "Data Requirements" 10. "Run Refinement sessions" 11. "Proactively manage project timelines, and deliverables" 12. "Conduct user acceptance testing and ensure that systems and processes are performing as expected" 13. "Communicate with stakeholders to provide updates on status and ensure alignment with business goals and objectives" 14. "Identify opportunities for process improvements and propose solutions to increase efficiency and effectiveness" Note: The original had extra

    wrappers around each

    . We'll just output the text. Then "ROLE REQUIREMENTS" ->

    ROLE REQUIREMENTS

    Then "Domain Expertise" maybe not a header? It appears as

    Domain Expertise: ...

    . So we can treat "Domain Expertise" as a subheader? But we only use

    for section headers. Could use

    Domain Expertise

    but the original header is not bold? It is under Domain Expertise:. That's not a clear header. Might just treat as part of paragraph? But we need to preserve content. Could just include as part of paragraph under "ROLE REQUIREMENTS". However we need to keep headings like "Domain Expertise" maybe as a subheader? The instruction: Use

    for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). So "Domain Expertise" is not listed but could be considered a subheader. But we can just include it as part of paragraph. But we have a heading "ROLE REQUIREMENTS" already. Then there are sub items: "Domain Expertise" with bullet points. Actually the structure:

    Domain Expertise: 

    • ...

    etc. So we need to output "Domain Expertise" maybe as a subheader? Could use

    Domain Expertise

    but that might be okay. However we must preserve original content word-for-word; adding a new tag might be considered adding content? But we are allowed to wrap with

    for section headers. The original didn't have a header tag for "Domain Expertise". It just had a paragraph with bold underline. So we could just keep it as part of paragraph under "ROLE REQUIREMENTS". But we need to preserve the text exactly. So we can output a paragraph that includes "Domain Expertise:" and then the bullet points? Actually the bullet points are under separate

    after that paragraph. So we could output a paragraph "Domain Expertise:" then a list of bullet points? But the bullet points are separate items. The instruction: Use
    • for list items (duties, requirements, qualifications, skills). So we can output a list under "Domain Expertise". But we need a header? Not required but we can just output the bullet items as list items under that section. But we need to indicate that they belong to Domain Expertise? Could just output them as list items without a header; but we need to preserve the text "Domain Expertise:" somewhere. Could output a paragraph with that text. Similarly "Work Experience" appears as a heading with bullet items. Then "Skills and Qualifications" appears as a heading with bullet items. Then "Skills" bold heading with a paragraph of skills separated by commas. Then "Competencies" bold heading with list of competency names each preceded by
      tags (empty). Actually they are empty
      tags. So there is no content. So we can ignore. Then "Education" bold heading. Then "Closing Date" bold heading with date. Then the italic paragraph about appointment. Then "The Old Mutual Story!" italic bold. We need to output all that. Given the complexity, maybe we can simplify: just output the content in order, using

      for major headings we identify: "Job Description", "KEY RESULT AREAS", "ROLE REQUIREMENTS", "Skills", "Competencies", "Education", "Closing Date". For subheadings like "Domain Expertise", we can just include as part of paragraph or maybe as

      Domain Expertise

      but that would be adding a header not present originally. Might be okay? The instruction: Use

      for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). It doesn't require that we must only use those exact words; we can use

      for any section header. So we can use

      Domain Expertise

      etc. Thus we can structure:

      Job Description

      ...

      KEY RESULT AREAS

      • ...
      ...

      ROLE REQUIREMENTS

      Domain Expertise:

      • Experience with system implementation, testing, and deployment, in Retail Banking
      • Salesforce knowledge/experience, ideally in a Retail Banking environment; Financial Service Cloud would be advantageous
      • Demonstrated success in collaborating with cross-functional teams, stakeholders, and vendors
      • Familiarity with regulatory compliance and risk management practices in the Retail Banking industry

      Work Experience:

      • We are seeking an individual with experience in one or more of the following:
      • Retail Banking Service
      • Retail Banking Operations
      • Salesforce

      Skills and Qualifications:

      • Bachelor's degree in Information Systems, Computer Science, Engineering, or related field
      • Pertinent Salesforce certifications.

      Skills

      Adaptive Thinking, Analytics Software, Business Case Development, Business Intelligence (BI) Analysis, Business Requirements Analysis, Business Requirements Elicitation, Computer Literacy, Current State Assessment, Database Reporting, Data Compilation, Data Controls, Gap Analysis, Readiness Assessments, Requirements Development, User Requirements Documentation

      Competencies

      Action Oriented

      Business Insight

      ... etc. Actually the original had
      tags for each competency but no text. So we just output the competency names? The original list includes "Action Oriented
      Business Insight
      ..." So the text is "Action Oriented", "Business Insight", etc. They are separated by
      tags. So we can output each as a paragraph? But we need to preserve the words exactly. So we can output each as a paragraph: "Action Oriented", "Business Insight", etc. But they are not in a list; they are just separate lines. We can output each as a separate

      maybe. But the instruction: Use

      • for list items (duties, requirements, qualifications, skills). Competencies are not a list? They are separate items but not in a list. Could output them as separate

        paragraphs. Thus we can output:

        Action Oriented

        Business Insight

        ... etc. But we must preserve the exact wording; they are exactly those words. Then "Education" heading. Then maybe a paragraph with nothing? Actually after "Education" there are many empty

        tags. Then "Closing Date" heading with date. Then the italic paragraph. Then "The Old Mutual Story!" italic bold. We need to preserve the italic bold tags? The text includes The Old Mutual Story!. So the visible text is "The Old Mutual Story!" with emphasis. We need to preserve that exactly, but we can output it as a paragraph with that text. Thus final HTML will be a series of tags. Now we must ensure we do not use any disallowed tags: no

        , no
        , no inline styles, no , no , no , no maybe allowed? The instruction only allows

        ,

        ,

        ,
        • . It doesn't forbid or but says "Use

          for introductory paragraphs and general text; Use

          for section headers; Use

          • for list items". It also says "No CSS classes, no inline styles, no
            tags, no
            tags". It doesn't forbid or but they are not in the allowed set. Probably we should avoid them. So we need to output the text without those tags. So we must strip , , , etc. But we must preserve the content word-for-word. The content includes those tags? The visible text does not include them; they are markup. So we can output just the visible text. That is okay. Thus we will output only

            ,

            ,

            ,
            • . No other tags.

        Translated by AI — may not be perfect

        Show original