TRANSPORTER

We need to produce HTML fragment with sections: About the role? Actually the posting includes "About Us" then "Short Description" then "Experience Required", "Education Requirements", "License/Certification Requirements", "Special Requirements". We need to map to headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each section heading. Only include sections that have real specific content. We have content: Short Description (responsibilities). Experience Required (skills). Education Requirements (qualifications). License/Certification Requirements (qualifications maybe). Special Requirements (physical requirements). Benefits, Pay, Schedule not present, so omit. Also "About the role" maybe not present; we have "About Us" but that's about the organization, not role. Could we use "About the role" heading for the short description? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which headings to use based on content. We have responsibilities (Short Description). We have experience required (skills). Education requirements (qualifications). License/certification (qualifications). Special requirements (maybe also qualifications or skills). We could combine some. We must not repeat job title as heading. No Job ID. Remove boilerplate. We need to preserve all substantive information. So we need to include the About Us paragraph? It's about the organization; maybe we could put under "About the role"? But that's not exactly role. However we could include a section "About the role" containing the short description? Actually "About the role" could be a brief summary of the role; we have Short Description which describes responsibilities. Could treat that as About the role. Then Responsibilities could be more detailed list? But we don't have a list; it's prose. Could still put responsibilities under that heading. Better: Use headings: About the role (short description), Responsibilities (maybe same as short description? Might be duplicate). To avoid duplication, we could put short description under About the role, and then Responsibilities as a list? But we don't have list items. Could we split the short description into bullet points? Not allowed to invent detail. So we should not create a Responsibilities section if we don't have distinct responsibilities beyond the short description. The instruction: Prefer a few substantive sections over many thin ones. So we could combine About the role and Responsibilities into one section? But we need to use headings from list; we could use "About the role" heading and put the short description there. Then we could have "Requirements" heading covering experience, education, license/certification, special requirements. Or split into Qualifications and Skills. Let's think. We have: - Experience Required: bullet-like sentences: Effective verbal and listening communication skills. Should possess the initiative and the ability to set and achieve high standards of performance. Ability to make progress on multiple assignments under time constraints. Ability to learn specific job duties and complete detailed work assignments. These are skills/abilities. - Education Requirements: High School diploma or equivalent. - License/Certification Requirements: BLS or CPR required within three (3) months of hire. - Special Requirements: Ability to lift, carry and move heavy objects. Ability to ascend and descend stairs. Ability to stand for extended periods of time. Must have the dexterity of hand and fingers in order to utilize tools, utensils and equipment. Ability to audibly receive instructions and to hear inquiries from patients, physicians, clients and team members. Ability to see and perceive depth with or without corrective lenses. These are physical requirements. Thus we could have sections: - About the role (short description) - Responsibilities (maybe we could treat short description as responsibilities; but we already used About the role). Could we omit About the role and just use Responsibilities? The instruction says use headings e.g. About the role, Responsibilities... It doesn't require us to use all; we can choose. So we could use Responsibilities heading for the short description. Then we could have Requirements heading for experience, education, license/certification, special requirements. Or split into Qualifications (education, license) and Skills (experience). Let's decide. We need to preserve all substantive information. So we need to include all those bullet-like sentences. We can structure:

Responsibilities

Responsible for the safe, timely and accurate transport of patients, medical equipment and patient-related items to their destinations enabling physicians, nurses, technicians, and therapists to perform their duties in an effective manner. Ensures positive patient and customer satisfaction, proper utilization of body mechanics, adherence to policies, procedures and standards established by Hospital, Department and Regulatory Agencies. Acts as a positive role model and team player demonstrating hospital mission and values. May perform dispatch duties as assigned which would require EPIC access.

Then

Requirements

Under that we could have sub-sections? Not allowed to add extra headings beyond h3? We could use

• for lists. So we can list items under Requirements. We need to include Experience Required, Education Requirements, License/Certification Requirements, Special Requirements. We can combine them into a single list under Requirements, but that might lose categorization. However we can still preserve all info. Better: Use

  Skills

  for experience required (skills).

  Qualifications

  for education and license/certification.

  Physical Requirements

  for special requirements. But the allowed headings list does not include Physical Requirements; but we could still use Requirements heading and then inside have sublists? The instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, not exclusive? Likely we should stick to those headings. So we should only use those headings. So we can use Requirements, Qualifications, Skills. That covers. Thus: - Responsibilities: short description. - Skills: Experience Required (verbal communication, initiative, multitasking, learning). - Qualifications: Education Requirements (HS diploma or equivalent) and License/Certification Requirements (BLS/CPR within 3 months). - Requirements: maybe we could put Special Requirements under Requirements? But we already used Requirements heading for something else. Actually we could use Requirements for Special Requirements, and Qualifications for education/license, Skills for experience. But we need to decide. We have three categories: experience (skills), education/license (qualifications), special requirements (physical). We could map: - Skills: Experience Required. - Qualifications: Education Requirements + License/Certification Requirements. - Requirements: Special Requirements. That uses three headings: Skills, Qualifications, Requirements. All are from the list. We must not create Pay/Benefits/Schedule sections. Now we need to output only HTML fragment. Let's craft:

  Responsibilities

  Responsible for the safe, timely and accurate transport of patients, medical equipment and patient-related items to their destinations enabling physicians, nurses, technicians, and therapists to perform their duties in an effective manner. Ensures positive patient and customer satisfaction, proper utilization of body mechanics, adherence to policies, procedures and standards established by Hospital, Department and Regulatory Agencies. Acts as a positive role model and team player demonstrating hospital mission and values. May perform dispatch duties as assigned which would require EPIC access.

  Skills

  • Effective verbal and listening communication skills.
  • Should possess the initiative and the ability to set and achieve high standards of performance.
  • Ability to make progress on multiple assignments under time constraints.
  • Ability to learn specific job duties and complete detailed work assignments.

  Qualifications

  • High School diploma or equivalent.
  • BLS or CPR required within three (3) months of hire.

  Requirements

  • Ability to lift, carry and move heavy objects.
  • Ability to ascend and descend stairs.
  • Ability to stand for extended periods of time.
  • Must have the dexterity of hand and fingers in order to utilize tools, utensils and equipment.
  • Ability to audibly receive instructions and to hear inquiries from patients, physicians, clients and team members.
  • Ability to see and perceive depth with or without corrective lenses.
  Check that we preserved all substantive information: Yes. We removed About Us boilerplate? We omitted the About Us paragraph about Cooper University Health Care. That is substantive information about the employer. Should we include it? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. The About Us section is substantive info about the organization. Should we include it? Possibly yes, as it's part of the posting. However the instruction about headings: we can only use certain headings; we could add an "About the role" heading? But About Us is about the organization, not role. Could we put it under a heading like "About the role"? Not accurate. But we could create a section without heading? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use

  for section headings (e.g. ...). Likely they expect us to use those headings only for sections we emit. But we could also include a paragraph without heading? The instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

  • for any list of duties/requirements/benefits, and

    for prose. It doesn't say we cannot have prose outside headings. But they want sections. Probably they expect each substantive chunk under a heading. The About Us could be under a heading like "About the role"? Not ideal. Maybe we could create a heading "About the role" and put the About Us there? That would be misleading. However the instruction 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 besides those examples, but they gave examples. Likely they want us to use those headings for sections we have content for. If we have no content for About the role, we shouldn't emit it. The About Us is not about the role, but maybe we could treat it as "About the role" loosely? Might be considered filler? The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". The About Us is real specific content about the employer. So we should include it. But we need a heading. Could we use "About the role" as heading and put the About Us there? That would be inaccurate but still content. However they might check for relevance? Not sure. Alternatively, we could not include a heading and just put a

    after the heading list? The instruction says use

    for section headings (e.g...). It doesn't say every

    must be under a heading. But they want structured semantic HTML. Usually you'd have headings separating sections. I think we should include a heading for About Us, maybe "About the role" is the closest. But we could also use "About the role" to describe the role, not the employer. However the About Us is about the employer, which provides context for the role. Might be acceptable. Better: we could add a heading "About the role" and put the short description there, and then put About Us as a

    before any heading? But that would be a stray paragraph. Let's re-read: "