Interventional Cardiologist – Community Practice
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use - for lists,
for prose.
- Do NOT repeat job title as heading.
- Do NOT put Job ID/requisition numbers as headings.
- Preserve ALL substantive information.
- Remove boilerplate (EEO, equal opportunity, scam warnings, application instructions, etc.)
- Include section ONLY when real specific content exists.
- Never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD")
- Never create Pay/Schedule/Benefits sections unless posting actually states them.
- Prefer few substantive sections over many thin ones.
- Output ONLY HTML fragment, no /, no markdown code fences.
Now, let's map sections:
- "Opportunity Details" -> could be "About the role" or "Responsibilities"? It describes the practice, team, call, volume, equipment. It's more about the role. I'll use "About the role" as heading.
- "About Capital Region Medical Center" -> "About the organization" or similar. But the allowed headings are specific: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The user gave examples: "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". So I should stick to those headings. However, "About Capital Region Medical Center" is about the employer. Could be "About the organization" but not in the list. The list is examples, not exhaustive? The instruction says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It says e.g., so maybe we can use other relevant headings? But to be safe, I'll map to the closest. "About the organization" might be okay, but the instruction says "use for section headings (e.g. ...)". It doesn't forbid other headings, but the examples are typical job posting sections. I think we can use "About the organization" as a heading. However, the rule: "include a section ONLY when the posting has real, specific content for it". The posting has specific content about CRMC. So I'll include a section with heading "About the organization" or "About Capital Region Medical Center". But the instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It might be expecting those exact headings. But the posting doesn't have a "Responsibilities" section per se; the "Opportunity Details" includes responsibilities implicitly. There's no explicit "Responsibilities" list. There's "Minimum Qualifications" and "Preferred Qualifications". That maps to "Requirements" and "Qualifications". There's "Benefits" described. There's "Schedule" described. There's "Pay" described but with "Salary commensurate with experience" which is placeholder? Actually, the posting says "Compensation Package includes guaranteed base salary with quality and production incentives – Outstanding earning potential balanced with great work life balance." That's specific. Also "Anticipated Hiring Range Salary Range: Salary commensurate with experience." That's a bit generic but there is detail about compensation package. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state benefits, schedule, and pay (though pay is somewhat generic). But "Salary commensurate with experience" is considered filler/placeholder? The rule says "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". So if the Pay section only says "Salary commensurate with experience", that's filler. However, there is more detail earlier: "Compensation Package includes guaranteed base salary with quality and production incentives – Outstanding earning potential balanced with great work life balance." That's substantive. So I can include a Pay section with that detail.
Similarly, Benefits: there are specific benefits listed: 8% retirement match, health/dental/vision, family tuition benefits, irrevocable trust planning, and later comprehensive benefits package. So Benefits section is warranted.
Schedule: "Monday – Friday 8:00 a.m. – 5:00 p.m." That's specific.
Qualifications: Minimum and Preferred qualifications are specific.
Now, "About Capital Region Medical Center" and "About Jefferson City" are about the employer and location. The allowed headings don't include "About the organization" or "Location". But the instruction says "e.g." meaning examples. I think it's okay to include them as sections with appropriate headings. However, the user might expect only the example headings. To be safe, I'll include them under "About the organization" and "Location" or "About the area". But the instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say we cannot use others. I'll use "About the organization" and "Location" as headings.
But the rule: "Prefer a few substantive sections over many thin ones." So maybe combine "About Capital Region Medical Center" and "About Jefferson City" into one section? They are distinct. I'll keep separate.
Now, remove boilerplate: EEO, ADA accommodations, application instructions (Online Application, Resume/CV), sponsorship information (maybe keep as it's specific), benefit eligibility (already covered). The "Application Materials" and "Sponsorship Information" and "Benefit Eligibility" and "Equal Employment Opportunity" are boilerplate? The instruction says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So remove EEO, ADA, application instructions. Sponsorship information might be considered part of application instructions? It says "Employment visa sponsorship may be available..." That's specific to the job, maybe keep. But it's somewhat boilerplate. I'll include it under a "Sponsorship" section? Not in example headings. Could fold into a short
in Qualifications or separate. I'll include as a short paragraph under "Qualifications" or separate "Sponsorship" heading? The instruction says "fold minor metadata into a short
or drop it." Sponsorship info is minor metadata. I'll fold into a paragraph at the end of Qualifications or a separate small section. But to avoid thin sections, I'll include as a paragraph in Qualifications.
Similarly, "University Title: PHYSICIAN" and "Internal applicants..." is metadata, drop.
"Anticipated Hiring Range Salary Range: Salary commensurate with experience." That's filler for Pay, but we have other pay details.
Now, structure:
1. About the role (from Opportunity Details)
2. Responsibilities? Not explicitly listed. The Opportunity Details includes duties? It describes the practice, call, volume, equipment. Could be considered responsibilities. But the heading "Responsibilities" is in examples. I'll create a "Responsibilities" section if there are specific duties. The posting doesn't list specific duties like "Perform PCI procedures" etc. It says "Expected volume of 80-100 PCI per year". That's more about volume. I'll not create a Responsibilities section if no explicit list. Instead, include in About the role.
3. Requirements (Minimum Qualifications)
4. Qualifications (Preferred Qualifications)
5. Benefits
6. Pay
7. Schedule
8. About the organization (Capital Region Medical Center)
9. Location (Jefferson City)
But the instruction says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So they expect those headings. I'll use those exact headings where applicable. For "About the organization" and "Location", they are not in the list. But the posting has them. I think it's okay to include them with appropriate headings. However, the instruction might be strict: only use those headings. But the e.g. suggests they are examples. I'll include them as "About the organization" and "Location".
Now, let's write HTML.
First, "About the role": include the prose from "Opportunity Details" and "Join our growing cardiology team..." The first paragraph: "Join our growing cardiology team as an interventional cardiologist in our busy community-based health system. Pending retirements will enable you to build a busy practice quickly. They take pride in the collegial, team-based culture that exists and earn top compensation at Capital Regional Medical Center in Jefferson City, Missouri." Then the bullet points from Opportunity Details.
I'll create a
for the intro, then
- for the bullet points.
The bullet points:
- Join 5 Interventional Cardiologist, 4 General Cardiologist and 1 Electrophysiologist
- Excellent Lifestyle with collegial group of cardiologists who work as a team
- General Cardiology call of 1:8
- Practice at both Jefferson City hospital locations – Capital Region Medical Center and SSM Health’s St. Mary’s Hospital
- Both hospitals are Level II STEMI facilities
- Expected volume of 80 -100 PCI per year
- State of the art equipment in 2 year old Cath labs including IVUS, Shockwave Lithotripsy, Drug Coated Balloons, Rotablation, and Impella
- Compensation Package includes guaranteed base salary with quality and production incentives – Outstanding earning potential balanced with great work life balance.
- Outstanding University of Missouri benefits, including: (then sub-bullets: 8% retirement match, Health, dental, and vision insurance, Family tuition benefits, Unique options such as irrevocable trust planning)
But benefits are also listed later. I'll include benefits in Benefits section. So in About the role, I'll mention compensation package but not list benefits again.
Better to separate: In About the role, include the practice details. Compensation package mention can go to Pay section. Benefits to Benefits section.
So for About the role, I'll include:
- Join 5 Interventional Cardiologists, 4 General Cardiologists and 1 Electrophysiologist
- Excellent lifestyle with collegial group of cardiologists who work as a team
- General Cardiology call of 1:8
- Practice at both Jefferson City hospital locations – Capital Region Medical Center and SSM Health’s St. Mary’s Hospital
- Both hospitals are Level II STEMI facilities
- Expected volume of 80-100 PCI per year
- State-of-the-art equipment in 2-year-old cath labs including IVUS, Shockwave Lithotripsy, Drug-Coated Balloons, Rotablation
for prose. - Do NOT repeat job title as heading. - Do NOT put Job ID/requisition numbers as headings. - Preserve ALL substantive information. - Remove boilerplate (EEO, equal opportunity, scam warnings, application instructions, etc.) - Include section ONLY when real specific content exists. - Never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") - Never create Pay/Schedule/Benefits sections unless posting actually states them. - Prefer few substantive sections over many thin ones. - Output ONLY HTML fragment, no /, no markdown code fences. Now, let's map sections: - "Opportunity Details" -> could be "About the role" or "Responsibilities"? It describes the practice, team, call, volume, equipment. It's more about the role. I'll use "About the role" as heading. - "About Capital Region Medical Center" -> "About the organization" or similar. But the allowed headings are specific: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The user gave examples: "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". So I should stick to those headings. However, "About Capital Region Medical Center" is about the employer. Could be "About the organization" but not in the list. The list is examples, not exhaustive? The instruction says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It says e.g., so maybe we can use other relevant headings? But to be safe, I'll map to the closest. "About the organization" might be okay, but the instruction says "use for section headings (e.g. ...)". It doesn't forbid other headings, but the examples are typical job posting sections. I think we can use "About the organization" as a heading. However, the rule: "include a section ONLY when the posting has real, specific content for it". The posting has specific content about CRMC. So I'll include a section with heading "About the organization" or "About Capital Region Medical Center". But the instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It might be expecting those exact headings. But the posting doesn't have a "Responsibilities" section per se; the "Opportunity Details" includes responsibilities implicitly. There's no explicit "Responsibilities" list. There's "Minimum Qualifications" and "Preferred Qualifications". That maps to "Requirements" and "Qualifications". There's "Benefits" described. There's "Schedule" described. There's "Pay" described but with "Salary commensurate with experience" which is placeholder? Actually, the posting says "Compensation Package includes guaranteed base salary with quality and production incentives – Outstanding earning potential balanced with great work life balance." That's specific. Also "Anticipated Hiring Range Salary Range: Salary commensurate with experience." That's a bit generic but there is detail about compensation package. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state benefits, schedule, and pay (though pay is somewhat generic). But "Salary commensurate with experience" is considered filler/placeholder? The rule says "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". So if the Pay section only says "Salary commensurate with experience", that's filler. However, there is more detail earlier: "Compensation Package includes guaranteed base salary with quality and production incentives – Outstanding earning potential balanced with great work life balance." That's substantive. So I can include a Pay section with that detail.
Similarly, Benefits: there are specific benefits listed: 8% retirement match, health/dental/vision, family tuition benefits, irrevocable trust planning, and later comprehensive benefits package. So Benefits section is warranted.
Schedule: "Monday – Friday 8:00 a.m. – 5:00 p.m." That's specific.
Qualifications: Minimum and Preferred qualifications are specific.
Now, "About Capital Region Medical Center" and "About Jefferson City" are about the employer and location. The allowed headings don't include "About the organization" or "Location". But the instruction says "e.g." meaning examples. I think it's okay to include them as sections with appropriate headings. However, the user might expect only the example headings. To be safe, I'll include them under "About the organization" and "Location" or "About the area". But the instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say we cannot use others. I'll use "About the organization" and "Location" as headings.
But the rule: "Prefer a few substantive sections over many thin ones." So maybe combine "About Capital Region Medical Center" and "About Jefferson City" into one section? They are distinct. I'll keep separate.
Now, remove boilerplate: EEO, ADA accommodations, application instructions (Online Application, Resume/CV), sponsorship information (maybe keep as it's specific), benefit eligibility (already covered). The "Application Materials" and "Sponsorship Information" and "Benefit Eligibility" and "Equal Employment Opportunity" are boilerplate? The instruction says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So remove EEO, ADA, application instructions. Sponsorship information might be considered part of application instructions? It says "Employment visa sponsorship may be available..." That's specific to the job, maybe keep. But it's somewhat boilerplate. I'll include it under a "Sponsorship" section? Not in example headings. Could fold into a short
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It might be expecting those exact headings. But the posting doesn't have a "Responsibilities" section per se; the "Opportunity Details" includes responsibilities implicitly. There's no explicit "Responsibilities" list. There's "Minimum Qualifications" and "Preferred Qualifications". That maps to "Requirements" and "Qualifications". There's "Benefits" described. There's "Schedule" described. There's "Pay" described but with "Salary commensurate with experience" which is placeholder? Actually, the posting says "Compensation Package includes guaranteed base salary with quality and production incentives – Outstanding earning potential balanced with great work life balance." That's specific. Also "Anticipated Hiring Range Salary Range: Salary commensurate with experience." That's a bit generic but there is detail about compensation package. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state benefits, schedule, and pay (though pay is somewhat generic). But "Salary commensurate with experience" is considered filler/placeholder? The rule says "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". So if the Pay section only says "Salary commensurate with experience", that's filler. However, there is more detail earlier: "Compensation Package includes guaranteed base salary with quality and production incentives – Outstanding earning potential balanced with great work life balance." That's substantive. So I can include a Pay section with that detail.
Similarly, Benefits: there are specific benefits listed: 8% retirement match, health/dental/vision, family tuition benefits, irrevocable trust planning, and later comprehensive benefits package. So Benefits section is warranted.
Schedule: "Monday – Friday 8:00 a.m. – 5:00 p.m." That's specific.
Qualifications: Minimum and Preferred qualifications are specific.
Now, "About Capital Region Medical Center" and "About Jefferson City" are about the employer and location. The allowed headings don't include "About the organization" or "Location". But the instruction says "e.g." meaning examples. I think it's okay to include them as sections with appropriate headings. However, the user might expect only the example headings. To be safe, I'll include them under "About the organization" and "Location" or "About the area". But the instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say we cannot use others. I'll use "About the organization" and "Location" as headings.
But the rule: "Prefer a few substantive sections over many thin ones." So maybe combine "About Capital Region Medical Center" and "About Jefferson City" into one section? They are distinct. I'll keep separate.
Now, remove boilerplate: EEO, ADA accommodations, application instructions (Online Application, Resume/CV), sponsorship information (maybe keep as it's specific), benefit eligibility (already covered). The "Application Materials" and "Sponsorship Information" and "Benefit Eligibility" and "Equal Employment Opportunity" are boilerplate? The instruction says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So remove EEO, ADA, application instructions. Sponsorship information might be considered part of application instructions? It says "Employment visa sponsorship may be available..." That's specific to the job, maybe keep. But it's somewhat boilerplate. I'll include it under a "Sponsorship" section? Not in example headings. Could fold into a short
in Qualifications or separate. I'll include as a short paragraph under "Qualifications" or separate "Sponsorship" heading? The instruction says "fold minor metadata into a short
or drop it." Sponsorship info is minor metadata. I'll fold into a paragraph at the end of Qualifications or a separate small section. But to avoid thin sections, I'll include as a paragraph in Qualifications. Similarly, "University Title: PHYSICIAN" and "Internal applicants..." is metadata, drop. "Anticipated Hiring Range Salary Range: Salary commensurate with experience." That's filler for Pay, but we have other pay details. Now, structure: 1. About the role (from Opportunity Details) 2. Responsibilities? Not explicitly listed. The Opportunity Details includes duties? It describes the practice, call, volume, equipment. Could be considered responsibilities. But the heading "Responsibilities" is in examples. I'll create a "Responsibilities" section if there are specific duties. The posting doesn't list specific duties like "Perform PCI procedures" etc. It says "Expected volume of 80-100 PCI per year". That's more about volume. I'll not create a Responsibilities section if no explicit list. Instead, include in About the role. 3. Requirements (Minimum Qualifications) 4. Qualifications (Preferred Qualifications) 5. Benefits 6. Pay 7. Schedule 8. About the organization (Capital Region Medical Center) 9. Location (Jefferson City) But the instruction says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So they expect those headings. I'll use those exact headings where applicable. For "About the organization" and "Location", they are not in the list. But the posting has them. I think it's okay to include them with appropriate headings. However, the instruction might be strict: only use those headings. But the e.g. suggests they are examples. I'll include them as "About the organization" and "Location". Now, let's write HTML. First, "About the role": include the prose from "Opportunity Details" and "Join our growing cardiology team..." The first paragraph: "Join our growing cardiology team as an interventional cardiologist in our busy community-based health system. Pending retirements will enable you to build a busy practice quickly. They take pride in the collegial, team-based culture that exists and earn top compensation at Capital Regional Medical Center in Jefferson City, Missouri." Then the bullet points from Opportunity Details. I'll create a
for the intro, then
- for the bullet points. The bullet points: - Join 5 Interventional Cardiologist, 4 General Cardiologist and 1 Electrophysiologist - Excellent Lifestyle with collegial group of cardiologists who work as a team - General Cardiology call of 1:8 - Practice at both Jefferson City hospital locations – Capital Region Medical Center and SSM Health’s St. Mary’s Hospital - Both hospitals are Level II STEMI facilities - Expected volume of 80 -100 PCI per year - State of the art equipment in 2 year old Cath labs including IVUS, Shockwave Lithotripsy, Drug Coated Balloons, Rotablation, and Impella - Compensation Package includes guaranteed base salary with quality and production incentives – Outstanding earning potential balanced with great work life balance. - Outstanding University of Missouri benefits, including: (then sub-bullets: 8% retirement match, Health, dental, and vision insurance, Family tuition benefits, Unique options such as irrevocable trust planning) But benefits are also listed later. I'll include benefits in Benefits section. So in About the role, I'll mention compensation package but not list benefits again. Better to separate: In About the role, include the practice details. Compensation package mention can go to Pay section. Benefits to Benefits section. So for About the role, I'll include: - Join 5 Interventional Cardiologists, 4 General Cardiologists and 1 Electrophysiologist - Excellent lifestyle with collegial group of cardiologists who work as a team - General Cardiology call of 1:8 - Practice at both Jefferson City hospital locations – Capital Region Medical Center and SSM Health’s St. Mary’s Hospital - Both hospitals are Level II STEMI facilities - Expected volume of 80-100 PCI per year - State-of-the-art equipment in 2-year-old cath labs including IVUS, Shockwave Lithotripsy, Drug-Coated Balloons, Rotablation