TF

Shared Beauty Advisor Clarins (120hr) - Foschini - Gateway

Full-time Kwazulu Natal, South Africa, ZA
Posted 3 weeks, 6 days ago 103 views 0 applications

Job Description

We need to output clean semantic HTML with

for intro paragraphs and general text,

for section headers (Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). Use
  • for list items. No CSS classes, no inline styles, no
    , no
    . Preserve all original content word-for-word, do not add, remove, summarise, or rephrase. We have raw HTML with many spans and divs. Need to extract the text content exactly as is, preserving spaces and punctuation, but we must output as HTML with appropriate tags. We need to identify sections: The text includes: - Responsibilities: (header) - then list items: Achievement of all store turnover, new accounts & rewards; Providing excellent customer service; Stock management; Daily stock counts; Visual merchandising; Execution of administrative tasks - Qualifications: (header) - list items: Beauty related qualification desirable; 2-3 years retail experience; 1-2 years cosmetics experience - Skills: (header) - list items: Excellent selling skills; Strong interest in retail and the cosmetic field in particular; The ability to communicate and persuade effectively at all levels; Ability to show initiative and be resourceful; Ability to source and implement effective solutions in a fast-paced environment; Customer Service Delivery; Planning & Organising; Strategic Sales Planning; Managing the Sales Process; Customer Value Management - Competencies and behaviours for success: (header) - list items: many items (some duplicates). Need to preserve exactly as given. - Then a line: Preference will be given, but not limited to candidates from designated groups in terms of the Employment Equity Act. We must preserve all original content word-for-word. Need to ensure we keep special characters like & (should stay as &? The original text includes "&" inside the responsibilities list: "Achievement of all store turnover, new accounts & rewards". That is HTML entity for &. We must preserve exactly that string. Similarly there are other & like "Planning & Organising". Also there are special spaces like  (non-breaking space?) In the text there are some weird spaces like "The ability". That's a narrow no-break space? We must preserve exactly as given. However when outputting as plain text inside HTML, we can keep the characters as they appear. The input includes Unicode characters like U+202F (narrow no-break space) maybe. We'll just copy them. We must not add or remove anything. So we need to output exactly the same textual content, but wrapped in appropriate tags. We must not use
    or
    . So we will use

    for each section header, then
    • for each list. For any paragraphs not in lists, we wrap in

      . There's no intro paragraph besides maybe none. The headers are given as strong text. We'll convert those to

      . We need to ensure we don't lose any text. Let's extract the exact strings. First, the Responsibilities header: "Responsibilities: " The inner text is "Responsibilities:" followed by a non-breaking space? Actually   is HTML entity for a space. We need to preserve that as " "? The original text includes the entity. The instruction: preserve ALL original content word-for-word. So we should keep " " as literal characters? In the source it's an HTML entity, but the visible text is a space. However "word-for-word" of the given raw text includes the entity " ". So we should output that exactly. But then we are wrapping in

      tags; inside we will put the header text exactly as it appears, including the entity. However note that the header originally had a tag around "Responsibilities:" and then a   after. The strong tag is not needed; we just need the text. The instruction: preserve all original content word-for-word. Does that mean we must keep the strong tags? No, we are to format as clean semantic HTML, using

      for section headers. So we should convert the header to

      and include the text content (excluding the markup). The text content is "Responsibilities:" plus a space (the  ). Should we keep the   as a space? The original visible text is "Responsibilities: " with a space after colon. The   is just a non-breaking space. In plain text, it's a space. I'd output a regular space. But to be strictly word-for-word of the visible text, we could output a regular space. The instruction says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. If we replace   with a regular space, we are changing the character entity. That's a change. However the visible output would be same but not exactly same characters. The safer is to keep the   entity as is. But inside an

      tag, if we write "Responsibilities: " that will be rendered as a space. That's okay. We'll keep the entity. Similarly for Qualifications header: "Qualifications:" with   after? Actually after Qualifications: there is a  . So there is a space after colon. We'll keep " ". Skills header: "Skills: " with   after colon. Competencies and behaviours for success: header: "Competencies and behaviours for success: " with   after colon. Preference line: "Preference will be given, but not limited to candidates from designated groups in terms of the Employment Equity Act." No trailing   after? Actually after that there is a  . So there is a space after the period? The text includes the period then  . We'll keep the period and then   maybe. Now list items: each
    • contains a

      with a span containing the text and then an EOP span with  . So the text inside each li is the visible text plus a trailing space (non-breaking). We need to preserve that. So each

    • content should be exactly the text from the inner span, including any   after? Actually the inner span is class="TextRun ..." and contains the visible text. After that there is a separate span class="EOP" with  . So the visible text does not include the  . The   is after the text, maybe to add spacing. If we preserve word-for-word, we should include that   after the text inside the
    • . But the
    • content currently is:

      ...Achievement of all store turnover, new accounts & rewards 

      . So the inner text of the p is the TextRun content plus the EOP content. So we need to output that combined: "Achievement of all store turnover, new accounts & rewards " (including the   entity). Similarly for each. Thus each list item should have the text exactly as appears, including the trailing  . Now we need to output HTML:

      Responsibilities: 

      then
      • Achievement of all store turnover, new accounts & rewards 
      • ... etc. But note that the header already had a   after colon; we will keep that. Now after the responsibilities list, there is a
         
        (empty div with a space). That's just a blank line; we should ignore as it's not meaningful content? It's a div with   (a space). According to rules, we should preserve all original content word-for-word. However we are not allowed to use
        . We must not add
        tags. But we could represent that space as a

        containing  ? However the instruction says use

        for introductory paragraphs and general text. That empty div is just a space; maybe we can ignore it as it's not meaningful content. But "preserve ALL original content word-for-word" suggests we should keep that space. However we cannot use

        . We could represent it as a

         

        . That would be a paragraph containing a non-breaking space. That seems acceptable: it's general text, so

        . It doesn't add or remove content; we just change the tag from

        to

        . Is that allowed? The rule: "Use

        for introductory paragraphs and general text". So we can convert that div to a p. It's still preserving the content (the  ). So we should output

         

        for that empty div. Similarly there are many empty divs with   between sections. We'll convert each to

         

        . But we must be careful not to add extra paragraphs that weren't there. The original had many
         
        separators. We'll turn each into

         

        . Now after the qualifications header and list, there is a

        Skills: 

        ... So there is a nested div before the Skills header. We'll treat the header as

        Skills: 

        . The surrounding divs we ignore. After skills list, there is a div with the Competencies header. After competencies list, there is a div with the Preference line. After that, there are closing divs. Thus final HTML will be a sequence of:

        Responsibilities: 

        • Achievement of all store turnover, new accounts & rewards 
        • Providing excellent customer service 
        • Stock management 
        • Daily stock counts 
        • Visual merchandising 
        • Execution of administrative tasks 

         

        Qualifications: 

        • Beauty related qualification desirable 
        • 2-3 years retail experience 
        • 1-2 years cosmetics experience 
           

         

        Skills: 

        • Excellent selling skills 
        • Strong interest in retail and the cosmetic field in particular 
        • The ability to communicate and persuade effectively at all levels 
        • Ability to show initiative and be resourceful 
        • Ability to source and implement effective solutions in a fast-paced environment 
        • Customer Service Delivery 
        • Planning & Organising 
        • Strategic Sales Planning 
        • Managing the Sales Process 
        • Customer Value Management 
           

         

        Competencies and behaviours for success: 

        • Taking on new opportunities and tough challenges with a sense of urgency, high energy, and enthusiasm. 
        • Effectively building formal and informal relationship networks inside and outside the organization. 
        • Building strong customer relationships and delivering customer-centric solutions. 
        • Making good and timely decisions that keep the organization moving forward. 
        • Anticipating and adopting innovations in business-building digital and technology applications. 
        • Creating a climate where people are motivated to do their best to help the organization achieve its objectives. 
        • Making good and timely decisions that keep the organization moving forward. 
        • Using a combination of feedback and reflection to gain productive insight into personal strengths and weaknesses. 
        • Good verbal/ written communication skills and good organisational skills 
        • Strong organizational and planning skills 
        • The ability to multi-task in a fast-paced environment 
        • The ability to work independently 
        • The ability to take initiative 
        • A high level of attention to detail 
           

         

        Preference will be given, but not limited to candidates from designated groups in terms of the Employment Equity Act. 

        But note: The preference line originally had ... and then a   after. We converted to

        with ...  . However the instruction says use

        for introductory paragraphs and general text. It's okay to keep inside

        . That's fine. But we must not add any extra tags like if not needed? We are preserving original content, which includes the tags. So we should keep them. The preference line originally had Preference will be given, but not limited to candidates from designated groups in terms of the Employment Equity Act. followed by a  . So we need to output exactly that inside a

        . So

        Preference will be given, but not limited to candidates from designated groups in terms of the Employment Equity Act. 

        . Now check for any other text: There might be some stray spaces or line breaks. We'll ignore. Now ensure we didn't miss any list items: In qualifications list, third item had "
         " after the text inside the

        . Actually the HTML:  
         
        . Wait let's examine: The third qualification item:

        1-2 years cosmetics experience 
         

        So after the TextRun "1-2 years cosmetics experience", there is a span containing " 
         ". That means a non-breaking space, then a line break tag, then another non-breaking space. We must preserve that exactly. So the list item content should be: "1-2 years cosmetics experience 
         ". Note that the
        tag is present. However the rules say: No
        tags. We are not allowed to use
        tags. But we must preserve original content word-for-word. This is a conflict: we cannot use
        tags per rules, but we must preserve original content. 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". So we must not output
          tags. However we must preserve all original content word-for-word. If we omit the
          , we are removing content. But maybe the
          is just an artifact of formatting and not meaningful content; but the rule says preserve ALL original content word-for-word. However earlier we removed many tags like ,
          , etc. We are already removing those. So the instruction to preserve content likely refers to the visible text, not the markup. The earlier instruction in the first part (job listing editor) said to remove all formatting artifacts and keep only job information. Then the second part says format as clean semantic HTML, preserving ALL original content word-for-word — do not add, remove, summarise, or rephrase. This likely refers to the textual content after stripping markup. So we should ignore the
          as a formatting artifact and not include it. Similarly the   entities are formatting artifacts; we might convert them to regular spaces. The earlier instruction said remove stray numbers or formatting artifacts. So we should treat   as a space and
          as a line break to be ignored (maybe convert to space?). But the instruction for HTML formatting says no
          tags. So we should not output
          . We'll treat   as a regular space. We'll also ignore the
          entirely (maybe replace with space?). But to be safe, we can just output a space where
          appears, but not include the tag. Given the conflict, I think the intention is to keep the textual content, not the markup. So we will output plain spaces for   and ignore
          . Also we should not output any
          tags. Thus we will output list items with just the visible text, and a trailing space? Actually the   after the text is just a space; we can output a regular space after the text, but that might be unnecessary. Usually we don't need trailing spaces. Safer to output just the visible text without extra spaces. The earlier instruction said remove stray numbers or formatting artifacts. So we will strip   and
          . So we will output just the visible text. Thus we need to decide: The earlier part (job listing editor) said remove formatting artifacts. The second part (format as clean semantic HTML) says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. This is contradictory. However given the context, the second part likely refers to the cleaned job text (after removing artifacts). So we should preserve the cleaned textual content word-for-word. So we will output the visible text only, no extra spaces or entities. Thus we will output:

          Responsibilities:

          • Achievement of all store turnover, new accounts & rewards
          • ... But we need to keep the & as it's part of the visible text? The visible text shows "&" but the source had

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

        Free cover letter for this job

        Upload your CV and get a tailored cover letter in seconds — free, no account needed.

        Generate a Cover Letter 📝

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?