Catering Manager - Pretoria

,

,

• ), no CSS/classes/inline styles/
  /
  , preserve ALL original content word-for-word, no summarizing, return ONLY the HTML. No markdown fences, no explanation, no preamble. Then there's "Job description:" followed by the actual text. I need to figure out which set of rules applies. The user message starts with "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." Then gives rules for HTML formatting. Then says "Job description:" and pastes the text. The first part about removing/keeping seems like a system prompt or context, but the actual task is the HTML formatting one. However, both sets of rules are present. Let me read carefully. The very first block: "You are a job listing editor. You receive raw scraped text from a job website... 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." This seems like a system instruction. Then: "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." with HTML tag rules. Then "Job description:" with the text. It's possible the user wants me to apply the HTML formatting rules to the job description text. The first part might be general context, but the specific task is the HTML formatting. I should combine both: clean the text (remove unwanted stuff) and then format it as clean semantic HTML per the rules. Let me examine the job description text provided: ``` 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, what needs to be removed per the first set of rules? - Social sharing text: none present - Author bylines: none - "You may also like": none - Navigation: none - Comments: none - Ads/promotions: none - Cookie/subscription notices: none - Duplicate text: maybe "TsAfrika Catering Solutions" appears twice (About Us and Qualifications context, but not exact duplicate) - Category labels that aren't part of the job: "Business Unit / Division:", "Job Type Classification:", "Location - Town / City:" - these might be considered category labels, but they contain actual job info (location, job type). The rules say "Remove category labels that aren't part of the job (e.g., "Internships" as a standalone line)". These seem like metadata fields that are part of the job listing structure. I need to decide whether to keep or remove them. The second set of rules (HTML formatting) doesn't mention removing them, but the first set says remove "Category labels that aren't part of the job (e.g., "Internships" as a standalone line)". "Business Unit / Division:", "Job Type Classification:", "Location - Town / City:" seem like they could be considered part of the job info. However, the first rule says remove them if they aren't part of the job. But the location and job type are definitely part of the job. I'll keep them but maybe format them appropriately. Actually, looking at the second set of rules: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". This is strong. It says preserve ALL original content. So I shouldn't remove anything unless it's explicitly listed as removal items in the first part, but the first part and second part might be conflicting. The user message structure: The first paragraph is "You are a job listing editor..." then "REMOVE all of the following..." then "KEEP and STRUCTURE..." then "Return ONLY the cleaned job text." Then a new section: "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." with HTML rules. Then "Rules: - Use

  ... - No CSS classes... - 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." Then "Job description:" and the text. I think the user wants me to take the job description text, clean it according to the first set of rules (remove social sharing, bylines, etc.), and then format it as clean semantic HTML per the second set of rules. But the second set says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". This seems contradictory with the first set's removal list. However, the first set's removal list includes things not present in the text (social sharing, bylines, etc.), so maybe I just need to apply the HTML formatting while keeping all text that is part of the job description, and not remove anything that's actually in the text, except maybe stray formatting artifacts. Let re-read carefully: The very first block might be a system prompt that's not part of the task I need to output. The actual task is: "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." with the rules following. The "Job description:" is the input. I need to output HTML. The 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. This is clear. I need to convert the given job description text into HTML using those tags, preserving all content word-for-word. Now, how to structure it? The text has sections: - Business Unit / Division: TsAfrika Catering Solutions - Job Type Classification: Full Time - Location - Town / City: Pretoria - About Us: paragraph(s) - Duties & Responsibilities: paragraph(s) - seems like a block of text, not clearly separated list items, but I can treat it as paragraphs or list items. The rule says "Use

    • for list items (dutities, requirements, qualifications, skills)". The Duties & Responsibilities text is continuous prose. I could keep it in

      tags, or break into

    • if I identify list items. But the rule says "Preserve ALL original content word-for-word". If I break it into
      • , I might need to rephrase or restructure, which violates "do not add, remove, summarise, or rephrase". However, I can wrap list items in
      • without changing words, just marking them as list items. But the text isn't originally separated by bullets; it's run-on sentences. The rule 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 text has no clear sections, just wrap paragraphs in

          . So I need to decide what constitutes "list items" vs "paragraphs". Looking at the text: "Duties & Responsibilities:" followed by a block that looks like prose: "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 ..." It's not bullet-formatted in the raw text, but it's clearly duties. I could treat each sentence or clause as a

        • , but that would be restructuring. The safe approach: since the rule says "If text has no clear sections, just wrap paragraphs in

          tags", and the text does have clear section headers (Duties & Responsibilities, Skills and Competencies, Qualifications), I can use

          for those section headers, and then wrap the content in

          tags, or use

          • where the content is naturally list-like. But the "Preserve ALL original content word-for-word" is strict. If I convert prose to
          • , I'm not adding/removing words, just marking up. But the order and separation might change. I think the intent is: if the original text has bullet points, keep them as
          • ; if it's prose, keep it in

            . The rule "Use

            • for list items (duties, requirements, qualifications, skills)" might mean that within those sections, if there are list items, use
              • . But the given text doesn't have explicit bullets; it's continuous text. However, looking closely at "Skills and Competencies:" the text is: "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" - this is also run-on, no bullets. "Qualifications:" similarly run-on. Given the strict "preserve ALL original content word-for-word", I should probably just use

                and

                tags, not force

                • unless it's clearly bullet-separated. But the rule says "Use
                  • for list items (duties, requirements, qualifications, skills)". It might be a requirement to format them as lists. I need to interpret this reasonably. Often in these tasks, the raw text has items separated by line breaks or semicolons, but here they're just spaces. I could insert line breaks as
                  • items without changing words, just marking each as a list item. But that would be adding structure not present, potentially violating "preserve ALL original content word-for-word" if the order of words within items changes. Actually, "word-for-word" means the textual content must be identical, not that I can't add HTML tags around it. Adding
                  • tags around phrases doesn't change the words themselves, it just marks them up. So I could split the duties text into separate
                  • elements, each containing a sentence or phrase, preserving the exact words. Let me look at the exact text for each section: "About Us:" then a long paragraph. I'll keep as

                    . "Duties & Responsibilities:" then the block. I could split into multiple

                    or

                  • . The rule says "Use
                    • for list items (duties, requirements, qualifications, skills)". Since it's labeled "Duties & Responsibilities", it's expected to be list items. I'll convert each sentence/clause to
                    • , but ensure all words are preserved exactly. Actually, to be safe and strictly follow "Preserve ALL original content word-for-word", I should not rephrase or restructure. I'll use

                      for the about us paragraph,

                      for section headers, and for the duties/skills/qualifications sections, I'll use

                      • but only if the text can be naturally divided. Since the user says "If text has no clear sections, just wrap paragraphs in

                        tags", and this text does have clear sections (Duties & Responsibilities, Skills and Competencies, Qualifications), I should use

                        for those section headers, and then the content. I'll use

                        for content that's prose, and

                        • for items that are list-like. But the content within those sections is not pre-bulleted. I need to decide. Let me re-read the rule: "Use
                          • for list items (duties, requirements, qualifications, skills)". This likely means: when presenting duties, requirements, qualifications, and skills, use
                            • to mark each item. The raw text has these sections, so I should output them as lists. Even if the original wasn't bulleted, the markup will make them list items. The "preserve ALL original content word-for-word" means I keep the exact text of each item, just wrap them in
                            • . How to split? I need to identify individual items. Looking at the duties text: it's a mix of sentences and phrases. I could split by periods, but some might be fragments. Let's list them out as best as I can: "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" That's 16 items. I could put each in
                            • . But the rule says "Preserve ALL original content word-for-word". If I split like this, I'm preserving the words within each
                            • , but I'm also potentially changing the meaning by isolating sentences. However, the instruction is to format as clean semantic HTML, and the rule explicitly says use
                              • for list items (duties, requirements, qualifications, skills). So I should do that. Similarly for "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" And "Qualifications": "Matric and tertiary qualifications" "Preferably own vehicle would be an added advantage" "5 - 8 years working experience as a Catering Manager or

  Translated by AI — may not be perfect

  Show original