Operations Specialist - Clinical Engineering

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: - About the role (maybe from the initial description) - Responsibilities (Job Responsibilities section) - Requirements/Qualifications (Job Qualifications) - Benefits (maybe from the "About Us" section, but that's more company info) - Pay (Expected Starting Pay Range) - Schedule (Shift, Schedule, Weekly Hours, FTE) - Location (Primary Location, Department) 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 (the 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 the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") - Never create Pay/Schedule/Benefits sections unless the posting actually states them - Prefer a few substantive sections over many thin ones - Output ONLY the HTML fragment — no /, no markdown code fences Now, let's parse the input: The input starts with metadata lines: Primary Location Burnet Campus Department Clinical Engineering Shift Day (United States of America) Schedule Full time Weekly Hours 40 FTE 1 Employee Status Regular Expected Starting Pay Range $55,182.40 - $69,076.80 Starting pay is based on experience, skills, and equity; exceptions may apply for highly qualified candidates. Additional pay (e.g., shift, on‑call, or weekend differentials) and benefits may apply. Annual pay may vary based on FTE status. Then "Job Responsibilities" with multiple subsections: - Facilities/Operations - Accreditation/ Regulatory/Compliance - Financial/Budget - Process/Quality Improvement - Project Mgt Each has bullet points (though they are written as paragraphs with hyphens). I need to convert them into lists. Then "Job Qualifications": Bachelor degree or equivalent combination of education and experience No experience required Then "About Us" section with company description and accolades. This is boilerplate but could be considered "About the role" or "About the company". The rules say to remove EEO/equal-opportunity boilerplate. The "About Us" includes EEO statement at the end. I should keep the company description but remove the EEO boilerplate. However, the rules say "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". So I should remove the EEO statement. The rest of "About Us" is company marketing, which might be considered boilerplate but could be included as "About the company" or "About us". The rules don't explicitly forbid it, but they say "Preserve ALL substantive information". The company description is substantive? It's generic marketing. The rules also say "Prefer a few substantive sections over many thin ones." I think I can include a brief "About the company" section with the description, but omit the EEO line. Also "Comprehensive Job Description Provided Upon Request." That's a note, maybe drop. Now, I need to decide on sections: 1. Pay: The posting has Expected Starting Pay Range and details. So include Pay section. 2. Schedule: The posting has Shift, Schedule, Weekly Hours, FTE, Employee Status. So include Schedule section. 3. Location/Department: Could be part of a "Details" or "Position Details" section. But the rules mention headings like "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". Not "Location". However, the metadata includes Primary Location and Department. I could fold them into a short

  at the top or create a "Position Details" section. The rules say "fold minor metadata into a short

  or drop it." So I can put location, department, shift, schedule, hours, FTE, status into a paragraph or a list under a "Position Details" heading? But the rules only allow specific headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Schedule" is allowed. "Pay" is allowed. "Location" is not listed. But 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, not exhaustive. However, they also say "include a section ONLY when the posting has real, specific content for it". The posting has specific location and department. I could create a "Position Details" heading, but to be safe, I'll fold them into a paragraph under a "Position Details" heading? But the rules say "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So metadata like location, department, shift, schedule, hours, FTE, status are minor metadata. I can fold them into a short

  at the beginning, maybe under a "Position Details" heading? But the rules say "use

  for section headings (e.g. ...)". It doesn't forbid other headings, but they want only those? The example list includes "Schedule" and "Pay". I think I should create a "Schedule" section for schedule details, and a "Pay" section for pay details. For location and department, I can include them in a brief introductory paragraph before sections, or as a "Position Details" section. Since the rules say "fold minor metadata into a short

  or drop it", I'll create a short paragraph at the top with location, department, shift, schedule, hours, FTE, status. But the output should be HTML fragment with sections. I'll start with a paragraph containing that metadata. Then sections: - Pay (since pay range is given) - Schedule (since schedule details are given) - Responsibilities (the main content) - Qualifications (Job Qualifications) - About the company (optional, but the "About Us" is substantive? It's marketing. I'll include it as "About the company" but remove EEO boilerplate.) But the rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states pay and schedule, so those are fine. Now, for Responsibilities: The job responsibilities are divided into subsections. I should preserve that structure. I can use

  for subsections? The rules only mention

  for section headings. They didn't mention

  . But to preserve structure, I could use

  for sub-sections within Responsibilities. However, the rules say "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid subheadings. But to keep it simple, I could make each responsibility area a list item with a bold label, or use nested lists. The input has hyphens for each bullet. I'll convert each bullet to

  . The subsections (Facilities/Operations, Accreditation/Regulatory/Compliance, etc.) are categories. I could make them

  headings within the Responsibilities section, then lists under each. That would be semantic. The rules don't prohibit

  . I'll do that. Similarly, Qualifications: two bullet points. Now, About Us: I'll include as "About the company" with the description, but remove the EEO line. The EEO line is: "Cincinnati Children’s is proud to be an Equal Opportunity Employer committed to creating an environment of dignity and respect for all our employees, patients, and families. All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, age, genetic information, national origin, sexual orientation, gender identity, disability or protected veteran status. EEO/Veteran/Disability". That's boilerplate, remove. Also "Comprehensive Job Description Provided Upon Request." Remove. Now, let's craft the HTML. First, a paragraph with metadata:

  Primary Location: Burnet Campus | Department: Clinical Engineering | Shift: Day (United States of America) | Schedule: Full time | Weekly Hours: 40 | FTE: 1 | Employee Status: Regular

  Then Pay section:

  Pay

  Expected Starting Pay Range: $55,182.40 - $69,076.80

  Starting pay is based on experience, skills, and equity; exceptions may apply for highly qualified candidates. Additional pay (e.g., shift, on‑call, or weekend differentials) and benefits may apply. Annual pay may vary based on FTE status.

  Schedule section:

  Schedule

  • Shift: Day (United States of America)
  • Schedule: Full time
  • Weekly Hours: 40
  • FTE: 1
  • Employee Status: Regular

  But note: the metadata already includes these. The rules say "fold minor metadata into a short

  or drop it." I already put them in a paragraph. But Schedule is a specific heading allowed. The posting has "Shift", "Schedule", "Weekly Hours", "FTE", "Employee Status". That's schedule details. I could include them in Schedule section as a list, and not repeat in the paragraph. I'll decide to put them in Schedule section and not in the paragraph. The paragraph can just have location and department. Let's do:

  Primary Location: Burnet Campus | Department: Clinical Engineering

  Then Schedule section with the rest. But the rules say "include a section ONLY when the posting has real, specific content for it". The posting has specific schedule details, so Schedule section is appropriate. Now Responsibilities section:

  Responsibilities

  Facilities/Operations

  • Direct and coordinate the daily operations of the dept./facility in collaboration with leadership.
  • Establish and monitor business processes.
  • Identify opportunities for improving cost and quality through in-depth analysis.
  • Develop and implement policies and procedures for improved utilization, quality and operations.
  • Ensure operations are efficient and cost effective.
  • Resolve issues re: staffing, utilization of facilities and equipment.
  • Develop and interpret policies and procedures for staff and ensure that all policies conform with guidelines.
  • Ensure compliance with all regulatory requirements.
  • Promote programmatic development, efficient work and patient flow, supply and instrument management, and a safe culture and environment.
  • Coordinate/manage facilities-related projects, monitor timelines for completion and provide direction for staff and vendors.
  • May manage purchase or repair maintenance of facility equipment.
  • Manage, allocate and coordinate space to meet the operational and strategic goals of the division and the needs of the individual program areas.
  • Collaborate with IT and design to ensure proper placement of items in clinical areas.
  • Assist with area commissioning and decommissioning process.

  Accreditation/Regulatory/Compliance

  • May define process and manage invention reporting required for federal and private compliance.
  • Update