Credit Risk Analyst

` for paragraphs, `

` for section headers, `

• ` for lists, no CSS/inline styles/
  /
  , preserve ALL original content word-for-word, no rephrasing/summarizing, return ONLY HTML, no markdown fences/explanation/preamble. 2. **Examine the Job Description Text:** The text has several sections: - Business Area: Risk - Workplace Type: On-site - Location - Town / City: Cape Town - Job Description: paragraph text - Key Responsibilities: list items (but formatted as inline text with line breaks, need to extract as ul/li) - Qualifications and Experience: paragraph/bulleted mix - Competencies: bullet points Let me carefully extract and structure everything word-for-word. Original text breakdown: ``` Business Area: Risk Workplace Type: On-site Location - Town / City: Cape Town Job Description: Based at our Head Office in Cape Town, this position requires that you to find innovative ways to leverage the vast amount of data and information at your disposal to create customer strategies that drive up profit within constraints. Work within the Risk and Analytics department to enhance Truworths’ company performance by providing information, analyses, reports and technical support for the development and implementation of solutions . Key Responsibilities: Assist team to achieve a balanced credit portfolio by accurately forecasting expected results Develop and implement champion/challenger customer strategies that deliver performance in line with Board expectations Monitor portfolio performance and ensure book performance meet pre-defined KPI’s by pro-actively proposing changes Modelling experience required (built and implemented statistical models) Investigating data integrity issues, testing assumptions and validating analytical results, ensuring accuracy of findings Create new account management strategies to optimise the business objectives within specific constraints Undertaking analysis to determine the impact of strategy changes to areas of application and account management strategies Presenting ideas via reports and presentations, outlining findings and making recommendations for improvements to senior stakeholders Forecasting and monitoring implemented strategies using statistical techniques Project manage the implementation of strategy changes into live systems Credit scoring experience (highly advantageous) Qualifications and Experience: Preferred relevant post-graduate Degree with mathematical or statistical oriented subjects Business Science Degree or Business finance degree 3+ or more years’ experience in consumer credit (within a Credit Risk analytics environment) with demonstrated ability to implement solutions based on findings from analytical projects Understanding of the credit life cycle Revolving store card or credit card experience advantageous Ability to work efficiently under pressure and within structured and unstructured parameters Advantageous to have predictive Analytics experience with a highly numerate background Must be able to monitor models and report back to relevant stakeholders High attention to detail driving a need for 100% accuracy High level of integrity and confidentiality Experienced user of Microsoft Office suite (Excel, PowerPoint, Word) Experience in SAS, SQL and/or Python preferred (base and/or Enterprise Guide and/or SAS Viya) advantageous Competencies: • Understanding of the credit life cycle • Revolving store card or credit card experience advantageous • Ability to work efficiently under pressure and within structured and unstructured parameters • Advantageous to have predictive Analytics experience with a highly numerate background • Must be able to monitor models and report back to the board • Must assist in growing team with relevant support, training programs and be seen as a mentor • High attention to detail driving a need for 100% accuracy • High level of integrity and confidentiality • Experienced user of Microsoft Office suite (Excel, PowerPoint, Word) • Experience in SAS preferred (base and/or Enterprise Guide and/or SAS Viya) extremely advantageous SQL/ Python. ``` Wait, the user said: "Rules: ... Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". And "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)". "If text has no clear sections, just wrap paragraphs in

    tags". I need to map the content to HTML tags while preserving exact wording. Let's parse section by section: - "Business Area:" then "Risk" - this is metadata. Should I include it? The rules say "Keep and Structure: Job title, Company/Organisation name, Location, Job description and responsibilities, Requirements/qualifications, How to apply / application instructions, Salary, Deadline / closing date, Job ID / reference number, Contract type / level". But also "Preserve ALL original content word-for-word". The metadata like Business Area, Workplace Type, Location might be considered part of the job listing. However, the rules for formatting say use

    for introductory paragraphs and general text,

    for section headers,

    • for list items. It doesn't explicitly say to drop metadata. But the "Keep and Structure" list doesn't include Business Area, Workplace Type. However, "Preserve ALL original content word-for-word" is strong. I think I should include everything that's in the provided text, as the user gave me the plain-text job description and wants it formatted as clean semantic HTML. I'll include all sections as they appear, using appropriate tags. Let's re-read carefully: "Your ONLY job is to format it as clean semantic HTML." and "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". So I must output every word from the input, formatted with the specified tags. Structure mapping: - "Business Area:" + "Risk" -> could be

      or

      ? Not a main section. Maybe

      since it's metadata line. - "Workplace Type:" + "On-site" -> similar. - "Location - Town / City:" + "Cape Town" -> similar. - "Job Description:" + the paragraph. The paragraph has two sentences. I'll wrap in

      . But there's a "Job Description:" header. Should I use

      for "Job Description"? The rules say use

      for section headers like Responsibilities, Qualifications, etc. "Job Description" might be a header. I'll treat "Job Description:" as an

      , and the text following as

      . But the rule says "Use

      for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". "Job Description" isn't listed, but it's a section. I could use

      for "Job Description:" and the text, or

      . To be safe, I'll follow the pattern: section header as

      , following content as

      or

      • . But the rule says "If text has no clear sections, just wrap paragraphs in

        tags". There are clear sections. Let's look at the actual sections present: - Business Area - Workplace Type - Location - Town / City - Job Description - Key Responsibilities - Qualifications and Experience - Competencies The "Keep and Structure" list mentions: Job title (not present in text?), Company/Organisation name (not present?), Location (present), Job description and responsibilities (present), Requirements/qualifications (present), How to apply / application instructions (not present), Salary (not present), Deadline / closing date (not present), Job ID / reference number (not present), Contract type / level (not present). The text doesn't have some of those, but I must preserve all original content. I'll format what's there. How to handle "Key Responsibilities:" followed by a long paragraph of text that's actually list items without bullets. The text: "Assist team to achieve a balanced credit portfolio by accurately forecasting expected results Develop and implement champion/challenger customer strategies that deliver performance in line with Board expectations Monitor portfolio performance and ensure book performance meet pre-defined KPI’s by pro-actively proposing changes Modelling experience required (built and implemented statistical models) Investigating data integrity issues, testing assumptions and validating analytical results, ensuring accuracy of findings Create new account management strategies to optimise the business objectives within specific constraints Undertaking analysis to determine the impact of strategy changes to areas of application and account management strategies Presenting ideas via reports and presentations, outlining findings and making recommendations for improvements to senior stakeholders Forecasting and monitoring implemented strategies using statistical techniques Project manage the implementation of strategy changes into live systems Credit scoring experience (highly advantageous)" This is a block of text under "Key Responsibilities:". The rule says "Use

        • for list items (duties, requirements, qualifications, skills)". But the original text doesn't have bullet points; it's continuous prose. However, it's clearly intended as a list of responsibilities. The rule says "Preserve ALL original content word-for-word". If I convert to
          • , I'm changing the structure but preserving content word-for-word within li elements. But the text is not naturally separated into list items; it's one continuous paragraph. The rule also says "If text has no clear sections, just wrap paragraphs in

            tags". But this has a clear section header "Key Responsibilities:". I need to decide: keep as

            or make

            • . The instruction: "Use
              • for list items (duties, requirements, qualifications, skills)". It doesn't say "always convert to ul". It says use for list items. If the content is paragraph-style, I should keep as

                . But it's ambiguous. Let's look at the exact text: it's a sequence of duties without bullet markers. I think the safest is to wrap the whole thing in a

                tag, as it's presented as continuous text. However, the section header "Key Responsibilities:" suggests it's a list. I could split by sentences or logical breaks, but the rule says "do not add, remove, summarise, or rephrase". Splitting into li would be adding structure not originally there, but it's required by the format rules. There's a conflict: "Preserve ALL original content word-for-word" vs "Use

                • for list items". I need to interpret this correctly. Typically in these prompts, the expectation is to extract the list items as
                • items, splitting on natural breaks (like sentence endings or logical points). But the text has no explicit separators. Let's examine the text flow: It's one long sentence/paragraph. If I split it, I'd be rephrasing/adding breaks. The rule "Preserve ALL original content word-for-word" might mean the text content inside tags must be exact, but tagging structure is allowed. I think I should treat it as a

                  block because it's not originally marked as a list. But the section header "Key Responsibilities:" is there. I'll check similar tasks: usually, if the text under a header is continuous prose, it stays as

                  . If it has bullet points or clear items, it becomes

                  • . Here, it's continuous. I'll keep as

                    . Next: "Qualifications and Experience:" followed by text that mixes sentences and what looks like bullet points but are run together. Again, continuous prose. I'll keep as

                    . "Competencies:" followed by bullet points with "•" symbols. The text: "• Understanding of the credit life cycle • Revolving store card or credit card experience advantageous • Ability to work efficiently under pressure and within structured and unstructured parameters • Advantageous to have predictive Analytics experience with a highly numerate background • Must be able to monitor models and report back to the board • Must assist in growing team with relevant support, training programs and be seen as a mentor • High attention to detail driving a need for 100% accuracy • High level of integrity and confidentiality • Experienced user of Microsoft Office suite (Excel, PowerPoint, Word) • Experience in SAS preferred (base and/or Enterprise Guide and/or SAS Viya) extremely advantageous SQL/ Python." Here, there are "•" bullet symbols. The rule says "Use

                    • for list items". These are clearly list items, even though they're separated by spaces instead of new lines, but they have "•" markers. I should convert them to
                      • , preserving the text inside li exactly (including the "•"? Or should I remove the bullet marker and use
                      • text? The rule says "Preserve ALL original content word-for-word". If I remove the "•", I'm changing the content. I should keep the "•" inside the
                      • , or maybe the "•" is considered formatting artifact. The user said "REMOVE all of the following: ... Stray numbers or formatting artifacts" but that was in the first prompt's context? Wait, the current prompt is a different task: "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." The rules are listed under "Rules:". It says "Use
                        • for list items (duties, requirements, qualifications, skills)". It doesn't say to remove bullet markers. I think I should keep the content as-is, including the "•" if present, or perhaps the "•" is part of the original text and must be preserved. I'll include the "•" inside the
                        • text, or maybe just the text without the symbol? To be safe and preserve word-for-word, I'll keep the exact text including the "•" characters, but wrap each in
                        • . However, the "•" might be considered a formatting artifact. Let's read the original: it's given as a single line with "•" separated by spaces. I'll treat each "• ..." as an
                        • item, keeping the "•" at the start, or maybe strip it? The rule "Preserve ALL original content word-for-word" suggests I should not strip it. I'll keep it. But if I put "•" inside
                        • , it's still word-for-word. I'll do that. Now, metadata sections: "Business Area:", "Workplace Type:", "Location - Town / City:". These are not in the "Keep and Structure" list, but "Preserve ALL original content word-for-word" applies. I'll include them. How to format? Use

                          or

                          ? They are section-like. I'll use

                          for each, or maybe

                          for the label and

                          for value? The rules say "Use

                          for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". "Business Area" etc. aren't listed, but I could use

                          . I'll use

                          for each metadata line, or combine. To preserve word-for-word, I'll just wrap the whole line in

                          . "Job Description:" header + paragraph. I'll use

                          Job Description

                          and then

                          the paragraph

                          . But the header "Job Description:" includes the colon. Should I include the colon in the

                          ? "Preserve ALL original content word-for-word". If I write

                          Job Description

                          , I'm dropping the colon. I should probably keep "Job Description:" as the header text, maybe

                          Job Description:

                          . But the rule lists examples without colons: "Responsibilities, Qualifications, ...". I'll include the colon to be safe, as removing it would change content. Similarly for "Key Responsibilities:", "Qualifications and Experience:", "Competencies:". Let's plan the HTML structure: ```

                          Business Area: Risk

                          Workplace Type: On-site

                          Location - Town / City: Cape Town

                          Job Description:

                          Based at our Head Office in Cape Town, this position requires that you to find innovative ways to leverage the vast amount of data and information at your disposal to create customer strategies that drive up profit within constraints. Work within the Risk and Analytics department to enhance Truworths’ company performance by providing information, analyses, reports and technical support for the development and implementation of solutions .

                          Key Responsibilities:

                          Assist team to achieve a balanced credit portfolio by accurately forecasting expected results Develop and implement champion/challenger customer strategies that deliver performance in line with Board expectations Monitor portfolio performance and ensure book performance meet pre-defined KPI’s by pro-actively proposing changes Modelling experience required (built and implemented statistical models) Investigating data integrity issues, testing assumptions and validating analytical results, ensuring accuracy of findings Create new account management strategies to optimise the business objectives within specific constraints Undertaking analysis to determine the impact of strategy changes to areas of application and account management strategies Presenting ideas via reports and presentations, outlining findings and making recommendations for improvements to senior stakeholders Forecasting and monitoring implemented strategies using statistical techniques Project manage the implementation of strategy changes into live systems Credit scoring experience (highly advantageous)

                          Qualifications and Experience:

                          Preferred relevant post-graduate Degree with mathematical or statistical oriented subjects Business Science Degree or Business finance degree 3+ or more years’ experience in consumer credit (within a Credit Risk analytics environment) with demonstrated ability to implement solutions based on findings from analytical projects Understanding of the credit life cycle Revolving store card or credit card experience advantageous Ability to work efficiently under pressure and within structured and unstructured parameters Advantageous to have predictive Analytics experience with a highly numerate background Must be able to monitor models and report back to relevant stakeholders High attention to detail driving a need for 100% accuracy High level of integrity and confidentiality Experienced user of Microsoft Office suite (Excel, PowerPoint, Word) Experience in SAS, SQL and/or Python preferred (base and/or Enterprise Guide and/or SAS Viya) advantageous

                          Competencies:

                          • • Understanding of the credit life cycle
                          • • Revolving store card or credit card experience advantageous
                          • • Ability to work efficiently under pressure and within structured and unstructured parameters
                          • • Advantage