Per Diem Nurse Practitioner
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). 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. We need to preserve all substantive information, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions). So we need to strip out the EEO statement at end, also maybe the "Circadia Health is an Equal Opportunity Employer..." etc. Also remove any duplicated lines. We need sections: maybe "About the role" (the description), "Responsibilities" (What You’ll Do), "Qualifications" (Must-Have Qualifications and Nice-to-Haves), "Compensation & Perks" (Compensation & Perks). Also maybe "Location" but not required heading; could be part of About the role? The instruction says include a section only when posting has real, specific content for it. Location is given: Rutland, VT; Brattleboro, VT; Bennington, VT. Could be part of About the role or a separate section? Not listed as standard headings but we could include as part of About the role paragraph. Probably better to include location in About the role. We must not create Pay/Schedule/Benefits sections unless posting actually states them. There is a "Compensation & Perks" section with pay: $3,000 - $5,200 a month, per diem, 25+ visit per day, minimum 4-8 days/month, paid per visit model, travel support reimbursed per federal rate. So we can have a Benefits section? Actually "Compensation & Perks" is a heading we can use. The instruction list includes Benefits, Pay, Schedule as possible headings. We could combine compensation and perks into a Benefits section, or we could have a Pay section and a Benefits section. Since they gave both compensation and perks, we could have a Pay section for salary range and a Benefits section for per diem, travel support, tools, laptop, etc. But we need to avoid thin sections. Perhaps combine into one "Compensation & Perks" section using
Compensation & Perks
. That's not in the list but it's okay? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive. Probably we should stick to those examples. So we could use "Benefits" heading for compensation and perks. Or "Pay" heading for salary and "Benefits" for other perks. Let's see: they gave compensation: $3,000 - $5,200 a month. Also per diem, 25+ visit per day, minimum 4-8 days/month, opportunity to increase days based on patient demand, paid per visit model, travel support reimbursed per federal rate, tools that help: AI documentation, in-app training, integrated workflows; company laptop + mobile tools. Mission + autonomy etc. So we could have Pay: salary range. Benefits: per diem, travel support, tools, laptop, mission autonomy. Schedule: maybe mention minimum 4-8 days/month, opportunity to increase days, 25+ visit per day (that's more about workload than schedule). Could be schedule.
But we need to avoid thin sections. Perhaps better to have one "Compensation & Perks" section, even if not exactly in examples, but it's still a heading. The instruction says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are typical but not strictly limited. Safer to use those exact headings where applicable. Let's map:
- About the role: we have description about role and location.
- Responsibilities: "What You’ll Do" bullet list.
- Qualifications: "Must-Have Qualifications" and "Nice-to-Haves". Could combine into Qualifications section with subpoints? Could separate into Requirements and Qualifications? But we have Must-Have Qualifications and Nice-to-Haves. Could treat Must-Have as Requirements, Nice-to-Haves as Skills? Or Qualifications. The instruction list includes Requirements, Qualifications, Skills. We could use Requirements for must-have, Skills for nice-to-haves (tech-savvy, Spanish). But also there is "Certified and licensed Nurse Practitioner in VT; ANCC (or equivalent) in Adult/Family/Geriatric/Acute." etc. That's qualifications. Let's decide: Use Requirements for must-have qualifications, Skills for nice-to-haves (tech-savvy, Spanish). Or we could have Qualifications for must-have and Skills for nice-to-haves. The instruction list includes both Requirements and Qualifications; maybe they expect Requirements for mandatory, Qualifications for preferred? Not sure. Let's look at typical job postings: Requirements = mandatory, Qualifications = maybe also mandatory but sometimes used interchangeably. Nice-to-haves = Skills. We'll do:
- Requirements
for Must-Have Qualifications.
- Skills
for Nice-to-Haves (tech-savvy, Spanish).
- Benefits: we have compensation and perks. Could use Benefits heading for all compensation and perks. Or we could split Pay and Benefits. Let's do Benefits heading for compensation and perks (including salary range, per diem, travel support, tools, laptop, mission autonomy). That seems substantive.
- Schedule: we have mention of minimum 4-8 days/month, opportunity to increase days based on patient demand, per diem, 25+ visit per day (that's workload). Could be schedule. But we already put that in Benefits. Might be thin if we separate. Better to keep schedule out if not explicit. The posting does not give explicit schedule like "full-time", "part-time", "shift". It gives per visit model and minimum days. That's more about compensation. So we can skip Schedule section.
Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits.
Now we need to output HTML fragment only, no /, no markdown fences.
We need to use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: EEO statement, duplicated lines, application instructions (none). Also remove "Circadia Health is an Equal Opportunity Employer..." and the AI tools note.
Also remove "About Circadia Health" company description? That is substantive? It's about the company, not the role. The instruction says we should not repeat the job title as a heading, but we can include company description? It's not listed as a standard heading but could be part of About the role? The posting includes "About Circadia Health" then "About The Role". The company description is maybe not needed for the role but could be considered background. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the company description somewhere. Where to put? Could be a paragraph before About the role heading, maybe as a
without heading. Since we cannot add a heading for it unless we treat it as "About the company" but not in list. Better to include it as a
before the first heading. That's allowed: we can have prose outside sections. The instruction says use
for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but we should follow the pattern. We'll include a brief
with company description.
Now let's extract content.
Company description:
"About Circadia Health Circadia Health is a growth-stage healthcare AI company on a mission to prevent avoidable hospitalizations and transform senior-care operations. Our Circadia Intelligence Platform combines: Contactless sensing that monitors respiration and motion with medical-grade accuracy Native predictive models that detect 85% of preventable adverse events several days in advance Enterprise integrations that operationalize predictions directly inside EHR, care-coordination, billing, and compliance workflows Today, our technology touches 40,000+ post-acute patients daily across skilled-nursing, home-health, and home-care networks. We are backed by leading healthcare and AI investors and headquartered in El Segundo, CA."
We need to format as prose. Could break into sentences.
Now About The Role:
"About The Role Transform patient care with AI — at the bedside and in the home. As a Circadia Nurse Practitioner, you'll work across both our skilled nursing and Home Health AI Care programs, seeing patients first, acting on predictive health signals in real time, and coaching facility teams to turn data into earlier interventions that reduce preventable readmissions. In our SNF partner facilities, you'll round on new admits, facility-flagged patients, and Circadia alerts. In the home health setting, you'll bring that same proactive model directly into patients' homes, extending high-quality care beyond the walls of a facility. Throughout, you'll blend direct patient care with tech-to-bedside integration through hands-on training, live demos, and shadowed assessments. Location(s): Rutland, VTBrattleboro, VTBennington, VT"
Note there is missing commas between locations; we should preserve as given but maybe add commas for readability? We must not invent or summarize away detail, but we can format? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Adding punctuation could be considered altering but not adding info. Probably okay to keep as is but we can add commas to separate? Might be considered inventing. Safer to keep exactly as written: "Location(s): Rutland, VTBrattleboro, VTBennington, VT". That's weird but we keep.
Now Responsibilities (What You’ll Do):
List:
- Direct patient care: Conduct initial and follow-up assessments on flagged residents; initiate/adjust plans of care; complete consent; coordinate with facility providers.
- Tech → bedside integration: Train and coach staff at the point of care, standardize use of Circadia into clinical workflows.
- Data into action: Interpret trend-based insights, prioritize high-risk patients, and drive timely interventions to prevent decline.
- Close the loop: Complete documentation/charts within the same day
- High-volume rounding: Efficiently complete visits across designated SNFs (typically 25+/day where appropriate), focusing on new admits, facility-flagged patients, and Circadia alerts.
- Quality & product feedback: Surface field insights to improve workflows and tech integration in a clinical setting
- Mentor & collaborate: Support NP onboarding, share best practices, and partner with clinical ops/product teams.
- Regional flexibility: Cover SNF sites and patient homes within a 30–40 mile radius. For locations outside that radius, mileage and lodging are covered per company policy.
We need to put each as
- inside
. The colon after each heading is part of the text.
Now Requirements (Must-Have Qualifications):
List:
- Certified and licensed Nurse Practitioner in VT; ANCC (or equivalent) in Adult/Family/Geriatric/Acute.
- Eligible for Medicare participation; company bills on your behalf.
- 2+ years NP experience with complex adult populations; able to practice independently.
- Valid VT driver’s license; comfortable traveling locally.
- Thrives in a dynamic, evolving startup environment.
- English required
We need to keep each as - .
Now Skills (Nice-to-Haves):
- Tech-savvy: Google Suite, multiple EMRs, Slack, AI transcription/tools.
Requirements
for Must-Have Qualifications. -Skills
for Nice-to-Haves (tech-savvy, Spanish). - Benefits: we have compensation and perks. Could use Benefits heading for all compensation and perks. Or we could split Pay and Benefits. Let's do Benefits heading for compensation and perks (including salary range, per diem, travel support, tools, laptop, mission autonomy). That seems substantive. - Schedule: we have mention of minimum 4-8 days/month, opportunity to increase days based on patient demand, per diem, 25+ visit per day (that's workload). Could be schedule. But we already put that in Benefits. Might be thin if we separate. Better to keep schedule out if not explicit. The posting does not give explicit schedule like "full-time", "part-time", "shift". It gives per visit model and minimum days. That's more about compensation. So we can skip Schedule section. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits. Now we need to output HTML fragment only, no /, no markdown fences. We need to use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: EEO statement, duplicated lines, application instructions (none). Also remove "Circadia Health is an Equal Opportunity Employer..." and the AI tools note.
Also remove "About Circadia Health" company description? That is substantive? It's about the company, not the role. The instruction says we should not repeat the job title as a heading, but we can include company description? It's not listed as a standard heading but could be part of About the role? The posting includes "About Circadia Health" then "About The Role". The company description is maybe not needed for the role but could be considered background. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the company description somewhere. Where to put? Could be a paragraph before About the role heading, maybe as a
without heading. Since we cannot add a heading for it unless we treat it as "About the company" but not in list. Better to include it as a
before the first heading. That's allowed: we can have prose outside sections. The instruction says use
for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but we should follow the pattern. We'll include a brief
with company description.
Now let's extract content.
Company description:
"About Circadia Health Circadia Health is a growth-stage healthcare AI company on a mission to prevent avoidable hospitalizations and transform senior-care operations. Our Circadia Intelligence Platform combines: Contactless sensing that monitors respiration and motion with medical-grade accuracy Native predictive models that detect 85% of preventable adverse events several days in advance Enterprise integrations that operationalize predictions directly inside EHR, care-coordination, billing, and compliance workflows Today, our technology touches 40,000+ post-acute patients daily across skilled-nursing, home-health, and home-care networks. We are backed by leading healthcare and AI investors and headquartered in El Segundo, CA."
We need to format as prose. Could break into sentences.
Now About The Role:
"About The Role Transform patient care with AI — at the bedside and in the home. As a Circadia Nurse Practitioner, you'll work across both our skilled nursing and Home Health AI Care programs, seeing patients first, acting on predictive health signals in real time, and coaching facility teams to turn data into earlier interventions that reduce preventable readmissions. In our SNF partner facilities, you'll round on new admits, facility-flagged patients, and Circadia alerts. In the home health setting, you'll bring that same proactive model directly into patients' homes, extending high-quality care beyond the walls of a facility. Throughout, you'll blend direct patient care with tech-to-bedside integration through hands-on training, live demos, and shadowed assessments. Location(s): Rutland, VTBrattleboro, VTBennington, VT"
Note there is missing commas between locations; we should preserve as given but maybe add commas for readability? We must not invent or summarize away detail, but we can format? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Adding punctuation could be considered altering but not adding info. Probably okay to keep as is but we can add commas to separate? Might be considered inventing. Safer to keep exactly as written: "Location(s): Rutland, VTBrattleboro, VTBennington, VT". That's weird but we keep.
Now Responsibilities (What You’ll Do):
List:
- Direct patient care: Conduct initial and follow-up assessments on flagged residents; initiate/adjust plans of care; complete consent; coordinate with facility providers.
- Tech → bedside integration: Train and coach staff at the point of care, standardize use of Circadia into clinical workflows.
- Data into action: Interpret trend-based insights, prioritize high-risk patients, and drive timely interventions to prevent decline.
- Close the loop: Complete documentation/charts within the same day
- High-volume rounding: Efficiently complete visits across designated SNFs (typically 25+/day where appropriate), focusing on new admits, facility-flagged patients, and Circadia alerts.
- Quality & product feedback: Surface field insights to improve workflows and tech integration in a clinical setting
- Mentor & collaborate: Support NP onboarding, share best practices, and partner with clinical ops/product teams.
- Regional flexibility: Cover SNF sites and patient homes within a 30–40 mile radius. For locations outside that radius, mileage and lodging are covered per company policy.
We need to put each as
- inside
. The colon after each heading is part of the text.
Now Requirements (Must-Have Qualifications):
List:
- Certified and licensed Nurse Practitioner in VT; ANCC (or equivalent) in Adult/Family/Geriatric/Acute.
- Eligible for Medicare participation; company bills on your behalf.
- 2+ years NP experience with complex adult populations; able to practice independently.
- Valid VT driver’s license; comfortable traveling locally.
- Thrives in a dynamic, evolving startup environment.
- English required
We need to keep each as - .
Now Skills (Nice-to-Haves):
- Tech-savvy: Google Suite, multiple EMRs, Slack, AI transcription/tools.
for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: EEO statement, duplicated lines, application instructions (none). Also remove "Circadia Health is an Equal Opportunity Employer..." and the AI tools note. Also remove "About Circadia Health" company description? That is substantive? It's about the company, not the role. The instruction says we should not repeat the job title as a heading, but we can include company description? It's not listed as a standard heading but could be part of About the role? The posting includes "About Circadia Health" then "About The Role". The company description is maybe not needed for the role but could be considered background. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the company description somewhere. Where to put? Could be a paragraph before About the role heading, maybe as a
without heading. Since we cannot add a heading for it unless we treat it as "About the company" but not in list. Better to include it as a
before the first heading. That's allowed: we can have prose outside sections. The instruction says use
for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but we should follow the pattern. We'll include a brief
with company description. Now let's extract content. Company description: "About Circadia Health Circadia Health is a growth-stage healthcare AI company on a mission to prevent avoidable hospitalizations and transform senior-care operations. Our Circadia Intelligence Platform combines: Contactless sensing that monitors respiration and motion with medical-grade accuracy Native predictive models that detect 85% of preventable adverse events several days in advance Enterprise integrations that operationalize predictions directly inside EHR, care-coordination, billing, and compliance workflows Today, our technology touches 40,000+ post-acute patients daily across skilled-nursing, home-health, and home-care networks. We are backed by leading healthcare and AI investors and headquartered in El Segundo, CA." We need to format as prose. Could break into sentences. Now About The Role: "About The Role Transform patient care with AI — at the bedside and in the home. As a Circadia Nurse Practitioner, you'll work across both our skilled nursing and Home Health AI Care programs, seeing patients first, acting on predictive health signals in real time, and coaching facility teams to turn data into earlier interventions that reduce preventable readmissions. In our SNF partner facilities, you'll round on new admits, facility-flagged patients, and Circadia alerts. In the home health setting, you'll bring that same proactive model directly into patients' homes, extending high-quality care beyond the walls of a facility. Throughout, you'll blend direct patient care with tech-to-bedside integration through hands-on training, live demos, and shadowed assessments. Location(s): Rutland, VTBrattleboro, VTBennington, VT" Note there is missing commas between locations; we should preserve as given but maybe add commas for readability? We must not invent or summarize away detail, but we can format? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Adding punctuation could be considered altering but not adding info. Probably okay to keep as is but we can add commas to separate? Might be considered inventing. Safer to keep exactly as written: "Location(s): Rutland, VTBrattleboro, VTBennington, VT". That's weird but we keep. Now Responsibilities (What You’ll Do): List: - Direct patient care: Conduct initial and follow-up assessments on flagged residents; initiate/adjust plans of care; complete consent; coordinate with facility providers. - Tech → bedside integration: Train and coach staff at the point of care, standardize use of Circadia into clinical workflows. - Data into action: Interpret trend-based insights, prioritize high-risk patients, and drive timely interventions to prevent decline. - Close the loop: Complete documentation/charts within the same day - High-volume rounding: Efficiently complete visits across designated SNFs (typically 25+/day where appropriate), focusing on new admits, facility-flagged patients, and Circadia alerts. - Quality & product feedback: Surface field insights to improve workflows and tech integration in a clinical setting - Mentor & collaborate: Support NP onboarding, share best practices, and partner with clinical ops/product teams. - Regional flexibility: Cover SNF sites and patient homes within a 30–40 mile radius. For locations outside that radius, mileage and lodging are covered per company policy. We need to put each as
- . The colon after each heading is part of the text.
Now Requirements (Must-Have Qualifications):
List:
- Certified and licensed Nurse Practitioner in VT; ANCC (or equivalent) in Adult/Family/Geriatric/Acute.
- Eligible for Medicare participation; company bills on your behalf.
- 2+ years NP experience with complex adult populations; able to practice independently.
- Valid VT driver’s license; comfortable traveling locally.
- Thrives in a dynamic, evolving startup environment.
- English required
We need to keep each as
- . Now Skills (Nice-to-Haves): - Tech-savvy: Google Suite, multiple EMRs, Slack, AI transcription/tools.