Travel Pharmacist - $3,439 per week
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.
- 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.
- 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.
Now, map content to sections:
- "About the role" could cover the description paragraph and maybe the highlights? But highlights are more like benefits or work environment. Could be "About the role" for description, "Responsibilities" for duties? The description says "As a Retail Pharmacist, you will oversee daily pharmacy operations, ensure patient safety, and provide medication counseling. Your collaboration with healthcare professionals and pharmacy technicians will enhance patient care." That's responsibilities. Also "Enjoy a flexible work schedule that supports work-life balance." That's schedule/benefits.
- "Highlights" list: collaborative work, flexible weekday and weekend shifts, supportive team environment. Could be under "Benefits" or "Schedule". Since they are highlights, maybe a "Highlights" section? But the allowed headings are specific: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Highlights" not in list. Could map to Benefits or Schedule. Flexible shifts -> Schedule. Collaborative work and supportive team -> Benefits? Might create a "Benefits" section with those.
- "Requirements" list: CPR Certification, Pharmacist License, EMR System, Background Check, MinExperienceRequired. That's clearly Requirements.
- Pay package info: "Pay package is based on 8 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's Pay information, but it's vague: "tax-free stipend amount to be determined." The rule says never create Pay section unless the posting actually states them. It does state pay package details, albeit not a specific number. It says "Pay package is based on 8 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That is a statement about pay. Should I include a Pay section? The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state pay package basis. But it's not a specific salary. However, it's substantive information about pay structure. I think include a Pay section with that info.
- Schedule: "40 hours per week", "Shift: 8 hours, days", "flexible weekday and weekend shifts". That's schedule info. Could create a Schedule section.
- Benefits: The highlights include collaborative work, flexible shifts, supportive team. Also "Enjoy a flexible work schedule that supports work-life balance." That's benefits/schedule. Could create a Benefits section with those.
- About Slate Healthcare: company description. Could be "About the company" but not in allowed headings. The allowed headings are only those listed. The rule says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says "e.g." meaning those are examples, but likely we should stick to those. The company description might not fit any. Could fold into a short
at the end or omit? The rule: "Preserve ALL substantive information". The company description is substantive about the employer. But the allowed headings don't include "About the company". Could we use "About the role"? Not appropriate. Maybe we can include it as a paragraph without a heading? The rule says "include a section ONLY when the posting has real, specific content for it". Could create a section "About the company" but not in the example list. 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, but says "e.g." So we can use other headings if needed. However, the rule also says "Prefer a few substantive sections over many thin ones." So maybe we can include an "About the company" section. But the user might expect only those headings. I'll include it as a section with heading "About Slate Healthcare" or "About the company". But the rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It might be safer to use only those. The company description could be placed under "About the role"? Not really. Could be a separate
at the end without heading? The rule says "Output ONLY the HTML fragment". It doesn't forbid plain paragraphs without headings. But the structure expects sections. I think I'll include a section "About the company" with the description.
But let's see the example: they gave a list of example headings. The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say "only these". So I can use other headings if needed. However, the rule "include a section ONLY when the posting has real, specific content for it" applies. The company description is real content. So I'll add a section "About Slate Healthcare".
Now, Job ID: "Slate Healthcare Job ID #7552ccde-0d35-4418-b076-22e6937783cb." Should fold into a short
or drop. I'll include it in a paragraph maybe at the end of the posting or in a metadata paragraph.
Start date, duration, hours, shift, employment type: these are details about the role. Could be in "About the role" or "Schedule". I'll include them in "About the role" as a list or paragraph.
Let's structure:
1. About the role: includes description paragraph, plus details like specialty, discipline, start date, duration, hours per week, shift, employment type. Could be a paragraph and a list.
2. Responsibilities: from description: oversee daily pharmacy operations, ensure patient safety, provide medication counseling, collaborate with healthcare professionals and pharmacy technicians.
3. Requirements: list of requirements.
4. Benefits: highlights: collaborative work with healthcare providers, flexible weekday and weekend shifts, supportive team environment, flexible work schedule supporting work-life balance.
5. Pay: pay package details.
6. Schedule: shift details (8 hours, days, 40 hours/week). But schedule info already in About the role. Could separate.
7. About Slate Healthcare: company description.
But we must avoid duplication. The schedule info appears in multiple places. I'll consolidate.
Let's draft HTML.
First, About the role:
About the role
As a Retail Pharmacist, you will oversee daily pharmacy operations, ensure patient safety, and provide medication counseling. Your collaboration with healthcare professionals and pharmacy technicians will enhance patient care. Enjoy a flexible work schedule that supports work-life balance.
- Specialty: Pharmacist
- Discipline: Allied Health Professional
- Start Date: 11/02/2026
- Duration: 13 weeks
- Hours per week: 40
- Shift: 8 hours, days
- Employment Type: Travel
But the description already includes some of that. The list is metadata. Good.
Responsibilities:
Responsibilities
- Oversee daily pharmacy operations
- Ensure patient safety
- Provide medication counseling
- Collaborate with healthcare professionals and pharmacy technicians to enhance patient care
Requirements:
Requirements
- CPR Certification
- Pharmacist License
- EMR System proficiency
- Background Check
- Minimum experience required
Benefits:
Benefits
- Collaborative work with healthcare providers
- Flexible weekday and weekend shifts
- Supportive team environment
- Flexible work schedule supporting work-life balance
Pay:
Pay
Pay package is based on 8 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined.
Schedule: Could be separate but already covered in About the role and Pay. Might not need separate Schedule section. The rule says never create Schedule section unless posting actually states them. It does state shift and hours. But we already have that in About the role. Could create a Schedule section with shift details. But to avoid thin sections, maybe omit Schedule section and keep in About the role.
About Slate Healthcare:
About Slate Healthcare
Slate Healthcare is a premier travel healthcare staffing agency, connecting healthcare professionals with thousands of opportunities at top-tier hospitals and facilities across the country.
We’re committed to supporting nurses and allied health professionals in building stable, fulfilling careers—while embracing the freedom and excitement that comes with travel. Our goal is simple: to offer flexibility, competitive pay, and personalized placements that align with each clinician’s lifestyle and career goals.
At Slate, we empower our professionals to choose when and where they work, while ensuring they receive the highest compensation possible—because we believe that exceptional care starts with empowered caregivers.
Job ID: include as a paragraph maybe at the end of About the role or separate. I'll add a paragraph after About the role or at the end.
Job ID: 7552ccde-0d35-4418-b076-22e6937783cb
But the rule: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short or drop it." So I'll fold into a short
at the end of the fragment.
Now, check for any boilerplate: The original has "Slate Healthcare is seeking a travel Pharmacist for a travel job in Bandon, Oregon." That's the job title and location. The page already shows title, but location might be important. Could include location in About
for prose. - Do NOT repeat job title as heading. - 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. - 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. Now, map content to sections: - "About the role" could cover the description paragraph and maybe the highlights? But highlights are more like benefits or work environment. Could be "About the role" for description, "Responsibilities" for duties? The description says "As a Retail Pharmacist, you will oversee daily pharmacy operations, ensure patient safety, and provide medication counseling. Your collaboration with healthcare professionals and pharmacy technicians will enhance patient care." That's responsibilities. Also "Enjoy a flexible work schedule that supports work-life balance." That's schedule/benefits. - "Highlights" list: collaborative work, flexible weekday and weekend shifts, supportive team environment. Could be under "Benefits" or "Schedule". Since they are highlights, maybe a "Highlights" section? But the allowed headings are specific: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Highlights" not in list. Could map to Benefits or Schedule. Flexible shifts -> Schedule. Collaborative work and supportive team -> Benefits? Might create a "Benefits" section with those. - "Requirements" list: CPR Certification, Pharmacist License, EMR System, Background Check, MinExperienceRequired. That's clearly Requirements. - Pay package info: "Pay package is based on 8 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's Pay information, but it's vague: "tax-free stipend amount to be determined." The rule says never create Pay section unless the posting actually states them. It does state pay package details, albeit not a specific number. It says "Pay package is based on 8 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That is a statement about pay. Should I include a Pay section? The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state pay package basis. But it's not a specific salary. However, it's substantive information about pay structure. I think include a Pay section with that info. - Schedule: "40 hours per week", "Shift: 8 hours, days", "flexible weekday and weekend shifts". That's schedule info. Could create a Schedule section. - Benefits: The highlights include collaborative work, flexible shifts, supportive team. Also "Enjoy a flexible work schedule that supports work-life balance." That's benefits/schedule. Could create a Benefits section with those. - About Slate Healthcare: company description. Could be "About the company" but not in allowed headings. The allowed headings are only those listed. The rule says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says "e.g." meaning those are examples, but likely we should stick to those. The company description might not fit any. Could fold into a short
at the end or omit? The rule: "Preserve ALL substantive information". The company description is substantive about the employer. But the allowed headings don't include "About the company". Could we use "About the role"? Not appropriate. Maybe we can include it as a paragraph without a heading? The rule says "include a section ONLY when the posting has real, specific content for it". Could create a section "About the company" but not in the example list. 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, but says "e.g." So we can use other headings if needed. However, the rule also says "Prefer a few substantive sections over many thin ones." So maybe we can include an "About the company" section. But the user might expect only those headings. I'll include it as a section with heading "About Slate Healthcare" or "About the company". But the rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It might be safer to use only those. The company description could be placed under "About the role"? Not really. Could be a separate
at the end without heading? The rule says "Output ONLY the HTML fragment". It doesn't forbid plain paragraphs without headings. But the structure expects sections. I think I'll include a section "About the company" with the description. But let's see the example: they gave a list of example headings. The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say "only these". So I can use other headings if needed. However, the rule "include a section ONLY when the posting has real, specific content for it" applies. The company description is real content. So I'll add a section "About Slate Healthcare". Now, Job ID: "Slate Healthcare Job ID #7552ccde-0d35-4418-b076-22e6937783cb." Should fold into a short
or drop. I'll include it in a paragraph maybe at the end of the posting or in a metadata paragraph. Start date, duration, hours, shift, employment type: these are details about the role. Could be in "About the role" or "Schedule". I'll include them in "About the role" as a list or paragraph. Let's structure: 1. About the role: includes description paragraph, plus details like specialty, discipline, start date, duration, hours per week, shift, employment type. Could be a paragraph and a list. 2. Responsibilities: from description: oversee daily pharmacy operations, ensure patient safety, provide medication counseling, collaborate with healthcare professionals and pharmacy technicians. 3. Requirements: list of requirements. 4. Benefits: highlights: collaborative work with healthcare providers, flexible weekday and weekend shifts, supportive team environment, flexible work schedule supporting work-life balance. 5. Pay: pay package details. 6. Schedule: shift details (8 hours, days, 40 hours/week). But schedule info already in About the role. Could separate. 7. About Slate Healthcare: company description. But we must avoid duplication. The schedule info appears in multiple places. I'll consolidate. Let's draft HTML. First, About the role:
About the role
As a Retail Pharmacist, you will oversee daily pharmacy operations, ensure patient safety, and provide medication counseling. Your collaboration with healthcare professionals and pharmacy technicians will enhance patient care. Enjoy a flexible work schedule that supports work-life balance.
- Specialty: Pharmacist
- Discipline: Allied Health Professional
- Start Date: 11/02/2026
- Duration: 13 weeks
- Hours per week: 40
- Shift: 8 hours, days
- Employment Type: Travel
Responsibilities
- Oversee daily pharmacy operations
- Ensure patient safety
- Provide medication counseling
- Collaborate with healthcare professionals and pharmacy technicians to enhance patient care
Requirements
- CPR Certification
- Pharmacist License
- EMR System proficiency
- Background Check
- Minimum experience required
Benefits
- Collaborative work with healthcare providers
- Flexible weekday and weekend shifts
- Supportive team environment
- Flexible work schedule supporting work-life balance
Pay
Pay package is based on 8 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined.
Schedule: Could be separate but already covered in About the role and Pay. Might not need separate Schedule section. The rule says never create Schedule section unless posting actually states them. It does state shift and hours. But we already have that in About the role. Could create a Schedule section with shift details. But to avoid thin sections, maybe omit Schedule section and keep in About the role. About Slate Healthcare:About Slate Healthcare
Slate Healthcare is a premier travel healthcare staffing agency, connecting healthcare professionals with thousands of opportunities at top-tier hospitals and facilities across the country.
We’re committed to supporting nurses and allied health professionals in building stable, fulfilling careers—while embracing the freedom and excitement that comes with travel. Our goal is simple: to offer flexibility, competitive pay, and personalized placements that align with each clinician’s lifestyle and career goals.
At Slate, we empower our professionals to choose when and where they work, while ensuring they receive the highest compensation possible—because we believe that exceptional care starts with empowered caregivers.
Job ID: include as a paragraph maybe at the end of About the role or separate. I'll add a paragraph after About the role or at the end.Job ID: 7552ccde-0d35-4418-b076-22e6937783cb
But the rule: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a shortor drop it." So I'll fold into a short
at the end of the fragment. Now, check for any boilerplate: The original has "Slate Healthcare is seeking a travel Pharmacist for a travel job in Bandon, Oregon." That's the job title and location. The page already shows title, but location might be important. Could include location in About