Travel Pharmacist - $2,738 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 (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, application instructions
- Include section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD")
- Never create Pay/Schedule/Benefits sections unless posting actually states them
- Prefer few substantive sections over many thin ones
- Output ONLY HTML fragment — no /, no markdown code fences
Now, let's structure:
The job details (specialty, discipline, start date, duration, hours, shift, employment type) are metadata. Could be a short
or a list. Since they are specific, I'll include them in a "Job Details" section or fold into a paragraph. The rules say fold minor metadata into short
or drop it. But these are substantive details about the assignment. I think a "Job Details" section with a list is appropriate, but the allowed headings are specific: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Job Details" is not in that list. However, the rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". The "e.g." suggests those are examples, not exhaustive. But the instruction: "include a section ONLY when the posting has real, specific content for it". I think we can create a heading like "Assignment Details" or "Job Details". But to be safe, maybe incorporate into "About the role" or a paragraph.
Better: The posting has a "Job Description & Requirements" section. The description is about the role. The requirements are not explicitly listed; the description includes duties. There's no separate requirements list. The "About Trustaff Allied" is company info. Benefits are listed.
I'll create sections:
- About the role (for the description)
- Benefits (for the benefits list)
- Maybe "Assignment Details" for the metadata (start date, duration, hours, shift). But the rules say "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." The metadata includes start date, duration, hours, shift. That's not minor; it's important. However, the allowed headings don't include "Assignment Details". Could use "Schedule" for shift/hours? Schedule heading is allowed. The posting says "Shift: 8 hours, days" and "40 hours per week". That could be Schedule. Also "Duration: 24 weeks" and "Start Date: 11/09/2026" could be part of Schedule or Assignment Details.
But the rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states shift and hours, so Schedule is appropriate. Pay is mentioned: "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 a Pay section. However, it says "tax-free stipend amount to be determined" - that's placeholder? It says "to be determined". The rule: never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "to be determined" is similar to TBD. So maybe we should not create a Pay section because the pay is not specified. But the posting does mention pay package based on shifts and hours, but stipend TBD. That's somewhat substantive but ends with TBD. I think we should include a Pay section with the info given, but not if it's just TBD. The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state pay package based on shifts and hours, but stipend TBD. That's stating something. However, the example of filler includes "TBD". So maybe we should not create a Pay section. But the posting also says "Industry-leading pay" in benefits. That's vague.
Let's examine the content:
- Job Description: "As a Pharmacist, you will dispense prescription medications to patients and offer expertise in the safe use of prescriptions. They also may conduct health and wellness screenings, provide immunizations, oversee the medications given to patients, and provide advice on healthy lifestyles." That's responsibilities.
- Requirements: Not explicitly listed. The posting says "Specialty: Pharmacist Discipline: Allied Health Professional". That's more metadata.
- About Trustaff Allied: company description.
- Benefits: listed as bullet points: Dental benefits, Medical benefits, Vision benefits, Guaranteed Hours, Referral bonus. Also in the company description: "Comprehensive benefits, including medical, dental, and vision", "401k with employer match", "Assistance with travel, compliance, and housing", "Great bonuses for completions, referring friends, and more". So benefits are substantive.
- 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." That's a pay detail but stipend TBD. Also "Industry-leading pay" in benefits. I think we can include a Pay section with the given info, but avoid placeholder. The rule says "never emit a heading followed by filler/placeholder text". If we include Pay, we must have real content. The content is "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 not entirely filler; it describes the basis. But "to be determined" is placeholder. However, the posting includes it. I think we should include it as a paragraph under Pay.
- Schedule: "Shift: 8 hours, days", "40 hours per week", "Duration: 24 weeks", "Start Date: 11/09/2026". That's schedule details.
- Job ID: "Trustaff Allied Job ID #2210791." Should be folded into a short
or dropped. I'll drop it or include in a metadata paragraph.
The rules: "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."
So I'll create a short paragraph for metadata: start date, duration, hours, shift, employment type, job ID maybe.
But the user wants semantic HTML with sections. I'll create sections for:
1. About the role (description)
2. Responsibilities (could be same as description, but description is prose. Could make a list of duties from the description.)
3. Schedule (shift, hours, duration, start date)
4. Pay (pay package details)
5. Benefits (list)
6. About Trustaff Allied (company description)
But the allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About Trustaff Allied" is not in the list, but it's company info. Could be "About the Company" but not listed. The rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests we can use other headings if needed. But to be safe, maybe incorporate company info into a paragraph or omit? The posting includes a substantial "About Trustaff Allied" section. It's substantive. I'll include it as a section with heading "About Trustaff Allied". The rules don't forbid other headings; they give examples. The instruction: "include a section ONLY when the posting has real, specific content for it". So I can create a heading "About Trustaff Allied".
But the user might expect only the example headings. However, the instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say "only these". So I'll use appropriate headings.
Let's structure:
- About the role
As a Pharmacist, you will dispense prescription medications to patients and offer expertise in the safe use of prescriptions. They also may conduct health and wellness screenings, provide immunizations, oversee the medications given to patients, and provide advice on healthy lifestyles.
- Responsibilities
- Dispense prescription medications to patients
- Offer expertise in the safe use of prescriptions
- Conduct health and wellness screenings
- Provide immunizations
- Oversee medications given to patients
- Provide advice on healthy lifestyles
But the description is prose; we can keep as prose under About the role, and also list responsibilities. The rules: "Use - for any list of duties/requirements/benefits, and
for prose." The description is prose, but it enumerates duties. Could convert to list. However, "Preserve ALL substantive information; do NOT invent or summarize away detail." Converting to list is okay as long as we preserve detail. But the description says "They also may conduct..." which is a bit vague. I'll keep as prose under About the role, and maybe not duplicate.
Better: Use About the role for the prose description. Then Responsibilities as a list extracted from that prose. But that duplicates. The rules don't forbid duplication but prefer not to. I'll just have About the role with the prose, and not a separate Responsibilities section unless there is a distinct list. The posting doesn't have a separate responsibilities list; it's in the description. So I'll just have About the role.
-
Schedule
- Start date: 11/09/2026
- Duration: 24 weeks
- Hours per week: 40
- Shift: 8 hours, days
- Employment type: Travel
- 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.
- Benefits
- Dental benefits
- Medical benefits
- Vision benefits
- Guaranteed hours
- Referral bonus
- 401k with employer match
- Assistance with travel, compliance, and housing
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, application instructions - Include section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") - Never create Pay/Schedule/Benefits sections unless posting actually states them - Prefer few substantive sections over many thin ones - Output ONLY HTML fragment — no /, no markdown code fences Now, let's structure: The job details (specialty, discipline, start date, duration, hours, shift, employment type) are metadata. Could be a short
or a list. Since they are specific, I'll include them in a "Job Details" section or fold into a paragraph. The rules say fold minor metadata into short
or drop it. But these are substantive details about the assignment. I think a "Job Details" section with a list is appropriate, but the allowed headings are specific: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Job Details" is not in that list. However, the rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". The "e.g." suggests those are examples, not exhaustive. But the instruction: "include a section ONLY when the posting has real, specific content for it". I think we can create a heading like "Assignment Details" or "Job Details". But to be safe, maybe incorporate into "About the role" or a paragraph. Better: The posting has a "Job Description & Requirements" section. The description is about the role. The requirements are not explicitly listed; the description includes duties. There's no separate requirements list. The "About Trustaff Allied" is company info. Benefits are listed. I'll create sections: - About the role (for the description) - Benefits (for the benefits list) - Maybe "Assignment Details" for the metadata (start date, duration, hours, shift). But the rules say "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." The metadata includes start date, duration, hours, shift. That's not minor; it's important. However, the allowed headings don't include "Assignment Details". Could use "Schedule" for shift/hours? Schedule heading is allowed. The posting says "Shift: 8 hours, days" and "40 hours per week". That could be Schedule. Also "Duration: 24 weeks" and "Start Date: 11/09/2026" could be part of Schedule or Assignment Details. But the rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states shift and hours, so Schedule is appropriate. Pay is mentioned: "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 a Pay section. However, it says "tax-free stipend amount to be determined" - that's placeholder? It says "to be determined". The rule: never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "to be determined" is similar to TBD. So maybe we should not create a Pay section because the pay is not specified. But the posting does mention pay package based on shifts and hours, but stipend TBD. That's somewhat substantive but ends with TBD. I think we should include a Pay section with the info given, but not if it's just TBD. The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state pay package based on shifts and hours, but stipend TBD. That's stating something. However, the example of filler includes "TBD". So maybe we should not create a Pay section. But the posting also says "Industry-leading pay" in benefits. That's vague. Let's examine the content: - Job Description: "As a Pharmacist, you will dispense prescription medications to patients and offer expertise in the safe use of prescriptions. They also may conduct health and wellness screenings, provide immunizations, oversee the medications given to patients, and provide advice on healthy lifestyles." That's responsibilities. - Requirements: Not explicitly listed. The posting says "Specialty: Pharmacist Discipline: Allied Health Professional". That's more metadata. - About Trustaff Allied: company description. - Benefits: listed as bullet points: Dental benefits, Medical benefits, Vision benefits, Guaranteed Hours, Referral bonus. Also in the company description: "Comprehensive benefits, including medical, dental, and vision", "401k with employer match", "Assistance with travel, compliance, and housing", "Great bonuses for completions, referring friends, and more". So benefits are substantive. - 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." That's a pay detail but stipend TBD. Also "Industry-leading pay" in benefits. I think we can include a Pay section with the given info, but avoid placeholder. The rule says "never emit a heading followed by filler/placeholder text". If we include Pay, we must have real content. The content is "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 not entirely filler; it describes the basis. But "to be determined" is placeholder. However, the posting includes it. I think we should include it as a paragraph under Pay. - Schedule: "Shift: 8 hours, days", "40 hours per week", "Duration: 24 weeks", "Start Date: 11/09/2026". That's schedule details. - Job ID: "Trustaff Allied Job ID #2210791." Should be folded into a short
or dropped. I'll drop it or include in a metadata paragraph. The rules: "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." So I'll create a short paragraph for metadata: start date, duration, hours, shift, employment type, job ID maybe. But the user wants semantic HTML with sections. I'll create sections for: 1. About the role (description) 2. Responsibilities (could be same as description, but description is prose. Could make a list of duties from the description.) 3. Schedule (shift, hours, duration, start date) 4. Pay (pay package details) 5. Benefits (list) 6. About Trustaff Allied (company description) But the allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About Trustaff Allied" is not in the list, but it's company info. Could be "About the Company" but not listed. The rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests we can use other headings if needed. But to be safe, maybe incorporate company info into a paragraph or omit? The posting includes a substantial "About Trustaff Allied" section. It's substantive. I'll include it as a section with heading "About Trustaff Allied". The rules don't forbid other headings; they give examples. The instruction: "include a section ONLY when the posting has real, specific content for it". So I can create a heading "About Trustaff Allied".
But the user might expect only the example headings. However, the instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say "only these". So I'll use appropriate headings.
Let's structure:
- About the role
About the role
As a Pharmacist, you will dispense prescription medications to patients and offer expertise in the safe use of prescriptions. They also may conduct health and wellness screenings, provide immunizations, oversee the medications given to patients, and provide advice on healthy lifestyles.
-Responsibilities
- Dispense prescription medications to patients
- Offer expertise in the safe use of prescriptions
- Conduct health and wellness screenings
- Provide immunizations
- Oversee medications given to patients
- Provide advice on healthy lifestyles
- for any list of duties/requirements/benefits, and
for prose." The description is prose, but it enumerates duties. Could convert to list. However, "Preserve ALL substantive information; do NOT invent or summarize away detail." Converting to list is okay as long as we preserve detail. But the description says "They also may conduct..." which is a bit vague. I'll keep as prose under About the role, and maybe not duplicate. Better: Use About the role for the prose description. Then Responsibilities as a list extracted from that prose. But that duplicates. The rules don't forbid duplication but prefer not to. I'll just have About the role with the prose, and not a separate Responsibilities section unless there is a distinct list. The posting doesn't have a separate responsibilities list; it's in the description. So I'll just have About the role. -
Schedule
- Start date: 11/09/2026
- Duration: 24 weeks
- Hours per week: 40
- Shift: 8 hours, days
- Employment type: Travel
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.
-Benefits
- Dental benefits
- Medical benefits
- Vision benefits
- Guaranteed hours
- Referral bonus
- 401k with employer match
- Assistance with travel, compliance, and housing