Surgical Technology Program Director and Faculty Instructor

We need to output only HTML fragment, no html/body tags, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove Job ID/requisition numbers as headings; fold minor metadata into short

or drop it. We need to extract sections: About the role (job description intro), Responsibilities (Teaching And Student Success, Program Leadership And Administration, Curriculum, Assessment, And Institutional Responsibilities, Special Assignments), Requirements (KSA's/Required Qualifications), Qualifications (Additional Considerations maybe?), Skills (maybe combine with qualifications?), Benefits (full state benefits mentioned), Pay (Hiring Range $63,037-95,886 Annually, plus full state benefits), Schedule (Work Schedule Monday – Friday 8:00 am – 10:00 pm as needed and scheduled. Or as scheduled). Also maybe location? Not required as heading. We must not repeat job title as heading. The page already shows it, so we don't output a heading for title. We must not put Job ID / requisition numbers as headings; we can fold minor metadata into a short

or drop it. So we could include a

with Position Number, Agency, etc? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we could include a short paragraph with Position Number, Agency, etc. But we need to preserve all substantive information. However, many of those metadata may be considered minor; but we need to preserve all substantive info. The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep the substantive info, but we can put minor metadata in a short

. The metadata like Position Number, Agency, etc might be considered minor but still substantive? The instruction says fold minor metadata into a short

or drop it. So we can include a short

with those details. We must not include boilerplate like EEO, ADA, E-Verify, etc. Also remove application instructions (Special Instructions to Applicants, etc). Also remove Background Check Statement etc. Also remove "Additional Information" etc. We need to ensure we don't create sections with filler like "commensurate with experience". We have actual pay range and benefits. We need to output only HTML fragment. Let's structure:

Position Number: 297F0042 | Agency: Germanna Community College | Work Location: Stafford - 179 | Hiring Range: $63,037-95,886 Annually, plus full state benefits | Work Schedule: Monday – Friday 8:00 am – 10:00 pm as needed and scheduled.

But we also have separate sections for Pay, Benefits, Schedule. Could combine? The instruction: Prefer a few substantive sections over many thin ones. So we could have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we could combine Pay and Benefits maybe? However they said include a section ONLY when posting has real specific content for it. We have Pay (hiring range) and Benefits (full state benefits). So we could have separate Pay and Benefits sections, or combine them into a "Compensation and Benefits" section but headings must be from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we must use those exact headings if we include them. So we could have Benefits and Pay separate. But we could also decide to not include Benefits if we combine with Pay? But they said prefer few substantive sections over many thin ones. Having both Benefits and Pay separate might be thin but still substantive. Could combine into one section but heading must be one of the allowed; we could choose either Benefits or Pay, but we need to include both pieces of info. Could put both under Benefits heading? But then Pay info would be under Benefits heading, which is not accurate but allowed? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid using other headings, but says use those for section headings. Likely they expect us to use those headings when appropriate. So we could have a Benefits section that includes both full state benefits and pay range. Or we could have Pay section with pay range and Benefits section with benefits. Both are substantive. But we also have Schedule info. So we could have Schedule section. Thus we could have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. That's many sections but each has content. We need to avoid filler like "commensurate with experience". We have actual content. Now we need to extract content for each. About the role: The introductory paragraphs about Germanna Community College mission, location, faculty role, etc. Should we include all that? Yes. Responsibilities: Combine Teaching And Student Success, Program Leadership And Administration, Curriculum, Assessment, And Institutional Responsibilities, Special Assignments. Could be a list. Requirements: KSA's/Required Qualifications (the bullet list). Qualifications: Additional Considerations (the list of preferred qualifications). Skills: maybe combine some skills from requirements? But we already have skills in Required Qualifications (Strong communication, interpersonal, organizational, and leadership skills...). Could put those under Skills section. But we already have Required Qualifications covering many. To avoid duplication, we could treat Required Qualifications as Requirements, Additional Considerations as Qualifications, and Skills maybe extracted from those? But we might duplicate. Better to follow instruction: Use sections only when posting has real specific content. We have content for Requirements (the required qualifications). We have content for Qualifications (additional considerations). We have content for Skills (maybe we can pull out skills like Strong communication, interpersonal, organizational, leadership skills, ability to satisfy clinical agency requirements, etc). But those are already in requirements. Could still list them under Skills. But to avoid too many thin sections, we could combine Requirements and Qualifications into one section? But headings are distinct. However we could decide to not include Qualifications if we incorporate additional considerations into Requirements? But they are separate categories: required vs preferred. The posting distinguishes them. So we should keep both. Skills: Could be derived from both but might be redundant. Perhaps we can omit Skills section if we feel it's thin. But we have explicit skills listed: Strong communication, interpersonal, organizational, and leadership skills. Demonstrated teaching ability, ability to satisfy clinical agency requirements, etc. That's substantive. Could put under Skills. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Now we need to format content. We need to use

• for any list of duties/requirements/benefits. So for Responsibilities, we should list each duty as
• . For Requirements (required qualifications) list each as
• . For Qualifications (additional considerations) list each as
• . For Skills list each as
• . For Benefits maybe just a

  (full state benefits). For Pay maybe a

  with range. For Schedule maybe a

  . We must not repeat job title as heading. No markdown. We need to strip boilerplate: EEO, ADA, E-Verify, etc. Also remove "Special Instructions to Applicants", "Background Check Statement", "Additional Information", "Quicklink for Posting". Also remove "Operation of a State Vehicle No", "Supervises Employees Yes", "Required Travel Travel between all Germanna Campuses will be required." That could be part of Responsibilities? It's about travel; maybe include under Responsibilities as a duty? Could include as a bullet under Responsibilities. Also remove "Posting Number FAC_2077P Recruitment Type General Public - G Number of Vacancies 1 Position End Date (if temporary) Job Open Date 09/24/2026 Job Close Date 10/24/2026 Open Until Filled Agency Website www.germanna.edu Contact Name Joshua Cave Email jcave@germanna.edu Phone Number". This is metadata; we could fold into a short

  at top. We need to preserve all substantive information: The job description, duties, requirements, qualifications, skills, benefits, pay, schedule, location, etc. Let's craft. First, a short metadata paragraph: maybe include Position Number, Agency, Work Location, etc. But we already have location maybe in About the role? Not needed. We'll include a short

  with Position Number, Agency, Work Location. Now About the role: We'll include paragraphs describing Germanna Community College, mission, location, faculty role, etc. We'll need to copy relevant sentences. Let's extract: "Germanna Community College is a public, open access institution of higher education in the Virginia Community College System. The College is a dynamic learning organization that serves as a Germanna regional leader and preferred partner where quality learning experiences enable students to participate effectively in the social, economic, political, intellectual, and cultural life of their communities. Germanna Community College is centrally located in Fredericksburg, VA between Washington D.C. and Richmond and between the Blue Ridge mountains and the Chesapeake Bay. Full of history, the area offers a community rich with diversity, the arts, technology, vineyards, hiking, canoeing/kayaking, and many other activities. Full-time faculty at Germanna Community College support the College mission, vision, and values and contribute to a culture designed to meet the community’s diverse and evolving educational needs. Faculty are dedicated to student success through teaching, mentoring, advising, and fostering critical thinking, independent learning, self-discovery, and problem-solving. This faculty position serves as both Surgical Technology faculty and Surgical Technology Program Director. The faculty member is responsible for teaching didactic, laboratory, simulation, and clinical courses; providing leadership for program accreditation and compliance; maintaining program quality and outcomes; overseeing adjunct faculty; participating in curriculum development and assessment; and supporting student recruitment, retention, and success. Teaching assignments may include day, evening, weekend, hybrid, online, and clinical instruction and may occur at any Germanna campus, center, or clinical affiliate as needed. This position supports compliance with Virginia Community College System requirements and applicable programmatic accreditation standards." That's substantive. Now Responsibilities: We'll break into bullet list. From "Teaching And Student Success" bullet list: - Normally teach 15 credit hours per semester during the academic year, with workload adjustments as approved for Program Director responsibilities. - Teach surgical technology courses in classroom, laboratory, simulation, clinical, hybrid, and online formats. - Utilize instructional strategies that promote active, collaborative, and inclusive learning. - Align instruction with course learning outcomes and program outcomes. - Provide timely feedback on assignments, assessments, and clinical performance. - Respond promptly to student communications. - Maintain regular and substantive interaction in all distance education courses. - Promote student engagement, retention, completion, credential attainment, and employment readiness. - Use the College learning management system and instructional technology effectively. - Maintain accurate records of attendance, grades, assessments, and student progress. From "Program Leadership And Administration": - Serve as the Surgical Technology Program Director. - Maintain compliance with Accreditation Review Council on Education in Surgical Technology and Surgical Assisting (ARC/STSA) standards and Commission on Accreditation of Allied Health Education Programs (CAAHEP) requirements. - Lead accreditation activities, reporting, self-studies, annual reviews, and site visit preparations. - Monitor program effectiveness through assessment of student learning outcomes, credentialing examination results, graduate outcomes, and employer feedback. - Coordinate program scheduling, curriculum review, and program improvement initiatives. - Recruit, orient, supervise, mentor, and evaluate