Theatre Stock Controller Fixed Term Contract
Netcare
Job Description
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; 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.
So we need to produce HTML with appropriate tags. The input is a messy text with many
, ,
, , etc. We need to extract actual job information and return cleaned HTML. But the instruction at top says "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." Then later says "You receive a plain-text job description. Your ONLY job is to format it as clean, readable format." Actually there are two different prompts? The user message starts with "You receive a plain-text job description. Your ONLY job is to format it as clean, readable format." Then rules about formatting as clean semantic HTML. So we need to output HTML.
We must remove all non-job info: social sharing, author bylines, related posts, navigation, comments, ads, cookie notices, duplicate text, category labels, stray numbers. But the entire text seems to be a job listing for Netcare Stock Controller. There's no obvious extraneous stuff like "Share" etc. However there are some empty and which we can ignore. Also there are some lines like "ROLE SUMMARY", "KEY WORK OUTPUT AND ACCOUNTABILITIES", etc. Those are section headers. We should keep them as perhaps. The example headers include Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role. Here we have "ROLE SUMMARY", "KEY WORK OUTPUT AND ACCOUNTABILITIES", "CONSISTENCY OF CARE", "Stock Control administration", "Stock take", "Risk, compliance and reporting", "Administration", "People Management", "TRANSFORMATION OF OUR SOCIETY", "Personal and professional development", "Build and maintain stakeholder relationships", "SKILLS PROFILE", "EDUCATION", "WORK EXPERIENCE", "KNOWLEDGE", "PHYSICAL REQUIREMENTS", "SKILLS", "Continuous Improvement", "Personal Work Ethic", "Building Relationships", "Communication", "Teamwork", "Technical Knowledge", "WORKING CONDITIONS", "NETCARE VALUES AND BEHAVIOURS", "Netcare Values", "The Netcare Way". Some of these are subsections. We need to decide how to structure. The rule says use for section headers. So we can convert all bold headings into . For example "ROLE SUMMARY" -> ROLE SUMMARY
. "KEY WORK OUTPUT AND ACCOUNTABILITIES" -> . "CONSISTENCY OF CARE" -> . "Stock Control administration" -> . etc. Also "SKILLS PROFILE" -> . "EDUCATION" -> . "WORK EXPERIENCE" -> . "KNOWLEDGE" -> . "PHYSICAL REQUIREMENTS" -> . "SKILLS" -> . "Continuous Improvement" -> . etc. "NETCARE VALUES AND BEHAVIOURS" -> . "Netcare Values" -> . "The Netcare Way" -> . Also "Essential", "Preferable" are not headers but labels for lists. They appear as separate
before
. We can keep them as or maybe as part of list? The rule says use
- for list items. The "Essential" and "Preferable" are not list items but category labels. Could keep as
or maybe as ? But rule says no inline styles, no CSS classes. We can just keep them as or maybe as
? But rule says for section headers. "Essential" and "Preferable" are not section headers, they are sub-labels. Could be kept as
or maybe as ? But they are not bold originally? In original they are plain text "Essential" and "Preferable". They appear as Essential
and Preferable
. We can keep them as or maybe as
? The rule says use for section headers, but doesn't forbid other heading levels. However to be safe, we can keep them as
or maybe as ? But the instruction says "Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". It doesn't say we cannot use other levels, but we should stick to those examples. "Essential" and "Preferable" could be considered sub-headers, but they are not typical. I think we can keep them as
or maybe as
if needed. But the rule says "If text has no clear sections, just wrap paragraphs in
tags". Since these are clear sections, we can treat them as
? Actually they are not section headers, they are category labels. I think we can keep them as
or maybe as but no inline styles. Better to keep as or maybe as
? Let's see typical job descriptions: "Education: Essential Grade 12..." The "Essential" is a label. I'd keep it as
or maybe as but no classes. I'll keep as or maybe as
? The rule says "Use for section headers". It doesn't forbid using for sub-headers. But to be safe, I'll keep them as
or maybe as ? Actually the original has them as plain text without bold. I'll keep them as or maybe as
? I think is acceptable. But the instruction says "Return ONLY the HTML. No markdown fences, no explanation, no preamble." So we just output HTML.
We need to preserve all content word-for-word. So we need to include all the bullet points exactly as given. Also the introductory paragraphs: "We provide meaningful careers that connect people with purpose." etc. Those are part of the role summary. We should include them as
or maybe as
? The first paragraph is a mission statement. It's not a section header. So keep as
. The second paragraph is also mission statement. Third paragraph is about Netcare values. Fourth paragraph is "Netcare invites you to be part of our journey." That's an intro. Then "ROLE SUMMARY" header. Then the summary paragraph. Then "KEY WORK OUTPUT AND ACCOUNTABILITIES" header. Then "CONSISTENCY OF CARE" header. Then "Stock Control administration" header. Then list. Then "Stock take" header. Then list. Then "Risk, compliance and reporting" header. Then list. Then "Administration" header. Then list. Then "People Management" header. Then list. Then "TRANSFORMATION OF OUR SOCIETY" header. Then "Personal and professional development" header. Then list. Then "Build and maintain stakeholder relationships" header. Then list. Then "SKILLS PROFILE" header. Then "EDUCATION" header. Then "Essential"
then list. Then "Preferable"
then list. Then "WORK EXPERIENCE" header. Then "Essential"
then list. Then "Preferred"
then list. Then "KNOWLEDGE" header. Then "Essential"
then list. Then "Preferred"
then list. Then "PHYSICAL REQUIREMENTS" header. Then list. Then "SKILLS" header. Then empty. Then "Continuous Improvement" header. Then list. Then "Personal Work Ethic" header. Then list. Then "Building Relationships" header. Then list. Then "Communication" header. Then list. Then "Teamwork" header. Then list. Then "Technical Knowledge" header. Then list. Then "WORKING CONDITIONS" header. Then list. Then "NETCARE VALUES AND BEHAVIOURS" header. Then "Netcare Values" header. Then list of values. Then "The Netcare Way" header. Then list of behaviors. Then final paragraph "Join the team committed to providing the best and safest health and care." That's a closing line. Should we include it? It's part of the job description. Yes, include as
.
Also there are some stray numbers? No. There are no stray numbers. There are some empty
and which we can omit. Also there is a Join the team...
which we can convert to without style.
We need to ensure no
, no
, no inline styles. So we must remove all style attributes. Also remove any tags? The rule says preserve all original content word-for-word. But we are formatting as HTML. The original has tags. Should we keep them? The rule says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". That means we should keep the text exactly, including bold markers? But the instruction says "No CSS classes, no inline styles, no s, no
tags". It doesn't say we cannot use tags. However the example of formatting uses for introductory paragraphs and general text. It doesn't mention preserving tags. But "preserve all original content word-for-word" might mean the text content, not necessarily the HTML tags. Usually when converting plain text to HTML, we would keep the bold markers as or . But the rule says "Use for introductory paragraphs and general text". It doesn't explicitly say to remove tags. However the original text includes tags. If we keep them, that's fine. But we need to decide. The safest is to keep the tags as they are, because they are part of the original content. But the rule says "No CSS classes, no inline styles, no s, no
tags". It doesn't forbid . So we can keep tags. However, the instruction "Return ONLY the HTML. No markdown fences, no explanation, no preamble." So we just output HTML.
But note: The original has many tags. For example "We provide meaningful careers that connect people with purpose." is wrapped in . We should keep that as We provide...
. Similarly for other bold headings. The headings like "ROLE SUMMARY" are wrapped in ? Actually in the text: "We provide meaningful careers that connect people with purpose.
" then "" then "We are united by a common purpose...
" etc. Then later "ROLE SUMMARY
" Wait, look: The text shows "
ROLE SUMMARY
" Actually the raw text: "
ROLE SUMMARY
" That's interesting. The heading "ROLE SUMMARY" is inside tag, and there is a
after it. But the rule says no
tags. So we must remove the
tags. But we need to preserve content word-for-word. Removing
tags is allowed because they are not content, they are formatting. The rule says "no
tags". So we should remove them. Similarly for other
tags. So we need to strip out all
tags. Also strip out any style attributes.
Also there are some
which we can just drop. And which we can drop style.
So the plan: Parse the text, extract all content, replace with (keep), remove
, remove style attributes, remove empty paragraphs, keep all text. Structure with for section headers (bold headings). For lists, keep - . For "Essential" and "Preferable", keep as
or maybe as
? I'll keep them as
because they are not section headers. But they are labels. Could also be but no inline styles. I'll keep as . However, the rule says "Use
for section headers". It doesn't say we cannot use other levels. But to be safe, I'll keep them as
or maybe as
? I think is acceptable. But the instruction says "Return ONLY the HTML. No markdown fences, no explanation, no preamble." So we just output HTML.
Let's examine the exact text. I'll copy it and process mentally.
First few paragraphs:
We provide meaningful careers that connect people with purpose.
We are united by a common purpose of providing the best and safest care; and by our shared values of Care, Truth, Participation, Compassion and Dignity.
Netcare invites you to be part of our journey.
Then:
ROLE SUMMARY
Person centred Health and care focuses on dignity and respect...
...
The Stock Controller is responsible for maintaining optimal stock levels...
...
The Stock Controller will be required to work in various different areas...
...
Then:
KEY WORK OUTPUT AND ACCOUNTABILITIES
CONSISTENCY OF CARE
Stock Control administration
...
Stock take
...
Risk, compliance and reporting
...
Administration
...
People Management
...
TRANSFORMATION OF OUR SOCIETY
Personal and professional development
...
Build and maintain stakeholder relationships
...
SKILLS PROFILE
EDUCATION
Essential
...
Preferable
...
WORK EXPERIENCE
Essential
...
Preferred
...
KNOWLEDGE
Essential
...
Preferred
...
PHYSICAL REQUIREMENTS
...
SKILLS
Continuous Improvement
...
Personal Work Ethic
...
Building Relationships
...
Communication
...
Teamwork
...
Technical Knowledge
...
WORKING CONDITIONS
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 📝
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. So we need to produce HTML with appropriate tags. The input is a messy text with many
, , before or maybe as part of list? The rule says use or maybe as ? But rule says no inline styles, no CSS classes. We can just keep them as or maybe as or maybe as ? But they are not bold originally? In original they are plain text "Essential" and "Preferable". They appear as Essential Preferable or maybe as or maybe as ? But the instruction says "Use or maybe as tags". Since these are clear sections, we can treat them as or maybe as but no inline styles. Better to keep as or maybe as or maybe as but no classes. I'll keep as or maybe as or maybe as ? Actually the original has them as plain text without bold. I'll keep them as or maybe as or maybe as . The second paragraph is also mission statement. Third paragraph is about Netcare values. Fourth paragraph is "Netcare invites you to be part of our journey." That's an intro. Then "ROLE SUMMARY" header. Then the summary paragraph. Then "KEY WORK OUTPUT AND ACCOUNTABILITIES" header. Then "CONSISTENCY OF CARE" header. Then "Stock Control administration" header. Then list. Then "Stock take" header. Then list. Then "Risk, compliance and reporting" header. Then list. Then "Administration" header. Then list. Then "People Management" header. Then list. Then "TRANSFORMATION OF OUR SOCIETY" header. Then "Personal and professional development" header. Then list. Then "Build and maintain stakeholder relationships" header. Then list. Then "SKILLS PROFILE" header. Then "EDUCATION" header. Then "Essential" then list. Then "Preferable" then list. Then "WORK EXPERIENCE" header. Then "Essential" then list. Then "Preferred" then list. Then "KNOWLEDGE" header. Then "Essential" then list. Then "Preferred" then list. Then "PHYSICAL REQUIREMENTS" header. Then list. Then "SKILLS" header. Then empty. Then "Continuous Improvement" header. Then list. Then "Personal Work Ethic" header. Then list. Then "Building Relationships" header. Then list. Then "Communication" header. Then list. Then "Teamwork" header. Then list. Then "Technical Knowledge" header. Then list. Then "WORKING CONDITIONS" header. Then list. Then "NETCARE VALUES AND BEHAVIOURS" header. Then "Netcare Values" header. Then list of values. Then "The Netcare Way" header. Then list of behaviors. Then final paragraph "Join the team committed to providing the best and safest health and care." That's a closing line. Should we include it? It's part of the job description. Yes, include as .
Also there are some stray numbers? No. There are no stray numbers. There are some empty Join the team... without style.
We need to ensure no for introductory paragraphs and general text. It doesn't mention preserving tags. But "preserve all original content word-for-word" might mean the text content, not necessarily the HTML tags. Usually when converting plain text to HTML, we would keep the bold markers as or . But the rule says "Use for introductory paragraphs and general text". It doesn't explicitly say to remove tags. However the original text includes tags. If we keep them, that's fine. But we need to decide. The safest is to keep the tags as they are, because they are part of the original content. But the rule says "No CSS classes, no inline styles, no We provide... We provide meaningful careers that connect people with purpose. We are united by a common purpose... ROLE SUMMARY ROLE SUMMARY ROLE SUMMARY which we can drop style.
So the plan: Parse the text, extract all content, replace with (keep), remove or maybe as because they are not section headers. But they are labels. Could also be but no inline styles. I'll keep as . However, the rule says "Use or maybe as We provide meaningful careers that connect people with purpose. We are united by a common purpose of providing the best and safest care; and by our shared values of Care, Truth, Participation, Compassion and Dignity. Netcare invites you to be part of our journey. KEY WORK OUTPUT AND ACCOUNTABILITIES CONSISTENCY OF CARE Stock Control administration Stock take Risk, compliance and reporting Administration People Management TRANSFORMATION OF OUR SOCIETY Personal and professional development Build and maintain stakeholder relationships SKILLS PROFILE EDUCATION Essential Preferable WORK EXPERIENCE Essential Preferred KNOWLEDGE Essential Preferred PHYSICAL REQUIREMENTS SKILLS Continuous Improvement Personal Work Ethic Building Relationships Communication Teamwork Technical Knowledge WORKING CONDITIONS Get an instant AI match score for this role — free, takes 3 minutes. The concierge rewrites your whole CV and writes a matching cover letter for this job — opens right here, nothing to paste. Upload your CV and get a tailored cover letter in seconds — free, no account needed.
, , etc. We need to extract actual job information and return cleaned HTML. But the instruction at top says "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." Then later says "You receive a plain-text job description. Your ONLY job is to format it as clean, readable format." Actually there are two different prompts? The user message starts with "You receive a plain-text job description. Your ONLY job is to format it as clean, readable format." Then rules about formatting as clean semantic HTML. So we need to output HTML.
We must remove all non-job info: social sharing, author bylines, related posts, navigation, comments, ads, cookie notices, duplicate text, category labels, stray numbers. But the entire text seems to be a job listing for Netcare Stock Controller. There's no obvious extraneous stuff like "Share" etc. However there are some empty and which we can ignore. Also there are some lines like "ROLE SUMMARY", "KEY WORK OUTPUT AND ACCOUNTABILITIES", etc. Those are section headers. We should keep them as
perhaps. The example headers include Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role. Here we have "ROLE SUMMARY", "KEY WORK OUTPUT AND ACCOUNTABILITIES", "CONSISTENCY OF CARE", "Stock Control administration", "Stock take", "Risk, compliance and reporting", "Administration", "People Management", "TRANSFORMATION OF OUR SOCIETY", "Personal and professional development", "Build and maintain stakeholder relationships", "SKILLS PROFILE", "EDUCATION", "WORK EXPERIENCE", "KNOWLEDGE", "PHYSICAL REQUIREMENTS", "SKILLS", "Continuous Improvement", "Personal Work Ethic", "Building Relationships", "Communication", "Teamwork", "Technical Knowledge", "WORKING CONDITIONS", "NETCARE VALUES AND BEHAVIOURS", "Netcare Values", "The Netcare Way". Some of these are subsections. We need to decide how to structure. The rule says use
for section headers. So we can convert all bold headings into
. For example "ROLE SUMMARY" ->
ROLE SUMMARY
. "KEY WORK OUTPUT AND ACCOUNTABILITIES" -> . "CONSISTENCY OF CARE" ->
. "Stock Control administration" ->
. etc. Also "SKILLS PROFILE" ->
. "EDUCATION" ->
. "WORK EXPERIENCE" ->
. "KNOWLEDGE" ->
. "PHYSICAL REQUIREMENTS" ->
. "SKILLS" ->
. "Continuous Improvement" ->
. etc. "NETCARE VALUES AND BEHAVIOURS" ->
. "Netcare Values" ->
. "The Netcare Way" ->
. Also "Essential", "Preferable" are not headers but labels for lists. They appear as separate
. We can keep them as
? But rule says
for section headers. "Essential" and "Preferable" are not section headers, they are sub-labels. Could be kept as
? The rule says use
for section headers, but doesn't forbid other heading levels. However to be safe, we can keep them as
for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". It doesn't say we cannot use other levels, but we should stick to those examples. "Essential" and "Preferable" could be considered sub-headers, but they are not typical. I think we can keep them as
if needed. But the rule says "If text has no clear sections, just wrap paragraphs in
? Actually they are not section headers, they are category labels. I think we can keep them as
? Let's see typical job descriptions: "Education: Essential Grade 12..." The "Essential" is a label. I'd keep it as
? The rule says "Use
for section headers". It doesn't forbid using
for sub-headers. But to be safe, I'll keep them as
? I think
is acceptable. But the instruction says "Return ONLY the HTML. No markdown fences, no explanation, no preamble." So we just output HTML.
We need to preserve all content word-for-word. So we need to include all the bullet points exactly as given. Also the introductory paragraphs: "We provide meaningful careers that connect people with purpose." etc. Those are part of the role summary. We should include them as
? The first paragraph is a mission statement. It's not a section header. So keep as
, no inline styles. So we must remove all style attributes. Also remove any tags? The rule says preserve all original content word-for-word. But we are formatting as HTML. The original has tags. Should we keep them? The rule says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". That means we should keep the text exactly, including bold markers? But the instruction says "No CSS classes, no inline styles, no
tags". It doesn't say we cannot use tags. However the example of formatting uses
tags". It doesn't forbid . So we can keep tags. However, the instruction "Return ONLY the HTML. No markdown fences, no explanation, no preamble." So we just output HTML.
But note: The original has many tags. For example "We provide meaningful careers that connect people with purpose." is wrapped in . We should keep that as
" Wait, look: The text shows "
" Actually the raw text: "
" That's interesting. The heading "ROLE SUMMARY" is inside tag, and there is a
after it. But the rule says no
tags. So we must remove the
tags. But we need to preserve content word-for-word. Removing
tags is allowed because they are not content, they are formatting. The rule says "no
tags". So we should remove them. Similarly for other
tags. So we need to strip out all
tags. Also strip out any style attributes.
Also there are some
, remove style attributes, remove empty paragraphs, keep all text. Structure with for section headers (bold headings). For lists, keep
? I'll keep them as
for section headers". It doesn't say we cannot use other levels. But to be safe, I'll keep them as
? I think
is acceptable. But the instruction says "Return ONLY the HTML. No markdown fences, no explanation, no preamble." So we just output HTML.
Let's examine the exact text. I'll copy it and process mentally.
First few paragraphs:
Person centred Health and care focuses on dignity and respect...
...
The Stock Controller is responsible for maintaining optimal stock levels...
...
The Stock Controller will be required to work in various different areas...
...
Then:
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
How well do you match?
Tailor your CV for this role
Free cover letter for this job
Let jobs find you
Leave your email and our AI matches you to new jobs across 24 African markets — free. You wait for the call.
Add your CV for real matches
Upload your CV and we score every new job against your real experience — only strong matches reach your inbox. Optional, but it makes your matches far sharper.
You're in.
We'll email you the moment a job matches your profile. Check your inbox for a welcome from My Job Concierge.
I'm ECHO, your MJC career assistant. I can help you find jobs, explore career tools, and connect with opportunities across Africa.