Paramedic – Night Shift
` for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule).
- Use `- ` for lists of duties/requirements/benefits.
- Use `
` for prose.
- Do NOT repeat job title as heading (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.
- 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. **Analyze the Provided Content:**
The user gave me a snippet that looks like a job posting, but it's very minimal. Let me extract the actual content:
"Role Overview This position is a vital member of the care team, providing advanced clinical support to physicians and nursing staff to ensure the delivery of high-quality, timely patient care. The role supports the organization’s mission, vision, values, and strategic goals. Key Responsibilities Assist in clinical procedures and patient care activitiesSupport physicians and nurses with advanced clinical tasksContribute to a collaborative and efficient healthcare environment Qualifications & Skills High school diploma or GEDCurrent Texas EMT-P License or National Registry EMT-P CertificationBasic Life Support (BLS) CertificationAdvanced Cardio Life Support (ACLS) CertificationPediatric Advanced Life Support (PALS) Certification within 90 days of hirePreferred: 1 year of relevant work experience"
Let me parse this into structured sections:
- There's a "Role Overview" section with prose.
- "Key Responsibilities" - but the text runs together: "Assist in clinical procedures and patient care activitiesSupport physicians and nurses with advanced clinical tasksContribute to a collaborative and efficient healthcare environment" - this looks like bullet points that got concatenated. I should split them into meaningful list items, but I need to be careful not to invent details. The original says: "Assist in clinical procedures and patient care activities", "Support physicians and nurses with advanced clinical tasks", "Contribute to a collaborative and efficient healthcare environment". These are three responsibilities. I'll format as `
- `.
- "Qualifications & Skills" section: "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", "Preferred: 1 year of relevant work experience". These are qualifications/skills. I'll format as `
- `.
- No "About the role" distinct from "Role Overview"? The role overview is essentially "About the role". I'll use `
` for sections that have real content.
- No Benefits, Pay, Schedule mentioned → I must NOT create those sections.
- No Job ID / requisition numbers → fine, drop or fold into `
`.
- Remove boilerplate: none present in this snippet, but I'll ensure none is included.
- Must output ONLY HTML fragment, no ``, ``, no markdown fences.
Now, I need to map the headings allowed: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". But the rule says: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." And "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text... and never create Pay/Schedule/Benefits sections unless the posting actually states them."
So I should only include sections that have real content. Let's see:
- "Role Overview" content exists → I can use "About the role" or keep "Role Overview"? The example says "About the role" as an example heading. I could use `About the role
` but the content is "Role Overview This position is...". I think I should use a heading that matches the content naturally. The rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say I must use exactly those words, but those are examples. I'll use headings that fit the content. Probably "About the role" for the overview, "Responsibilities" for key responsibilities, "Qualifications" or "Qualifications & Skills" for the qualifications section. But I need to be careful: the posting has "Qualifications & Skills" as a combined heading in the text. I'll split or use "Qualifications & Skills" as a heading. However, the rule says "do NOT repeat the job title as a heading (the page already shows it)" - job title isn't really repeated here, but the snippet starts with "Role Overview". I'll assume the job title is elsewhere.
Let me re-read the snippet carefully. It starts with "Role Overview This position is...". That's the content. I should probably use `About the role
` or `Role Overview
`. The rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". I'll use "About the role" as the heading for the first prose section, since it's described as "Role Overview". But to be safe and precise, I could use "Role Overview" as the heading. The rule says "e.g." so it's not exclusive. I'll use headings that match the content exactly but as ``. Actually, the rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". I think I should use those exact labels when applicable, but if the content says "Role Overview", I can use that. However, the rule also says "do NOT repeat the job title as a heading (the page already shows it)". The job title isn't given here, so I won't worry.
Let me structure:
- The prose part: "This position is a vital member of the care team, providing advanced clinical support to physicians and nursing staff to ensure the delivery of high-quality, timely patient care. The role supports the organization’s mission, vision, values, and strategic goals." → This is "About the role" or "Role Overview". I'll use `About the role
` and then `
...
`. But wait, the rule says "Preserve ALL substantive information; do NOT invent or summarize away detail." So I should keep the exact text. I'll put the exact text in a ``.
- "Key Responsibilities Assist in clinical procedures and patient care activitiesSupport physicians and nurses with advanced clinical tasksContribute to a collaborative and efficient healthcare environment" → I'll split into three `
- ` items. The headings: "Responsibilities" is one of the example headings. I'll use `
Responsibilities
`.
- "Qualifications & Skills High school diploma or GEDCurrent Texas EMT-P License or National Registry EMT-P CertificationBasic Life Support (BLS) CertificationAdvanced Cardio Life Support (ACLS) CertificationPediatric Advanced Life Support (PALS) Certification within 90 days of hirePreferred: 1 year of relevant work experience" → I'll split into list items. Heading: "Qualifications & Skills" is an example heading, but the rule says use those as examples. I could use `Qualifications & Skills
` or `Qualifications
`. Since the content says "Qualifications & Skills", I'll use that. But note: the rule says "never emit a heading followed by filler/placeholder text". I must ensure each list item is substantive. The qualifications are specific: "High school diploma or GED", "Current Texas EMT-P License or National Registry EMT-P Certification", etc. These are real. I'll list them.
Now, check constraints:
- No Pay/Schedule/Benefits sections since not in posting.
- No boilerplate.
- Output only HTML fragment, no /, no markdown fences.
Let me construct the HTML:
About the role
This position is a vital member of the care team, providing advanced clinical support to physicians and nursing staff to ensure the delivery of high-quality, timely patient care. The role supports the organization’s mission, vision, values, and strategic goals.
Responsibilities
- Assist in clinical procedures and patient care activities
- Support physicians and nurses with advanced clinical tasks
- Contribute to a collaborative and efficient healthcare environment
Qualifications & Skills
- 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
- Preferred: 1 year of relevant work experience
Wait, the rule says: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It lists "Qualifications" and "Skills" as separate examples, but the content combines them as "Qualifications & Skills". I could split into `Qualifications
` and `Skills
`, but the content doesn't naturally separate them into two distinct sections with real content; it's a combined list. The rule says "include a section ONLY when the posting has real, specific content for it". If I split them, I might create a "Skills" section with no content or filler. Better to keep as "Qualifications & Skills" or just "Qualifications". I'll use "Qualifications & Skills" as the heading since that's what the posting uses, and it has real content.
Also, note: "Do NOT repeat the job title as a heading (the page already shows it)" - the posting doesn't have a job title in the snippet, so fine.
"Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." - none present.
"Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." - none in snippet.
"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
` for prose. - Do NOT repeat job title as heading (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. - 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. **Analyze the Provided Content:** The user gave me a snippet that looks like a job posting, but it's very minimal. Let me extract the actual content: "Role Overview This position is a vital member of the care team, providing advanced clinical support to physicians and nursing staff to ensure the delivery of high-quality, timely patient care. The role supports the organization’s mission, vision, values, and strategic goals. Key Responsibilities Assist in clinical procedures and patient care activitiesSupport physicians and nurses with advanced clinical tasksContribute to a collaborative and efficient healthcare environment Qualifications & Skills High school diploma or GEDCurrent Texas EMT-P License or National Registry EMT-P CertificationBasic Life Support (BLS) CertificationAdvanced Cardio Life Support (ACLS) CertificationPediatric Advanced Life Support (PALS) Certification within 90 days of hirePreferred: 1 year of relevant work experience" Let me parse this into structured sections: - There's a "Role Overview" section with prose. - "Key Responsibilities" - but the text runs together: "Assist in clinical procedures and patient care activitiesSupport physicians and nurses with advanced clinical tasksContribute to a collaborative and efficient healthcare environment" - this looks like bullet points that got concatenated. I should split them into meaningful list items, but I need to be careful not to invent details. The original says: "Assist in clinical procedures and patient care activities", "Support physicians and nurses with advanced clinical tasks", "Contribute to a collaborative and efficient healthcare environment". These are three responsibilities. I'll format as `
- `.
- "Qualifications & Skills" section: "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", "Preferred: 1 year of relevant work experience". These are qualifications/skills. I'll format as `
- `.
- No "About the role" distinct from "Role Overview"? The role overview is essentially "About the role". I'll use `
` for sections that have real content. - No Benefits, Pay, Schedule mentioned → I must NOT create those sections. - No Job ID / requisition numbers → fine, drop or fold into `
`. - Remove boilerplate: none present in this snippet, but I'll ensure none is included. - Must output ONLY HTML fragment, no ``, ``, no markdown fences. Now, I need to map the headings allowed: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". But the rule says: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." And "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text... and never create Pay/Schedule/Benefits sections unless the posting actually states them." So I should only include sections that have real content. Let's see: - "Role Overview" content exists → I can use "About the role" or keep "Role Overview"? The example says "About the role" as an example heading. I could use `
About the role
` but the content is "Role Overview This position is...". I think I should use a heading that matches the content naturally. The rule says "usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say I must use exactly those words, but those are examples. I'll use headings that fit the content. Probably "About the role" for the overview, "Responsibilities" for key responsibilities, "Qualifications" or "Qualifications & Skills" for the qualifications section. But I need to be careful: the posting has "Qualifications & Skills" as a combined heading in the text. I'll split or use "Qualifications & Skills" as a heading. However, the rule says "do NOT repeat the job title as a heading (the page already shows it)" - job title isn't really repeated here, but the snippet starts with "Role Overview". I'll assume the job title is elsewhere. Let me re-read the snippet carefully. It starts with "Role Overview This position is...". That's the content. I should probably use `
About the role
` or `Role Overview
`. The rule says "usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". I'll use "About the role" as the heading for the first prose section, since it's described as "Role Overview". But to be safe and precise, I could use "Role Overview" as the heading. The rule says "e.g." so it's not exclusive. I'll use headings that match the content exactly but as `
`. Actually, the rule says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". I think I should use those exact labels when applicable, but if the content says "Role Overview", I can use that. However, the rule also says "do NOT repeat the job title as a heading (the page already shows it)". The job title isn't given here, so I won't worry. Let me structure: - The prose part: "This position is a vital member of the care team, providing advanced clinical support to physicians and nursing staff to ensure the delivery of high-quality, timely patient care. The role supports the organization’s mission, vision, values, and strategic goals." → This is "About the role" or "Role Overview". I'll use `
About the role
` and then `...
`. But wait, the rule says "Preserve ALL substantive information; do NOT invent or summarize away detail." So I should keep the exact text. I'll put the exact text in a ``. - "Key Responsibilities Assist in clinical procedures and patient care activitiesSupport physicians and nurses with advanced clinical tasksContribute to a collaborative and efficient healthcare environment" → I'll split into three `
- ` items. The headings: "Responsibilities" is one of the example headings. I'll use `
Responsibilities
`. - "Qualifications & Skills High school diploma or GEDCurrent Texas EMT-P License or National Registry EMT-P CertificationBasic Life Support (BLS) CertificationAdvanced Cardio Life Support (ACLS) CertificationPediatric Advanced Life Support (PALS) Certification within 90 days of hirePreferred: 1 year of relevant work experience" → I'll split into list items. Heading: "Qualifications & Skills" is an example heading, but the rule says use those as examples. I could use `Qualifications & Skills
` or `Qualifications
`. Since the content says "Qualifications & Skills", I'll use that. But note: the rule says "never emit a heading followed by filler/placeholder text". I must ensure each list item is substantive. The qualifications are specific: "High school diploma or GED", "Current Texas EMT-P License or National Registry EMT-P Certification", etc. These are real. I'll list them. Now, check constraints: - No Pay/Schedule/Benefits sections since not in posting. - No boilerplate. - Output only HTML fragment, no /, no markdown fences. Let me construct the HTML:About the role
This position is a vital member of the care team, providing advanced clinical support to physicians and nursing staff to ensure the delivery of high-quality, timely patient care. The role supports the organization’s mission, vision, values, and strategic goals.
Responsibilities
- Assist in clinical procedures and patient care activities
- Support physicians and nurses with advanced clinical tasks
- Contribute to a collaborative and efficient healthcare environment
Qualifications & Skills
- 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
- Preferred: 1 year of relevant work experience
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It lists "Qualifications" and "Skills" as separate examples, but the content combines them as "Qualifications & Skills". I could split into `
Qualifications
` and `Skills
`, but the content doesn't naturally separate them into two distinct sections with real content; it's a combined list. The rule says "include a section ONLY when the posting has real, specific content for it". If I split them, I might create a "Skills" section with no content or filler. Better to keep as "Qualifications & Skills" or just "Qualifications". I'll use "Qualifications & Skills" as the heading since that's what the posting uses, and it has real content. Also, note: "Do NOT repeat the job title as a heading (the page already shows it)" - the posting doesn't have a job title in the snippet, so fine. "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a shortor drop it." - none present. "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." - none in snippet. "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
- `.
- No "About the role" distinct from "Role Overview"? The role overview is essentially "About the role". I'll use `