Job Description
for intro paragraphs and general text,
for section headers (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 , no
. Preserve all original content word-for-word, no addition/removal/summarizing/rephrasing.
We need to parse the given raw text (which includes HTML tags with styles etc). We need to extract the content and produce HTML as per rules.
Given the raw text:
It's fun to work in a company where people truly BELIEVE in what they're doing!
Responsible for production of Sushi within the department .Competencies:
Ingredient knowledge & recipe specifications
Food Safety compliance & training
Good knowledge of different sushi recipes
Business Minded
Customer Orientation
Express and implied ethical responsibilities.
Relevant systems knowledge
Sushi Onboarding programme
Understanding of production cards and production plan
Understanding of relevant SOP
Minimum Requirements:
Grade 12
Experience in cutting and filleting fish
Demonstrated ability in preparing of all fish related products
Broad knowledge of fish
Ability to communicate in English
Key Responsibilities:
Production
Follow production plan to ensure sales growth and minimize waste on a weekly basis
Produce sushi recipes according to the production plan
Ensure that the work environment is clean all the time
Sales/ Turnover/ Gross Margin
Ensure readiness of upcoming of promotional lines in conjunction with the Sushi Chef.
Administration
Assist with monthly Stocktakes
Conduct waste scanning daily
Food Safety
Ensure adherence to food safety procedures
Maintain hygiene standards
Maintain cold chain all the time
Prevent cross contamination in the department
Self – Management
Continually drive and model PnP values at all levels
Make an effort to stay relevant and up to date with new legislation and development etc.
Take ownership and accountability for tasks and activities and demonstrate effective self-management.
Maintain a positive attitude and respond openly to feedback
Closing Date 25 September 2026
If you like wild growth and working with happy, enthusiastic over-achievers, you'll enjoy your career with us!
Discover who we are
We need to produce HTML with for intro paragraphs and general text,
for section headers, - for list items.
We need to preserve all original content word-for-word. That means we cannot change the text, but we can wrap it in tags. We need to remove any HTML tags that were present (like style attributes) and just keep the text content. Also need to remove empty paragraphs.
We need to identify sections: The text includes:
- Intro: "It's fun to work in a company where people truly BELIEVE in what they're doing!" (maybe also blank lines)
- Then "Responsible for production of Sushi within the department." (note there is a special space after department? It shows a non-breaking space? We'll keep as is.)
- Then a section "Competencies:" with list items each in separate
tags. Those are list items (competencies). Should we treat as list? The instruction: Use
- for list items (duties, requirements, qualifications, skills). Competencies could be considered skills? Probably yes. So we should wrap each competency line in
- inside a
under a header "Competencies". However 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 list Competencies explicitly, but we can still use for any section header? The rule: Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). It says e.g., implying those are examples; we can still use for other section headers like Competencies, Minimum Requirements, Key Responsibilities, Closing Date, etc. Probably yes.
Thus we will produce:
It's fun to work in a company where people truly BELIEVE in what they're doing!
Responsible for production of Sushi within the department.
Competencies
- Ingredient knowledge & recipe specifications
- Food Safety compliance & training
- Good knowledge of different sushi recipes
- Business Minded
- Customer Orientation
- Express and implied ethical responsibilities.
- Relevant systems knowledge
- Sushi Onboarding programme
- Understanding of production cards and production plan
- Understanding of relevant SOP
Minimum Requirements
- Grade 12
- Experience in cutting and filleting fish
- Demonstrated ability in preparing of all fish related products
- Broad knowledge of fish
- Ability to communicate in English
Key Responsibilities
We need to structure responsibilities: There's a heading Key Responsibilities: then subheadings Production, Sales/Turnover/Gross Margin, Administration, Food Safety, Self – Management. Each subheading has list items.
We could treat each subheading as a ? But rule only allows for section headers. We could keep subheadings as
...? but we cannot add because we must preserve original content word-for-word. The original content includes Production etc. We must preserve that exactly. So we need to keep the bold tags? The instruction says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. That includes the tags? The original content includes HTML tags with . However earlier we were told to output clean semantic HTML, using only ,
, - . No CSS classes, no inline styles, no , no
. It didn't forbid or tags. It said use for introductory paragraphs and general text,
for section headers, - for list items. It didn't say we cannot use other tags like or . However the instruction to preserve original content word-for-word suggests we should keep the and tags as they appear. But we also need to output only HTML; we can keep and as they are. However the earlier instruction: "Use
for introductory paragraphs and general text. Use
for section headers ... Use - for list items. No CSS classes, no inline styles, no s, no
tags." It doesn't forbid other tags like , , . So we could keep them.
But we also need to remove style attributes etc. The original had ... etc. We should strip those attributes but keep the inner text. For and tags, they have no style attributes, so we can keep them.
Thus we need to parse the original and produce HTML with minimal tags: we keep and where they appear, but we remove style attributes and empty spans.
Let's extract the text content with tags:
Original snippet:
It's fun to work in a company where people truly BELIEVE in what they're doing!
We should convert to It's fun to work in a company where people truly BELIEVE in what they're doing!
(the HTML entity ' should be kept as apostrophe? It's part of original content; we should keep the entity? The instruction says preserve ALL original content word-for-word. That includes the entity '. So we should keep it as ' not convert to apostrophe. However typical HTML output would treat it as entity; but we need to output exactly the same characters. The original shows '. We should keep that. So we output It's fun to work in a company where people truly BELIEVE in what they're doing!
Similarly for other text.
Next blank paragraphs: we can ignore.
Then "Responsible for production of Sushi within the department ." There's a non-breaking space after department? It shows a special space. We'll keep as is: "Responsible for production of Sushi within the department ." (including the space before period?). We'll keep exactly.
Then we have Competencies:
. This is a paragraph containing bold text "Competencies:" with a space after colon inside the span? Actually Competencies: includes a space after the closing span but inside the b. So the text is "Competencies: " (with trailing space). We need to preserve that. So we output Competencies:
but we need to strip style attributes (none). However we also need to wrap the following competency lines in - . The competency lines are each in
...
. They have nested spans. We should keep the inner text but strip spans. So each line becomes - Ingredient knowledge & recipe specifications
etc. Note the ampersand is encoded as &. We should keep that.
Thus we will output:
Competencies:
- Ingredient knowledge & recipe specifications
- Food Safety compliance & training
- Good knowledge of different sushi recipes
- Business Minded
- Customer Orientation
- Express and implied ethical responsibilities.
- Relevant systems knowledge
- Sushi Onboarding programme
- Understanding of production cards and production plan
- Understanding of relevant SOP
Note we need to preserve trailing spaces inside the - ? The original lines have a space after the text before closing span? Eg: Good knowledge of different sushi recipes There's a non-breaking space after recipes and then another span with a space. So the text includes a space after recipes and then another space. We should keep them as part of the text. So the li content should be "Good knowledge of different sushi recipes " (including the spaces). Hard to represent but we can keep as is: "Good knowledge of different sushi recipes " (maybe two spaces). We'll just copy the inner text exactly as appears between the outer
tags after stripping spans. Let's extract: The original line:
Good knowledge of different sushi recipes
. The inner text is "Good knowledge of different sushi recipes " followed by a non-breaking space (the second span). So combined: "Good knowledge of different sushi recipes " (with a space after). We'll keep that.
Similarly for Business Minded and Customer Orientation lines have trailing spaces.
We'll keep them.
Next: Minimum Requirements:
then list items each in tags.
We'll output:
Minimum Requirements:
- Grade 12
- Experience in cutting and filleting fish
- Demonstrated ability in preparing of all fish related products
- Broad knowledge of fish
- Ability to communicate in English
Then we have some empty paragraphs.
Then Key Responsibilities:
Then
Production
This line includes a
then Production. The
is a line break; we are not allowed to use
tags per rule: "No CSS classes, no inline styles, no s, no
tags". So we must remove the
tag. But we must preserve original content word-for-word. Conflict: we cannot keep
because rule forbids
. However the rule says "No CSS classes, no inline styles, no s, no
tags". So we must omit
. But then we are not preserving original content word-for-word. Which rule takes precedence? The instruction says: "Your ONLY job is to format it as clean semantic HTML." Then rules: Use for intro paragraphs and general text, Use
for section headers, Use - 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. This is contradictory if original contains
. However maybe the original
is just an artifact from conversion and we can drop it because it's not meaningful content. The rule says preserve ALL original content word-for-word, but also says no
tags. Likely they expect us to remove the
as it's just formatting. We'll follow the higher-level rule: no
tags. So we will omit the
. We'll keep the Production text.
Thus we will output:
Production
Then the list items under Production: each in tags.
We need to decide whether to wrap them in
- . The rule says use
- for list items (duties, requirements, qualifications, skills). These are duties under Production. So we should wrap them in a list. However there are subheadings like Sales/ Turnover/ Gross Margin etc. We could treat each subheading as a separate list group? Or we could make a single list with all items, but that would lose subheadings. Better to keep subheadings as
...
and then each group's items as - . That seems reasonable.
Thus after
Production
we output a with the three production duties.
Then Sales/ Turnover/ Gross Margin
then a with its one duty.
Then Administration
then with its two duties.
Then Food Safety
then with its four duties.
Then Self – Management
then with its four duties.
Note there is a space before and after the dash? Original: "Self – Management" includes an en dash? We'll keep as is.
Then after that we have Closing Date 25 September 2026
. This is not a list; we can keep as Closing Date 25 September
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 📝
My Job Concierge
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.
Almost there
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.
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.
. Preserve all original content word-for-word, no addition/removal/summarizing/rephrasing. We need to parse the given raw text (which includes HTML tags with styles etc). We need to extract the content and produce HTML as per rules. Given the raw text:
It's fun to work in a company where people truly BELIEVE in what they're doing!
Responsible for production of Sushi within the department .Competencies:
Ingredient knowledge & recipe specifications
Food Safety compliance & training
Good knowledge of different sushi recipes
Business Minded
Customer Orientation
Express and implied ethical responsibilities.
Relevant systems knowledge
Sushi Onboarding programme
Understanding of production cards and production plan
Understanding of relevant SOP
Minimum Requirements:
Grade 12
Experience in cutting and filleting fish
Demonstrated ability in preparing of all fish related products
Broad knowledge of fish
Ability to communicate in English
Key Responsibilities:
Production
Follow production plan to ensure sales growth and minimize waste on a weekly basis
Produce sushi recipes according to the production plan
Ensure that the work environment is clean all the time
Sales/ Turnover/ Gross Margin
Ensure readiness of upcoming of promotional lines in conjunction with the Sushi Chef.
Administration
Assist with monthly Stocktakes
Conduct waste scanning daily
Food Safety
Ensure adherence to food safety procedures
Maintain hygiene standards
Maintain cold chain all the time
Prevent cross contamination in the department
Self – Management
Continually drive and model PnP values at all levels
Make an effort to stay relevant and up to date with new legislation and development etc.
Take ownership and accountability for tasks and activities and demonstrate effective self-management.
Maintain a positive attitude and respond openly to feedback
Closing Date 25 September 2026
If you like wild growth and working with happy, enthusiastic over-achievers, you'll enjoy your career with us!
Discover who we are
We need to produce HTML withfor intro paragraphs and general text,
for section headers, - for list items.
We need to preserve all original content word-for-word. That means we cannot change the text, but we can wrap it in tags. We need to remove any HTML tags that were present (like style attributes) and just keep the text content. Also need to remove empty paragraphs.
We need to identify sections: The text includes:
- Intro: "It's fun to work in a company where people truly BELIEVE in what they're doing!" (maybe also blank lines)
- Then "Responsible for production of Sushi within the department." (note there is a special space after department? It shows a non-breaking space? We'll keep as is.)
- Then a section "Competencies:" with list items each in separate
tags. Those are list items (competencies). Should we treat as list? The instruction: Use
- for list items (duties, requirements, qualifications, skills). Competencies could be considered skills? Probably yes. So we should wrap each competency line in
- inside a
under a header "Competencies". However 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 list Competencies explicitly, but we can still use for any section header? The rule: Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). It says e.g., implying those are examples; we can still use for other section headers like Competencies, Minimum Requirements, Key Responsibilities, Closing Date, etc. Probably yes.
Thus we will produce:
It's fun to work in a company where people truly BELIEVE in what they're doing!
Responsible for production of Sushi within the department.
Competencies
- Ingredient knowledge & recipe specifications
- Food Safety compliance & training
- Good knowledge of different sushi recipes
- Business Minded
- Customer Orientation
- Express and implied ethical responsibilities.
- Relevant systems knowledge
- Sushi Onboarding programme
- Understanding of production cards and production plan
- Understanding of relevant SOP
Minimum Requirements
- Grade 12
- Experience in cutting and filleting fish
- Demonstrated ability in preparing of all fish related products
- Broad knowledge of fish
- Ability to communicate in English
Key Responsibilities
We need to structure responsibilities: There's a heading Key Responsibilities: then subheadings Production, Sales/Turnover/Gross Margin, Administration, Food Safety, Self – Management. Each subheading has list items.
We could treat each subheading as a ? But rule only allows for section headers. We could keep subheadings as
...? but we cannot add because we must preserve original content word-for-word. The original content includes Production etc. We must preserve that exactly. So we need to keep the bold tags? The instruction says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. That includes the tags? The original content includes HTML tags with . However earlier we were told to output clean semantic HTML, using only ,
, - . No CSS classes, no inline styles, no , no
. It didn't forbid or tags. It said use for introductory paragraphs and general text,
for section headers, - for list items. It didn't say we cannot use other tags like or . However the instruction to preserve original content word-for-word suggests we should keep the and tags as they appear. But we also need to output only HTML; we can keep and as they are. However the earlier instruction: "Use
for introductory paragraphs and general text. Use
for section headers ... Use - for list items. No CSS classes, no inline styles, no s, no
tags." It doesn't forbid other tags like , , . So we could keep them.
But we also need to remove style attributes etc. The original had ... etc. We should strip those attributes but keep the inner text. For and tags, they have no style attributes, so we can keep them.
Thus we need to parse the original and produce HTML with minimal tags: we keep and where they appear, but we remove style attributes and empty spans.
Let's extract the text content with tags:
Original snippet:
It's fun to work in a company where people truly BELIEVE in what they're doing!
We should convert to It's fun to work in a company where people truly BELIEVE in what they're doing!
(the HTML entity ' should be kept as apostrophe? It's part of original content; we should keep the entity? The instruction says preserve ALL original content word-for-word. That includes the entity '. So we should keep it as ' not convert to apostrophe. However typical HTML output would treat it as entity; but we need to output exactly the same characters. The original shows '. We should keep that. So we output It's fun to work in a company where people truly BELIEVE in what they're doing!
Similarly for other text.
Next blank paragraphs: we can ignore.
Then "Responsible for production of Sushi within the department ." There's a non-breaking space after department? It shows a special space. We'll keep as is: "Responsible for production of Sushi within the department ." (including the space before period?). We'll keep exactly.
Then we have Competencies:
. This is a paragraph containing bold text "Competencies:" with a space after colon inside the span? Actually Competencies: includes a space after the closing span but inside the b. So the text is "Competencies: " (with trailing space). We need to preserve that. So we output Competencies:
but we need to strip style attributes (none). However we also need to wrap the following competency lines in - . The competency lines are each in
...
. They have nested spans. We should keep the inner text but strip spans. So each line becomes - Ingredient knowledge & recipe specifications
etc. Note the ampersand is encoded as &. We should keep that.
Thus we will output:
Competencies:
- Ingredient knowledge & recipe specifications
- Food Safety compliance & training
- Good knowledge of different sushi recipes
- Business Minded
- Customer Orientation
- Express and implied ethical responsibilities.
- Relevant systems knowledge
- Sushi Onboarding programme
- Understanding of production cards and production plan
- Understanding of relevant SOP
Note we need to preserve trailing spaces inside the - ? The original lines have a space after the text before closing span? Eg: Good knowledge of different sushi recipes There's a non-breaking space after recipes and then another span with a space. So the text includes a space after recipes and then another space. We should keep them as part of the text. So the li content should be "Good knowledge of different sushi recipes " (including the spaces). Hard to represent but we can keep as is: "Good knowledge of different sushi recipes " (maybe two spaces). We'll just copy the inner text exactly as appears between the outer
tags after stripping spans. Let's extract: The original line:
Good knowledge of different sushi recipes
. The inner text is "Good knowledge of different sushi recipes " followed by a non-breaking space (the second span). So combined: "Good knowledge of different sushi recipes " (with a space after). We'll keep that.
Similarly for Business Minded and Customer Orientation lines have trailing spaces.
We'll keep them.
Next: Minimum Requirements:
then list items each in tags.
We'll output:
Minimum Requirements:
- Grade 12
- Experience in cutting and filleting fish
- Demonstrated ability in preparing of all fish related products
- Broad knowledge of fish
- Ability to communicate in English
Then we have some empty paragraphs.
Then Key Responsibilities:
Then
Production
This line includes a
then Production. The
is a line break; we are not allowed to use
tags per rule: "No CSS classes, no inline styles, no s, no
tags". So we must remove the
tag. But we must preserve original content word-for-word. Conflict: we cannot keep
because rule forbids
. However the rule says "No CSS classes, no inline styles, no s, no
tags". So we must omit
. But then we are not preserving original content word-for-word. Which rule takes precedence? The instruction says: "Your ONLY job is to format it as clean semantic HTML." Then rules: Use for intro paragraphs and general text, Use
for section headers, Use - 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. This is contradictory if original contains
. However maybe the original
is just an artifact from conversion and we can drop it because it's not meaningful content. The rule says preserve ALL original content word-for-word, but also says no
tags. Likely they expect us to remove the
as it's just formatting. We'll follow the higher-level rule: no
tags. So we will omit the
. We'll keep the Production text.
Thus we will output:
Production
Then the list items under Production: each in tags.
We need to decide whether to wrap them in
- . The rule says use
- for list items (duties, requirements, qualifications, skills). These are duties under Production. So we should wrap them in a list. However there are subheadings like Sales/ Turnover/ Gross Margin etc. We could treat each subheading as a separate list group? Or we could make a single list with all items, but that would lose subheadings. Better to keep subheadings as
...
and then each group's items as - . That seems reasonable.
Thus after
Production
we output a with the three production duties.
Then Sales/ Turnover/ Gross Margin
then a with its one duty.
Then Administration
then with its two duties.
Then Food Safety
then with its four duties.
Then Self – Management
then with its four duties.
Note there is a space before and after the dash? Original: "Self – Management" includes an en dash? We'll keep as is.
Then after that we have Closing Date 25 September 2026
. This is not a list; we can keep as Closing Date 25 September
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. Those are list items (competencies). Should we treat as list? The instruction: Use
- for list items (duties, requirements, qualifications, skills). Competencies could be considered skills? Probably yes. So we should wrap each competency line in
- inside a
- under a
- Ingredient knowledge & recipe specifications
- Food Safety compliance & training
- Good knowledge of different sushi recipes
- Business Minded
- Customer Orientation
- Express and implied ethical responsibilities.
- Relevant systems knowledge
- Sushi Onboarding programme
- Understanding of production cards and production plan
- Understanding of relevant SOP
- Grade 12
- Experience in cutting and filleting fish
- Demonstrated ability in preparing of all fish related products
- Broad knowledge of fish
- Ability to communicate in English
- . No CSS classes, no inline styles, no , no
. It didn't forbid or tags. It said usefor introductory paragraphs and general text,
for section headers,
- for list items. It didn't say we cannot use other tags like or . However the instruction to preserve original content word-for-word suggests we should keep the and tags as they appear. But we also need to output only HTML; we can keep and as they are. However the earlier instruction: "Use
for introductory paragraphs and general text. Use
for section headers ... Use
- for list items. No CSS classes, no inline styles, no s, no
tags." It doesn't forbid other tags like , , . So we could keep them. But we also need to remove style attributes etc. The original had... etc. We should strip those attributes but keep the inner text. For and tags, they have no style attributes, so we can keep them. Thus we need to parse the original and produce HTML with minimal tags: we keep and where they appear, but we remove style attributes and empty spans. Let's extract the text content with tags: Original snippet:
It's fun to work in a company where people truly BELIEVE in what they're doing!
We should convert toIt's fun to work in a company where people truly BELIEVE in what they're doing!
(the HTML entity ' should be kept as apostrophe? It's part of original content; we should keep the entity? The instruction says preserve ALL original content word-for-word. That includes the entity '. So we should keep it as ' not convert to apostrophe. However typical HTML output would treat it as entity; but we need to output exactly the same characters. The original shows '. We should keep that. So we outputIt's fun to work in a company where people truly BELIEVE in what they're doing!
Similarly for other text. Next blank paragraphs: we can ignore. Then "Responsible for production of Sushi within the department ." There's a non-breaking space after department? It shows a special space. We'll keep as is: "Responsible for production of Sushi within the department ." (including the space before period?). We'll keep exactly. Then we haveCompetencies:
. This is a paragraph containing bold text "Competencies:" with a space after colon inside the span? Actually Competencies: includes a space after the closing span but inside the b. So the text is "Competencies: " (with trailing space). We need to preserve that. So we outputCompetencies:
but we need to strip style attributes (none). However we also need to wrap the following competency lines in- . The competency lines are each in
...
. They have nested spans. We should keep the inner text but strip spans. So each line becomes - Ingredient knowledge & recipe specifications etc. Note the ampersand is encoded as &. We should keep that. Thus we will output:
- Ingredient knowledge & recipe specifications
- Food Safety compliance & training
- Good knowledge of different sushi recipes
- Business Minded
- Customer Orientation
- Express and implied ethical responsibilities.
- Relevant systems knowledge
- Sushi Onboarding programme
- Understanding of production cards and production plan
- Understanding of relevant SOP
- ? The original lines have a space after the text before closing span? Eg: Good knowledge of different sushi recipes There's a non-breaking space after recipes and then another span with a space. So the text includes a space after recipes and then another space. We should keep them as part of the text. So the li content should be "Good knowledge of different sushi recipes " (including the spaces). Hard to represent but we can keep as is: "Good knowledge of different sushi recipes " (maybe two spaces). We'll just copy the inner text exactly as appears between the outer
tags after stripping spans. Let's extract: The original line:
Good knowledge of different sushi recipes
. The inner text is "Good knowledge of different sushi recipes " followed by a non-breaking space (the second span). So combined: "Good knowledge of different sushi recipes " (with a space after). We'll keep that. Similarly for Business Minded and Customer Orientation lines have trailing spaces. We'll keep them. Next:Minimum Requirements:
then list items each intags. We'll output:
Minimum Requirements:
- Grade 12
- Experience in cutting and filleting fish
- Demonstrated ability in preparing of all fish related products
- Broad knowledge of fish
- Ability to communicate in English
Key Responsibilities:
Then
This line includes a
Production
then Production. The
is a line break; we are not allowed to use
tags per rule: "No CSS classes, no inline styles, nos, no
tags". So we must remove the
tag. But we must preserve original content word-for-word. Conflict: we cannot keep
because rule forbids
. However the rule says "No CSS classes, no inline styles, nos, no
tags". So we must omit
. But then we are not preserving original content word-for-word. Which rule takes precedence? The instruction says: "Your ONLY job is to format it as clean semantic HTML." Then rules: Usefor intro paragraphs and general text, Use
for section headers, Use
- 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. This is contradictory if original contains
. However maybe the original
is just an artifact from conversion and we can drop it because it's not meaningful content. The rule says preserve ALL original content word-for-word, but also says no
tags. Likely they expect us to remove the
as it's just formatting. We'll follow the higher-level rule: no
tags. So we will omit the
. We'll keep the Production text. Thus we will output:Production
Then the list items under Production: each intags. We need to decide whether to wrap them in
- . The rule says use
- for list items (duties, requirements, qualifications, skills). These are duties under Production. So we should wrap them in a list. However there are subheadings like Sales/ Turnover/ Gross Margin etc. We could treat each subheading as a separate list group? Or we could make a single list with all items, but that would lose subheadings. Better to keep subheadings as
...
and then each group's items as- . That seems reasonable.
Thus after
Production
we output a- with the three production duties.
Then
Sales/ Turnover/ Gross Margin
then a- with its one duty.
Then
Administration
then- with its two duties.
Then
Food Safety
then- with its four duties.
Then
Self – Management
then- with its four duties.
Note there is a space before and after the dash? Original: "Self – Management" includes an en dash? We'll keep as is.
Then after that we have
Closing Date 25 September 2026
. This is not a list; we can keep asClosing Date 25 September
- . That seems reasonable.
Thus after
- for list items (duties, requirements, qualifications, skills). These are duties under Production. So we should wrap them in a list. However there are subheadings like Sales/ Turnover/ Gross Margin etc. We could treat each subheading as a separate list group? Or we could make a single list with all items, but that would lose subheadings. Better to keep subheadings as
- . The rule says use
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 📝
Competencies:
- . The competency lines are each in
- for list items. No CSS classes, no inline styles, no
- for list items. It didn't say we cannot use other tags like or . However the instruction to preserve original content word-for-word suggests we should keep the and tags as they appear. But we also need to output only HTML; we can keep and as they are. However the earlier instruction: "Use
header "Competencies". However 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 list Competencies explicitly, but we can still use
for any section header? The rule: Use
for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). It says e.g., implying those are examples; we can still use
for other section headers like Competencies, Minimum Requirements, Key Responsibilities, Closing Date, etc. Probably yes. Thus we will produce:
It's fun to work in a company where people truly BELIEVE in what they're doing!
Responsible for production of Sushi within the department.
Competencies
Minimum Requirements
Key Responsibilities
We need to structure responsibilities: There's a heading Key Responsibilities: then subheadings Production, Sales/Turnover/Gross Margin, Administration, Food Safety, Self – Management. Each subheading has list items. We could treat each subheading as a? But rule only allows
for section headers. We could keep subheadings as
...? but we cannot add because we must preserve original content word-for-word. The original content includes Production etc. We must preserve that exactly. So we need to keep the bold tags? The instruction says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. That includes the tags? The original content includes HTML tags with . However earlier we were told to output clean semantic HTML, using only
,
,
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.