TF

Furniture Consultant (40hr) - @home Livingspace - The Grove (Nelspruit)

Full-time Gauteng, South Africa, ZA
Posted 4 hours, 24 minutes ago 9 views 0 applications

Job Description

Here's a thinking process: 1. **Analyze User Input:** - User is acting as a job listing editor - I receive raw scraped text from a job website - My job: extract ONLY actual job information, return clean, readable format - Must REMOVE: social sharing, author bylines, "you may also like", navigation, comments, ads/promotions, cookie/subscription notices, duplicate text, category labels not part of job, stray numbers/formatting artifacts - Must KEEP and STRUCTURE: job title, company/name, location, job description/responsibilities, requirements/qualifications, how to apply, salary, deadline/closing date, job ID/reference number, contract type/level - Return ONLY the cleaned job text. No commentary, headers like "Here is the cleaned version", or markdown formatting. Just the clean job listing text. Wait, the actual prompt I need to respond to has two parts: - First part: "You are a job listing editor... Return ONLY the cleaned job text." - Second part: "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." with specific HTML rules. - Then it gives "Job description:" with the actual text to process. Let me re-read carefully. The user message starts with "You are a job listing editor..." and then later says "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." And then provides rules for HTML formatting, and then gives the job description text. Actually, looking at the structure, it seems like the user wants me to take the provided job description text, clean it according to the rules, and output clean semantic HTML. The first paragraph about "You are a job listing editor..." might be system context, but the actual task is the HTML formatting task described later. Let me read the very end: "Job description:" followed by the text, then the rules about

,

,
  • , no CSS classes, no inline styles, no
    , no
    , preserve ALL original content word-for-word, if no clear sections just wrap paragraphs in

    , return ONLY the HTML. No markdown fences, no explanation, no preamble. So I need to take the given job description text, parse it, and output clean semantic HTML using only

    ,

    ,
      ,
    • tags. I must preserve ALL original content word-for-word. I should not add, remove, summarise, or rephrase. Let me look at the job description text carefully. It's a mix of plain text and some HTML-like tags: `
      • Grade 12 (Matric).
      `, `

      Experience:

      `, etc. The text contains `` tags which I need to handle. The rules say: "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", "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". Key challenge: The text has `` tags with content inside. I need to preserve the content word-for-word. Should I strip the `` tags but keep the text inside? Or keep them as-is? The rules say "Preserve ALL original content word-for-word". The `` appears to be a marker from the scraping tool, not part of the original job content. But the instruction says preserve ALL original content word-for-word. However, the overall task description at the top says: "REMOVE all of the following: ... Stray numbers or formatting artifacts". The `` could be considered a formatting artifact from the scraping platform. Let me re-read the very first part: "You receive raw scraped text from a job website. Your job is to extract ONLY the actual job information and return it in a clean, readable format. REMOVE all of the following: - Social sharing text ... - Author bylines ... - "You may also like" / related posts sections - Navigation text ... - Comments sections - Advertisements or promotions - Cookie/subscription notices - Duplicate text ... - Category labels that aren't part of the job (e.g., "Internships" as a standalone line) - Stray numbers or formatting artifacts" Then: "KEEP and STRUCTURE: - Job title - Company/Organisation name - Location - Job description and responsibilities - Requirements/qualifications - How to apply / application instructions - Salary (if mentioned) - Deadline / closing date - Job ID / reference number - Contract type / level" "Return ONLY the cleaned job text. Do not add any commentary, headers like "Here is the cleaned version", or markdown formatting. Just the clean job listing text." Then the second part: "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." with rules about

        ,

        ,
        • , no CSS classes, no inline styles, no
          , no
          , preserve ALL original content word-for-word, if text has no clear sections, just wrap paragraphs in

          tags, return ONLY the HTML. No markdown fences, no explanation, no preamble. There's a conflict: The first part says "Return ONLY the cleaned job text" (plain text), the second part says "format it as clean semantic HTML" and gives HTML rules. The final job description text contains HTML tags like `

            `, `
          • `, ``, ``, ``, ``. I need to decide: The user prompt seems to combine both instructions, but the actual task to perform is likely the HTML formatting one, since it's the last part and provides specific tag rules. However, the "preserve ALL original content word-for-word" is tricky with the `` tags. Maybe I should strip the `data-teams="true"` part and keep just the text, or keep the spans as-is but without classes? The rules say "No CSS classes, no inline styles". `` could be seen as a class or attribute. I should probably remove the `data-teams="true"` attribute but keep the inner text, or just remove the span tags entirely and keep the text. But "preserve ALL original content word-for-word" might mean keep everything exactly as-is, including the span tags? That would conflict with "No CSS classes". Let me read carefully: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". This likely means the textual content must be preserved exactly, but the formatting tags from the scraped text might be considered non-content. The HTML rules say "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 I should transform the structure into the specified HTML tags, but keep the text content identical. How to handle ``? It's not one of the allowed tags (

              ,

              ,
                ,
              • ), and it has an attribute `data-teams="true"` which could be considered a CSS class or inline style artifact. I think the intent is to strip such scraping artifacts and keep only the text. But "preserve ALL original content word-for-word" might mean I should keep the span tags and their content as-is, maybe by just moving the text into the appropriate

                or

              • tags and removing the span wrapper. Or perhaps I should keep the span tags but strip the attribute? The rules say "No CSS classes, no inline styles". `data-teams="true"` is not a class, but it's an attribute. To be safe, I'll remove the `data-teams="true"` wrapper and just keep the text inside, as the span is clearly a scraping artifact. However, "preserve ALL original content word-for-word" is strict. Maybe I should keep the exact text including any markup that's part of the original job content? But `` is clearly a scraping platform tag, not job content. Let me look at the text structure. It's a job description for a Furniture Consultant. It has sections: Responsibilities? Actually the text starts with "The Furniture Consultant is responsible for providing expertise...". Then there's a list of requirements/experience, skills, behaviors, and then a "Preference will be given..." section, then another list of duties/responsibilities. I need to parse it and reorganize into

                sections and
                • lists, using

                  for intro text. The rules say: "Use

                  for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". So I should identify natural sections and label them with

                  . Let me outline the text content: - Intro: "The Furniture Consultant is responsible for providing expertise in furnishing, decor, and household appliances. They analyse customer profiles to provide personalized recommendations and actively engage with customers. Additionally, they perform sales transactions and stay updated with the latest trends and product releases." - Then: `
                  • Grade 12 (Matric).
                  ` -> This seems like a minimum requirement/education. Should be under Qualifications or Education. - `

                  Experience:

                  ` -> Header "Experience:" - Then list of experience requirements with `` items. - `

                  Skills:

                  ` -> Skills section - List of skills with `` - `

                  Behaviours:

                  ` -> Behaviors section - List of behaviors - `

                   

                  ` -> empty paragraph? Keep as-is maybe. - `

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

                  ` -> Note about EE Act - `
                  • Deliver an exceptional customer experience as a brand ambassador for @home Livingspace.
                  • ...` -> This is a list of duties/responsibilities, probably the "Key Duties" or "Responsibilities" section. The text has `` wrapping almost every line. I need to decide how to handle them. Since the rule says "No CSS classes, no inline styles", and `data-teams="true"` is an attribute, I should probably strip the span tags and keep the text. But "preserve ALL original content word-for-word" might mean I should keep the exact text including the span markup? That would be messy and violate the "No CSS classes" rule if I keep the attribute. I think the most reasonable interpretation is to extract the text content from the spans and place it in the appropriate HTML tags, removing the span wrappers since they are formatting artifacts from the scraping tool. The top-level instruction says "REMOVE all of the following: ... Stray numbers or formatting artifacts". The `` is a formatting artifact. However, the second part says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". This is tricky. Maybe it means preserve the text content word-for-word, not the markup. I'll assume I need to keep the exact text strings, but I can rewrap them into the new HTML structure. The words themselves must not be changed, but the tags around them can be restructured. Let me plan the HTML output structure: First, the job title: "The Furniture Consultant" - but where does it appear? The text starts with "The Furniture Consultant is responsible...". I might need to extract the title. The text doesn't have a separate title line, but the first phrase is the title/role. I'll use it as an

                    or

                    . The rules say use

                    for section headers. I could make "The Furniture Consultant" an

                    , but it's not exactly a section header. Maybe I'll put it as a

                    introductory line, or as an

                    "Job Title". But the rules say "Use

                    for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". So I should use those

                    tags for those sections. The job title itself might be wrapped in a

                    or I could just start with the description. Let me re-read the text carefully and map it to the required structure. Text breakdown (cleaning span tags, keeping text): 1. "The Furniture Consultant is responsible for providing expertise in furnishing, decor, and household appliances. They analyse customer profiles to provide personalized recommendations and actively engage with customers. Additionally, they perform sales transactions and stay updated with the latest trends and product releases." 2. "Grade 12 (Matric)." -> education requirement 3. "Experience:" then list items: - "Proven sales experience with a track record of achieving or exceeding targets." - "Experience working in a target-driven and/or commission-based sales environment." - "Experience selling premium, high-value, lifestyle, luxury, or aspirational products will be advantageous." - "Strong customer engagement and relationship-building experience." - "Experience converting customer interactions into sales outcomes." - "Furniture, homeware, décor, telecommunications, automotive, financial services, luxury retail, or similar sales experience will be advantageous but is not essential." 4. "Skills:" then list items: - "Communication skills" - "Interpersonal skills." - "Strong negotiation." - "Commercially aware." - "Ability to identify customer needs and provide tailored solutions." - "Strong relationship-building capability." - "Ability to thrive in a fast-paced retail environment." - "Organizational and administrative skills." - "Professionalism and accountability." - "Flexible and adaptable to meet business requirements, including weekends, public holidays, and evening shifts" 5. "Behaviours:" then list items: - "Adhering to Standards - Ensures quality and compliance in the delivery of their work" - "Continual Improvement - Actively seeks opportunities to continually improve processes" - "Decision Making - Analyses complex situations to ensure effective and timely choices" - "Driving & Persevering" - "Leading Others - Inspires and guides others to achieve collective goals" - "Meeting Customer Expectations - Consistently delivers exceptional customer service" - "Planning & Organizing - Uses a structured approach to effectively manage tasks" - "Relating & Networking" 6. Empty paragraph "

                     

                    " - maybe just keep as

                     

                    or ignore? The rules say preserve ALL original content word-for-word. So I should include it as

                     

                    or maybe just

                    ? The text has ` ` which is an HTML entity. I'll keep it as

                     

                    . 7. "

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

                    " -> This is a note. I'll keep as

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

                    after removing span. 8. "
                    • Deliver an exceptional customer experience as a brand ambassador for @home Livingspace.
                    • ..." -> This is a list of duties/responsibilities. There are 8 items. I'll put them under a section labeled with

                      , maybe "Key Duties" or "Responsibilities". The section header could be "Key Duties" or "About the Role". The rules list examples: "Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role". I'll use

                      Key Duties

                      or

                      Responsibilities

                      . Since the text starts with "The Furniture Consultant is responsible for...", maybe "Responsibilities" is appropriate. But there's also a separate list at the end. I'll use

                      Key Duties

                      for the final list, and perhaps the earlier experience/skills/behaviors are also duties but structured differently. Actually, looking at the structure, the text has: - Intro paragraph - Education requirement (Grade 12) - Experience section with bullet points - Skills section with bullet points - Behaviours section with bullet points - EE Act preference note - Another bullet list of duties (8 items) The rules say to use

                      for section headers. I'll create sections: maybe "Qualifications" for education, "Experience" for experience list, "Skills" for skills list, "Behaviours" for behaviors list, "Key Duties" for the final list. But the intro paragraph doesn't have a header; it's just general text, so it goes in

                      . Let me decide on the exact HTML output. I need to output ONLY the HTML, no markdown fences, no explanation, no preamble. I'll strip `` and ``, keep the text inside. I'll also keep ``, ``,

        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 📝

        Join Our Kenya Channels

        Get free job alerts on your phone

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?