Glaucoma Surgeon | Coastal Virginia
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use - for lists
- Use
for prose
- Do NOT repeat job title as heading
- Do NOT put Job ID/requisition numbers as headings
- Preserve ALL substantive information
- Remove boilerplate (cookie/navigation/legal/EEO/scam-warning)
- Include section ONLY when real specific content exists
- Never emit heading followed by filler/placeholder text
- Never create Pay/Schedule/Benefits sections unless posting actually states them
- Output ONLY HTML fragment, no /, no markdown code fences
Looking at the content:
- There's no explicit "Responsibilities" or "Requirements" section, but there are details about the role: BC/BE, fellowship-trained Glaucoma Surgeon, immediate clinical/surgical glaucoma demand, expand glaucoma services, surgical mix including MIGS, traditional glaucoma procedures, cataract surgery, diverse pathology, complex cases.
- "Why Join Our Team?" is essentially benefits/reasons to join - list format
- "Compensation & Benefits" is explicit with list
- "Practice in Coastal Virginia" is location/lifestyle info
- Contact info at end - should I include? The rules say remove application instructions, but contact info might be considered part of the posting. However, "application instructions" likely includes how to apply. The contact info is "Let's Connect Rachel Tankersley..." - this is recruitment contact. I think I should include it as a brief paragraph or maybe a section? But the rules say "remove application instructions". This is contact info for the recruiter. I'll include it as a short paragraph at the end, maybe under a "Contact" heading? But the rules say only use headings from the list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Contact" is not in that list. So maybe just a paragraph without heading.
Let me structure:
1. About the role (or Company Overview) - combine the first two paragraphs about EyeCare Partners and the opportunity.
2. Why Join Our Team? - this is essentially Benefits/Reasons. Could be "Benefits" heading? But the heading list includes "Benefits". The posting has "Why Join Our Team?" which is a list of reasons. I'll use
Benefits
and list them.
3. Compensation & Benefits - this is Pay and Benefits combined. The heading list has "Pay" and "Benefits". But the posting has a section "Compensation & Benefits" with a list. I could split into Pay and Benefits, but the list includes both salary and benefits. The rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states "Compensation & Benefits". I could create a "Pay" section for salary items and "Benefits" for benefits items. But the list is mixed. Let's see: "Competitive base salary + production incentives" - pay; "Sign-on bonus and relocation assistance" - pay; "CME allowance" - benefit; "Comprehensive medical and dental benefits" - benefit; "STD/LTD and paid time off" - benefit; "Retirement benefits" - benefit; "Professional liability coverage" - benefit; "Long-term growth and partnership potential" - could be both. I think it's okay to have a "Compensation & Benefits" heading? But the allowed headings are specific: Pay, Benefits. The rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So I should use those exact headings. I'll create a "Pay" section for compensation items and a "Benefits" section for benefits items. However, the posting has a single section. I'll split them logically.
4. Practice in Coastal Virginia - this is location/lifestyle. Not in the heading list. Could be "About the role" or maybe "Schedule"? No. The rules say prefer a few substantive sections over many thin ones. I could include it as a paragraph under "About the role" or as a separate section with a heading not in the list? The rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, but likely they want only those headings. However, the posting has a distinct section about location. I could use "About the role" to encompass the role and location. Or maybe "Schedule" is not appropriate. I'll include it as a paragraph under "About the role" or as a separate section with a generic heading? The rules say "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid other headings, but the examples are given. I think it's safer to use only the suggested headings. I'll incorporate the location info into "About the role".
5. Contact info - I'll put as a paragraph at the end without heading.
Now, let's extract lists:
Why Join Our Team? list:
- Immediate clinical and surgical glaucoma volume
- Established patient base and strong regional referral network
- Broad surgical mix including MIGS, traditional glaucoma procedures, and cataract surgery
- Diverse glaucoma pathology and complex cases
- Collaborative team of ophthalmologists and subspecialists
- Advanced diagnostic and surgical technology
- Experienced clinical and surgical support teams
- Multi-location network throughout Coastal Virginia
- Opportunity to help grow and shape glaucoma services across the region
- Long-term leadership, professional growth, and partnership potential
Compensation & Benefits list:
- Competitive base salary + production incentives
- Sign-on bonus and relocation assistance
- CME allowance
- Comprehensive medical and dental benefits
- STD/LTD and paid time off
- Retirement benefits
- Professional liability coverage
- Long-term growth and partnership potential
Note: "Long-term growth and partnership potential" appears in both lists. I'll keep in both? The posting has it in both sections. I'll preserve as is.
Now, the role description: "BC/BE, fellowship-trained Glaucoma Surgeon", "immediate clinical and surgical glaucoma demand", "expand glaucoma services across a well-established regional network". Also "Build a thriving glaucoma practice while enjoying the lifestyle of Coastal Virginia." etc.
I'll create:
About the role
EyeCare Partners is the nation’s leading provider of clinically integrated eye care. Our national network of over 300 ophthalmologists and 700 optometrists provides a lifetime of care to our patients with a mission to enhance vision, advance eye care and improve lives. Based in St. Louis, Missouri, over 650 ECP-affiliated practice locations provide care in 18 states and 80 markets, providing services that span the eye care continuum. Tidewater Eye Center and Virginia Eye Consultants have joined together, creating an expanded ophthalmology network across Coastal Virginia and an exciting opportunity for continued growth.
As we expand specialty eye care throughout the Hampton Roads and Williamsburg regions, we are seeking a BC/BE, fellowship-trained Glaucoma Surgeon to join our growing team. This is an outstanding opportunity to step into immediate clinical and surgical glaucoma demand while helping expand glaucoma services across a well-established regional network.
Build a thriving glaucoma practice while enjoying the lifestyle of Coastal Virginia. The Hampton Roads region offers waterfront communities, beaches, history, dining, entertainment, and a variety of urban and suburban communities. Whether you're completing glaucoma fellowship or are an experienced surgeon considering your next opportunity, this is an exciting time to join Tidewater Eye Center and Virginia Eye Consultants as we continue expanding specialty eye care throughout the region.
Benefits
- Immediate clinical and surgical glaucoma volume
- Established patient base and strong regional referral network
- Broad surgical mix including MIGS, traditional glaucoma procedures, and cataract surgery
- Diverse glaucoma pathology and complex cases
- Collaborative team of ophthalmologists and subspecialists
- Advanced diagnostic and surgical technology
- Experienced clinical and surgical support teams
- Multi-location network throughout Coastal Virginia
- Opportunity to help grow and shape glaucoma services across the region
- Long-term leadership, professional growth, and partnership potential
Pay
- Competitive base salary + production incentives
- Sign-on bonus and relocation assistance
Benefits
(but we already used Benefits heading. Can't have two Benefits headings. The rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we can't repeat, but typically you'd have one Benefits section. However, the posting has two distinct sections: "Why Join Our Team?" and "Compensation & Benefits". The latter includes both pay and benefits. I could combine all benefits into one Benefits section, but the "Why Join Our Team?" are more like professional benefits/reasons to join, while "Compensation & Benefits" includes traditional benefits. The rules say "Benefits" heading. I think I should have one Benefits section that includes both? But the user said "Preserve ALL substantive information". I'll keep them separate but maybe use "Benefits" for the first list and "Pay" for compensation, and then for the traditional benefits, also under "Benefits"? That would be two Benefits sections. Not ideal.
Alternative: Use "Benefits" for the "Why Join Our Team?" list, and for the compensation section, split into "Pay" and "Benefits" but that would duplicate heading. Maybe I can rename the first to "Why Join Our Team" but the rules say use those specific headings. The examples include "Benefits". The posting's "Why Join Our Team?" is essentially benefits of joining. I'll use "Benefits" for that. Then for the "Compensation & Benefits" section, I'll put compensation items under "Pay" and the benefits items (CME, medical, dental, etc.) under "Benefits" as well? But that would be two Benefits sections. I could combine all benefits into one Benefits section, but they are distinct categories. The rules say "Prefer a few substantive sections over many thin ones." So maybe combine all benefits into one Benefits section. However, the "Why Join Our Team?" list is 10 items, and the compensation benefits are 6 items (excluding pay). I'll combine them into one Benefits section with two sub-lists? But the HTML structure is just - . I could have two separate
under the same heading. That's acceptable.
But the heading "Benefits" would appear once. I'll do:
Benefits
- Immediate clinical and surgical glaucoma volume
... (all 10 items)
- CME allowance
- Comprehensive medical and dental benefits
- STD/LTD and paid time off
- Retirement benefits
- Professional liability
for prose - Do NOT repeat job title as heading - Do NOT put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/scam-warning) - Include section ONLY when real specific content exists - Never emit heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits sections unless posting actually states them - Output ONLY HTML fragment, no /, no markdown code fences Looking at the content: - There's no explicit "Responsibilities" or "Requirements" section, but there are details about the role: BC/BE, fellowship-trained Glaucoma Surgeon, immediate clinical/surgical glaucoma demand, expand glaucoma services, surgical mix including MIGS, traditional glaucoma procedures, cataract surgery, diverse pathology, complex cases. - "Why Join Our Team?" is essentially benefits/reasons to join - list format - "Compensation & Benefits" is explicit with list - "Practice in Coastal Virginia" is location/lifestyle info - Contact info at end - should I include? The rules say remove application instructions, but contact info might be considered part of the posting. However, "application instructions" likely includes how to apply. The contact info is "Let's Connect Rachel Tankersley..." - this is recruitment contact. I think I should include it as a brief paragraph or maybe a section? But the rules say "remove application instructions". This is contact info for the recruiter. I'll include it as a short paragraph at the end, maybe under a "Contact" heading? But the rules say only use headings from the list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Contact" is not in that list. So maybe just a paragraph without heading. Let me structure: 1. About the role (or Company Overview) - combine the first two paragraphs about EyeCare Partners and the opportunity. 2. Why Join Our Team? - this is essentially Benefits/Reasons. Could be "Benefits" heading? But the heading list includes "Benefits". The posting has "Why Join Our Team?" which is a list of reasons. I'll use
Benefits
and list them. 3. Compensation & Benefits - this is Pay and Benefits combined. The heading list has "Pay" and "Benefits". But the posting has a section "Compensation & Benefits" with a list. I could split into Pay and Benefits, but the list includes both salary and benefits. The rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states "Compensation & Benefits". I could create a "Pay" section for salary items and "Benefits" for benefits items. But the list is mixed. Let's see: "Competitive base salary + production incentives" - pay; "Sign-on bonus and relocation assistance" - pay; "CME allowance" - benefit; "Comprehensive medical and dental benefits" - benefit; "STD/LTD and paid time off" - benefit; "Retirement benefits" - benefit; "Professional liability coverage" - benefit; "Long-term growth and partnership potential" - could be both. I think it's okay to have a "Compensation & Benefits" heading? But the allowed headings are specific: Pay, Benefits. The rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So I should use those exact headings. I'll create a "Pay" section for compensation items and a "Benefits" section for benefits items. However, the posting has a single section. I'll split them logically.
4. Practice in Coastal Virginia - this is location/lifestyle. Not in the heading list. Could be "About the role" or maybe "Schedule"? No. The rules say prefer a few substantive sections over many thin ones. I could include it as a paragraph under "About the role" or as a separate section with a heading not in the list? The rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, but likely they want only those headings. However, the posting has a distinct section about location. I could use "About the role" to encompass the role and location. Or maybe "Schedule" is not appropriate. I'll include it as a paragraph under "About the role" or as a separate section with a generic heading? The rules say "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid other headings, but the examples are given. I think it's safer to use only the suggested headings. I'll incorporate the location info into "About the role".
5. Contact info - I'll put as a paragraph at the end without heading.
Now, let's extract lists:
Why Join Our Team? list:
- Immediate clinical and surgical glaucoma volume
- Established patient base and strong regional referral network
- Broad surgical mix including MIGS, traditional glaucoma procedures, and cataract surgery
- Diverse glaucoma pathology and complex cases
- Collaborative team of ophthalmologists and subspecialists
- Advanced diagnostic and surgical technology
- Experienced clinical and surgical support teams
- Multi-location network throughout Coastal Virginia
- Opportunity to help grow and shape glaucoma services across the region
- Long-term leadership, professional growth, and partnership potential
Compensation & Benefits list:
- Competitive base salary + production incentives
- Sign-on bonus and relocation assistance
- CME allowance
- Comprehensive medical and dental benefits
- STD/LTD and paid time off
- Retirement benefits
- Professional liability coverage
- Long-term growth and partnership potential
Note: "Long-term growth and partnership potential" appears in both lists. I'll keep in both? The posting has it in both sections. I'll preserve as is.
Now, the role description: "BC/BE, fellowship-trained Glaucoma Surgeon", "immediate clinical and surgical glaucoma demand", "expand glaucoma services across a well-established regional network". Also "Build a thriving glaucoma practice while enjoying the lifestyle of Coastal Virginia." etc.
I'll create:
About the role
About the role
EyeCare Partners is the nation’s leading provider of clinically integrated eye care. Our national network of over 300 ophthalmologists and 700 optometrists provides a lifetime of care to our patients with a mission to enhance vision, advance eye care and improve lives. Based in St. Louis, Missouri, over 650 ECP-affiliated practice locations provide care in 18 states and 80 markets, providing services that span the eye care continuum. Tidewater Eye Center and Virginia Eye Consultants have joined together, creating an expanded ophthalmology network across Coastal Virginia and an exciting opportunity for continued growth.
As we expand specialty eye care throughout the Hampton Roads and Williamsburg regions, we are seeking a BC/BE, fellowship-trained Glaucoma Surgeon to join our growing team. This is an outstanding opportunity to step into immediate clinical and surgical glaucoma demand while helping expand glaucoma services across a well-established regional network.
Build a thriving glaucoma practice while enjoying the lifestyle of Coastal Virginia. The Hampton Roads region offers waterfront communities, beaches, history, dining, entertainment, and a variety of urban and suburban communities. Whether you're completing glaucoma fellowship or are an experienced surgeon considering your next opportunity, this is an exciting time to join Tidewater Eye Center and Virginia Eye Consultants as we continue expanding specialty eye care throughout the region.
Benefits
- Immediate clinical and surgical glaucoma volume
- Established patient base and strong regional referral network
- Broad surgical mix including MIGS, traditional glaucoma procedures, and cataract surgery
- Diverse glaucoma pathology and complex cases
- Collaborative team of ophthalmologists and subspecialists
- Advanced diagnostic and surgical technology
- Experienced clinical and surgical support teams
- Multi-location network throughout Coastal Virginia
- Opportunity to help grow and shape glaucoma services across the region
- Long-term leadership, professional growth, and partnership potential
Pay
- Competitive base salary + production incentives
- Sign-on bonus and relocation assistance
Benefits
(but we already used Benefits heading. Can't have two Benefits headings. The rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we can't repeat, but typically you'd have one Benefits section. However, the posting has two distinct sections: "Why Join Our Team?" and "Compensation & Benefits". The latter includes both pay and benefits. I could combine all benefits into one Benefits section, but the "Why Join Our Team?" are more like professional benefits/reasons to join, while "Compensation & Benefits" includes traditional benefits. The rules say "Benefits" heading. I think I should have one Benefits section that includes both? But the user said "Preserve ALL substantive information". I'll keep them separate but maybe use "Benefits" for the first list and "Pay" for compensation, and then for the traditional benefits, also under "Benefits"? That would be two Benefits sections. Not ideal.
Alternative: Use "Benefits" for the "Why Join Our Team?" list, and for the compensation section, split into "Pay" and "Benefits" but that would duplicate heading. Maybe I can rename the first to "Why Join Our Team" but the rules say use those specific headings. The examples include "Benefits". The posting's "Why Join Our Team?" is essentially benefits of joining. I'll use "Benefits" for that. Then for the "Compensation & Benefits" section, I'll put compensation items under "Pay" and the benefits items (CME, medical, dental, etc.) under "Benefits" as well? But that would be two Benefits sections. I could combine all benefits into one Benefits section, but they are distinct categories. The rules say "Prefer a few substantive sections over many thin ones." So maybe combine all benefits into one Benefits section. However, the "Why Join Our Team?" list is 10 items, and the compensation benefits are 6 items (excluding pay). I'll combine them into one Benefits section with two sub-lists? But the HTML structure is just - . I could have two separate
under the same heading. That's acceptable.
But the heading "Benefits" would appear once. I'll do:
Benefits
- Immediate clinical and surgical glaucoma volume
... (all 10 items)
- CME allowance
- Comprehensive medical and dental benefits
- STD/LTD and paid time off
- Retirement benefits
- Professional liability
- under the same heading. That's acceptable.
But the heading "Benefits" would appear once. I'll do:
- Immediate clinical and surgical glaucoma volume ... (all 10 items)
- CME allowance
- Comprehensive medical and dental benefits
- STD/LTD and paid time off
- Retirement benefits
- Professional liability