Vascular Sonographer Technician

The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and apply the rules. First, I need to identify the sections. The job posting has: - Job Description Summary with entity, worker type, etc. (metadata) - Education: Bachelors Degree or equivalent - Work Experience: 2-4 years - Licenses/Certificates: RVS/RDCS/RVT or equivalent preferred, Current BLS - Benefits list - Physical Requirements list - Additional Job Description with Minimum Training and Education, Required Licensure, Certifications, Registrations - Some boilerplate at the end (EEO, E-Verify) Rules: - Use

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 (page already shows it) - Do NOT put Job ID / requisition numbers as headings — fold minor metadata into short

  or drop it - Preserve ALL substantive information; do NOT invent or summarize away detail - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions - Include a section ONLY when posting has real, specific content for it — 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 a few substantive sections over many thin ones - Output ONLY HTML fragment — no /, no markdown code fences Now, let's map the content to sections. The posting has: - Education requirement: Bachelors Degree or equivalent - Work Experience: 2-4 years - Licenses/Certificates: RVS/RDCS/RVT or equivalent preferred, Current BLS - Benefits: list of benefits - Physical Requirements: long list - Additional Job Description: Minimum Training and Education, Required Licensure, Certifications, Registrations Also, there is metadata at top: Entity, Worker Type, Worker Sub-Type, Cost Center, Pay Rate Type, Pay Grade, Scheduled Weekly Hours, Work Shift. These are minor metadata; fold into a short

  or drop. Since they are specific (e.g., Scheduled Weekly Hours 32, Pay Rate Type Hourly, Pay Grade Health-29), maybe include in a short paragraph under a "Position Details" or similar? But the rules say do not put Job ID/requisition numbers as headings. These are not job ID but position details. Could include in a

  at top. The user wants sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we only include if there is real content. We have: - Requirements/Qualifications: Education, Work Experience, Licenses/Certificates, Minimum Training and Education, Required Licensure, Certifications, Registrations - Benefits: list - Physical Requirements: list - Possibly "About the role" but not explicitly described. There's a line "If you like working with energetic enthusiastic individuals, you will enjoy your career with us!" That's fluff, maybe not substantive. We also have Pay Rate Type Hourly, Pay Grade Health-29, Scheduled Weekly Hours 32, Work Shift (not specified). That could be a "Pay and Schedule" section? But the rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state Pay Rate Type, Pay Grade, Scheduled Weekly Hours. So we could include a "Pay and Schedule" section with those details. But the user said "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So we can use those headings if content exists. Let's decide sections: 1. Position Details (maybe not a standard heading, but we can use a

  for metadata) 2. Requirements (or Qualifications) - includes education, experience, licenses, certifications, training 3. Benefits - list 4. Physical Requirements - list 5. Pay and Schedule - includes pay rate type, pay grade, scheduled weekly hours, work shift But the rule: "Prefer a few substantive sections over many thin ones." So maybe combine Requirements and Qualifications into one section. Also, the "Additional Job Description" includes Minimum Training and Education and Required Licensure, Certifications, Registrations. That's essentially qualifications. Thus, I'll create: -

  Requirements

  with sub-lists for Education, Experience, Licenses & Certifications, Training & Education, Required Licensure & Certifications -

  Benefits

  with list -

  Physical Requirements

  with list -

  Pay and Schedule

  with details But the user said "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I should use those exact headings if appropriate. "Requirements" is listed. "Benefits" is listed. "Pay" and "Schedule" are separate but we can combine. Also, there is no "Responsibilities" section in the posting. The posting doesn't list duties. So we shouldn't create a Responsibilities heading. There is no "About the role" description. There is no "Skills" section. Thus, we'll have Requirements, Benefits, Physical Requirements, Pay and Schedule. But Physical Requirements is not in the example headings. However, the rule says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It says "e.g.", so we can use other headings if needed. Physical Requirements is a substantive section. Now, the metadata at top: Entity, Worker Type, Worker Sub-Type, Cost Center, Pay Rate Type, Pay Grade, Scheduled Weekly Hours, Work Shift. I'll fold into a short

  at the beginning, maybe under a "Position Details" heading? But the rule says do not put Job ID/requisition numbers as headings. This is not a job ID but position details. Could include as a

  before sections. I'll output a

  with the metadata, then sections. Now, let's structure the HTML. First, a paragraph for metadata:

  Entity: MUSC Community Physicians (MCP) | Worker Type: Employee | Worker Sub-Type: Regular | Cost Center: CC004931 MCP - Beaufort Vascular Surgery | Pay Rate Type: Hourly | Pay Grade: Health-29 | Scheduled Weekly Hours: 32 | Work Shift: Not specified

  But Work Shift is not given a value; it's just "Work Shift" label. In the text: "Work Shift Job Description Additional Job Description". Actually the raw text: "Work Shift Job Description Additional Job Description". It seems the Work Shift value is missing. So I'll say "Work Shift: Not specified". Now, Requirements section: I'll combine Education, Work Experience, Licenses/Certificates, Minimum Training and Education, Required Licensure, Certifications, Registrations. I'll use

  with nested lists or separate lists. Better to use subheadings within the section? But we only have

  for main sections. Within a section, we can use

  ? The rules don't forbid, but they only mention

  for section headings. Could use or

  for subcategories. I'll use

  with
  • containing bold labels. For example:

    Requirements

    • Education: Bachelor's degree or equivalent
    • Work Experience: 2-4 years
    • Licenses/Certificates: RVS/RDCS/RVT or equivalent preferred; Current BLS
    • Minimum Training and Education: Graduation from an accredited Vascular Technology, Cardiovascular Technology, or Ultrasonography program preferred. Equivalent work experience considered. Vascular Sonographers must have a minimum of two years of vascular-specific scanning experience and approval by the Supervisor for Vascular Sonographer II position. Current staff must have all Consistent or Mentor ratings on most recent annual evaluation and no written reprimands within a calendar year. Incoming Vascular Sonographers must have minimum two years vascular-specific scanning experience and acceptable references from prior supervisors/managers. Active membership in a related professional organization such as SDMS or SVU required.
    • Required Licensure, Certifications, Registrations: Certification by ARDMS as Registered Vascular Technologist (RVT) or by CCI as Registered Vascular Specialist (RVS) required prior to hire. Current AHA Basic Life Support (BLS) or American Red Cross BLS for Healthcare Providers certification required.
    Benefits section: list each benefit.

    Benefits

    • Health, dental, vision, and life insurance
    • Employer Sponsored Retirement Plan
    • Paid time off and extended sick leave
    • Paid Parental Leave
    • Disability insurance plan options
    • Continuous professional and clinical training
    • Competitive pay
    • Annual Merit Increase
    • Wellbeing resources
    • Tuition Reimbursement
    • Employee perks and discounts
    • Employee referral program
    • Flexible schedule options
    • Certification incentive program
    Physical Requirements: long list. I'll include as a list.

    Physical Requirements

    • Ability to perform job functions while standing (Frequent)
    • Ability to perform job functions while sitting (Frequent)
    • Ability to perform job functions while walking (Frequent)
    • Ability to climb stairs (Infrequent)
    • Ability to work indoors (Continuous)
    • Ability to work from elevated areas (Frequent)
    • Ability to work in confined/cramped spaces (Infrequent)
    • Ability to perform job functions from kneeling positions (Infrequent)
    • Ability to bend at the waist (Frequent)
    • Ability to squat and perform job functions (Infrequent)
    • Ability to perform repetitive motions with hands/wrists/elbows and shoulders (Frequent)
    • Ability to reach in all directions (Frequent)
    • Possess good finger dexterity (Continuous)
    • Ability to fully use both legs (Continuous)
    • Ability to fully use both hands/arms (Continuous)
    • Ability to lift and carry 15 lbs. unassisted (Infrequent)
    • Ability to lift/lower objects 15 lbs. from/to floor from/to 36 inches unassisted (Infrequent)
    • Ability to lift from 36 inches to overhead 15 lbs. (Infrequent)
    • Ability to maintain 20/40 vision, corrected, in one eye or with both eyes (Continuous)