Job Description
for section headers. Maybe Responsibilities is a section header; sub-sections Customer Service etc could be too? They are subsections under Responsibilities. The instruction: Use for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). So Responsibilities should be h4. Sub-sections like Customer Service, Solutions Analysis, etc are also headers but maybe h4 or h5? The examples include Key Duties. Could be h4 for top-level and h5 for sub-headers. But rule says no CSS classes etc. Need preserve all content. We can use h4 for Responsibilities, Skills, Competencies, Education, Closing Date. For sub-headers Customer Service etc, maybe h5. But the prompt says "Use for section headers" and lists e.g. Responsibilities... It doesn't forbid h5. To be safe, use h4 for main sections and h5 for sub-section headers. But maybe they expect only h4. Let's inspect.
Original:
for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). So Responsibilities should be h4. Sub-sections like Customer Service, Solutions Analysis, etc are also headers but maybe h4 or h5? The examples include Key Duties. Could be h4 for top-level and h5 for sub-headers. But rule says no CSS classes etc. Need preserve all content. We can use h4 for Responsibilities, Skills, Competencies, Education, Closing Date. For sub-headers Customer Service etc, maybe h5. But the prompt says "Use for section headers" and lists e.g. Responsibilities... It doesn't forbid h5. To be safe, use h4 for main sections and h5 for sub-section headers. But maybe they expect only h4. Let's inspect.
Original:
Let's Write Africa's Story Together!
intro paragraph about Old Mutual.Job Description
Then paragraph "Provides advice..." This is job description summary.Responsibilities
Customer Service
...Network of Influence
thenna? weird "na" maybe artifact.
Skills
list items: Ability to Sell..., Communication, etc.Competencies
Balances Stakeholders, Builds Networks, etc. empty.Education
National Certification (Nat Cert) (Required)Closing Date
04 November 2026 , 23:59 The appointment will be made... The Old Mutual Story! Need clean HTML. Remove all style attributes, spans emphasis-2, b tags? Preserve original content word-for-word. The bold/italic formatting can be removed? "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase." But formatting tags like , , are not content? They are markup. We need clean semantic HTML. We can drop inline styles and non-semantic tags, but keep text. For emphasis, maybe no need to preserve unless it affects text? The instruction says return ONLY cleaned job text, no markdown fences. It says preserve all original content word-for-word. I think we should keep text exactly, but can omit formatting tags. However if we omit , text remains same words. That's okay. But maybe they want no inline styles, no classes. We can output plain text with paragraphs. Need structure. Let's decide final HTML. Title? The first line "Let's Write Africa's Story Together!" might be a tagline, not necessarily job title. There is no explicit job title. Could be missing. We shouldn't invent. But maybe job title is absent. We can include intro paragraph. The "Job Description" heading then summary paragraph. Then Responsibilities section. Need handle "na" after Network of Influence. It appears as text "na". Is that artifact? It might be stray number/formatting artifact. The instructions say remove stray numbers or formatting artifacts. "na" likely artifact. Should we remove? It is not part of job content? It seems stray. Remove. Also empty and . Remove. Skills list: "Ability to Sell (Inactive), Communication, Company Policies, Credit Policies, Customer Centric Selling, Digital Savvy (Inactive), Interpersonal Relationship Management, Numeracy, Sales" These are list items separated by commas. Need wrap in- . Could split each comma item into separate li. Or keep as one li? Semantic list items should each be an li. Since comma-separated, likely each is a skill. Use
- Ability to Sell (Inactive) ...
- Sales . Need preserve commas? If each li includes trailing comma? Better omit commas between li items because list items shouldn't have commas. But "preserve all original content word-for-word" - commas are part of text. However in a
- for list items. It expects each item. Commas are separators, not content. I think omit commas. But to preserve word-for-word, maybe include commas within each li except last? That would be odd. Let's see examples: "Use
- for list items (duties, requirements, qualifications, skills)" They don't mention commas. Usually scraped text has commas; we should split. Commas are not essential. I'll split into individual skills without commas. That is acceptable.
Competencies: each competency on its own line, no commas. Use
- Balances Stakeholders ...
- Manages Complexity . Note there are empty before competencies; remove. Education: "National Certification (Nat Cert) (Required)" Could be
- National Certification (Nat Cert) (Required) . Closing Date: "04 November 2026 , 23:59" Keep. Maybe
04 November 2026, 23:59
(remove extra space before comma? Original has space before comma. Preserve? "04 November 2026 , 23:59" has space before comma. Word-for-word includes space. But formatting artifact? It's a date. I'd keep as "04 November 2026, 23:59"? Hmm. The instruction says remove stray numbers or formatting artifacts. A space before comma is minor. To preserve word-for-word, keep "04 November 2026 , 23:59". But in HTML, spaces matter. I can keep exact. Maybe normalize to "04 November 2026, 23:59" because comma spacing is typographic. But "preserve all original content word-for-word" suggests exact. I'll keep exact: "04 November 2026 , 23:59". Actually that looks bad but okay. Appointment statement: "The appointment will be made from the designated group in line with the Employment Equity Plan of Old Mutual South Africa and the specific business unit in question." Keep as. Old Mutual Story! maybe tagline, not job info. Could remove? It is not job information. The instructions: REMOVE category labels, stray numbers, etc. "The Old Mutual Story!" is a tagline, maybe promotional. But it's part of page. Should we keep? It's not job info. The editor task says extract ONLY actual job information. Taglines not job info. Remove. But "preserve all original content" conflicts. The first rule says remove social sharing, author bylines, related posts, navigation, comments, ads, cookie notices, duplicate text, category labels not part of job. "The Old Mutual Story!" is a brand tagline, not job info. Likely remove. But maybe it's part of job description? It appears at end. I think remove. Intro paragraph: "Old Mutual is a firm believer in the African opportunity and our diverse talent reflects this." This is company context, not job info? It could be part of job description. It mentions company. Keep? It's not job-specific but company background. The editor says extract actual job information. This is general company statement. Could keep as intro. It doesn't harm. But maybe remove? The prompt says "REMOVE all of following: ... Category labels..." Not explicitly. It says extract ONLY actual job information. A general company mission statement isn't job info. But it's relevant context. I'd keep it as introductory paragraph. It doesn't contain job details. The user wants clean job listing; including company intro is okay. But "actual job information" maybe exclude. Hmm. Let's read prompt carefully: "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 list removals. Then "KEEP and STRUCTURE: Job title, Company/Organisation name, Location, Job description and responsibilities, Requirements/qualifications, How to apply / application instructions, Salary, Deadline / closing date, Job ID / reference number, Contract type / level." So we should keep job description, responsibilities, skills, competencies, education, closing date, appointment statement. Company name is Old Mutual. Intro paragraph maybe not needed but harmless. I think keep intro paragraph as it introduces company. It doesn't violate. But "ONLY actual job information" might mean remove non-job stuff. However the intro is part of job listing. I'll keep. Job title: none explicit. Could maybe infer from "Let's Write Africa's Story Together!"? No. We cannot add. Maybe leave out. But KEEP job title if mentioned. Not mentioned. So no title. Could include "Job Description" heading? That's a section. Fine. Location: not mentioned. No location. Salary: not mentioned. Deadline: Closing Date. Contract type/level: not mentioned. Job ID: not mentioned. How to apply: not mentioned. Only appointment statement. Need produce HTML only. No markdown fences. No explanation. Just HTML. Let's craft final HTML. Potential structure:
Let's Write Africa's Story Together!
Old Mutual is a firm believer in the African opportunity and our diverse talent reflects this.
Job Description
Provides advice on a specific range of products to a specific allocated market and are individually accountable for achieving results through their own efforts.
Responsibilities
Customer Service
Carry out standard customer service activities and handle simple customer inquiries.
... etc. But wait: The original hasResponsibilities
andCustomer Service
. If using h4 for Responsibilities, sub-headers maybe h5. Good. Should "Job Description" be h4? Yes. For Skills, Competencies, Education, Closing Date, use h4. Sub-headers under Responsibilities: Customer Service, Solutions Analysis, Receiving Visitors, CRM Data, Customer Needs Clarification, Customer Relationship Development / Prospecting, Operational Compliance, Business Development, Sales Opportunities Creation, Data Exploration, Network of Influence. These are 11 subsections. Use h5. Need ensure no empty or . Remove. The "na" after Network of Influence: remove. Skills list: "Ability to Sell (Inactive), Communication, Company Policies, Credit Policies, Customer Centric Selling, Digital Savvy (Inactive), Interpersonal Relationship Management, Numeracy, Sales" Split into li. Maybe "Digital Savvy (Inactive)" etc. Good. Competencies: "Balances Stakeholders", "Builds Networks", "Communicates Effectively", "Customer Focus", "Ensures Accountability", "Instills Trust", "Interpersonal Savvy", "Manages Complexity". Use ul. Education: "National Certification (Nat Cert) (Required)" -> li. Closing Date: "04 November 2026 , 23:59" -> p. Appointment statement -> p. Old Mutual Story! -> remove. Check if any "You may also like" etc none. Need final answer exactly HTML. No markdown fences. But the system says "Return ONLY the HTML. No markdown fences, no explanation, no preamble." So final should be just code block? Wait, "No markdown fences" means don't use ```html? It says no markdown fences. But if we output raw HTML without backticks, that's fine. However in these tasks, they often expect code block? The instruction says no markdown fences. So output plain HTML text. But if no fences, it may render as HTML? In chat, raw HTML might be displayed as text. That's okay. We should not include ```. Just start with. But maybe to ensure formatting, no fences. The user explicitly says no markdown fences. So final answer begins with
Let's Write... Need be careful with apostrophe: "Let's" originally encoded. We should output "Let's" not entity. Word-for-word original content includes "Let's" (decoded). Use straight apostrophe. Good. Also "Old Mutual is a firm believer..." no issues. Let's consider if "Job Description" heading should be kept as
Job Description
and then the summary paragraph. Yes. Potential issue: The first line "Let's Write Africa's Story Together!" might be a title. Could put in? But it's not a section header. The rules say use
for introductory paragraphs. So
. Good. Potential issue: "Provides advice..." is a sentence fragment? It says "Provides advice on a specific range of products to a specific allocated market and are individually accountable..." Grammar odd but preserve. Potential issue: "Customer Relationship Development / Prospecting" includes slash. Keep. Potential issue: "Network of Influence" followed by blank then "na". Remove. Potential issue: "Competencies" has empty
before. Remove. Potential issue: "Education" has "National Certification (Nat Cert) (Required)" with double space. Keep one? Word-for-word has double space. But formatting artifact? It's not stray number. I'd keep as "National Certification (Nat Cert) (Required)" maybe collapse double space? The instruction says preserve word-for-word. Double space is whitespace. I can keep double space inside li. But HTML collapses multiple spaces? Actually browsers collapse multiple whitespace in rendering, but source preserves. To preserve, include two spaces. But it's ugly. The instruction says remove stray numbers or formatting artifacts; double space maybe artifact. I'd keep single space. Hmm. Maybe better to preserve exact text including double space. But in HTML, multiple spaces are often collapsed. The requirement "preserve all original content word-for-word" means text content, not whitespace formatting. I think single space is fine. But to be safe, include double space? Let's decide: "National Certification (Nat Cert) (Required)" with two spaces. It's not a stray number. I'll keep two spaces. Actually in final HTML, if I write two spaces, it's preserved in source. Good. Similarly closing date "04 November 2026 , 23:59" has space before comma. Keep exact. Now, should we include "Company/Organisation name" as a heading? Not necessary. But maybe addCompany: Old Mutual
? The original doesn't have a company heading. The intro mentions Old Mutual. We can infer. But adding extra info not in original violates "do not add". The KEEP list includes Company name, but if not explicitly labeled, we can just rely on intro. I won't add a separate company line. Location: not present. Don't add. Salary: not present. Don't add. Contract type: not present. Don't add. How to apply: not present. Don't add. Job ID: not present. Don't add. Thus final HTML. Let's draft:Let's Write Africa's Story Together!
Old Mutual is a firm believer in the African opportunity and our diverse talent reflects this.
Job Description
Provides advice on a specific range of products to a specific allocated market and are individually accountable for achieving results through their own efforts.
Responsibilities
Customer Service
Carry out standard customer service activities and handle simple customer inquiries.
Solutions Analysis
Assess compliance with established standards and protocols for routine inquiries.
<
- for list items (duties, requirements, qualifications, skills)" They don't mention commas. Usually scraped text has commas; we should split. Commas are not essential. I'll split into individual skills without commas. That is acceptable.
Competencies: each competency on its own line, no commas. Use
- , commas between items are not standard. We can include commas inside each li? That would duplicate commas. Maybe keep one li with all items separated by commas? That violates list semantics. The instruction says use
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 📝