Surgical Technologist - Operating Room

. But we need to decide sections. We have Minimum Requirements: "Certification as a surgical tech is preferred. Able to be on call 1 time per week and every 5th weekend (Friday, Saturday and Sunday). Experience One year of experience to be proficient in all phases of assigned duties." Also BONUS & RELOCATION ELIGIBLE! Sign-on bonus is available with 2 year commitment - up to $10,000! Must have at least one year of experience. Relocation also available as qualified. That's about Pay? Actually sign-on bonus is pay/benefit. Could be Pay section? The instruction: include Pay section only if posting actually states them. It mentions sign-on bonus up to $10,000 with 2 year commitment. That's pay-related. Also maybe we can include Pay section with that detail. Benefits: "We offer health, dental, vision, paid time off, and so much more! Review our benefit summary at: https://www.cvmc.org/about-cvmc/careers/benefits" That's benefits. Schedule: "Able to be on call 1 time per week and every 5th weekend (Friday, Saturday and Sunday)." That's schedule info. Qualifications: maybe certification preferred, experience one year. Could be Requirements or Qualifications. The instruction: Use headings for Requirements, Qualifications, Skills. We need to decide which sections have real specific content. We have Minimum Requirements: certification preferred, on-call schedule, one year experience. That's requirements. We also have "Experience One year of experience to be proficient in all phases of assigned duties." That's also requirement. We have "BONUS & RELOCATION ELIGIBLE! Sign-on bonus is available with 2 year commitment - up to $10,000! Must have at least one year of experience.Relocation also available as qualified." That's bonus/relocation, could be part of Benefits or Pay. We have no explicit Skills section. Thus we can create sections: - About the role (p) - Responsibilities (maybe we can extract duties from the summary? But we already used About the role for summary. Could we split: About the role = brief intro; Responsibilities = list of duties (direct care, indirect nursing functions, etc.) We can make a

list. Let's extract duties: From summary: - direct and indirect professional nursing care to patients - serves as patient advocate - provides teaching, counseling and emotional comfort to patients and family members - Provides direct care to assigned patients in conformance with hospital policies, professional standards, physician orders, and approved plan of care. - Responsible for indirect nursing functions and activities of assigned nursing personnel. - Functions within limits of Vermont Nurse Practice Act, Code of Ethics for Nurses, and hospital and nursing department policies and procedures. - Supports philosophy, objectives, and goals of nursing department. - Nursing process will be utilized in the provision of patient care. That's a list. We can put those as
• . Then Requirements: certification preferred, able to be on call 1 time per week and every 5th weekend, one year experience. Qualifications: maybe same as requirements? But we can combine? The instruction: prefer a few substantive sections over many thin ones. So maybe we just have About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. That's six sections. But we need to avoid duplication: on-call appears both in Requirements and Schedule. We could put schedule info in Schedule section, and requirement about on-call could be moved to Schedule? But requirement includes on-call as part of availability; we could keep it in Requirements but also mention schedule. However duplication is okay if it's same content? Might be considered duplicated lines. Better to separate: Requirements: certification preferred, one year experience. Schedule: on-call 1 time per week and every 5th weekend. Pay: sign-on bonus up to $10,000 with 2 year commitment, relocation available. Benefits: health, dental, vision, paid time off, etc. Let's craft. We must not include boilerplate like "Learn More About Our Team" links etc. Those are navigation/application instructions? They are not boilerplate but they are promotional links. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Learn More About Our Team" links are not exactly application instructions but they are promotional. Might be considered navigation? Probably we should drop them as they are not substantive job info. The instruction says to preserve ALL substantive information; do NOT invent or summarize away detail. The links to YouTube and fact sheet are not substantive job details; they are extra info. Could be considered navigation? Safer to drop them. Thus we keep only core job description. Now produce HTML fragment:

  About the role

  ... (summary)

  Responsibilities

  • ...
  ...

  Requirements

  • Certification as a surgical tech is preferred.
  • Minimum one year of experience to be proficient in all phases of assigned duties.

  Benefits

  • Health insurance
  • Dental insurance
  • Vision insurance
  • Paid time off
  • Additional benefits (see benefit summary)
  But we need to preserve the exact wording: "We offer health, dental, vision, paid time off, and so much more! Review our benefit summary at: https://www.cvmc.org/about-cvmc/careers/benefits". We can keep that as a

  maybe. But instruction: Use

  • for any list of duties/requirements/benefits. So we can make list items for each benefit: health, dental, vision, paid time off. And maybe a note about benefit summary link. Should we include the link? It's substantive info about where to review benefits. Might keep as a

    after list. Pay: "Sign-on bonus is available with 2 year commitment - up to $10,000! Relocation also available as qualified." We can make

    or

    . Since it's not a list, we can use

    . Schedule: "Able to be on call 1 time per week and every 5th weekend (Friday, Saturday and Sunday)." Use

    . Make sure not to include duplicated lines: we have experience mentioned in Requirements and also in Pay (must have at least one year of experience). That's duplication. We should avoid duplication: maybe keep experience only in Requirements, and not repeat in Pay. Pay section can just mention sign-on bonus and relocation. Thus Pay: "Sign-on bonus is available with a 2‑year commitment – up to $10,000. Relocation assistance is available for qualified candidates." Now check for any other duplication: The on-call appears only in Schedule. Now ensure we didn't miss any substantive info: The initial sentence "We are more than just science. At our heart, we are 1700 employees united by an inspiration to care for our community. We are CVMC." That's about the organization; could be part of About the role? Might be considered boilerplate? It's descriptive of the employer, not the role. Might be considered substantive? It's about the organization, could be kept in About the role as intro. But the instruction: "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." This is not metadata; it's about the organization. Could be included in About the role as a preamble. However the "Position Summary" already starts after that. The first sentences are generic about CVMC. Might be considered boilerplate? Not exactly navigation/legal. It's describing the employer. Might be okay to keep. But we need to preserve ALL substantive information. So we should include that as part of About the role. Thus About the role paragraph: "We are more than just science. At our heart, we are 1700 employees united by an inspiration to care for our community