RC

Maintenance Lead

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

Job Description

Here's a thinking process: 1. **Analyze User Input:** - **Role:** Job listing editor - **Task:** Extract ONLY actual job information from raw scraped text, return clean, readable format - **Specific Instructions for this prompt:** - Use `

` for introductory paragraphs and general text - Use `

` for section headers (list provided: 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. - **Input Text:** A plain-text job description from "RCL Foods" for a "Maintenance Lead" position. It contains company info, job type, location, job description, minimum requirements, duties & responsibilities. - **Key constraints:** - Must output HTML only - Must use specific tags: `

    `, `

    `, `
      `, `
    • ` - No other tags allowed - Must preserve all content word-for-word - Must structure according to sections if clear, otherwise `

      ` - The input text has clear sections: "Minimum Requirements", "Duties & Responsibilities", and within that, sub-sections like "Health & Safety", "Governance", "Production Plant Reliability", etc. But the user said: "Use

      for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". This implies I should map the existing section headers to these, or use them as `

      ` tags. But the instruction also says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". This is slightly contradictory if I'm supposed to re-map headers to specific `

      ` labels. Let re-read carefully: "Use

      for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)" This likely means: when there are sections, use `

      ` tags for the section headings, and the examples given are the typical ones. I should use the actual section headers from the text, but wrap them in `

      `. Or perhaps I should use exactly those labels if they match, but the text has "Minimum Requirements" and "Duties & Responsibilities". The examples list: "Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role". The text has "Minimum Requirements" and "Duties & Responsibilities". I think the intent is: use `

      ` for section headers, and the content under them should be `
      • ` lists where appropriate. But the instruction "Preserve ALL original content word-for-word" is strong. I need to decide how to handle this. Let's look at the text structure: - "Company: RCL Foods" etc. but those are labels, maybe I should extract the actual job info. - The text has: "Functions: Engineering", "Job Type Classification: Permanent", "Location - Town / City: Boksburg", "Job Description:", then paragraphs, then "Minimum Requirements:", then "Duties & Responsibilities:" with many sub-headings like "Health & Safety", "Governance", etc. The rule: "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)". I need to output HTML. I should probably: - Start with `

          ` for any introductory text before sections. - Use `

          ` for each major section header. The examples given are generic; I'll use the actual headers from the text, but wrap them in `

          `. However, the instruction says "e.g." so maybe I should map the text's headers to those categories. But "Preserve ALL original content word-for-word" means I shouldn't change the header text. I'll use the actual headers as `

          ` content. Let's parse the text carefully and structure it. Text breakdown: - "Company: RCL Foods" -> maybe not part of the job listing core? The user said "extract ONLY the actual job information". But also "Preserve ALL original content word-for-word". I think I should include all text that's part of the job description, but maybe strip labels like "Company:", "Functions:", "Job Type Classification:", "Location - Town / City:"? The prompt says: "REMOVE all of the following:" in the first part, but this second prompt says "Your ONLY job is to format it as clean semantic HTML." and gives rules about tags, preserving content word-for-word. It doesn't explicitly say to remove those labels, but the first prompt's rules might be superseded by the second's specific instructions. Let's read the second prompt carefully: "Rules: - 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." It doesn't say to remove the labels like "Company:", "Functions:", etc. But the first prompt said "REMOVE all of the following: - Social sharing text - Author bylines - "You may also like" - Navigation text - Comments sections - Advertisements or promotions - Cookie/subscription notices - Duplicate text - Category labels that aren't part of the job - Stray numbers or formatting artifacts". The second prompt is a new instruction set, but it might be an override or continuation. The user says "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." Then lists rules. I should follow the second prompt's rules strictly. It says "Preserve ALL original content word-for-word". That means I should keep everything, including "Company:", "Functions:", etc., unless they are considered "not part of the job". But the instruction says preserve all original content. I'll include everything as-is, but format with the specified tags. However, the text has things like "Company: RCL Foods" on one line, "Functions: Engineering" on another, "Job Type Classification: Permanent", "Location - Town / City: Boksburg". These are not sentences but key-value pairs. How to handle with `

            ` and `

            `? The rule says "Use

            for introductory paragraphs and general text" and "Use

            for section headers (e.g. ...)". I could treat the top part as introductory paragraphs, each on its own line, wrapped in `

            `. Or I could omit them if they're not "actual job information", but the preserve rule says keep all. I'll include them in `

            ` tags, as they are general text. Let's look at the section "Minimum Requirements:" and "Duties & Responsibilities:". The "Duties & Responsibilities:" has sub-headings like "Health & Safety", "Governance", "Production Plant Reliability", etc. The rule says "Use

            • for list items (duties, requirements, qualifications, skills)". So the sub-items under each sub-heading might be list items. But the text under each sub-heading is prose, not bullet points. For example: "Health & Safety Responsible for health and safety with regards to all equipment to ensure a safe environment to operate and work on for all staff. Ensure the engineering team adheres to the Siqalo safety policies and procedures. ..." This is a paragraph that starts with the category name. The rule says "Use
              • for list items (duties, requirements, qualifications, skills)". I need to decide if I should convert the prose into lists, or keep as `

                `. The instruction says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". If I convert to `

                • `, I'm restructuring, which might violate "do not rephrase" but the content words are preserved, just tagged differently. However, the rule also says "Use
                  • for list items (duties, requirements, qualifications, skills)". This implies that where there are lists of duties/requirements, use lists. But the text is written in paragraph form, not as a list. I could keep them as `

                    `, but the rule says use `

                    • ` for list items. Maybe I should identify actual list items and wrap those in `
                    • `, and keep the rest as `

                      `. But it's ambiguous. Let's re-read: "Use

                      • for list items (duties, requirements, qualifications, skills)". This could mean: if the original text has list items (like bullet points), keep them as `
                        • `. If it's prose, use `

                          `. The given text doesn't have explicit bullet points; it's continuous text with section headings. I think the safest is to wrap each paragraph or continuous text in `

                          `, and use `

                          ` for the main section headers ("Minimum Requirements", "Duties & Responsibilities", and maybe the sub-headings like "Health & Safety", etc.). But the rule lists specific header examples: "Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role". The text has "Minimum Requirements" and "Duties & Responsibilities". I'll map "Minimum Requirements" to `

                          ` perhaps as "Requirements" or keep as "Minimum Requirements" inside `

                          `. The rule says "Use

                          for section headers (e.g. ...)". The "e.g." means examples, not exhaustive. I'll use `

                          ` for the section headers that exist in the text. I need to output HTML only. Let's plan the structure: The text starts with: Company: RCL Foods Functions: Engineering Job Type Classification: Permanent Location - Town / City: Boksburg Job Description: [paragraphs] Minimum Requirements: [text] Duties & Responsibilities: [sub-sections with prose] I'll wrap each line of labels and values in `

                          `, but that might not be ideal. Actually, the instruction "Use

                          for introductory paragraphs and general text" suggests that any text that isn't a section header or list item should be in `

                          `. The labels like "Company:" could be part of `

                          `. But to keep it clean, maybe I should just treat the whole thing as sections and paragraphs. Let's think differently: The user wants clean semantic HTML. I'll produce HTML where: - The job title, company, location etc. are in `

                          ` or as part of the structure. - Section headers use `

                          `. - List items use `
                          • ` where appropriate, but since the text is prose, I'll use `

                            ` for prose sections, unless I can identify actual bullet-worthy items. The instruction "Use

                            • for list items (duties, requirements, qualifications, skills)" might mean I should extract duties/requirements into lists. But it also says "Preserve ALL original content word-for-word". If I put prose into `
                            • `, the content is preserved but the formatting changes. I think the intent is: if the source has list items (like "- duty 1"), use `
                            • `. If it's continuous text, use `

                              `. I'll assume the latter. Let's look at the sub-headings under "Duties & Responsibilities": "Health & Safety", "Governance", "Production Plant Reliability", "Engineering Team Leadership", "Budgets and Administration", "Planned Maintenance", "Repairs / Overhauls", "Stock Control", "Governance" (duplicate), "Information and Data Management", "Ad hoc/Other". Each has a paragraph of text. I could wrap each paragraph in `

                              `, and the sub-heading could be an `

                              ` or part of the `

                              `. The rule says "Use

                              for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". It doesn't explicitly say to use `

                              ` for every sub-heading, but I could. However, "Preserve ALL original content word-for-word" means I shouldn't change "Health & Safety" to something else. I'll use `

                              ` for the main sections "Minimum Requirements" and "Duties & Responsibilities", and for sub-headings, I'll probably just keep them as part of `

                              ` or use `

                              ` as well. To be safe, I'll use `

                              ` for any clear section header I encounter, wrapping the header text. Let's re-read the rule: "Use

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

                              ` for sections that match these or are clearly section dividers. The text has "Minimum Requirements:" and "Duties & Responsibilities:". I'll use `

                              Minimum Requirements

                              ` and `

                              Duties & Responsibilities

                              `. For the sub-headings under "Duties & Responsibilities", I'll probably just wrap the text in `

                              `, since they are not top-level section headers but categories within a section. But the rule says "Use

                              for section headers (e.g. ...)" - it might imply all section headers should be `

                              `. I'll use `

                              ` for each sub-heading as well, to be consistent with "semantic HTML" and the rule. However, that might create many `

                              ` tags, and the content under them is prose. I'll do: `

                              Health & Safety

                              ` followed by `

                              ...

                              `. But the rule says "Use
                              • for list items (duties, requirements, qualifications, skills)". If I use `

                                ` then `

                                `, that's fine. If I use `

                                ` then `
                                • `, I'd have to break the prose into items, which might change the structure but preserve content. Given the strict "preserve all original content word-for-word", I think keeping prose as `

                                  ` is safer, and using `

                                  ` only for main section headers. But the rule says "Use
                                  • for list items (duties, requirements, qualifications, skills)". Maybe I should identify if there are actual list items. Looking at the text, there are no bullet points; it's all paragraph text. So I'll use `

                                    ` for those. Let's decide on a concrete output structure: ```

                                    Company: RCL Foods

                                    Functions: Engineering

                                    Job Type Classification: Permanent

                                    Location - Town / City: Boksburg

                                    Job Description

                                    ...job description text...

                                    Minimum Requirements

                                    ...minimum requirements text...

                                    Duties & Responsibilities

                                    Health & Safety
                                    ? But rule only mentions

                                    , no

                                    allowed. So maybe I just use `

                                    ` for the sub-content, or `

                                    ` for each sub-heading. The rule says "Use

                                    for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". It doesn't forbid using `

                                    ` for other headers, but it gives examples. I'll use `

                                    ` for the main sections, and for sub-headings, I'll incorporate them into `

                                    ` or use `

                                    ` as well. To strictly follow "Use

                                    for section headers", I'll treat each sub-heading as a section header and use `

                                    `. But then I need to decide what follows. I'll do `

                                    Health & Safety

                                    ...text...

                                    `. That seems reasonable. However, the prompt says "If text has no clear sections, just wrap paragraphs in

                                    tags". This text has clear sections. Let's parse the exact text and map it. I'll write the HTML step by step, ensuring every word from the input is preserved exactly, including colons, capitalization, etc. Input text verbatim (I'll copy parts): "Company: RCL Foods Functions: Engineering Job Type Classification: Permanent Location - Town / City: Boksburg Job Description: RCL Foods is currently looking for a Maintenance Lead to join our Groceries & Spreads Business Unit . The role is based in Boksburg and will report to the Engineering Manager . Purpose of the role: This position will provide hand on expertise and leadership of the engineering staff, operators and artisans and assistants ensuring the proactive maintenance, repair, and service of equipment within the production plant. Problem Solving Where problems have

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?