Part-time Financial Advisor

for intro 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
  , no
  . Return only HTML. We need to parse the given raw text (which includes HTML tags with styles etc). We must extract the content and produce clean HTML. Given the raw text includes many

  etc. We need to ignore those and just output content with appropriate tags. Let's extract the content: First line:

  Let's Write Africa's Story Together!

  Content: "Let's Write Africa's Story Together!" (the HTML entity ' is apostrophe). Should preserve as is? The rule: preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. So we need to keep the exact characters as they appear in the source, but we can convert HTML entities? The source includes ' which is an HTML entity for apostrophe. If we output as plain text, we should keep the entity? Usually we would output the actual character? The instruction: preserve ALL original content word-for-word. The original content includes the entity '. So we should keep that exactly. However, typical HTML output would interpret it as apostrophe; but we are outputting HTML, so the entity will be rendered as apostrophe anyway. It's fine to keep the entity. Thus first line: Let's Write Africa's Story Together! Next:

  Old Mutual is a firm believer in the African opportunity and our diverse talent reflects this.

  Content: "Old Mutual is a firm believer in the African opportunity and our diverse talent reflects this." Then there are empty

  tags. Then

  Part-time opportunity:

  Then a

  with list items. We need to decide section headers. The content includes: - "Part-time opportunity:" maybe not a section header but could be considered intro. Then list items under that. Then after list, there is empty p. Then

  Skills

  Then empty p. Then a line: "Building Trust, Consultative Selling, Customer-Focused, Customer Service, Customer Understanding, Direct Selling, Identifying Sales Opportunities, Oral Communications, Probing Questions, Qualifying Prospects, Sales Data Management, Sales Software, Strategic Selling, Strengthening Customer Relationships" Then empty p. Then
  (empty) Then

  Competencies

  Then empty p. Then a series of lines each preceded by
  etc. Actually the pattern: after Competencies, there is empty p, then
  then "Action Oriented", then
  , then "Balances Stakeholders", etc. So each competency is on its own line after an empty h3. We need to decide how to represent these. According to rules, we should use

  for section headers like Skills, Competencies, Education, etc. And use

  • for list items (duties, requirements, qualifications, skills). For Skills, we have a comma-separated list; we could treat each skill as list item. For Competencies, each line is a competency; we could treat as list. Education: "NQF Level 5 - Higher, Advance or Occupational Certificate or equivalent" Closing Date: "29 September 2026 , 23:59" Then an italic bold paragraph about appointment. Then final line:

    The Old Mutual Story!

    Content: "The Old Mutual Story!" with emphasis. We need to output HTML with

    for intro paragraphs and general text. Use

    for section headers. Use

    • for list items. We must preserve all original content word-for-word. So we cannot change punctuation, spacing, etc. However we need to wrap in tags. We need to decide what constitutes a section header. The original text uses Skills, Competencies, Education, Closing Date. Also maybe "Part-time opportunity:" could be considered a header but not in list of examples. Could treat as

      as well? The rule 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 headers, but we should follow the pattern. Likely we should treat Skills, Competencies, Education, Closing Date as

      . Also maybe "Part-time opportunity:" could be a

      but it's not in the examples; but we could still use

      as a header. However the rule says "Use

      for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". It doesn't say we cannot use for others, but we should use for those. Safer to treat "Part-time opportunity:" as a

      with bold? But we cannot use inline styles or tags? The rule says use

      for introductory paragraphs and general text. It doesn't forbid using inside

      . However we must preserve original content word-for-word, which includes the tags. But we are to output HTML; we could keep the inside

      . However the rule says "Use

      for introductory paragraphs and general text". It doesn't forbid other tags inside. But we should avoid adding extra tags not needed. However we must preserve original content word-for-word, which includes the tags. If we replace with nothing, we would be removing content. So we need to keep the bold markup? The original content includes Part-time opportunity:. If we output just plain text "Part-time opportunity:" we would be removing the tags, which is a change. The rule says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. That suggests we should keep the exact original text, including HTML tags? But we are to output clean semantic HTML, removing styling etc. The instruction earlier: "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." The given job description includes HTML tags with styles etc. We need to strip those and produce clean semantic HTML. So we are allowed to remove the style tags and classes, but we must keep the textual content. The bold tags likely indicate semantic emphasis; we could represent that with or but the rule says use

      for introductory paragraphs and general text,

      for section headers,

      • for list items. It doesn't forbid using or inside

        . However to preserve original content word-for-word, we need to keep the meaning of bold. Using is acceptable semantic HTML. But the rule didn't forbid using . It only said use

        for introductory paragraphs and general text,

        for section headers,

        • for list items. It didn't say we cannot use other tags. So we can use to represent bold. Thus we can convert Part-time opportunity: to

          Part-time opportunity:

          . That preserves the bold semantics. Similarly for Skills we will make

          Skills

          (since it's a section header). The bold is not needed as header already implies. For Competencies ->

          Competencies

          Education ->

          Education

          Closing Date ->

          Closing Date

          The italic bold paragraph:

          The appointment will be made from the designated group in line with the Employment Equity Plan of Old Mutual South Africa and the specific business unit in question.

          We could represent as

          The appointment will be made from the designated group in line with the Employment Equity Plan of Old Mutual South Africa and the specific business unit in question.

          Finally the emphasis-2 span with italic bold bold: The Old Mutual Story! We could output

          The Old Mutual Story!

          (note double bold becomes strong). Or we could keep double strong? Not needed. Now the list items under "Part-time opportunity:" are currently in a
          • ... Already list items. We need to preserve them as list items under maybe a
            under a section? The rule says use
            • for list items (duties, requirements, qualifications, skills). So we can keep them as
              • ... The preceding text "Part-time opportunity:" could be a header (

                ) and then the list. Now the Skills line: it's a comma-separated list of skills. We should convert each skill to

                inside a

                under

                Skills

                . The original text: "Building Trust, Consultative Selling, Customer-Focused, Customer Service, Customer Understanding, Direct Selling, Identifying Sales Opportunities, Oral Communications, Probing Questions, Qualifying Prospects, Sales Data Management, Sales Software, Strategic Selling, Strengthening Customer Relationships". We need to split by commas and trim spaces. Must preserve original content word-for-word: we cannot change the wording, but we can split into list items; each item must be exactly as appears between commas, preserving internal punctuation. The original includes hyphens, etc. We'll produce list items exactly as they appear (including hyphen). Ensure no extra spaces. Similarly Competencies: each line after an empty

                is a competency: "Action Oriented", "Balances Stakeholders", "Builds Networks", "Collaborates", "Communicates Effectively", "Customer Focus", "Drives Results", "Ensures Accountability". We'll make list items. Education: "NQF Level 5 - Higher, Advance or Occupational Certificate or equivalent". This is a sentence; we can keep as

                under

                Education

                . No list needed. Closing Date: "29 September 2026 , 23:59". Note there is a space before comma. We'll keep exactly. Now the introductory paragraphs before "Part-time opportunity:": - "Let's Write Africa's Story Together!" - "Old Mutual is a firm believer in the African opportunity and our diverse talent reflects this." We can wrap each in

                . Also there are empty

                tags we ignore. Now after the list, there is empty p then Skills header. Now after Skills list, there is empty p then

                then Competencies header. We'll ignore empty tags. Now after Competencies list, there are empty p then Education header. Now after Education paragraph, empty p then Closing Date header. After Closing Date line, empty p then italic bold paragraph. After that, empty p then final emphasis line. Now produce HTML. We must not use
                , no classes, no inline styles, no
                . Use only

                ,

                ,

                ,
                • , , as needed. Let's construct. Start:

                  Let's Write Africa's Story Together!

                  Old Mutual is a firm believer in the African opportunity and our diverse talent reflects this.

                  Then maybe a

                  for the Part-time opportunity header? We'll use

                  Part-time opportunity:

                  (preserving colon). Then the list. But the original had Part-time opportunity:. We'll make

                  Part-time opportunity:

                  ? However header already bold; we can just use

                  Part-time opportunity:

                  . The bold is not needed. But to preserve original content word-for-word, we might need to keep the bold semantics. Using

                  already implies heading; it's okay. I'll use

                  Part-time opportunity:

                  Then
                  with list items. List items as given: - Part-time Financial Adviser - Grade 12 - Currently in an existing role which he or she wants to retain, but supplement value proposition and/or income by offering financial advice - Access to in-segment market and existing network - DOFA/Fit & proper - A valid Driver’s licence and own car - A clear criminal and credit check - Proven computer literacy and digital dexterity - Excellent communication skills (written and verbal) - Sound planning and organising abilities - Ability to collate, analyse and synthesize information - Entrepreneurial mindset - Sound business acumen - GRIT, resilience and tenacity to stay the course. - Sales orientation Note: "DOFA/Fit & proper" includes & entity. We must preserve that exactly. So list item: "DOFA/Fit & proper". Also "Driver’s licence" includes a curly apostrophe? The source: "Driver’s licence". That's a curly apostrophe (unicode). We'll keep as is. Now after list, we have Skills.

                  Skills

                  • Building Trust
                  • Consultative Selling
                  • Customer-Focused
                  • Customer Service
                  • Customer Understanding
                  • Direct Selling
                  • Identifying Sales Opportunities
                  • Oral Communications
                  • Probing Questions
                  • Qualifying Prospects
                  • Sales Data Management
                  • Sales Software
                  • Strategic Selling
                  • Strengthening Customer Relationships
                  Now Competencies:

                  Competencies

                  • Action Oriented
                  • Balances Stakeholders
                  • Builds Networks
                  • Collaborates
                  • Communicates Effectively
                  • Customer Focus
                  • Drives Results
                  • Ensures Accountability
                  Now Education:

                  Education

                  NQF Level 5 - Higher, Advance or Occupational Certificate or equivalent

                  Now Closing Date:

                  Closing Date

                  29 September 2026 , 23:59

                  Now the italic bold paragraph:

                  The appointment will be made from the designated group in line with the Employment Equity Plan of Old Mutual South Africa and the specific business unit in question.

                  Now final emphasis:

                  The Old Mutual Story!

                  Check we haven't missed any content: The original also had some empty

                  and

                  tags; we ignored them as they have no content. Now ensure we haven't added or removed any content. Let's verify each piece. Original content pieces: 1. Let's Write Africa's Story Together! -> we have p with that exact string. 2. Old Mutual is a firm believer in the African opportunity and our diverse talent reflects this. -> p with that exact string. 3. Part-time opportunity: -> we used h4 Part-time opportunity: (no bold). The original had bold. We lost bold styling but kept text. Is that considered removal? The rule says preserve ALL original content word-for-word. The bold tags are part of original content. If we drop them, we are removing markup. However the instruction earlier: "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." The given job description includes HTML tags with styles etc. So we are to strip those and produce clean semantic HTML. So we can drop the tags and replace with semantic heading or strong. That seems acceptable per the task. The rule about preserving content likely refers to the textual content, not the markup. So okay. 4. List items: we kept each exactly. Check each list item for exactness: - "Part-time Financial Adviser" matches. - "Grade 12" matches. - "Currently in an existing role which he or she wants to retain, but supplement value proposition and/or income by offering financial advice" matches. - "Access to in-segment market and existing network" matches. - "DOFA/Fit & proper" matches (including &). - "A valid Driver’s licence and own car" matches (including curly apostrophe). - "A clear criminal and credit check" matches. - "Proven computer literacy and digital dexterity" matches. - "Excellent communication skills (written and verbal)" matches. - "Sound planning and organising abilities" matches. - "Ability to collate, analyse and synthesize information" matches. - "Entrepreneurial mindset" matches. - "Sound business acumen" matches. - "GRIT, resilience and tenacity to stay the course." matches (including period). - "Sales orientation" matches. Now Skills: we split by commas. Need to ensure we didn't lose any punctuation inside items. Let's verify each: Original string: "Building Trust, Consultative Selling, Customer-Focused, Customer Service, Customer Understanding, Direct Selling, Identifying Sales Opportunities, Oral Communications, Probing Questions, Qualifying Prospects, Sales Data Management,

  Translated by AI — may not be perfect

  Show original