Jobs · Healthcare · Oregon

Travel Pharmacist - $2,669 per week

Trustaff · Lebanon, OR · 2 days ago
On-siteHealthcareInternship
The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and apply the rules. First, I need to identify the sections that have real, specific content. The posting includes: - Job details (specialty, discipline, start date, duration, hours, shift, employment type) - Job description (what a Pharmacist does) - About Trustaff Allied (company info) - Benefits list Rules: - Use

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 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") - 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 Let me structure: 1. Job Details: Could be a section "About the role" or "Job Details". The posting has specific details: specialty, discipline, start date, duration, hours per week, shift, employment type. I'll create a section "About the role" with a paragraph summarizing these details, maybe a list. 2. Job Description: The paragraph describing what a Pharmacist does. Could be "Responsibilities" or "About the role". Since it's a description of the role, I'll use "Responsibilities" as a heading with a paragraph. 3. About Trustaff Allied: This is company info. Could be "About the company" but the allowed headings are limited: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About the company" is not in the list. However, the rule says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". The "e.g." suggests these are examples, but we should stick to those. The posting has "About Trustaff Allied" which is company description. I could fold it into a paragraph under "About the role" or create a section "About the company"? But the rule says use those headings. Maybe we can use "About the role" for the job details and description, and "Benefits" for benefits. The company info might be considered boilerplate? But it's specific to the agency. The rule says remove boilerplate, but this is specific to Trustaff Allied. However, the user said "Preserve ALL substantive information". I think we should include it. Perhaps under a heading "About the company" but not in the example list. The rule 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." meaning for example. I think we can use other relevant headings. But to be safe, maybe we can incorporate company info into a paragraph under "About the role" or create a section "About the agency". However, the instruction: "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 we can fold minor metadata into a short

    . The company description is not minor metadata; it's substantive. I'll create a section "About the company" with

    but the example list doesn't include it. The rule says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It might be that we should only use those headings. But the posting doesn't have Requirements, Qualifications, Skills, Pay, Schedule (except shift details). It has Benefits. So we can have: - About the role (including job details and description) - Benefits But the company info is separate. Could be part of "About the role"? Might be odd. Alternatively, we can have a section "About the agency" but not in the list. I think it's okay to use a heading not in the example if it's appropriate. The rule says "use

    for section headings (e.g. ...)" meaning those are typical, but not exhaustive. I'll include "About the agency" as a heading. But the user said: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". The company info is real and specific. Let's structure: - About the role: includes job details (specialty, discipline, start date, duration, hours, shift, employment type) and the description of pharmacist duties. - About the agency: the Trustaff Allied description. - Benefits: list of benefits. Pay: The posting says "Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's not a specific pay amount; it's a description of pay package. The rule says never create Pay section unless the posting actually states them. It states a pay package description but not a specific number. Could be considered a Pay section? The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It states pay package details, but it's vague. I think we can include a Pay section with that paragraph. But the rule also says "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The pay description says "tax-free stipend amount to be determined." That's like TBD. So maybe we should not create a Pay section. Instead, fold into About the role. Schedule: The posting has shift details: "Shift: 12 hours, rotating" and "36 hours per week". That's schedule info. Could create a Schedule section. But the rule says never create Schedule section unless the posting actually states them. It does state shift and hours. So we could create a Schedule section. However, the example headings include Schedule. I'll include a Schedule section with the shift details. But the rule: "Prefer a few substantive sections over many thin ones." So maybe combine schedule into About the role. Let's decide on sections: 1. About the role: includes job details (specialty, discipline, start date, duration, hours per week, employment type) and the pharmacist description. Also include shift? Could be separate Schedule. 2. Schedule: shift details (12 hours, rotating, 36 hours per week). That's specific. 3. About the agency: Trustaff Allied description. 4. Benefits: list of benefits. Pay: not specific, so omit. Job ID: fold into a short paragraph or drop. The rule says fold minor metadata into a short

    or drop it. I'll drop it. Now, write HTML. We need to use

    for headings,
    • for lists,

      for prose. Let's draft:

      About the role

      Specialty: Pharmacist

      Discipline: Allied Health Professional

      Start Date: ASAP

      Duration: 13 weeks

      Hours per week: 36

      Employment Type: Travel

      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.

      But better to use a list for the metadata? The rule says use
      • for any list of duties/requirements/benefits. The metadata is not a list of duties/requirements/benefits. It's key-value pairs. Could use

        for each. Or a definition list? But only allowed tags:

        ,
          ,
        • ,

          . So use

          for each line. Alternatively, combine into a single paragraph: "This travel Pharmacist position in Lebanon, Oregon starts ASAP for a 13-week duration, with 36 hours per week on 12-hour rotating shifts." That's more prose. But preserve ALL substantive information. So include all details. I'll do:

          About the role

          Specialty: Pharmacist

          Discipline: Allied Health Professional

          Start Date: ASAP

          Duration: 13 weeks

          Hours per week: 36

          Employment Type: Travel

          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.

          Schedule

          Shift: 12 hours, rotating

          36 hours per week

          About the agency

          Trustaff Allied is a travel healthcare agency with a traveler-first attitude. When you join the Trustaff family, you’re more than just a body filling a role—you're a vibrant individual with dreams and aspirations. As one of the nation's leading travel healthcare companies, your recruiter will work with you one-on-one to guide your career and help you achieve your goals.

          You decide when and where you want to work. Enjoy industry-leading pay, benefits, and bonuses. Experience new people and places. Grow your clinical skills and expand your experience. Travel healthcare lets you take your professional career to the next level while maintaining your flexibility and freedom. At Trustaff, we put you first, so you never have to compromise your work or pay. We are proud to have one of the highest nurse retention rates in the country.

          Some of the other reasons people choose us include:

          • Priority access to thousands of travel healthcare jobs
          • Industry-leading pay
          • Guaranteed weekly hours
          • Experienced recruiters
          • 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

          Benefits

          • Dental benefits
          • Medical benefits
          • Vision benefits
          • Guaranteed Hours
          • Referral bonus
          Note: The benefits list appears twice? In the posting, there is a "Benefits" section with a list, and also in the "About Trustaff Allied" section there is a list that includes "Comprehensive benefits, including medical, dental, and vision". The explicit "Benefits" section at the end lists: Dental benefits, Medical benefits, Vision benefits, Guaranteed Hours, Referral bonus. I'll include both? The rule says preserve ALL substantive information. The "About Trustaff Allied" includes a list of reasons to choose them, which includes

Similar jobs