Insurance Representative

We need to output HTML fragment with sections only if real content. The posting includes overview, job description, disclaimer. No explicit sections like About the role, Responsibilities, Requirements, etc. We need to map content to appropriate headings if they exist. The posting does not have explicit headings like "About the role", "Responsibilities", etc. It has overview paragraphs and job description paragraphs. We could treat "About the role" as maybe the overview? But we must not invent sections; only include a section when posting has real, specific content for it. The posting does not have explicit headings; we could still create sections based on content? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use those headings if the posting contains that content. If not, we should not create them. So we need to see if the posting contains content that matches those sections. It has overview about company and role, maybe "About the role" could be covered. But we must not invent heading if not explicitly present. However, the instruction says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we must only use those exact headings; it's examples. We could create a heading like "Overview" if appropriate. But they gave examples; maybe we should stick to those. The posting does not have explicit "About the role" heading, but we could infer that the overview is about the role. However, the rule: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So if we create an "About the role" section, we need to put content there. The posting does have content describing the role: "Becoming an independent insurance agent with HealthMarkets is an opportunity unlike any other..." etc. That seems specific. So we could create an

About the role

and put that content. Similarly, there is a job description section: "Never worked in the health insurance industry before? It’s no problem..." That could be "Responsibilities" or maybe "Job Description". Could map to "Responsibilities". The content includes entrepreneurial spirit, drive, start own business, schedule flexibility, support, training, resources. That's more about what the role entails, maybe responsibilities. We also have a disclaimer about independent contractor status, commission only, licensing, etc. That could be "Qualifications" or "Requirements"? Not exactly. Could be "Requirements" (licensing). But the disclaimer includes licensing info, commission only, etc. Could be "Qualifications". However, we need to avoid filler. The disclaimer is specific content. We should not include sections like Benefits, Pay, Schedule unless explicitly stated. The posting mentions "achieve financial success on their own time and schedule", "you work for yourself", "schedule". That's schedule info. It says "you work for yourself" and "you’ve got the time because you work for yourself". That's schedule flexibility. Could we create a Schedule section? It mentions schedule but not specific hours. It's more about flexibility. Might be considered schedule content. The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state schedule flexibility: "achieve financial success on their own time and schedule." So we could include a Schedule section with that content. Pay: It mentions commission only opportunity, financial success. Not specific pay numbers. It says "commission only opportunity". That's pay structure. Could we create Pay section? It mentions compensation type. The rule: never create Pay section unless posting actually states them. It does state commission only. So we could include Pay section with that detail. Benefits: Not mentioned besides resources, support, training. Not explicit benefits like health insurance, retirement. So we should not create Benefits. We need to preserve all substantive information, not invent or summarize away detail. So we need to include all paragraphs. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. The posting includes a disclaimer that is legal but seems substantive (licensing, commission only). It's not boilerplate? It's a disclaimer about independent contractor status. Might be considered legal but it's substantive to the role. We should keep it. Also there are numbers like "48640-HM-0523" and "51934-HM-0326" which are likely job IDs/requisition numbers. According to rule: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can drop those numbers or include them in a short p. Probably drop them. We need to output only HTML fragment, no /, no markdown fences. Thus structure:

About the role

... overview paragraphs ...

Responsibilities

... job description paragraphs ...

Qualifications

... disclaimer about licensing, independent contractor, commission only ...

Schedule

... schedule flexibility content ...

Pay

... commission only opportunity ...

maybe multiple sentences. Responsibilities: job description block excluding schedule sentences? But schedule sentences are part of job description. However we moved schedule to its own section. We could keep schedule sentences in Responsibilities as well, but that would duplicate. Better to split