Paramedic – Day Shift

Here's a thinking process: 1. **Analyze User Input:** - Input is a job posting fragment with sections: "Role Overview", "Qualifications & Certifications", and "Key Responsibilities" - I need to reformat this into clean, well-structured semantic HTML - Rules: - Use `

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

• ` for any list of duties/requirements/benefits - Use `

  ` for prose - Do NOT repeat the job title as a heading (page already shows it) - Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a 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 - IMPORTANT: 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") and 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 2. **Identify Sections & Content from Input:** - "Role Overview This position provides advanced clinical support to physicians and nursing staff, ensuring the delivery of high-quality, timely patient care. It is a vital member of the care team, aligned with organizational mission, vision, and strategic goals." - "Qualifications & Certifications High school diploma or GED Current Texas EMT-P License or National Registry EMT-P Certification Basic Life Support (BLS) Certification Advanced Cardio Life Support (ACLS) Certification Pediatric Advanced Life Support (PALS) Certification within 90 days of hire Experience Preferred: 1 year of relevant work experience" - "Key Responsibilities Provide advanced clinical support to healthcare professionals Assist in delivering efficient, high-quality patient care Support organizational mission and strategic objectives" 3. **Map to HTML Elements per Rules:** - Section headings: The rules say use `

  ` for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But I should use relevant ones from the posting. The input has "Role Overview", "Qualifications & Certifications", "Key Responsibilities". I need to map these to the suggested heading names, but only if they have real content. The rules say "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It's giving examples of valid heading names. I should use concise, semantic headings that match the content. Probably: "About the role" or just keep "Role Overview" but as

  . Let's look at the exact wording: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". This means I can use those exact labels or similar. I'll map: - "Role Overview" → could be "About the role" or keep "Role Overview". I'll use "About the role" since it's in the example and fits, but the rule says "e.g." so it's optional. To be safe, I'll use headings that match the content exactly but as

  . Actually, re-read: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". I think I should use these as the heading text if they match, or use the examples. I'll use "About the role", "Responsibilities", "Requirements" (or "Qualifications"). The input has "Qualifications & Certifications" and "Key Responsibilities". I'll map to "Qualifications" and "Responsibilities". I'll also check if I need an "About the role" section. The input has "Role Overview" which contains prose. I can make that "About the role". - Lists: Use `

  • ` for any list of duties/requirements/benefits. The input has lists within sections: qualifications list, responsibilities list. I'll format those as unordered lists. - Prose: Use `

    ` for prose. The "Role Overview" paragraph is prose. - Headings: Do NOT repeat the job title as a heading (page already shows it). The input doesn't show a job title, so fine. - Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it. No job ID in input. - Preserve ALL substantive information; do NOT invent or summarize away detail. I need to include all the specifics: high school diploma or GED, Texas EMT-P License, National Registry EMT-P Certification, BLS, ACLS, PALS within 90 days, 1 year preferred experience. All responsibilities details. - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. None present in input, good. - IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Never create Pay/Schedule/Benefits sections unless the posting actually states them. The input doesn't have Pay, Schedule, or Benefits sections, so I must NOT create them. - Prefer a few substantive sections over many thin ones. I'll include only the sections that have content: About the role, Responsibilities, Qualifications. I won't invent Skills, Benefits, Pay, Schedule. Let's decide on headings mapping: - "Role Overview" → "About the role" (since the example lists "About the role", and the content is an overview paragraph) - "Key Responsibilities" → "Responsibilities" (exact match to example) - "Qualifications & Certifications" → "Qualifications" (match example) Now, format each: "About the role" section: Prose: "This position provides advanced clinical support to physicians and nursing staff, ensuring the delivery of high-quality, timely patient care. It is a vital member of the care team, aligned with organizational mission, vision, and strategic goals." → `

    This position provides advanced clinical support to physicians and nursing staff, ensuring the delivery of high-quality, timely patient care. It is a vital member of the care team, aligned with organizational mission, vision, and strategic goals.

    ` "Responsibilities" section: List of duties: - Provide advanced clinical support to healthcare professionals - Assist in delivering efficient, high-quality patient care - Support organizational mission and strategic objectives → `

    Responsibilities

    • Provide advanced clinical support to healthcare professionals
    • Assist in delivering efficient, high-quality patient care
    • Support organizational mission and strategic objectives
    ` "Qualifications" section: The input has "Qualifications & Certifications" with: - High school diploma or GED - Current Texas EMT-P License or National Registry EMT-P Certification - Basic Life Support (BLS) Certification - Advanced Cardio Life Support (ACLS) Certification - Pediatric Advanced Life Support (PALS) Certification within 90 days of hire - Experience Preferred: 1 year of relevant work experience I need to format this as a list. The "Experience Preferred" is part of qualifications. I'll include all as `
  • ` items. I'll group them under one `
    `. `

    Qualifications

    • High school diploma or GED
    • Current Texas EMT-P License or National Registry EMT-P Certification
    • Basic Life Support (BLS) Certification
    • Advanced Cardio Life Support (ACLS) Certification
    • Pediatric Advanced Life Support (PALS) Certification within 90 days of hire
    • 1 year of relevant work experience preferred
    ` Check rules: "use
    • for any list of duties/requirements/benefits". Yes. "Preserve ALL substantive information; do NOT invent or summarize away detail." I'm keeping all details. "never emit a heading followed by filler/placeholder text" - I'm not. "never create Pay/Schedule/Benefits sections unless the posting actually states them" - I'm not creating them. "Output ONLY the HTML fragment — no /, no markdown code fences." - I'll output just the HTML. Let's construct the final HTML fragment carefully. I need to ensure the headings are

      . The examples say "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I'll use "About the role", "Responsibilities", "Qualifications". That matches. One thing: The input's "Role Overview" is a prose description. I'll make it "About the role". The content is all there. Let's double-check the qualifications list. The input says: "Qualifications & Certifications High school diploma or GED Current Texas EMT-P License or National Registry EMT-P Certification Basic Life Support (BLS) Certification Advanced Cardio Life Support (ACLS) Certification Pediatric Advanced Life Support (PALS) Certification within 90 days of hire Experience Preferred: 1 year of relevant work experience" I'll list them all as `

      `. I'll combine the "Experience Preferred" as a separate li or include it. I'll keep exact phrasing: "1 year of relevant work experience preferred" or "Experience Preferred: 1 year of relevant work experience". I'll preserve the exact text: "Experience Preferred: 1 year of relevant work experience". But in a list, it might be better as a single line. I'll just put it as is. Actually, rule: "Preserve ALL substantive information; do NOT invent or summarize away detail." So I should keep the exact text "Experience Preferred: 1 year of relevant work experience". I'll put it as an `

      ` item. Let's draft:

      About the role

      This position provides advanced clinical support to physicians and nursing staff, ensuring the delivery of high-quality, timely patient care. It is a vital member of the care team, aligned with organizational mission, vision, and strategic goals.

      Responsibilities

      • Provide advanced clinical support to healthcare professionals
      • Assist in delivering efficient, high-quality patient care
      • Support organizational mission and strategic objectives

      Qualifications

      • High school diploma or GED
      • Current Texas EMT-P License or National Registry EMT-P Certification
      • Basic Life Support (BLS) Certification
      • Advanced Cardio Life Support (ACLS) Certification
      • Pediatric Advanced Life Support (PALS) Certification within 90 days of hire
      • Experience Preferred: 1 year of relevant work experience

      Check if any section has placeholder/filler. No. Check if I'm repeating job title. No job title in input. Check if I have Pay/Schedule/Benefits. No. Check if I removed boilerplate. None present. One thing