RC

Semi-skilled Artisan

Full-time Gauteng, South Africa, ZA
Posted 1 hour, 10 minutes ago 40 views 0 applications

Job Description

Here's a thinking process: 1. **Analyze User Input:** - User is acting as a job listing editor/scraper formatter - I need to take the provided raw job description text - I need to output clean semantic HTML following specific rules - Rules: use

for paragraphs,

for section headers,
  • for lists, no classes/styles/divs/br, preserve ALL original content word-for-word, no rephrasing, if no clear sections just wrap in

    , output ONLY HTML, no markdown fences/explanation/preamble 2. **Examine the Job Description Text:** Let me copy the exact text provided: ``` Company: RCL Foods Functions: Engineering Job Type Classification: Permanent Location - Town / City: Pretoria West Job Description: RCL FOODS is a deeply rooted South African food manufacturer that produces some of the country’s most-loved brands, including Yum Yum peanut butter, Nola mayonnaise, Ouma rusks, and Selati sugar, just to name a few. At the heart of our culture and strategy is our Purpose – WE GROW WHAT MATTERS – which reflects our belief in collectively doing that little more to create a positive impact that truly matters. Visit our website: www.rclfoods.com RCL FOODS is seeking a motivated and enthusiastic Semi-skilled Artisans to join our Milling Division to assist artisans with daily maintenance and constructive work. Minimum Requirements: N4 mechanical/ electrical (minimum) N5 and above would be an advantage. Trade tested Electrician OR Trade tested Millwright OR Trade tested Fitter OR Trade tested fitter and turner OR Trade tested boiler maker (Advantageous) Matric passed (Grade 12) or equivalent. Knowledge of hand tools and basic hand skills. Must be physically strong and healthy. Flour Milling/ Milling work experience of 5 years and above will be an advantage. Ability to read, write and communicate in English, compulsory. Computer Literacy. Must be willing to learn and grow professionally. Duties & Responsibilities: Perform preventative and corrective maintenance tasks. Perform standby duties, work shifts, attend to breakdowns, do fault finding and carry out emergency repairs. Complete job cards and update vehicle records. Order spare parts (consumables), interpret spares and workshop manuals. Housekeeping, Participate in Total Productive Maintenance, as well as Health and Safety responsibilities. Ensure your workplace is clean, neat always. Conduct adhoc operationally relevant duties ``` 3. **Identify the Structure & Sections:** - Company: RCL Foods - Functions: Engineering - Job Type Classification: Permanent - Location - Town / City: Pretoria West - Job Description: (paragraph text) - Minimum Requirements: (list/paragraph text) - Duties & Responsibilities: (list/paragraph text) The user rules say: - Use

    for introductory 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
      s, no
      tags - Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase - If text has no clear sections, just wrap paragraphs in

      tags - Return ONLY the HTML. No markdown fences, no explanation, no preamble. Important: "Preserve ALL original content word-for-word". This means I must keep every word, punctuation, etc. exactly as is. But I need to structure it with HTML tags. Let's look at the sections: - "Company:" followed by "RCL Foods" - this is a line. How to handle? The rules say use

      for section headers like Responsibilities, Qualifications, etc. "Company" isn't in the listed header examples, but it is a section. I should probably treat it as a header or paragraph. The rule says "Use

      for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". It says "e.g.", so it's not exhaustive. But "Company" might be better as a

      or a header. I need to be careful. Actually, looking at the raw text, it has labels like "Company:", "Functions:", "Job Type Classification:", "Location - Town / City:", "Job Description:", "Minimum Requirements:", "Duties & Responsibilities:". These are part of the scraped text. The user says "REMOVE all of the following: ..." in the first part, but then says "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." and gives rules. The first part about removing social sharing etc. seems like context from the system prompt, but the actual task is: take the job description text and format as HTML. I need to decide how to handle the labels. The rule says "Preserve ALL original content word-for-word". So I should keep "Company:", "RCL Foods", etc. But how to markup? I could treat "Company:" as a header and "RCL Foods" as the content, or wrap them in paragraphs. The rule says use

      for section headers (e.g. Responsibilities, Qualifications, ...). It doesn't explicitly say to strip the labels, but the "REMOVE" list earlier included "Category labels that aren't part of the job (e.g., "Internships" as a standalone line)". However, that was part of the first prompt's "REMOVE" list, but the actual task rules are the ones under "Rules:". I need to follow the Rules. Let's re-read the Rules carefully: - Use

      for introductory 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
        s, no
        tags - Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase - If text has no clear sections, just wrap paragraphs in

        tags - Return ONLY the HTML. No markdown fences, no explanation, no preamble. The key is "Preserve ALL original content word-for-word". So I must include every token from the input text. The input text has labels and values. I need to decide how to mark them up while preserving everything. Possible approach: Treat each line or group as a paragraph or list item, but keep the exact text. For example: - `

        Company

        ` but that changes "Company:" to "Company". I must preserve word-for-word, so I should keep "Company:" as text. Maybe `

        Company: RCL Foods

        ` or `

        Company:

        ` but then "RCL Foods" needs to be included. Wait, the input text is: ``` Company: RCL Foods Functions: Engineering Job Type Classification: Permanent Location - Town / City: Pretoria West Job Description: RCL FOODS is a deeply rooted... ... Minimum Requirements: N4 mechanical/ electrical... ... Duties & Responsibilities: Perform preventative... ... ``` I need to output HTML that contains all these words exactly. I can wrap groups in

        or

        or
        • . The rule says "Use

          for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". The listed headers are specific. "Company", "Functions", "Job Type Classification", "Location - Town / City", "Job Description", "Minimum Requirements", "Duties & Responsibilities" are not in that exact list, but they are section headers. The rule says "e.g.", so it's not exclusive. However, to be safe, I could treat the main content sections (Minimum Requirements, Duties & Responsibilities) as using

          and
          • , and the other labels as

            or just part of the flow. But "Preserve ALL original content word-for-word" is the strongest constraint. I cannot omit colons or change text. I need to include every character exactly as is. Let me think about how to structure this. I'll go line by line or group by group, using appropriate tags, but ensuring the text content is unchanged. Structure ideas: - The very first part: "Company:\nRCL Foods" could be `

            Company:\nRCL Foods

            ` or `

            Company:

            RCL Foods

            `. But "word-for-word" might mean I shouldn't break it arbitrarily. Maybe better to wrap the whole thing in

            tags if it's introductory. But there are clear sections. Actually, re-reading: "If text has no clear sections, just wrap paragraphs in

            tags". This text has clear sections: Job Description, Minimum Requirements, Duties & Responsibilities. The others are metadata. I need to output HTML. Let's plan: - I'll treat "Company:" and "RCL Foods" as a paragraph: `

            Company:\nRCL Foods

            ` but the newline might be tricky. I can keep the newline as a space or keep it as \n inside HTML? HTML whitespace collapses, but I need to preserve content word-for-word. The rule says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". It doesn't say I must preserve whitespace/layout exactly, but I must not remove or change words. I think it's safer to keep the exact text strings, and use tags around them, possibly with spaces instead of newlines, but I need to be careful. Maybe I should treat each line as a separate

            or

            element, with the text content exactly as given. For example: `

            Company:

            RCL Foods

            ` but that splits the text, which might be considered changing it. The original has "Company:\nRCL Foods" on separate lines. If I put them in separate paragraphs, I'm altering the structure but not the words. The rule says "do not add, remove, summarise, or rephrase". Adding tags is allowed per the task, but I must not change the text content. Let's look at how to handle "Minimum Requirements:" followed by text. The rule says "Use
            • for list items (duties, requirements, qualifications, skills)". The "Minimum Requirements" section has text that is not clearly a list; it's prose with some "OR" options. But the rule says use
              • for list items. However, it also says "Preserve ALL original content word-for-word". If I convert the requirements text into a list, I might need to break it into items, which could change the text. The text is: "N4 mechanical/ electrical (minimum) N5 and above would be an advantage. Trade tested Electrician OR Trade tested Millwright OR Trade tested Fitter OR Trade tested fitter and turner OR Trade tested boiler maker (Advantageous) Matric passed (Grade 12) or equivalent. Knowledge of hand tools and basic hand skills. Must be physically strong and healthy. Flour Milling/ Milling work experience of 5 years and above will be an advantage. Ability to read, write and communicate in English, compulsory. Computer Literacy. Must be willing to learn and grow professionally." This is paragraph text. The rule says "Use
                • for list items (duties, requirements, qualifications, skills)". It doesn't say I MUST use lists for everything called "Requirements". It says use them for list items. If the text isn't naturally a list, I should just wrap in

                  . The rule also says: "If text has no clear sections, just wrap paragraphs in

                  tags". This text has sections. I think the safest approach is: - For section headers that are in the suggested list (Responsibilities, Qualifications, etc.), use

                  . - For other headers, use

                  or just include them as text. - For paragraph text, use

                  . - For list items, use

                  • , but only if the text is clearly separated items. The "Minimum Requirements" and "Duties & Responsibilities" might be better as paragraphs since they are continuous text. But the rule says "Use
                    • for list items (duties, requirements, qualifications, skills)". It might expect me to parse the duties and requirements into lists. However, "Preserve ALL original content word-for-word" conflicts with breaking prose into list items, because I'd have to split sentences or phrases, which changes the text structure. The rule says "do not add, remove, summarise, or rephrase". If I put each sentence in an
                    • , I'm not removing or rephrasing, just tagging. But the order and grouping might change. Let's re-read carefully: "Use
                      • for list items (duties, requirements, qualifications, skills)". This is a guideline for when there are list items. It doesn't force me to convert everything into lists. The next rule: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". This is paramount. I think I should output the text with appropriate HTML tags wrapping paragraphs and headers, but keeping the exact text. I'll use

                        for section headers that clearly are sections, and

                        for body text. For the "Minimum Requirements" and "Duties & Responsibilities", I'll treat them as paragraphs since they are prose, unless I can naturally split them into list items without altering words. But splitting might be risky. Let's examine the "Duties & Responsibilities:" text: "Perform preventative and corrective maintenance tasks. Perform standby duties, work shifts, attend to breakdowns, do fault finding and carry out emergency repairs. Complete job cards and update vehicle records. Order spare parts (consumables), interpret spares and workshop manuals. Housekeeping, Participate in Total Productive Maintenance, as well as Health and Safety responsibilities. Ensure your workplace is clean, neat always. Conduct adhoc operationally relevant duties" This could be a list of duties, but it's written as sentences. I could make each sentence an

                      • , but that would split the text. The rule says "Preserve ALL original content word-for-word". If I put them in
                      • , the words are preserved, but the formatting changes. Is that allowed? The task is to "format it as clean semantic HTML". Changing from prose to a list is formatting, but the content words must remain exactly. I think it's safer to keep them as

                        paragraphs, because the rule "If text has no clear sections, just wrap paragraphs in

                        tags" suggests that when there are sections, we use appropriate tags, but the primary goal is preserving content. Actually, the rule says: "Use

                        • for list items (duties, requirements, qualifications, skills)". It might be that the expected output for a job listing is to have duties and requirements as lists. But the "preserve word-for-word" is a strong constraint. I need to balance. Let's see the exact input again. The "Minimum Requirements:" section has text that includes "OR" options, which are naturally list-like. "Trade tested Electrician OR Trade tested Millwright OR ...". I could mark those as list items, but then I'd have to handle the "OR" branching, which might be complex. Maybe the best approach is to output the whole thing as a series of

                          tags, with

                          for the main section headers that are in the list, and

                          for others. But I must include all text. Let's try to structure it logically while preserving text: I'll output:

                          Company: RCL Foods

                          Functions: Engineering

                          Job Type Classification: Permanent

                          Location - Town / City: Pretoria West

                          Job Description

                          RCL FOODS is a deeply rooted South African food manufacturer that produces some of the country’s most-loved brands, including Yum Yum peanut butter, Nola mayonnaise, Ouma rusks, and Selati sugar, just to name a few. At the heart of our culture and strategy is our Purpose – WE GROW WHAT MATTERS – which reflects our belief in collectively doing that little more to create a positive impact that truly matters. Visit our website: www.rclfoods.com RCL FOODS is seeking a motivated and enthusiastic Semi-skilled Artisans to join our Milling Division to assist artisans with daily maintenance and constructive work.

                          Minimum Requirements

                          N4 mechanical/ electrical (minimum) N5 and above would be an advantage. Trade tested Electrician OR Trade tested Millwright OR Trade tested Fitter OR Trade tested fitter and turner OR Trade tested boiler maker (Advantageous) Matric passed (Grade 12) or equivalent. Knowledge of hand tools and basic hand skills. Must be physically strong and healthy. Flour Milling/ Milling work experience of 5 years and above will be an advantage. Ability to read, write and communicate in English, compulsory. Computer Literacy. Must be willing to learn and grow professionally.

                          Duties & Responsibilities

                          Perform preventative and corrective maintenance tasks. Perform standby duties, work shifts, attend to breakdowns, do fault finding and carry out emergency repairs. Complete job cards and update

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 South Africa 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?