Jobs · Healthcare · South Carolina

Travel CT Tech - $3,051 per week

AHS Staffing · North Charleston, SC · 1 mo ago
On-siteHealthcareInternship
We need to output HTML fragment with sections only if real specific content. The posting includes: Job Description & Requirements (but no actual description? It lists specialty, discipline, start date, duration, hours, shift, employment type, job ID, pay package note). There's no actual responsibilities or requirements listed beyond those. There's a section "About AHS Staffing" with prose. There's no explicit Benefits, Pay, Schedule sections with concrete details (pay package is based on 12 hour shifts and 36.0 hours per week with tax-free stipend amount to be determined). That's vague; we should not create Pay/Schedule/Benefits sections unless posting actually states them. It 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 specific pay amount, so we should not create Pay section. Schedule? It mentions shift: 12 hours, days, 36 hours per week. That's schedule info. Could we create a Schedule section? The rule: only create Pay/Schedule/Benefits sections if posting actually states them. It does state shift and hours, so we could include Schedule section with that info. However we need to avoid filler like "not specified". The schedule is specified: 12 hour shifts, days, 36 hours per week. So we can include Schedule section with that. Benefits: The About AHS Staffing paragraph mentions benefits: industry-leading benefits, including comprehensive medical coverage, 401(k) matching, competitive pay packages, licensure reimbursement, weekly pay, and more. That's specific enough to create Benefits section with those items as list. Responsibilities/Requirements: Not provided beyond specialty etc. Could we create a Requirements section with the listed items: Specialty, Discipline, Start Date, Duration, Hours, Shift, Employment Type? Those are more like job details, not responsibilities. But we could treat them as Requirements? The rule: Use
  • for any list of duties/requirements/benefits. The posting includes "Job Description & Requirements" heading but no actual duties. However we have details like Specialty: CT Technologist, Discipline: Allied Health Professional, Start Date: ASAP, Duration: 13 weeks, 36 hours per week, Shift: 12 hours, days, Employment Type: Travel. Those could be considered requirements. We should include them as a list under a section like "Requirements". But we need a heading: use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use

    Requirements

    and list those items. We should not repeat job title as heading. Also drop Job ID/requisition numbers as headings; we can fold minor metadata into a short

    or drop it. The Job ID #788273 is minor metadata; we could drop it or include in a short p. Probably drop it. We need to remove boilerplate: cookie/navigation/legal/EEO etc. Not present. We need to preserve all substantive information. So include: Specialty, Discipline, Start Date, Duration, Hours, Shift, Employment Type, Pay package note (though vague), About AHS Staffing paragraph, Benefits list. We should not create Pay section because pay amount not specified. However we could include the pay package note under Requirements or maybe under a separate "Compensation" but rule says only create Pay section if posting actually states them. It does state "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, but it's still some info about pay. However the rule says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state something about pay package, albeit vague. Should we create a Pay section with that note? 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 note includes "subject to confirmation" and "tax-free stipend amount to be determined." That's somewhat placeholder. Might be considered filler. Safer to not create Pay section. Instead we could include that note in a paragraph under Requirements or maybe under a general "Details" section but we don't have a generic heading. Could we include it in a

    after the Requirements list? Probably okay. Schedule: we have shift and hours details, which are specific. So we can create Schedule section. Benefits: we have specific benefits list. Thus sections: Requirements, Schedule, Benefits, About AHS Staffing (maybe as "About the agency" but we can use

    About AHS Staffing

    though not in list but allowed? The rule 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 can use About AHS Staffing as heading. We need to output only HTML fragment. Structure:

    Requirements

    • Specialty: CT Technologist
    • Discipline: Allied Health Professional
    • Start Date: ASAP
    • Duration: 13 weeks
    • Hours: 36 hours per week
    • Shift: 12 hours, days
    • Employment Type: Travel
    Maybe also include Pay package note as a

    after the list? Could be separate

    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.

    But that is somewhat pay info; we decided not to make Pay section. Could include as a paragraph under Requirements or after. Better to include as a

    after the list, maybe under a

    Compensation

    ? But we decided not to create Pay section. However the note is about pay package; it's not filler like "commensurate with experience". It does give basis: based on 12 hour shifts and 36 hours per week. That's somewhat specific. But still stipend amount TBD. Might be okay to include as a paragraph. But the rule: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". If we made a Pay section with that note, it would be heading followed by placeholder text (stipend amount to be determined). That's not allowed. So we should not create Pay section. Instead we can incorporate that note into a paragraph without a heading, maybe under Requirements or as a general note. We could add a

    after the Requirements list:

    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 okay because it's not a heading. Now Schedule section:

    Schedule

    • Shift: 12 hours, days
    • Hours: 36 hours per week
    But we already listed shift and hours in Requirements; could duplicate. Better to keep Schedule separate with those details, and maybe remove from Requirements to avoid duplication. However we need to preserve all substantive information; duplication is okay but maybe redundant. We could keep both but it's repetitive. Better to move shift and hours to Schedule and keep Requirements with specialty, discipline, start date, duration, employment type. Then Schedule has shift and hours. Thus: Requirements list: - Specialty: CT Technologist - Discipline: Allied Health Professional - Start Date: ASAP - Duration: 13 weeks - Employment Type: Travel Schedule list: - Shift: 12 hours, days - Hours: 36 hours per week Benefits list from About AHS Staffing: comprehensive medical coverage, 401(k) matching, competitive pay packages, licensure reimbursement, weekly pay, and more. We'll output as
    • ...
    . About AHS Staffing paragraph: we need to keep the prose but maybe trim the benefits list because we moved it to Benefits section. However the rule says preserve ALL substantive information; we can't remove the benefits mention from the About paragraph if we move it to a list; but we can keep the paragraph without the list? The paragraph currently: "When you're on assignment with us, you'll get access to industry-leading benefits, including comprehensive medical coverage, 401(k) matching, competitive pay packages, licensure reimbursement, weekly pay, and more." If we move the list to Benefits section, we could keep a shorter sentence: "When you're on assignment with us, you'll get access to industry-leading benefits." But that would be summarizing away detail, which is not allowed. We must preserve all substantive information; we cannot remove the specifics. So we need to keep the paragraph as is, and also have a Benefits section listing them. That would duplicate the benefit details. Duplication is allowed? The rule didn't forbid duplication, only said preserve all substantive information; not invent or summarize away detail. Duplication preserves detail, so it's okay. However we might consider moving the benefits list to a Benefits section and keep the paragraph but maybe rephrase to avoid duplication? But we cannot summarize away detail; we could keep the paragraph as is and also have a Benefits section that lists them; that's fine. Thus About AHS Staffing section will include the full paragraph. Now output HTML fragment. We need to ensure no extra text outside HTML. Let's craft:

    Requirements

    • Specialty: CT Technologist
    • Discipline: Allied Health Professional
    • Start Date: ASAP
    • Duration: 13 weeks
    • Employment Type: Travel

    Schedule

    • Shift: 12 hours, days
    • Hours: 36 hours per week

    Benefits

    • Comprehensive medical coverage
    • 401(k) matching
    • Competitive pay packages
    • Licensure reimbursement
    • Weekly pay
    • More

    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.

    About AHS Staffing

    At AHS Staffing, we are committed to providing a personalized, transparent, and rewarding experience. We go beyond the transactional nature of the industry by offering individualized job matching, clear communication, no-nonsense pay rates, and dedicated recruiter support 24/7. When you're on assignment with us, you'll get access to industry-leading benefits, including comprehensive medical coverage, 401(k) matching, competitive pay packages, licensure reimbursement, weekly pay, and more. Easily manage your day-to-day with our mobile app where you can view your assignment details, manage your compliance and licensing documents, submit timecards, and browse new jobs to land your next adventure. As a nationally recognized and award-winning agency, we understand the importance of providing a seamless experience from application to placement. Our top priority is matching you with assignments that align with both your personal and professional goals. Join us to experience working with an agency that truly prioritizes your success and well-being and see why thousands of healthcare professionals continue to trust us with their careers.

    Check for any boilerplate: none. We included Pay package note as a paragraph

Similar jobs