KC

DFS Business Development Manager - Dar es Salaam

Full-time Tanzania, United Republic of, TZ
Posted 1 week ago 29 views 0 applications

Job Description

Here's a thinking process: 1. **Analyze User Input:** - User is acting as a job listing editor. - I receive raw scraped text from a job website. - Goal: Extract ONLY actual job information, return clean, readable format. - Must remove: social sharing, author bylines, "you may also like", navigation, comments, ads, cookie notices, duplicate text, stray category labels, stray numbers/formatting artifacts. - Must keep and structure: job title, company, location, description/responsibilities, requirements/qualifications, how to apply, salary, deadline, job ID/reference, contract type/level. - Output: ONLY the cleaned job text, no commentary, no headers, no markdown. - Then there's a second part: "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." - Rules for HTML formatting: - Use `

` for intro paragraphs and general text - Use `

` for section headers (Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role) - Use `
  • ` for list items (duties, requirements, qualifications, skills) - No CSS classes, no inline styles, no `
    `s, no `
    ` tags - Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase - If text has no clear sections, just wrap paragraphs in `

    ` tags - Return ONLY the HTML. No markdown fences, no explanation, no preamble. - The actual job description text is provided between `Job description:` and the end of the input. Wait, I need to figure out which task to do. The user message starts with "You are a job listing editor..." then has rules, then says "Return ONLY the cleaned job text...". Then it says "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." Then gives HTML formatting rules, and then provides the job description text. This looks like two separate instructions in one prompt, or maybe the second is the actual task to perform on the provided text. Let me read carefully. The very first part describes the role and what to remove/keep, and says "Return ONLY the cleaned job text. Do not add any commentary, headers like "Here is the cleaned version", or markdown formatting. Just the clean job listing text." Then the second part says "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." with specific HTML rules, and "Return ONLY the HTML. No markdown fences, no explanation, no preamble." Then the job description text is provided. I think the actual task is to take the job description text and format it as clean semantic HTML per the rules. The first part might be context/setup, but the concrete task with the actual text is the HTML formatting one. However, both have "Return ONLY..." constraints. I need to decide which one to output. Let me re-read the beginning: "You are a job listing editor. You receive raw scraped text from a job website. Your job is to extract ONLY the actual job information and return it in a clean, readable format." Then it lists remove/keep items. Then "Return ONLY the cleaned job text. Do not add any commentary..." Then: "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." with HTML rules. Then the job description text. I think the user wants me to process the given job description text and output it as clean semantic HTML, following the HTML rules. The first part might be a general description of the role, but the specific task is the HTML formatting. However, both constraints "Return ONLY the cleaned job text" and "Return ONLY the HTML" are present. I need to see which text is the actual input to transform. The job description text is enclosed in `Job description:` and then the text. That's likely the input. The HTML rules are the transformation format. I should output HTML. But wait, the first set of rules says "Remove all of the following: - Social sharing text... - Author bylines... - "You may also like"... - Navigation text... - Comments sections... - Advertisements or promotions... - Cookie/subscription notices... - Duplicate text... - Category labels... - Stray numbers or formatting artifacts." And "KEEP and STRUCTURE: - Job title - Company/Organisation name - Location - Job description and responsibilities - Requirements/qualifications - How to apply / application instructions - Salary (if mentioned) - Deadline / closing date - Job ID / reference number - Contract type / level" Then it says "Return ONLY the cleaned job text. Do not add any commentary, headers like "Here is the cleaned version", or markdown formatting. Just the clean job listing text." The second set says "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." with specific tags `

    `, `

    `, `
    • `, no classes/styles/div/br, preserve all content word-for-word, etc. "Return ONLY the HTML. No markdown fences, no explanation, no preamble." I'm conflicted. Maybe I should do both? But the output should be only one thing. Let me look at the structure. The user message might be a test where I need to extract the job info and then format it as HTML, or maybe the first part is the instruction set, and the second part is the actual task. The presence of the job description text at the end suggests I need to process it. Let me analyze the job description text to understand its structure. It starts with `
      1. ` items under an `
          `. Then there's a table with qualifications, experience requirements, and footnotes. The HTML rules say: "Use

          for introductory paragraphs and general text", "Use

          for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)", "Use
          • for list items (duties, requirements, qualifications, skills)", "No CSS classes, no inline styles, no
            s, no
            tags", "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase", "If text has no clear sections, just wrap paragraphs in

            tags", "Return ONLY the HTML. No markdown fences, no explanation, no preamble." Key challenge: The input text has a lot of presentational markup (spans, styles, ol/li with inline styles). I need to extract the pure text content, strip the formatting artifacts, and reformat into semantic HTML using only `

            `, `

            `, `
              `, `
            • `. I must preserve ALL original content word-for-word. That means I can't omit any text, but I need to strip the HTML tags and inline styles that aren't part of the actual content. Let me parse the text mentally and identify the actual content: The job description seems to be for a DFS (Digital Financial Services) Business Growth role. Responsibilities are listed as bullet points under an ordered list. Then there are qualification requirements in a table, then experience, then footnotes. I need to extract: - Responsibilities (the li items) - Qualifications/requirements (the table rows) - Experience requirement (4 years) - Footnote about need types (RQ, AA) But the rules say "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". So I need to include every word that's in the original text, but present it in the new HTML structure. Let me try to extract the text content from the provided markup, ignoring the presentational tags but keeping the text. Original text blocks: 1. Responsibilities (under `
                ` with `
              1. ` items): - "Drive DFS Business Growth" - "Develop and execute area specific strategies to increase customer acquisition, transaction volumes, and revenue across all digital and other channels in Dar Es Salaam." - "Expand Mobile and Internet Banking Adoption" - "Lead initiatives to onboard retail, SME, and corporate customers onto mobile banking and internet banking platforms while driving usage." - "Grow Merchant Acquiring Business" - "Identify, acquire, and manage merchants for POS, KCB LIPA, and online payment acceptance solutions to increase card and digital payment usage." - "Develop Agency Banking Network" - "Recruit, onboard, train, and manage agency banking partners to improve financial service accessibility and transaction growth." - "Build Strategic Partnerships" - "Establish and maintain relationships with business organizations, payment service providers, tourism stakeholders, and community organizations to drive DFS adoption." - "Market Intelligence and Opportunity Identification" - "Analyze market trends, competitor activities, customer behavior, and emerging opportunities to inform growth strategies." - "Manage Sales Pipeline and Business Development Activities" - "Generate leads, conduct sales presentations, negotiate commercial terms, and close business opportunities across DFS products." - "Monitor Performance and Deliver Growth Targets" - "Track key performance indicators (KPIs) including customer acquisition, active users, transaction volumes, merchant growth, agent productivity, and revenue generation." - "Coordinate Cross-Functional Execution" - "Work closely with business segments, operations, technology, risk & compliance, marketing, and branch teams to ensure successful implementation and adoption of DFS solutions" 2. Qualification table: - "MINIMUM POSITION QUALIFICATION REQUIREMENTS" - Table headers: Particulars, Detail, Specific Field or Qualification, Need Type [1] - Row 1: Education, Bachelor’s degree, Bachelor in Banking/Finance or equivalent, RQ - Row 2: Professional Qualifications, Merchant Acquiring and card background, AA - Row 3: Master’s Degree, Business Administration, AA - Footnote: "Need Types are : RQ = Required, AA = Added Advantage" 3. Experience: - "Total Minimum No of Years Experience Required" = 4 Now, the HTML rules want me to use `

                ` for section headers like "Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role". I need to structure the output with these headers, but the instruction also says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". This is tricky because I'm adding HTML tags, but the constraint likely means don't alter the text content itself. Also: "If text has no clear sections, just wrap paragraphs in

                tags". This text has clear sections (responsibilities, qualifications, experience, footnote). I need to output HTML only. No markdown fences. So I should output something like:

                Responsibilities

                • Drive DFS Business Growth
                • Develop and execute area specific strategies to increase customer acquisition, transaction volumes, and revenue across all digital and other channels in Dar Es Salaam.
                • ... etc ...

                Qualifications

                • Bachelor’s degree in Banking/Finance or equivalent (Required)
                • ... but I need to preserve word-for-word. So maybe I should keep the exact text and just wrap in appropriate tags. Let me re-read the HTML rules carefully: - "Use

                  for introductory paragraphs and general text" - "Use

                  for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)" - "Use
                  • for list items (duties, requirements, qualifications, skills)" - "No CSS classes, no inline styles, no
                    s, no
                    tags" - "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase" - "If text has no clear sections, just wrap paragraphs in

                    tags" - "Return ONLY the HTML. No markdown fences, no explanation, no preamble." I think I need to structure the entire job description into sections using `

                    ` headers, and use `
                    • ` for lists where appropriate, and `

                      ` for other text. But I must include ALL original text word-for-word. Let me try to map the content to the HTML structure. First, identify sections present in the text: - Responsibilities (the long list of li items) - Qualification Requirements (the table with Particulars/Detail/Specific Field/Need Type) - Experience (4 years minimum) - Need Types explanation (RQ = Required, AA = Added Advantage) The HTML rules list possible headers: "Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role". I should use relevant ones. I need to be careful: "Preserve ALL original content word-for-word" means I can't paraphrase or omit any text. So if a line says "Drive DFS Business Growth", I must include exactly that, possibly as a list item or paragraph text. Let me think about how to structure this HTML. Since the input has an ordered list of responsibilities, I'll use `

                      • ` or `
                        1. `? The rules say "Use
                          • for list items (duties, requirements, qualifications, skills)". It doesn't mention `
                              `, but says use `
                              • `. I'll use `
                                • ` to comply, or maybe `
                                  1. ` if it's ordered, but the rule explicitly says `
                                    • `. I'll use `
                                      • ` to be safe, or I could use `
                                          ` if the content is inherently ordered, but the rule says "Use
                                          • for list items". I'll stick with `
                                            • `. However, the rule also says "No ... no
                                              tags". The original text has `
                                              ` tags inside some li spans. I need to remove those and just keep the text. Let me extract pure text from the responsibilities: From the first `
                                              1. ` block, each `
                                              2. ` has a strong phrase followed by a paragraph text. I need to combine or separate them? The original has `Drive DFS Business Growth
                                                Develop and execute area specific strategies...`. The text content is "Drive DFS Business Growth" and "Develop and execute area specific strategies to increase customer acquisition, transaction volumes, and revenue across all digital and other channels in Dar Es Salaam." I need to preserve both. I could put them as separate `
                                              3. ` items, or combine within one `
                                              4. `. Since the rule says preserve word-for-word, I'll include both phrases as they appear, perhaps as text within the `
                                              5. `. But the original structure has the strong text as a heading-like phrase, then the description. I need to decide how to mark this. Maybe I can use `

                                                ` inside `

                                              6. `, but the rules say use `
                                                • ` for list items, and `

                                                  ` for introductory paragraphs and general text. I could have `

                                                • Drive DFS Business Growth

                                                  Develop and execute ...

                                                • `, but that adds `

                                                  ` inside `

                                                • `, which might be okay, but the rules don't explicitly forbid `

                                                  ` inside `

                                                • `, they just say use `
                                                  • ` for list items. However, the rule "Use

                                                    for introductory paragraphs and general text" might conflict. Let me re-read: "Use

                                                    for introductory paragraphs and general text - Use

                                                    for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role) - Use
                                                    • for list items (duties, requirements, qualifications, skills)". It doesn't say I can't use `

                                                      ` inside `

                                                    • `, but it might be implied that list items contain just text or the specified tags. To be safe, I'll structure each responsibility as a single `
                                                    • ` with the full text, possibly combining the strong phrase and the description into one line, since the original has them on separate lines but with `
                                                      `. I'll remove the `
                                                      ` and combine. But "Preserve ALL original content word-for-word" means I must include every word, but I can change the markup. So I can write: `
                                                    • Drive DFS Business Growth Develop and execute area specific strategies to increase customer acquisition, transaction volumes, and revenue across all digital and other channels in Dar Es Salaam.
                                                    • ` — but that merges two separate thoughts without clear separation. Maybe better to keep them as separate `
                                                    • ` items? Looking at the original, each `
                                                    • ` has one strong phrase and one description. There are 17 `
                                                    • ` items in the first ol. Each has a pattern: `Phrase
                                                      Description.`. I'll treat each as one list item with two sentences or a phrase and a sentence. Given the strict "no
                                                      " rule, I need to inline them. I could do: `
                                                    • Drive DFS Business Growth. Develop and execute area specific strategies to increase customer acquisition, transaction volumes, and revenue across all digital and other channels in Dar Es Salaam.
                                                    • ` — adding a period. But does that preserve word-for-word? The original has "Drive DFS Business Growth" followed by a line break and then the description. If I add a period, I'm adding a character not originally there, but it's for readability. The rule says "do not add, remove, summarise, or rephrase". Adding a period could be seen as adding. I should perhaps keep them as separate lines without `
                                                      `, maybe using separate `

                                                      ` tags, but within `

                                                    • `? This is tricky. Alternative: Since the rule says "If text has no clear sections, just wrap paragraphs in

                                                      tags", and this text has clear sections, I should use the section headers. Maybe I should treat each `

                                                    • `'

    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 📝

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?