SVS Vision - Doctor of Optometry - Western Detroit Region

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job posting. Content: - Opening: "SVS Vision is currently seeking an Optometrist to join our team! Join an experienced, cohesive teams serving patients in Western Detroit!. You will have the autonomy to build the practice that you want. In this role, you'll provide comprehensive eye care services, recommend vision-enhancing products, and promote good eye health through patient education. SVS Vision is seeking a team player with excellent clinical skills and attitude who always keeps the patient's best interests in mind. The ability to be flexible to support a fast-paced environment is also essential to this role." That's about the role/responsibilities. Then "Practice Highlights:" list: No Call Position, Dedicated Staff to Support Patient Care, Advanced Technology (iCare Tonometers, Retinal Cameras, etc.), Comprehensive Eye Exams, Contact Lens Fittings, Refractive Services. Then "Compensation & Benefits:" list: Competitive Guaranteed Salary While You Grow Your Practice, Health, Dental, Vision, Life Insurance, Generous CME Reimbursement, Paid Time Away to Ensure Exceptional Work/Life Balance, Occurrence Based Malpractice Insurance, Short- Term & Long-Term Disability Insurance, Unique Voluntary Benefits (i.e. Pet Insurance, Legal Services, Identity Theft Protection), Retirement - 401K. Then "About the Community:" description of Livonia, Michigan. Then "SVS Vision CARES is the way we serve every patient..." that's like a description of values. Then "About SVS Vision:" description of company. Then "Minimum Knowledge, Experience & Skills Requirements:" bullet list: • OD Degree from ACOE approved College of Optometry • Ability to communicate with customers and teammates Must be legally authorized to work in country of employment without sponsorship for employment visa status. Then EEO statement etc. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should drop the EEO line. We need to produce sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. - About the role: could be the introductory paragraph describing role. Could be "About the role" heading. - Responsibilities: list of duties: provide comprehensive eye care services, recommend vision-enhancing products, promote good eye health through patient education, be flexible to support fast-paced environment, etc. Also maybe "Practice Highlights" could be considered responsibilities? But they are more about practice environment. Could be part of responsibilities or qualifications? Probably responsibilities. - Requirements: Minimum Knowledge, Experience & Skills Requirements: OD degree, ability to communicate, legally authorized to work. - Qualifications: maybe similar to requirements? Could be OD degree etc. But we have only one set. Could combine Requirements and Qualifications? But we need to follow instruction: use headings only when posting has real specific content for it. We have content for Requirements (the bullet list). Could also have Qualifications (maybe same). But we might not need both; we can choose one. The instruction: "Prefer a few substantive sections over many thin ones." So we should avoid splitting similar content into multiple thin sections. So we could have a single section like "Requirements" covering OD degree, communication, work authorization. Or we could have "Qualifications" covering that. Which heading is more appropriate? The list is titled "Minimum Knowledge, Experience & Skills Requirements". That's like Requirements. So we use

Requirements

. - Skills: maybe we could extract skills like excellent clinical skills, attitude, team player, flexibility, communication. But those are already in responsibilities/about role. Could be a Skills section but might be thin. Better to incorporate into About the role or Responsibilities. - Benefits: we have Compensation & Benefits list. That includes salary, insurance, CME reimbursement, PTO, malpractice, disability, voluntary benefits, retirement. So we can have Benefits heading. - Pay: The posting mentions "Competitive Guaranteed Salary While You Grow Your Practice". That's pay info. Could be separate Pay section, but we already have Benefits includes salary. Could combine Pay and Benefits into one Benefits section? The instruction says include a section ONLY when posting has real specific content for it. It does not forbid combining Pay and Benefits under Benefits heading. But we have separate headings list; we could decide to have Benefits covering both compensation and benefits. That would be substantive. Pay alone would be thin (just salary). So better to have Benefits section covering compensation and benefits. - Schedule: No mention of schedule (e.g., full-time, part-time, hours). Not present. So we omit Schedule. - About the role: we have introductory paragraph. Could be About the role. - Responsibilities: we could list duties: provide comprehensive eye care services, recommend vision-enhancing products, promote good eye health through patient education, be flexible to support fast-paced environment, etc. Also maybe "Practice Highlights" could be considered responsibilities? But they are more about practice environment. Could be separate section like "Practice Highlights" but not in allowed headings. Could incorporate into Responsibilities or About the role. - About the Community: not in allowed headings list. Could we include as a section? Not allowed headings; only those listed. So we should drop it or incorporate into something else? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but maybe we can use others? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should not create headings like About the Community or About SVS Vision. We should incorporate that content elsewhere or drop it? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we cannot drop substantive info like About the Community or About SVS Vision. But we cannot create headings outside the allowed list? The instruction says use

for section headings (e.g. ...). It might be that those are the allowed headings; we should not create other headings. But we need to preserve all substantive info. How to incorporate community and company description without a heading? Could wrap them in

under a relevant heading like About the role? But that might be odd. Perhaps we can treat them as part of "About the role" or "Responsibilities"? Not ideal. Alternatively, maybe we can create headings for those as well, but the instruction says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not an exhaustive list. So we could also use other headings like "About the Community", "About SVS Vision". However, the instruction also says "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." It doesn't forbid other headings. It just gives examples. So we can use headings for other sections like About the Community, About SVS Vision, Practice Highlights, etc. But we need to follow the pattern: use

for section headings. So we can use any heading we want, as long as it's

. The examples are just illustrative. Thus we can create sections: About the role, Responsibilities, Requirements, Benefits, About the Community, About SVS Vision, Practice Highlights maybe. But we need to avoid thin sections. We need to ensure each heading has substantive content. Let's list substantive blocks: 1. Intro paragraph: "SVS Vision is currently seeking an Optometrist to join our team! Join an experienced, cohesive teams serving patients in Western Detroit!. You will have the autonomy to build the practice that you want. In this role, you'll provide comprehensive eye care services, recommend vision-enhancing products, and promote good eye health through patient education. SVS Vision is seeking a team player with excellent clinical skills and attitude who always keeps the patient's best interests in mind. The ability to be flexible to support a fast-paced environment is also essential to this role." This could be About the role. 2. Practice Highlights list: No Call Position, Dedicated Staff to Support Patient Care, Advanced Technology (iCare Tonometers, Retinal Cameras, etc.), Comprehensive Eye Exams, Contact Lens Fittings, Refractive Services. Could be a section "Practice Highlights". 3. Compensation & Benefits list: Competitive Guaranteed Salary While You Grow Your Practice, Health, Dental, Vision, Life Insurance, Generous CME Reimbursement, Paid Time Away to Ensure Exceptional Work/Life Balance, Occurrence Based Malpractice Insurance, Short- Term & Long-Term Disability Insurance, Unique Voluntary Benefits (i.e. Pet Insurance, Legal Services, Identity Theft Protection), Retirement - 401K. Could be Benefits. 4. About the Community paragraph: Livonia, Michigan description. Could be About the Community. 5. SVS Vision CARES description: Connect, create comfort..., Assess..., Recommend..., Educate..., See It Through... Could be "SVS Vision CARES" or "Patient Care Philosophy". 6. About SVS Vision paragraph: company history, locations, etc. Could be About SVS Vision. 7. Minimum Knowledge, Experience & Skills Requirements bullet list: OD degree, ability to communicate, legally authorized to work. Could be Requirements. We also have EEO line to drop. We need to avoid thin sections: each of these seems substantive. We need to use

• for any list of duties/requirements/benefits. So for Practice Highlights, Benefits, Requirements we need lists. For prose paragraphs, use

  . We need to not repeat job title as heading. We need to output only HTML fragment. Let's craft:

  About the role

  SVS Vision is currently seeking an Optometrist to join our team! Join an experienced, cohesive team serving patients in Western Detroit. You will have the autonomy to build the practice that you want. In this role, you'll provide comprehensive eye care services, recommend vision-enhancing products, and promote good eye health through patient education. SVS Vision is seeking a team player with excellent clinical skills and attitude who always keeps the patient's best interests in mind. The ability to be flexible to support a fast-paced environment is also essential to this role.

  Practice Highlights

  • No Call Position
  • Dedicated Staff to Support Patient Care
  • Advanced Technology (iCare Tonometers, Retinal Cameras, etc.)
  • Comprehensive Eye Exams
  • Contact Lens Fittings
  • Refractive Services

  Benefits

  • Competitive Guaranteed Salary While You Grow Your Practice
  • Health, Dental, Vision, Life Insurance
  • Generous CME Reimbursement
  • Paid Time Away to Ensure Exceptional Work/Life Balance
  • Occurrence Based Malpractice Insurance
  • Short‑Term & Long‑Term Disability Insurance
  • Unique Voluntary Benefits (e.g., Pet Insurance, Legal Services, Identity Theft Protection)
  • Retirement - 401K

  About the Community

  Livonia