DC Specialist- Centurion

,

for section headers,

• for list items. No CSS classes, no inline styles, no
  , no
  . Must preserve all original content word-for-word, no addition, removal, summarizing, rephrasing. Must convert the given raw HTML (with inline styles etc.) into proper semantic HTML. We need to extract the content and restructure. First, let's parse the raw text. Given:

  Let's Write Africa's Story Together!

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

  Job Description

  Join Old Mutual’s Personal Financial Advice Team as a Development Coach – Shape the Future of Financial Advice! The role is based in Centurion, Johannesburg.

  Are you a high-energy coach who thrives in the real world, not the classroom? Do you believe in hands-on guidance, not theory? If yes, Old Mutual’s Personal Finance Advice (PFA) team wants you!

   

  We’re looking for Development Coaches who are passionate about execution, coaching, and making a tangible impact in the lives of new financial advisers.

   

  What You’ll Do:

  • Coach, don’t just train – Guide new advisers in the field, reinforcing habits and behaviours that lead to long-term success.
  • Drive performance from Day 1 – Equip advisers with the skills, discipline, and mindset to thrive in their first 24 months.
  • Partner for success – Work hand-in-hand with Business Managers to align coaching with real business goals.
  • Leverage tech, stay human – Help advisers integrate digital tools while building trust through personal, high-touch engagement.
  • Travel + virtual – Deliver consistent, high-impact coaching across regions via in-person and remote methods. 

  What You Bring:

  ✔ 5+ years in financial services, preferably in coaching, enablement, or field execution
  ✔ A relevant degree or diploma (Business, Finance, Coaching, or similar)
  ✔ Deep understanding of sales, compliance, and what drives adviser success
  ✔ Proven ability to coach for behaviour change in a fast-paced, performance-driven environment
  ✔ Tech-savvy with a human-first coaching style

   

  Why Join Us?

  ✅ Shape the next generation of financial advisers
  ✅ Make a real impact on adviser performance and community financial wellness
  ✅ Operate nationally with flexible, remote working and regional travel
  ✅ Be part of a 180-year legacy while driving modern, high-performance coaching

  If you’re ready to lead from the front and help build a new breed of client-centric, digitally enabled financial advisers, apply now.

   

  Old Mutual – #CoachingThatCounts #ExecutionExcellence #GrowWithUs

   

   

  Skills

  Building Trust, Change Management, Client Needs Assessments, Commercial Acumen, Consultative Selling, Customer-Focused, Customer Service, Customer Understanding, Direct Selling, Executing Plans, Identifying Customer Needs, Identifying Sales Opportunities, Sales Software, Strengthening Customer Relationships, Upselling

  Competencies

  Builds Effective Teams

  Builds Networks

  Business Insight

  Collaborates

  Communicates Effectively

  Customer Focus

  Drives Results

  Ensures Accountability

  Education

  Closing Date

  17 September 2026 , 23:59

  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.

  The Old Mutual Story!

  We need to produce HTML with

  for paragraphs,

  for section headers (like Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). The original has headings like "Job Description", "What You’ll Do:", "What You Bring:", "Why Join Us?", "Skills", "Competencies", "Education", "Closing Date". Also there is an introductory part: "Let's Write Africa's Story Together!" and "Old Mutual is a firm believer...". Also there is a line: "Join Old Mutual’s Personal Financial Advice Team as a Development Coach – Shape the Future of Financial Advice! The role is based in Centurion, Johannesburg." This seems like a summary/intro. We must preserve all original content word-for-word. So we need to output exactly the same text but wrapped in appropriate tags. We cannot add or remove any characters. Must preserve spaces, punctuation, special characters like ' (which is an apostrophe), + (plus sign), etc. Also there are non-breaking spaces ( ) represented as  ? Actually they appear as a space but maybe it's a non-breaking space. We must keep them as is. We must not add any extra text like "Here is the cleaned version". Just output HTML. We need to decide which parts are section headers. According to rules: 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", "What You’ll Do:", "What You Bring:", "Why Join Us?", "Skills", "Competencies", "Education", "Closing Date" as section headers and wrap them in

  . However "Job Description" might be considered a section header. Also "What You’ll Do:" maybe considered Responsibilities. "What You Bring:" maybe Qualifications/Requirements. "Why Join Us?" maybe About the Role or Benefits. "Skills", "Competencies", "Education", "Closing Date" are clearly sections. We also have list items: The "What You’ll Do:" section has

  • items. Those should stay as
    • . The "What You Bring:" section currently is a series of lines with ✔ ...
      . Those are not wrapped in
      • . According to rules, we should use
        • for list items (duties, requirements, qualifications, skills). The "What You Bring:" appears to be a list of requirements. So we should convert those lines into
          • items. However we must preserve original content word-for-word. Changing the format from ✔ ...
            to
          • ...
          would alter the content (removing the span and checkmark). The checkmark is part of the content: "✔". We must preserve it. So we could keep the same content but wrap each line in
          • tags, preserving the inner HTML (including the span and checkmark). That would be adding
          • tags but not removing content. That's allowed because we are adding tags, not altering text. The rule: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". Adding tags is okay as long as we don't change the text content. So we can wrap each line in
          • and keep the inner content exactly. Similarly, the "Why Join Us?" section has lines with ✅ ...
            . Those could be turned into
            • as well. The "Skills" section currently is a plain line: "Building Trust, Change Management, ...". That's a comma-separated list. Should we turn into
              • items? The rule says use
                • for list items (duties, requirements, qualifications, skills). So we should split the skills into list items. However we must preserve original content word-for-word. If we split, we would be adding
                • tags and removing commas? Actually we could keep the commas inside
                • but that would change the representation (the original had a single line with commas separating items). If we wrap each skill in
                • , we would be removing the commas between items (or we could keep them inside each
                • but then we would have extra commas). The original text: "Building Trust, Change Management, Client Needs Assessments, Commercial Acumen, Consultative Selling, Customer-Focused, Customer Service, Customer Understanding, Direct Selling, Executing Plans, Identifying Customer Needs, Identifying Sales Opportunities, Sales Software, Strengthening Customer Relationships, Upselling". If we turn each into
                • we would lose the commas separating them (unless we keep the commas inside each
                • but then we would have duplicates). The rule says preserve ALL original content word-for-word. Adding tags is okay, but we cannot remove or change any characters. If we wrap each skill in
                • and keep the commas inside the
                • , the commas remain, but we would also have the commas as part of each item, which changes the visual but the characters are still there. However we would also be adding
                • and
                tags, which is allowed. The original text had commas separating items; after wrapping each item in
                • , the commas would still be present inside each
                • (if we keep them). But then the list would show each item with a trailing comma, which is not exactly the same as original but the characters are still present. However the original had commas between items, not after each item (except maybe the last). If we keep the commas inside each
                • , we would have commas after each item, which adds extra commas? Actually original: "Building Trust, Change Management, Client Needs Assessments, Commercial Acumen, Consultative Selling, Customer-Focused, Customer Service, Customer Understanding, Direct Selling, Executing Plans, Identifying Customer Needs, Identifying Sales Opportunities, Sales Software, Strengthening Customer Relationships, Upselling". There is a comma after each item except after the last "Upselling". If we wrap each item in
                • and keep the exact same text inside each
                • , we would have:
                • Building Trust,
                ??? Wait we need to decide how to split. The original string includes commas and spaces. To split into items, we would need to remove the commas that separate items, or keep them as part of items. If we keep them, each
                • would contain a trailing comma (except maybe last). That would add a comma after each item, which is not present in original after the last item but is present after each item except last. Actually original already has a comma after each item except last. So if we keep the comma inside each
                • , we would have exactly the same as original: each
                • contains the item plus a trailing comma (except last). That would preserve the commas. However the visual separation would be
                • Building Trust,
                • Change Management,
                ... which when rendered would show each item with a comma, but the original had commas separating items, not each item having a comma after it. But the characters are same: original had "Building Trust, Change Management, ...". If we output "
                • Building Trust,
                • Change Management,
                ", the concatenated inner text (without tags) would be "Building Trust, Change Management, ". Actually there would be a space after comma inside each
                • . The original had a space after each comma. So the concatenated inner text would be "Building Trust, Change Management, Client Needs Assessments, ..." exactly same as original, because the commas and spaces are inside each
                • . The only difference is that we have added
                • and
                tags around each item. That's allowed. Thus we can convert the skills line into a
                with each skill as
                • preserving the internal text (including commas). However we need to split the string at commas. But we must be careful not to lose any characters. We'll need to parse the string and split by ", " (comma space) maybe. But there are also items like "Customer-Focused" which includes a hyphen, no comma inside. So splitting by ", " should work. However there is also "Identifying Customer Needs, Identifying Sales Opportunities" etc. So splitting by ", " yields items. But we must ensure we don't inadvertently split inside an item that contains a comma (none appear). So safe. Similarly for Competencies: The text appears as: "Builds Effective Teams
                  Builds Networks
                  Business Insight
                  Collaborates
                  Communicates Effectively
                  Customer Focus
                  Drives Results
                  Ensures Accountability" There are
                  empty tags between each competency. The original includes those empty

                  tags. We must preserve them word-for-word. So we cannot remove them. However we need to output semantic HTML: we should use

                  for section headers, and

                  • for list items. The empty

                    tags are not needed; but we must preserve all original content. If we remove them, we would be removing content (the

                    tags). That's not allowed. So we must keep them as they appear. However we could wrap each competency in
                  • and keep the
                    tags as part of the content inside
                  • . That would preserve them. But the original had
                    between items, not inside items. If we put each competency as
                  • Builds Effective Teams
                    Builds Networks... that would be wrong. We need to think: The original text after "Competencies" includes:
                    Builds Effective Teams
                    Builds Networks
                    Business Insight
                    Collaborates
                    Communicates Effectively
                    Customer Focus
                    Drives Results
                    Ensures Accountability

                    Translated by AI — may not be perfect

                    Show original