TS

Catering Manager - Pretoria

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

Job Description

Here's a thinking process: 1. **Analyze User Input:** - **Role:** Job listing editor - **Task:** Extract ONLY actual job information, return clean, readable format - **Constraints:** Remove specific items (social sharing, bylines, related posts, navigation, comments, ads, cookie notices, duplicate text, stray category labels, numbers/formatting artifacts) - **Keep/Structure:** Job title, company, location, description, requirements, how to apply, salary, deadline, job ID, contract type - **Output:** ONLY cleaned job text, no commentary, no markdown, no headers like "Here is the cleaned version" Wait, the user actually gave me a specific format change request in the second part: - "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." - Rules: Use

for paragraphs,

for section headers,
  • for lists, no CSS/inline styles/
    /
    , preserve ALL original content word-for-word, no summarizing, if no clear sections just wrap in

    , return ONLY HTML, no markdown fences, no explanation, no preamble. Then they provide the job description text. I need to output clean semantic HTML based on the rules. The previous "job listing editor" framing with removal rules seems to be a system prompt or context, but the actual task given is: "format it as clean semantic HTML" with specific tags and rules. The user says: "Rules: ... Preserve ALL original content word-for-word ... Return ONLY the HTML. No markdown fences, no explanation, no preamble." Let me re-read carefully. The user message starts with "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." Then lists rules. Then says "Job description:" and pastes the text. Then says "Return ONLY the HTML. No markdown fences, no explanation, no preamble." So I need to take the provided job description text, and convert it to clean semantic HTML using

    ,

    ,
      ,
    • tags, preserving all content word-for-word, no additions, no removals, no summarizing. Let me parse the job description text and structure it. Text: Business Unit / Division: TsAfrika Catering Solutions Job Type Classification: Full Time Location - Town / City: Pretoria About Us: TsAfrika Catering Solutions is looking to appoint a Catering Manager to oversee catering operations, ensure excellent food quality, and maintain strong client relationships. The successful candidate will manage the catering team and drive operational excellence across the site. As a leading African Integrated Workplace Management Solutions Provider, Tsebo Solutions Group offers clients reduced costs, risk and complexities together with increased quality, efficiency and productivity . We specialise in Catering , Facilities Management , Cleaning and Hygiene , Pest Control , Protection , Energy , Procurement , Workspace Design , Engineering, Remote Camps , and more. Developing our people – the heart of Tsebo – is the foundation of our purpose. The result is a knowledgeable workforce that is in touch with every nuance of our clients’ needs. DOWNLOAD OUR ONE-PAGER to find out more about who we are in a nutshell. Duties & Responsibilities: Take full responsibility and management of the unit Need to be able to work in a demanding environment. Setting and management of service delivery standards Lead, motivate, train and develop a team of staff Implement and maintain operational controls in line within budgetary requirements Ensure quality of food preparation, presentation and service is up to standard by meeting all quality star grading standards in all areas of responsibility as per grading checklist Ensure all policies and procedures are complied with Daily HR and IR issues (including training, development & performance management) Analyse and pre-empt client needs and possible complaints Take responsibility for all functions by organising, preparing & co-ordinating. Management of all administration, finances, debtors, budgets, etc. Process paperwork and compile & understand weekly & monthly P & L Relationship building with the client and customers on a daily basis (essential) Must be able to work long hours and over weekends should there be a need Stay abreast of latest food trends and best practices Skills and Competencies: Strong judgement and problem solving skills Excellent people skills Strong interpersonal and communicative skills (verbal and written) Flexibility with regards to working hours Attention to detail Client service orientated Business management principles Fully computer literate Excellent food skills Qualifications: Matric and tertiary qualifications Preferably own vehicle would be an added advantage 5 - 8 years working experience as a Catering Manager or similar role Strong operational and people -management skills Knowledge of food safety, hygiene standards and HACCP Experience in stock control, budgeting and cost management Excellent communication and customer service skills Ability to manage a high paced catering environment Now, I need to format this as clean semantic HTML using: -

      for introductory paragraphs and general text -

      for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role) -
      • 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. Key consideration: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". This is tricky with HTML formatting because I need to keep all the exact text, but I need to wrap things in appropriate tags. The text has sections like "About Us", "Duties & Responsibilities", "Skills and Competencies", "Qualifications". These seem like natural sections to use

        for. But the instruction says "Use

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

        for those section headers. However, "Preserve ALL original content word-for-word" means I shouldn't rephrase or change the text. But I can add tags around it. The tags themselves aren't part of the "content" in terms of meaning, but I need to be careful not to alter the text. I'll just wrap section headers in

        and the following text in

        or

        • as appropriate. Let's look at the structure: - "Business Unit / Division:" then "TsAfrika Catering Solutions" - this is probably a paragraph or line. - "Job Type Classification:" then "Full Time" - "Location - Town / City:" then "Pretoria" - "About Us:" then a paragraph of text. - "Duties & Responsibilities:" then a block of text that looks like sentences separated by periods, but it's actually a list of duties in prose form. The instruction says "
          • for list items (duties, requirements, qualifications, skills)". But the text isn't clearly separated into bullet points; it's a continuous paragraph. However, I can interpret each sentence or meaningful chunk as an
          • if it makes sense, but the rule says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". If I split it into
          • items, I'm not removing or summarizing, just restructuring into list tags. But the rule also says "If text has no clear sections, just wrap paragraphs in

            tags". The "Duties & Responsibilities:" section has clear text but not clearly separated list items. I need to decide: should I treat it as paragraphs

            , or as

            • ? The instruction says "Use
              • for list items (duties, requirements, qualifications, skills)". It doesn't say I must convert everything to lists; it says use them for list items. If the text isn't naturally in list items, I might just use

                . But the text under "Duties & Responsibilities:" looks like it could be bullet points if I split on certain delimiters, but it's not consistently formatted. Let me read it again: "Take full responsibility and management of the unit Need to be able to work in a demanding environment. Setting and management of service delivery standards Lead, motivate, train and develop a team of staff Implement and maintain operational controls in line within budgetary requirements Ensure quality of food preparation, presentation and service is up to standard by meeting all quality star grading standards in all areas of responsibility as per grading checklist Ensure all policies and procedures are complied with Daily HR and IR issues (including training, development & performance management) Analyse and pre-empt client needs and possible complaints Take responsibility for all functions by organising, preparing & co-ordinating. Management of all administration, finances, debtors, budgets, etc. Process paperwork and compile & understand weekly & monthly P & L Relationship building with the client and customers on a daily basis (essential) Must be able to work long hours and over weekends should there be a need Stay abreast of latest food trends and best practices" This is actually a continuous paragraph with line breaks maybe from the source, but it's all one block. I think the safest approach per rules is: since it's not clearly separated into discrete list items, I'll wrap it in

                tags. But the rule says "Use

                • for list items (duties, requirements, qualifications, skills)". It doesn't forbid using

                  for non-list text. I'll use

                  for section headers, and then

                  for the text under each section, except maybe for "Qualifications:" which has some list-like items but still prose. Let's see "Qualifications:" text: "Matric and tertiary qualifications Preferably own vehicle would be an added advantage 5 - 8 years working experience as a Catering Manager or similar role Strong operational and people -management skills Knowledge of food safety, hygiene standards and HACCP Experience in stock control, budgeting and cost management Excellent communication and customer service skills Ability to manage a high paced catering environment" - this is also prose, not bullet-separated. However, the instruction says "Use

                  • for list items (duties, requirements, qualifications, skills)". It might expect me to parse each bullet or each duty into
                  • . But "Preserve ALL original content word-for-word" conflicts if I'm splitting sentences that might run together. I need to interpret carefully. Perhaps the intent is that if the original text has list items (like each duty on a new line or bullet), I should use
                    • . If it's just prose, use

                      . The given text seems to be from a job posting where duties are listed in a paragraph form. I'll treat each section's main body as

                      , except maybe I can split on clear separators like "and" or periods, but that would be summarizing/rephrasing? Actually, splitting on periods into

                    • would change the structure but not the content word-for-word if I keep the exact sentences. But the text has no consistent bullet markers. I think best is to wrap each section's content in

                      , and use

                      for headers. But the rule explicitly says "Use
                      • for list items (duties, requirements, qualifications, skills)". This suggests I should convert the duties/requirements/skills into lists. Let me re-read: "Use
                        • for list items (duties, requirements, qualifications, skills)". It doesn't say "only if they are already lists", it says use them for list items. I think I need to parse the text into list items. How to split? The duties text has sentences separated by periods. I could treat each sentence as an
                        • . But some sentences are run-on or connected. Let's look at the original formatting from the user prompt: it's presented as a continuous block under each heading. In the raw text, there are line breaks maybe, but in the prompt it's shown as continuous. I need to make a decision. Given the strict "preserve ALL original content word-for-word", I should not split sentences in a way that changes meaning or adds/removes words. But wrapping in
                        • tags doesn't change the words, it just tags them. I could split on periods and put each sentence in an
                        • , but I need to keep the period punctuation. However, the last sentence might not have a period, etc. This could be error-prone. Alternative: Use

                          for all prose sections, and only use

                          • if there are clear list items. The rule says "If text has no clear sections, just wrap paragraphs in

                            tags". The text does have clear sections (About Us, Duties & Responsibilities, etc.), but the content within each section may or may not be list items. I think the safest interpretation is: use

                            for the section headers (the headings like "Duties & Responsibilities:", "Skills and Competencies:", "Qualifications:"). Then, for the text under each, since it's not clearly separated into individual list items (no bullets, just prose), I'll wrap them in

                            . But the rule says "Use

                            • for list items (duties, requirements, qualifications, skills)". This might mean I should use them for those categories, implying I should convert them to lists. Let me see the exact wording: "Use
                              • for list items (duties, requirements, qualifications, skills)". It's a rule about which tag to use for which content. It doesn't say "always use
                                • for these sections". It says use them for list items. If the content is not in list item format, perhaps I should just use

                                  . I'll check typical job scraping tasks: often, duties and requirements are given as bullet points in the original HTML, but when scraped as plain text, they might lose bullets. The instruction says "Preserve ALL original content word-for-word". If I convert to

                                  • , I'm preserving content but restructuring. I think it's acceptable as long as I don't omit or change words. I'll try to split the text into reasonable list items. But how to split reliably? The duties text: I could split on periods followed by spaces, but need to be careful with abbreviations like "P & L" which has an ampersand and space. "weekly & monthly P & L" - the "&" might cause splitting issues. Maybe I should just use

                                    for all content sections, and use

                                    for headers. The rule "Use
                                    • for list items (duties, requirements, qualifications, skills)" might be a guideline for when the content is actually list items. Since the provided text doesn't have clear list delimiters, I'll use

                                      . But I risk violating the rule if the expectation is to use

                                      • . Let me re-read the user's message carefully. User: "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." The third rule says "Use

                                          • for list items (duties, requirements, qualifications, skills)". This seems to indicate that for the content relating to duties, requirements, qualifications, skills, I should use
                                            • . The parenthetical "(duties, requirements, qualifications, skills)" likely means those are the types of list items to use
                                              • for. So I should convert the duties section into
                                                • items, the qualifications into
                                                  • items, and the skills into
                                                    • items. How to split? I need to parse the prose into individual items. Let me attempt to split the duties text into separate duties. Looking at the text: "Take full responsibility and management of the unit Need to be able to work in a demanding environment. Setting and management of service delivery standards Lead, motivate, train and develop a team of staff Implement and maintain operational controls in line within budgetary requirements Ensure quality of food preparation, presentation and service is up to standard by meeting all quality star grading standards in all areas of responsibility as per grading checklist Ensure all policies and procedures are complied with Daily HR and IR issues (including training, development & performance management) Analyse and pre-empt client needs and possible complaints Take responsibility for all functions by organising, preparing & co-ordinating. Management of all administration, finances, debtors, budgets, etc. Process paperwork and compile & understand weekly & monthly P & L Relationship building with the client and customers on a daily basis (essential) Must be able to work long hours and over weekends should there be a need Stay abreast of latest food trends and best practices" This is actually one long paragraph from the job posting, but it's meant to be duties. In many job postings, this kind of text is continuous. If I must use
                                                      • , I have to decide on splitting. Perhaps I can split on the sentences that start with capital letters or are separated by periods. Let's identify sentences: 1. "Take full responsibility and management of the unit" 2. "Need to be able to work in a demanding environment." 3. "Setting and management of service delivery standards" 4. "Lead, motivate, train and develop a team of staff" 5. "Implement and maintain operational controls in line within budgetary requirements" 6. "Ensure quality of food preparation, presentation and service is up to standard by meeting all quality star grading standards in all areas of responsibility as per grading checklist" 7. "Ensure all policies

    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 Tanzania 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?