Physical Therapy - 18996673

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info; remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a 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") and never create Pay/Schedule/Benefits sections unless posting actually states them. Prefer few substantive sections over many thin ones. We need to parse the posting. Posting: "Join Our Team as a Physical Therapist in Albuquerque, NM!** - **Exciting Opportunity**: Experience a thriving work environment that values your skills and dedication. **Shift Information**: Enjoy a balanced 8-hour day shift to maintain your work-life harmony. **Experience Required**: Open to candidates with any level of experience — new graduates are welcome! **Essential Certifications**: - General Certifications: ACLS, BLS/BCLS, PALS, NRP - Rehabilitation Certifications: ASHA, CHT, ACP Training **Onboarding Process**: - Complete necessary documentation with our partner before starting your assignment. - If you hold a compact license, please obtain a permanent one as soon as possible. - Permanent license required for South Carolina applicants. **Rehire Policy**: - Candidates who have worked perm/PRN within the last year at our partner will need to wait one year before reapplying. - For former travelers, please provide name and DOB to check rehire eligibility. **Start Date**: Be ready to begin on 9/14. **Requirements**: - Experience in a similar setting. - Must hold an active license. **Equipment**: All necessary equipment will be provided during the interview. **Parking**: Convenient parking will be arranged for your first day. **Dress Code**: Instructions will be provided during your first day information session. **Why Catalytic Solutions (CatSol)**: At CatSol, we connect dedicated therapists with rewarding assignments across the country. Enjoy competitive pay, seamless onboarding, and a supportive recruiter who’s with you every step of the way. Join us — where your expertise makes a difference every day." We need to extract sections: About the role (maybe "Exciting Opportunity" and description). Responsibilities? Not explicit. Requirements: "Experience in a similar setting. Must hold an active license." Also "Experience Required: Open to candidates with any level of experience — new graduates are welcome!" That's more like qualifications/experience. Also "Essential Certifications" list. "Onboarding Process". "Rehire Policy". "Start Date". "Equipment". "Parking". "Dress Code". "Why Catalytic Solutions (CatSol)" includes benefits: competitive pay, seamless onboarding, supportive recruiter. We need to decide which sections to output. The instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map content to these headings. We should not create sections that have no real content. We need to preserve all substantive info. We can combine some info into sections like "About the role" (exciting opportunity, shift information, start date). "Requirements" (experience, license). "Qualifications" (certifications). "Benefits" (competitive pay, seamless onboarding, supportive recruiter). "Onboarding Process" maybe could be part of Benefits or separate? But we have a heading list includes Onboarding? Not listed but we can create custom heading? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples but we can use other headings? Probably we should stick to those headings; but we can also create other headings if needed? It says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings for sections; we can also use other headings if needed but they gave examples. Safer to use those headings only. So we need to map content to those headings. We have: - About the role: could include exciting opportunity, shift information, start date, maybe equipment, parking, dress code? Those are logistical details. Could be part of About the role. - Responsibilities: Not explicitly given. Could we infer? Not given. So we should not create Responsibilities section if no specific content. - Requirements: "Experience in a similar setting. Must hold an active license." Also "Experience Required: Open to candidates with any level of experience — new graduates are welcome!" That's more like qualifications but could be part of Requirements. - Qualifications: Certifications list. - Skills: Not given. - Benefits: "competitive pay, seamless onboarding, supportive recruiter". Also maybe equipment, parking, dress code? Those are more logistical but could be benefits. - Pay: The posting mentions "competitive pay" but not specific amount. According to instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It says "competitive pay" is stated, so we can include Pay section? But they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "competitive pay". So we could include a Pay section with that phrase. However they also said prefer few substantive sections over many thin ones. So maybe we combine Pay into Benefits. - Schedule: Shift Information: "Enjoy a balanced 8-hour day shift". That's schedule info. So we could have Schedule section. Thus we could have sections: About the role, Requirements, Qualifications, Benefits (including pay, onboarding, equipment, parking, dress code, supportive recruiter), Schedule. But we need to avoid filler/placeholder text. All content is substantive. We need to use

  • for any list of duties/requirements/benefits. So for lists we should use
    • . For prose, use

      . We need to output only HTML fragment, no /, no markdown. Let's structure:

      About the role

      Exciting Opportunity: Experience a thriving work environment that values your skills and dedication.

      Shift Information: Enjoy a balanced 8-hour day shift to maintain your work-life harmony.

      Start Date: Be ready to begin on 9/14.

      Equipment: All necessary equipment will be provided during the interview.

      Parking: Convenient parking will be arranged for your first day.

      Dress Code: Instructions will be provided during your first day information session.

      But we might combine some into
      if they are list-like. However they are separate sentences; could be

      each. Alternatively we could make a

      for logistical items: Equipment, Parking, Dress Code. But they are not duties/requirements/benefits? They are benefits? Might be considered benefits. The instruction: Use
      • for any list of duties/requirements/benefits. So if we treat those as benefits, we could list them. But we also have Benefits section: competitive pay, seamless onboarding, supportive recruiter. We could combine all benefits into a
        . Let's think: We want few substantive sections. Maybe we can have: - About the role (exciting opportunity, shift, start date) - Requirements (experience, license) - Qualifications (certifications) - Benefits (pay, onboarding, equipment, parking, dress code, supportive recruiter) - Schedule (maybe already covered in About the role shift). Actually shift is schedule; we could put schedule in About the role. But we need to avoid duplication. Let's decide: Section About the role: includes exciting opportunity, shift information, start date. Section Requirements: experience in similar setting, must hold active license, open to any level (new graduates welcome). Actually that's more qualifications but okay. Section Qualifications: essential certifications list. Section Benefits: competitive pay, seamless onboarding, supportive recruiter, equipment provided, parking arranged, dress code instructions. We could also include Onboarding Process and Rehire Policy as part of Benefits or separate? They are substantive. Could be part of Benefits or maybe a separate section like "Additional Information". But we only have allowed headings list; we could put them under Benefits as well. But we need to preserve all substantive info. So we need to include Onboarding Process and Rehire Policy. We could add a section "Onboarding" but not in allowed headings. However we could treat it as part of Benefits? Might be okay but could be considered separate. Better to create a section "Onboarding Process" using

        even if not in examples? The instruction says "Use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive. So we can use other headings as needed, but we should follow the pattern. So we can create headings for Onboarding Process, Rehire Policy, etc. Thus we can have multiple sections: About the role, Requirements, Qualifications, Benefits, Onboarding Process, Rehire Policy, Schedule (if separate). But we need to avoid thin sections. However each of those has substantive content. Let's list all substantive content: - Exciting Opportunity: thriving work environment values skills and dedication. - Shift Information: balanced 8-hour day shift. - Experience Required: Open to any level — new graduates welcome. - Essential Certifications: General Certifications: ACLS, BLS/BCLS, PALS, NRP; Rehabilitation Certifications: ASHA, CHT, ACP Training. - Onboarding Process: Complete necessary documentation with partner before starting assignment. If you hold a compact license, please obtain a permanent one as soon as possible. Permanent license required for South Carolina applicants. - Rehire Policy: Candidates who have worked perm/PRN within the last year at our partner will need to wait one year before reapplying. For former travelers, please provide name and DOB to check rehire eligibility. - Start Date: Be ready to begin on 9/14. - Requirements: Experience in a similar setting. Must hold an active license. - Equipment: All necessary equipment will be provided during the interview. - Parking: Convenient parking will be arranged for your first day. - Dress Code: Instructions will be provided during your first day information session. - Why Catalytic Solutions (CatSol): At CatSol, we connect dedicated therapists with rewarding assignments across the country. Enjoy competitive pay, seamless onboarding, and a supportive recruiter who’s with you every step of the way. Join us — where your expertise makes a difference every day. Thus we have many pieces. We need to avoid duplication: "Experience Required" and "Requirements" both talk about experience. We can combine. We need to avoid filler: none. We need to use

        • for any list of duties/requirements/benefits. So for certifications list, we should use
          • . For onboarding process steps, we can use
            • . For rehire policy points,
              • . For benefits list (competitive pay, seamless onboarding, supportive recruiter, equipment, parking, dress code) we can use
                • . For requirements (experience, license) we can use
                  • . For shift information maybe just

                    . We need to decide sections. Potential sections:

                    About the role

                    Exciting Opportunity: Experience a thriving work environment that