Data Scientist

for paragraphs,

for section headers,

• for list items. Must preserve original content word-for-word, no additions, no removals. Must not add CSS classes, inline styles, no
  , no
  . Must return only HTML. We have raw text with HTML tags already present:

  tags etc. But we need to produce HTML ourselves, preserving content. The input includes HTML tags like

  and   etc. We must treat the raw text as given, but we need to output HTML that preserves the content word-for-word. Likely we should strip existing tags and reformat according to rules. However the instruction: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". That means we must keep the exact text content, but we can change formatting (tags). So we need to extract the textual content (including spaces  ?) and then wrap in appropriate tags. We need to identify sections: The text includes headings like "JOB DESCRIPTION", "GENERAL JOB INFORMATION", then lines with labels and values. Then "JOB PURPOSE", "JOB CONTEXT", then blank line, then "KEY RESPONSIBILITIES" with bullet points (starting with •). Then "JOB PROFILE" with sub-sections "Experience & Qualifications" and "Skills, Capabilities & Direct attributes". Then a paragraph about Ecobank commitment. We need to use

  for section headers (e.g., Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). So we should treat headings like "JOB DESCRIPTION", "GENERAL JOB INFORMATION", "JOB PURPOSE", "JOB CONTEXT", "KEY RESPONSIBILITIES", "JOB PROFILE", "Experience & Qualifications", "Skills, Capabilities & Direct attributes" as headers? The instruction says use

  for section headers (e.g., Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). It doesn't forbid using for other headings, but likely we should use

  for each major section heading. We'll wrap each heading line in

  . Then the content under each heading should be in

  paragraphs, and bullet lists in

  • . We must preserve original content word-for-word, including spaces and   entities? The original includes   for spaces. We should keep them as is. Also there are "&" in "Experience & Qualifications". Must keep that. We need to strip existing HTML tags like

    ,
    , etc., and reapply our own. Let's extract the raw text content from the given input, ignoring tags. Input:

    JOB DESCRIPTION
    GENERAL JOB INFORMATION
    Job Title:                                Data Scientist
    Organization/ Department:    Group Technology / Data Analytics
    Reports to:                             Lead, Data Science
    Salary Grade/ Band :                 3B

    JOB PURPOSE
    Reporting to the Lead, Data Science, the Data Scientist will support work on our core business products and customer transactions by assisting in the development of machine learning models under guidance and using industry best practice.
    The Data Scientist will apply developing programming skills to assist with building, deploying, implementing, and maintaining predictive models and rating algorithms. The individual in this role will gain familiarity with different ways of capturing data, including REST APIs, and support the building of pipelines for real-time consumption and analysis of internal and external data sources.

    JOB CONTEXT
    Supporting hypothesis testing, machine learning and analytical designs for prediction, forecasting, and product and business development, with guidance from senior colleagues.

    
    KEY RESPONSIBILITIES
    •    Apply developing skills in quantitative analysis, data mining, and the presentation of data to help see beyond the numbers and understand how our customers and users interact with both business products and systems.
    •    Assist in designing and evaluating data experiments.
    •    Support the monitoring of key product metrics.
    •    Help build key data sets to empower operational and exploratory analysis.
    •    Assist in evaluating and defining metrics for the data warehouse.
    •    Contribute to understanding user behaviours and long-term trends.
    •    Support product teams through the presentation of data-based recommendations.
    •    Help communicate state of business, experiment results, etc. to product teams.
    •    Gain exposure to the Big Data ecosystem (Hadoop, Hive, MapReduce) and, where required, MySQL and Oracle.
    •    Assist in building and maintaining pipelines via querying tools and the ETL framework for the Data Warehouse.
    •    Collaborate with the analytics team to help formulate innovative solutions and support the application of modelling techniques.
    •    Support the identification of business opportunities through data mining.
    •    Partner with other units of the team to fulfil ad-hoc data requests and respond to business enquiries in a timely manner.
    •    Provide L1/L2 support alongside junior colleagues, managing and resolving the team’s tickets through the SysAid ticket management system.

    JOB PROFILE
    Experience & Qualifications
    •    B.A. / B.Sc. in Computer Science, Math, Physics, Engineering, Economics, Statistics or other technical field.
    •    Some experience in SQL or other programming languages.
    •    Basic development exposure to at least one scripting language (Python, PHP, Perl, etc.).
    •    Ability to communicate the results of analyses in a clear and effective manner with product and leadership teams.
    •    Foundational understanding of statistics (e.g., hypothesis testing, regression analysis).
    •    Growing ability to manipulate data sets through statistical software (e.g., R, SAS, SPSS or Minitab) or other methods.
    •    Passion for working with big data and an interest in customer and financial models.
    •    Awareness of Data Warehouse design and strategy concepts.
    •    Understands relational database and star schema concepts.
    •    Understands data profiling and data quality/testing concepts.
    •    Experience with Microsoft Excel / PowerPivot.
    •    Financial industry experience is a plus.
    •    Strong analytical skills, problem solver, and attention to detail.
    •    Foundational exposure to statistical modelling techniques.
    •    Exposure to Big Data technologies.
    •    The ability to understand unique business needs and translate them into technical requirements, with support.
    Skills, Capabilities & Direct attributes
    •    Demonstrated ability to handle multiple projects and deadlines.
    •    Must be Customer Service oriented.
    •    Must be a result-driven and action-oriented individual.
    •    Must be a true Team player.
    •    Must also be self-motivated and able to work independently and autonomously when asked.
    •    Must possess strong analytical and problem-solving skills.
    •    Must possess strong abilities and interest in analyzing and extracting useful, business-related information from large amounts of Customer and pricing data.

    “Ecobank is committed to providing equal opportunities to all and fostering an inclusive and diverse workplace. To this end, we encourage applications from individuals regardless of their nationality, race, gender, age, social class, religion, beliefs, and disability while fully adhering to the local laws and regulations established where Ecobank operates.”
    
     

    We need to parse. Let's extract textual content ignoring tags but preserving   and &. We'll replace
    with newline maybe. But we need to preserve content exactly, including line breaks? The original content includes line breaks indicated by
    . We should preserve them as line breaks in output? The instruction: preserve ALL original content word-for-word. That includes the line breaks? The original text had
    tags representing line breaks. If we remove those tags, we lose the line break representation. But we can convert
    to actual newline characters in the output text, which is still preserving the content (the line break). However the instruction says do not add, remove, summarise, or rephrase. Changing
    to a newline is not adding or removing content; it's representing the same line break. Probably acceptable. Similarly,   is a non-breaking space; we should keep it as   entity? The original content includes  . If we keep it as is, it's fine. We'll not convert to regular space. We need to output HTML with

    ,

    ,

    • . We must not use
      tags. So we need to represent line breaks via

      blocks. Thus we will parse sections. Let's manually rewrite. First section: JOB DESCRIPTION and GENERAL JOB INFORMATION appear on same line separated by
      . Actually first

      contains: JOB DESCRIPTION
      GENERAL JOB INFORMATION
      Job Title:     ... etc. So we have three lines: "JOB DESCRIPTION", "GENERAL JOB INFORMATION", then the details. We could treat "JOB DESCRIPTION" as a heading, then "GENERAL JOB INFORMATION" as another heading? Or combine? The instruction says use

      for section headers like Responsibilities, Qualifications, etc. It doesn't forbid other headings. We'll treat each line that is all caps and ends without colon as a heading. Thus:

      JOB DESCRIPTION

      GENERAL JOB INFORMATION

      Then the details lines: each line like "Job Title:     ... Data Scientist". Those are not headings; they are content. We'll put them in

      paragraphs. Possibly each line as separate

      or combine into one

      with line breaks? Since we cannot use
      , we should separate each line into its own

      . That preserves content (line breaks become paragraph breaks). That's acceptable. Thus after the two headings, we will have

      Job Title:                                Data Scientist

      etc. But note there are multiple spaces and  . We'll keep them exactly. Next

      block: JOB PURPOSE heading then two sentences. So

      JOB PURPOSE

      then

      Reporting to the Lead, Data Science, the Data Scientist will support work on our core business products and customer transactions by assisting in the development of machine learning models under guidance and using industry best practice.

      then

      The Data Scientist will apply developing programming skills to assist with building, deploying, implementing, and maintaining predictive models and rating algorithms. The individual in this role will gain familiarity with different ways of capturing data, including REST APIs, and support the building of pipelines for real-time consumption and analysis of internal and external data sources.

      Next: JOB CONTEXT heading then one sentence.

      JOB CONTEXT

      Supporting hypothesis testing, machine learning and analytical designs for prediction, forecasting, and product and business development, with guidance from senior colleagues.

      Then there is a

      
      KEY RESPONSIBILITIES
      ... So there is a blank line before KEY RESPONSIBILITIES. The

      contains a
      then KEY RESPONSIBILITIES then
      then bullet lines. Thus we have an empty line (just
      ) then heading KEY RESPONSIBILITIES then bullet list. We'll treat the empty line as maybe a

      with nothing? But we should not add empty paragraphs. Probably we can ignore the blank line; just treat heading. Thus

      KEY RESPONSIBILITIES

      then each bullet line as
    • inside
      . Bullet lines start with "•    " then text. We need to keep the bullet character and spaces? The bullet is a Unicode bullet •. We'll keep it as part of the
      • content. The spaces after bullet are   entities; we keep them. Thus
        • •    Apply developing skills in quantitative analysis, data mining, and the presentation of data to help see beyond the numbers and understand how our customers and users interact with both business products and systems.
        ... etc. After responsibilities, next

        block: JOB PROFILE heading then two subheadings: "Experience & Qualifications" and "Skills, Capabilities & Direct attributes". Each followed by bullet list. Thus:

        JOB PROFILE

        Experience & Qualifications

        ... bullets ...

        Skills, Capabilities & Direct attributes

        ... bullets ...
        Finally the Ecobank commitment paragraph: It's inside a

        with quotes and then
        
         . So we have a paragraph with the quoted text, then two line breaks, then a non-breaking space. We'll treat the quoted text as a

        . The blank lines and   maybe we can ignore as they are just formatting. But to preserve content word-for-word, we need to represent them. However we cannot use
        . We could represent the two line breaks as empty

        tags? That would add empty paragraphs, which might be considered adding content? But empty

        adds nothing visible but is an element. Might be considered adding. Safer to ignore the blank lines and   as they are just formatting not meaningful content. The instruction says preserve ALL original content word-for-word. That's tricky. However typical interpretation: preserve the textual content, not the exact markup. The   is a space; we could replace with a regular space? That would change the entity but not the visual space. Might be considered altering. But we cannot use
        tags, so we must convert line breaks to something else. The instruction says no
        tags. So we must replace line breaks with something else, likely paragraph breaks. That's a transformation but necessary to comply with HTML constraints. Likely acceptable. Thus we will output:

        JOB DESCRIPTION

        GENERAL JOB INFORMATION

        Job Title:                                Data Scientist

        Organization/ Department:    Group Technology / Data Analytics

        Reports to:                           Lead, Data Science

        Salary Grade/ Band :                 3B

        JOB PURPOSE

        Reporting to the Lead, Data Science, the Data Scientist will support work on our core business products and customer transactions by assisting in the development of machine learning models under guidance and using industry best practice.

        The Data Scientist will apply developing programming skills to assist with building, deploying, implementing, and maintaining predictive models and rating algorithms. The individual in this role will gain familiarity with different ways of capturing data, including REST APIs, and support the building of pipelines for real-time consumption and analysis of internal and external data sources.

        JOB CONTEXT

        Supporting hypothesis testing, machine learning and analytical designs for prediction, forecasting, and product and business development, with guidance from senior colleagues.

        KEY RESPONSIBILITIES

        • •    Apply developing skills in quantitative analysis, data mining, and the