AD

Client Success Administrator

Full time Huawei Office Park, ZA
Posted 2 weeks, 1 day ago 100 views 0 applications

Job Description

We need to output clean semantic HTML per rules. Input includes HTML tags already, but we must output only HTML with

,

,
  • . No CSS classes, no inline styles, no
    , no
    . Must preserve all original content word-for-word, but we need to transform to proper tags. However we must not add or remove content. We need to keep the text exactly as given, but we can change tags to appropriate semantic ones. The original includes

    Position:

    etc. We need to replace those with appropriate tags: maybe

    for section headers. The instruction: Use

    for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). So we need to convert each heading to

    . Also we need to wrap introductory paragraphs in

    . The content includes many

    tags which we must strip style attributes and just keep

    . Also need to remove and tags? The rules say preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. That means we cannot remove tags like or because that would be removing content? Actually they are part of content. But we also must not use CSS classes, inline styles,

    ,
    . The original includes and tags inside headings. We could keep them? But they are tags; we are allowed to keep them? The instruction: Use

    for introductory paragraphs and general text; Use

    for section headers; Use
    • for list items. No CSS classes, no inline styles, no
      s, no
      tags. It doesn't forbid other tags like or . However we should aim to output clean semantic HTML; likely we should strip those formatting tags and just keep text. But "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase" suggests we cannot remove any text content, but we can change tags? Changing tags is not removing content, it's changing markup. The text inside tags remains same. Removing and would remove those tags but not the text; is that considered removing content? The content is the text; tags are not content. Usually "content" refers to the textual content. So we can strip styling tags. Safer to keep them? But they'd be inline styling? and are not CSS classes or inline styles, they are HTML tags. The rules didn't forbid them. However they said Use

      for introductory paragraphs and general text; Use

      for section headers; Use
      • for list items. That implies we should not use other tags for those purposes. But we could still have inside a

        maybe? Might be okay but not needed. Better to produce:

        Position:

        Client Success Administrator

        Job Description:

        To provide administrative support to the Client Success team on site

        Location:

        Huawei Office Park

        Contract Type:

        Permanent

        Minimum Requirements:

        Experience:

        • A minimum of +2 years’ HR administration experience

        Qualification:

        • Grade 12

        Additional Requirements:

        • Contract Renewals
        • Compliance Management
        • Employee Relations (liaise with assignees)
        • Attention to detail
        • Conducting recruitment checks
        • Drafting offers and Onboarding
        • Coordinate Induction

        Roles and Responsibilities:

        • Ensure correct backing documentation is attached to original invoices in preparation for delivery and scanned for payroll purposes;
        • Assist Assignees with Financial Services related products;
        • Assist operations with preparation of documentation for assignees; Complete site specific reports for operations;
        • Conduct compliance audits of files with a checklist in place in the front of each file;
        • Deliver invoices timeously and obtain proof of delivery and ensure proper record keeping thereof;
        • Draft information/reports on request;
        • Ensure compliance with all regulatory and legislative requirements , SOP's and corporate governance;
        • Ensure that the Client Success team is presented with accurate payroll data processed within deadline;
        • Maintain assignee files ensuring all documentation is scanned and uploaded onto Axapta (FTC updated with annexure A, licenses as required);
        • Process all payroll related transactions including COID, Annual Leave, Sick Leave, Family Responsibility leave;
        • Process Time and Attendance via payroll input sheets or automation;
        • Ensure that all client invoice queries are dealt with timeously in liaison with Credit Control and / or escalated as necessary;
        • Ensure that all client invoice queries are dealt with timeously in liaison with Credit Control and / or escalated as necessary;
        • Ensure own understanding and adherence to client service delivery to meet or exceed expectations;
        • Ensure that all client invoice queries are dealt with timeously in liaison with Credit Control and / or escalated as necessary;
        • Effectively participate as a team member to ensure effective and efficient service delivery and in execution of specified tasks.
        • Continuously follow up and engage with clients and Credit Control to ensure that invoices are paid timeously and within payment terms;
        We need to preserve original content word-for-word. Check we didn't lose any text: The original had duplicate lines for "Ensure that all client invoice queries are dealt with timeously in liaison with Credit Control and / or escalated as necessary;" appears three times. We kept three? Let's see: In our list we have that line appears three times? We have: - after "Process Time and Attendance..." we have "Ensure that all client invoice queries are dealt with timeously in liaison with Credit Control and / or escalated as necessary;" (first) - later "Ensure own understanding and adherence to client service delivery to meet or exceed expectations;" (different) - then "Ensure that all client invoice queries are dealt with timeously in liaison with Credit Control and / or escalated as necessary;" (second) - then "Effectively participate as a team member..." - then "Continuously follow up..." We missed one duplicate? Original had three occurrences of that line. Let's count original: List items: 1. Ensure correct backing documentation... 2. Assist Assignees... 3. Assist operations... 4. Conduct compliance audits... 5. Deliver invoices... 6. Draft information/reports... 7. Ensure compliance with all regulatory... 8. Ensure that the Client Success team... 9. Maintain assignee files... 10. Process all payroll related transactions... 11. Process Time and Attendance... 12. Ensure that all client invoice queries are dealt with timeously in liaison with Credit Control and / or escalated as necessary; 13. Ensure own understanding and adherence... 14. Ensure that all client invoice queries are dealt with timeously in liaison with Credit Control and / or escalated as necessary; 15. Effectively participate as a team member... 16. Continuously follow up and engage... So there are two occurrences of that line (items 12 and 14). Actually there are two, not three. The text shows three? Let's re-check original snippet: after item 11, there is line: "Ensure that all client invoice queries are dealt with timeously in liaison with Credit Control and / or escalated as necessary;" then later after item 13: "Ensure own understanding and adherence to client service delivery to meet or exceed expectations;" then item 14: "Ensure that all client invoice queries are dealt with timeously in liaison with Credit Control and / or escalated as necessary;" then item 15: "Effectively participate as a team member..." then item 16: "Continuously follow up and engage...". So exactly two duplicates. We have both. Good. Check we didn't miss any other items: we have all 16 items. Now ensure we didn't add extra spaces or change punctuation. We kept the text exactly as inside
      • tags. Need to ensure we preserved special characters like + which is HTML entity for plus sign. In original Minimum Requirements: "A minimum of +2 years’ HR administration experience". We kept that as is. Good. Also there is "SOP's". We kept that. Now check we removed all style attributes and extra empty

        tags. We removed them. That's okay as they were empty; removing them does not remove content. The instruction says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. Removing empty

        tags is removing tags but not content. Might be acceptable. However to be safe, we could keep empty

        tags as

        but they'd be empty paragraphs. The rules say use

        for introductory paragraphs and general text; empty paragraphs maybe okay but they'd be unnecessary. I'd keep them? The instruction says preserve ALL original content word-for-word. Empty

        tags are part of original content. If we remove them, we are removing content (the tags). But the phrase "content" likely refers to textual content. Usually in such tasks they want to strip formatting. I'd keep them? But they'd be empty

        which adds no text but still a tag. The rule says No CSS classes, no inline styles, no
        s, no
        tags. It doesn't forbid empty

        . I'd keep them to be safe. However they'd be unnecessary but not violating any rule. Let's include them as they were. Original had many

        and

        Job Description:

        etc. We need to preserve the text inside but we can change tags. For the headings we changed to

        . For the empty paragraphs we could keep as

        . But we also removed style attributes. That's removing inline styles, which is prohibited? The rule says No CSS classes, no inline styles. So we must remove inline styles. That's okay because we are not allowed to have them. So we must strip style attributes. That's removing them, but it's required by rule. So we must remove style attributes. That's fine. Thus we need to output HTML with only

        ,

        ,
        • . No other tags. So we must not keep or . So we strip them. That's okay because we are not allowed to have other tags? The rule didn't explicitly forbid or , but they said Use

          for introductory paragraphs and general text; Use

          for section headers; Use
          • for list items. It implies we should not use other tags for those purposes. Using inside a

            might be considered not following the rule. Safer to not use them. Thus final output as above, with empty

            tags where there were empty paragraphs? We removed them; but we could keep empty

            to preserve the placeholder. However they'd be empty paragraphs with no content, which is okay. But we removed many empty

            tags; maybe we should keep them as

            to preserve the original structure? The instruction says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. If we remove empty

            tags, we are removing content (the tags). But maybe they consider content as the visible text. I'd keep them to be safe. However they'd be empty

            which adds no visible text but still a tag. The rule says No CSS classes, no inline styles, no
            s, no
            tags. Empty

            is fine. Let's decide to keep empty

            tags as

            where they originally existed. But we need to know where they were. Looking at original: After

            Position:

            Client Success Administrator

            So after the position line, there were two empty

            tags. Then

            Job Description:

            then text "To provide administrative support..." then

            then

            Location:

            etc. Thus there are many empty paragraphs. We could keep them as

            . That would add no visible text but preserve original markup count. However the instruction says Use

            for introductory paragraphs and general text. Empty paragraphs are still

            . So we can keep them. Thus we need to output:

            Position:

            Client Success Administrator

            Job Description:

            To provide administrative support to the Client Success team on site

            Location:

            Huawei Office Park

            Contract Type:

            Permanent

            Minimum Requirements:

            Experience:

            • A minimum of +2 years’ HR administration experience

            Qualification:

            • Grade 12

            Additional Requirements:

            • Contract Renewals
            • Compliance Management
            • Employee Relations (liaise with assignees)
            • Attention to detail
            • Conducting recruitment checks
            • Drafting offers and Onboarding
            • Coordinate Induction

            Roles and Responsibilities:

              ...list items...
            We need to ensure we didn't add any extra

            beyond those originally present. Let's map. Original after Position: two empty p's. We'll output two

            . After Job Description heading: there was a

            Job Description:

            which we convert to

            Job Description:

            . Then the text line "To provide administrative support..." then two empty p's. So after that text we output two

            . After Location heading: similar pattern: after heading, two empty p's. After Contract Type heading: after heading, two empty p's. After Minimum Requirements heading: after heading, there is

            Experience:

            then empty p, then ul, then empty p, empty p, then

            Qualification:

            then empty p, then ul, then empty p, empty p, empty p? Let's check original:

            Minimum Requirements:

            Experience:

            • A minimum of +2 years’ HR administration experience

            Qualification:

            • Grade 12

            Additional Requirements:

            ... So after Qualification ul, there are two empty p's (the style ones) before Additional Requirements heading. Thus we need to replicate that. After Additional Requirements heading: there is a ul directly, then three empty p's? Original: after the ul, there is

            Roles and Responsibilities:

            ... So three empty p's. After Roles and Responsibilities heading: directly ul, then ends. Thus we need to output accordingly. Let's construct final HTML. We'll output:

            Position:

            Client Success Administrator

            Job Description:

            To provide administrative support to the Client Success team on site

            Location:

            Huawei Office Park

            Contract Type:

            Permanent

            Minimum Requirements:

            Experience:

            • A minimum of +2 years’ HR administration experience

            Qualification:

            • Grade 12

            Additional Requirements:

            • Contract Renewals
            • Compliance Management
            • Employee Relations (liaise with assignees)
            • Attention to detail
            • Conducting recruitment checks
            • Drafting offers and Onboarding
            • Coordinate Induction

            Roles and Responsibilities:

            • Ensure correct backing documentation is attached to original invoices in preparation for delivery and scanned for payroll purposes;
            • Assist Assignees with Financial Services related products;
            • Assist operations with preparation of documentation for assignees; Complete site specific reports for operations;
            • Conduct compliance audits of files

      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 ✍️

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?