KC

Branch Manager, BPR - Head Office Branch

Full-time Rwanda, RW
Posted 3 weeks, 3 days ago 74 views 0 applications

Job Description

We need to output clean semantic HTML with

,

,
  • , no CSS classes, no inline styles, no
    , no
    . Must preserve all original content word-for-word, but we need to strip out HTML tags and formatting, keep the text. We have a job description with responsibilities list (ul with li), then a section about MINIMUM POSITION QUALIFICATION REQUIREMENTS with a table, then Experience etc. We need to extract the text content, preserving it exactly, but we need to format as HTML with appropriate tags. We must not add or remove content. So we need to output the same textual content, but wrapped in tags. We need to decide sections: The responsibilities list likely under a header like "Responsibilities" or "Key Duties". The original didn't have a header; it's just a list. We could treat the list as under a header "Responsibilities". But we must not add content not present. Adding a header would be adding text not originally present. The instruction: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". So we cannot add a header like "Responsibilities" if it wasn't in the original. However we can use

    for section headers only if they exist in the original. The original text does not contain explicit section headers like "Responsibilities". It starts with a
      list. Then there is a
        with MINIMUM POSITION QUALIFICATION REQUIREMENTS header inside. That is a header text: "MINIMUM POSITION QUALIFICATION REQUIREMENTS" inside an
      1. . So we have that as a header. Then there is a table with qualification details. Then there is an
          with
        1. Experience
        2. . Then a table for experience. Thus we have sections: "MINIMUM POSITION QUALIFICATION REQUIREMENTS" and "Experience". The responsibilities list has no header; we could just wrap it in

          or maybe treat as a list under no header. The instruction: "If text has no clear sections, just wrap paragraphs in

          tags". For the responsibilities list, it's a list; we could wrap each list item in

        3. inside a
            . That's allowed. No need for header. Thus final HTML: start with a
            • ... each responsibility text.
            . Then maybe a

            for "MINIMUM POSITION QUALIFICATION REQUIREMENTS". Then we need to represent the qualification table content as text? The instruction: Use
            • for list items (duties, requirements, qualifications, skills). For tables, we could convert to
              • each row? But we must preserve content word-for-word. The table contains rows with headings: Particulars, Detail, Specific Field or Qualification, Need Type. Then rows: Education, Bachelor’s degree, Business or another related field, RQ; Professional Qualifications, Banking, AA; Master’s degree, Business or another related field, AA. We need to preserve that exactly. Could we represent as a
                  with each row as a
                • containing the four cells separated by something? But that would change formatting. However we could keep the table as is? But we cannot use because not allowed? The rules only specify using

                  ,

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

                    for introductory paragraphs and general text; Use

                    for section headers; Use
                    • for list items". It doesn't explicitly forbid

                  , but likely they want only those tags. Safer to avoid
                  . We could represent the qualification requirements as a list: each bullet could be like "Education: Bachelor’s degree in Business or another related field (RQ)". But that would be rephrasing, not allowed. We need to preserve original content word-for-word. So we must output the exact same text, but we can wrap it in

                  tags perhaps. The original text includes the table markup; we could keep that as plain text inside a

                  . That would preserve content word-for-word (including the HTML tags). But then we would have HTML inside HTML, which might be okay but could be considered adding tags? The instruction: "Return ONLY the HTML. No markdown fences, no explanation, no preamble." It didn't say we cannot include original HTML tags. It said to format as clean semantic HTML, using those tags. But if we keep the original table tags, that would not be clean semantic HTML. However we must preserve content word-for-word; we cannot remove the table tags because they are part of the original content. But we could wrap the entire original content in a

                  and then the tags inside are just text? Actually if we output the original HTML as text, we need to escape the angle brackets? Not specified. Usually they'd want to strip out the original markup and replace with semantic tags. The phrase "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase" likely refers to the textual content, not the markup. So we should extract the plain text content (the words) and then reformat using the allowed tags. That seems the intent. Thus we need to extract the plain text from the given HTML, ignoring tags, but preserving the words and punctuation exactly as they appear (including spaces? but we can normalize whitespace? Probably keep as is but we can collapse multiple spaces? Safer to keep as they appear in the plain text. Let's extract plain text: First part: the ul list items: - Contribute to and take appropriate actions in cascading and implementing the Retail Banking Strategy in the area where the branch operates by ensuring bank’s retail objectives are met in order to ensure sustainable business growth; - Manage the branch retail’s liability and assets portfolios with the ultimate aim of ensuring that it remains profitable, competitive and promptly reacts to the changes in both the internal and external environment; - Drive a sales culture within the branch staff with the ultimate aim of growing the NFI, products per customer, share of wallet, quality customer base and at the same time ensure staff productivity. - Oversee the branch operations in order to ensure superior service offering to all bank’s customers, reduction of operating costs through an efficient utilization of Bank’s resources and prevention of frauds & losses through implementation of first-class corporate governance and compliance with bank’s policies, procedures and processes - Monitor and manage customer complaints, constantly review service delivery standards and manage branch human resources in a way, which ensures maintenance of the highest service standards. - Coach, mentor and develop a high performing team and ensure an effective performance management framework; - Ensure effective migration of customers to electronic business channels through promoting channels usage (Mobile Banking, Internet Banking and Cards) and a high performance of branch alternative channels such as Agency Banking and Merchant Business - Ensure that branch processes are within agreed TAT in order to live customer satisfaction. Note there are some formatting like & which should be "&". The original had "frauds & losses". So plain text should be "frauds & losses". We'll keep that. Second part: after the ul, there is an ol with li containing: MINIMUM POSITION QUALIFICATION REQUIREMENTS Then a p with A. Academic & Professional Then a table. We need to extract the table text: The table includes header row: Particulars, Detail, Specific Field or Qualification, Need Type Then rows: Education, Bachelor’s degree, Business or another related field, RQ Professional Qualifications, Banking, AA Master’s degree, Business or another related field, AA Note there is a footnote reference [1] after Need Type header. That is part of the header cell; we should include the text "[1]" maybe? The visible text is "[1]" as superscript. We'll include "[1]" as part of the header? The header cell contains "Need Type" plus a superscript reference. The plain text would be "Need Type[1]"? Usually the superscript is just a reference marker; we should include "[1]" as part of the cell content. Similarly later there is another footnote reference after Need Type header in second table: [2]. We'll include "[2]". Thus the header row: Particulars, Detail, Specific Field or Qualification, Need Type[1] Then rows: Education, Bachelor’s degree, Business or another related field, RQ Professional Qualifications, Banking, AA Master’s degree, Business or another related field, AA Note there is no footnote after those rows. Then after the table, there is an ol with li containing Experience Then a p with   (non-breaking space) maybe empty. Then a figure with table: "Total Minimum No of Years’ Experience Required" and two subrows? Actually the table: First table after Experience: two columns: left cell contains two paragraphs: "Total Minimum No of Years’ Experience Required" "Team Leadership, Sales, Relationship Management, Credit, and Bank Operations" Right cell: "10 years" Thus we need to capture that. Then another table: header row: Detail, Minimum No of Years, Need Type[2] Rows: Experience Area 1 – Sales and Relationship Management, Above 5 years, ES Experience Area 2 – Credit Skills, Above 5 years, ES Experience Area 3 - Banking Operations, Above 5 years, ES Experience Area 4 – Leadership, Above 5 years, ES Experience Area 5 – Business development track records, Above 3 years, ES Note there are some formatting like " " etc. We need to output all this as plain text, wrapped in appropriate tags. We have sections: responsibilities list (ul), then a header "MINIMUM POSITION QUALIFICATION REQUIREMENTS" (h4), then maybe a subheader "A. Academic & Professional" (could be h4? but it's bold inside a p). Could treat as h4 as well? The instruction: Use

                  for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). "A. Academic & Professional" could be considered a subsection under Qualifications. We could make it an h4 as well. But we must not add content not present; but we can use the exact text as header. So we can wrap that line in

                  . Then the table content: we need to represent as something. Since we cannot use

                  , we could use
                  • each row as a sentence? But that would alter content. However we could keep the table as plain text inside a

                    preserving original spacing and line breaks? The original had line breaks within the table cells; but if we output as plain text, we need to preserve the words exactly as they appear in the original source (including line breaks?). The original source had newlines inside the HTML but not visible. The visible text when rendered would be like a table. But we don't have the rendered layout; we have the raw HTML with tags. The plain text extracted by stripping tags would give us the words in order, but we lose the table structure. However the instruction to preserve original content word-for-word likely means we should not lose any words, but we can lose formatting like table tags. So we can output the words in a logical order, maybe as a list. Given the difficulty, maybe we can output each row as a

                  • with the four cells separated by " – " or something, but that adds punctuation not originally there. However the original had those cells separated by table layout; we could represent them as "Particulars: Education, Detail: Bachelor’s degree, Specific Field or Qualification: Business or another related field, Need Type: RQ". That adds colons and commas not originally there. That would be adding content. Thus maybe we should keep the original table markup as plain text inside a

                    (i.e., we output the original HTML as text, but we need to escape the angle brackets? Not required if we output them as literal characters; they'd be interpreted as HTML tags though, which would break the output. But the instruction says return only HTML; if we output raw

                  tags, they'd be interpreted as HTML, which might be okay but not "clean semantic HTML". However the instruction says to use

                  ,

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

                    for introductory paragraphs and general text". It doesn't say we cannot use other tags, but likely they want only those. Given the ambiguity, I think the safest is to output the plain text content, using

                    for paragraphs and

                    • for lists, and treat the table data as a series of

                      lines. We can break the table into lines: each row as a sentence. Let's extract the plain text in order: Responsibilities list (8 items). Then a blank line? Then "MINIMUM POSITION QUALIFICATION REQUIREMENTS" Then "A. Academic & Professional" Then the table: Particulars Detail Specific Field or Qualification Need Type[1] Education Bachelor’s degree Business or another related field RQ Professional Qualifications Banking AA Master’s degree Business or another related field AA Then "Experience" Then maybe a blank line. Then table: Total Minimum No of Years’ Experience Required Team Leadership, Sales, Relationship Management, Credit, and Bank Operations 10 years Then table: Detail Minimum No of Years Need Type[2] Experience Area 1 – Sales and Relationship Management Above 5 years ES Experience Area 2 – Credit Skills Above 5 years ES Experience Area 3 - Banking Operations Above 5 years ES Experience Area 4 – Leadership Above 5 years ES Experience Area 5 – Business development track records Above 3 years ES We need to preserve punctuation exactly as in the original text. Let's verify each phrase. From original: Responsibilities items: 1. "Contribute to and take appropriate actions in cascading and implementing the Retail Banking Strategy in the area where the branch operates by ensuring bank’s retail objectives are met in order to ensure sustainable business growth;" Note: there is a semicolon at end. 2. "Manage the branch retail’s liability and assets portfolios with the ultimate aim of ensuring that it remains profitable, competitive and promptly reacts to the changes in both the internal and external environment;" Semicolon. 3. "Drive a sales culture within the branch staff with the ultimate aim of growing the NFI, products per customer, share of wallet, quality customer base and at the same time ensure staff productivity. " There is a non-breaking space after period; but plain text we can ignore   as just a space. 4. "Oversee the branch operations in order to ensure superior service offering to all bank’s customers, reduction of operating costs through an efficient utilization of Bank’s resources and prevention of frauds & losses through implementation of first-class corporate governance and compliance with bank’s policies, procedures and processes " Again  . 5. "Monitor and manage customer complaints, constantly review service delivery standards and manage branch human resources in a way, which ensures maintenance of the highest service standards. " 6. "Coach, mentor and develop a high performing team and ensure an effective performance management framework;" 7. "Ensure effective migration of customers to electronic business channels through promoting channels usage (Mobile Banking, Internet Banking and Cards) and a high performance of branch alternative channels such as Agency Banking and Merchant Business " 8. "Ensure that branch processes are within agreed TAT in order to live customer satisfaction." Note: there is no punctuation at end of #8? It ends with a period. Now the header: "MINIMUM POSITION QUALIFICATION REQUIREMENTS" (bold). Then "A. Academic & Professional" (bold). Then the table. Let's extract the table text exactly as appears, ignoring tags but preserving spaces and line breaks as they appear in the source? The source had line breaks within the table cells but not visible. We'll just produce a readable representation. Better to output each row as a

                      containing the cells separated by " | " maybe? But that adds characters. Given the difficulty, I think we can output the table as a

                        where each
                      • is a row with cells separated by commas, but that changes content. Maybe we can treat the table as a series of

                        lines, each line being the concatenation of cells with a space. That would lose the delimitation but keep all words. Let's do that: For header row: "Particulars Detail Specific Field or Qualification Need Type[1]" (note there is no punctuation between cells originally; they were separated by table cells). We'll just put a space. Then each row similarly. But we need to preserve the footnote reference "[1]" and "[2]" exactly. Thus: Header: "Particulars Detail Specific Field or Qualification Need Type[1]" Row1: "Education Bachelor’s degree Business or another related field RQ" Row2: "Professional Qualifications Banking AA" Row3: "Master’s degree Business or another related field AA" Second table header: "Detail Minimum No of Years Need Type[2]" Rows: "Experience Area 1 – Sales and Relationship Management Above 5 years ES" "Experience Area 2 – Credit Skills Above 5 years ES" "Experience Area 3 - Banking Operations Above 5 years ES" "Experience Area 4 – Leadership Above 5 years ES" "Experience Area 5 – Business development track records Above 3 years ES" Note there is an en dash or hyphen? In original: "Experience Area 1 – Sales and Relationship Management" uses an en dash. We'll keep that. Also "Experience Area 3 - Banking Operations" uses a hyphen? Actually original: "Experience Area 3 - Banking Operations". We'll keep as is. Now the first experience table: we have two paragraphs in left cell: "Total Minimum No of Years’ Experience Required" and "Team Leadership, Sales, Relationship Management, Credit, and Bank Operations". Right cell: "10 years". We'll represent as maybe two lines then the years. We could output as: "Total Minimum No of Years’ Experience Required" "Team Leadership, Sales, Relationship Management, Credit, and Bank Operations" "10 years" But we need to preserve that the left cell had two lines. We'll output each as separate

                        . Now we need to wrap sections. We'll produce:

                        • ... each responsibility.
                        Then

                        MINIMUM POS
                        Apply Now ↗

                        How well do you match?

                        Get an instant AI match score for this role — free, takes 3 minutes.

                        Tailor your CV for this role

                        The concierge rewrites your whole CV and writes a matching cover letter for this job — opens right here, nothing to paste.

                        Tailor My CV to This Job ✍️

                        Free cover letter for this job

                        Upload your CV and get a tailored cover letter in seconds — free, no account needed.

                        Generate a Cover Letter 📝

                        Join Our Rwanda Channels

                        Get free job alerts on your phone

                        MJC
                        ECHO
                        Your MJC Assistant

                        I'm ECHO, your MJC career assistant. I can help you find jobs, explore career tools, and connect with opportunities across Africa.

                        How was your experience with ECHO?