Travel CT Technologist - $3,709 per week

We need to output HTML fragment with sections only if real specific content. The posting includes: About AHS Staffing (description), Job Description & Requirements (but not detailed duties). It lists Specialty, Discipline, Start Date, Duration, 40 hours per week, Shift: 8 hours, Employment Type: Travel, Pay package based on 8 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. No specific duties/responsibilities listed. No qualifications/skills listed. No benefits specifics beyond generic description in About AHS Staffing (but that is about agency benefits). We can include About the role? Not present. Could include About AHS Staffing as a section maybe "About the agency". But headings allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should only include sections where there is real specific content. We have 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 somewhat vague but it's specific about basis. It's not a number, but it's still content. Should we include Pay section? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state Pay package based on 8 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. That's stating something about pay, albeit vague. I'd include Pay section with that sentence. Schedule: we have Shift: 8 hours, 40 hours per week. That's schedule info. So we can include Schedule section. 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/Qualifications/Skills: none specific. So we omit those. About the role: not present; we have About AHS Staffing which is about agency, not role. Could we use "About the role" heading for that? No, that would be inaccurate. Better to not include About the role. Could we include a section like "About the agency"? Not allowed headings list. So we might not include any heading for that paragraph, but we need to preserve all substantive information. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to include that paragraph somewhere. If we don't have a heading for it, we can just put it as a

without a heading? The rules: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

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

  for prose. It doesn't say every paragraph must be under a heading, but we should structure with headings where appropriate. We could have a heading like "About AHS Staffing" but not in allowed list. However the instruction says use

  for section headings (e.g. About the role, Responsibilities, ...). The e.g. suggests those are examples, not exclusive list? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should map the About AHS Staffing content under maybe "Benefits"? But that's about benefits, not agency description. Could we put it under "About the role"? Not accurate but maybe acceptable as placeholder? The rule: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". If we put About the role heading but the content is about agency, that's not specific to role, but still substantive. Might be considered not matching heading. Safer to omit heading and just put the paragraph as a

  at top? The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." It didn't require headings for every piece. So we can just have a

  for the agency description, then

  Benefits

  with list, then

  Pay

  with

  , then

  Schedule

  with

  . That seems okay. We must not include boilerplate like cookie/navigation/legal/EEO etc. None present. Let's craft:

  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.

  Then Benefits section: we already mentioned benefits in that paragraph, but we should not duplicate. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we already included benefits in the agency paragraph, we could still create a Benefits section with list, but that would duplicate content. Duplication is not prohibited explicitly, but we should avoid duplicated lines. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should avoid duplicated lines. The benefits appear in the agency paragraph; if we also list them in Benefits section, that duplicates. Better to not duplicate; we could keep the agency paragraph as is, and not create a separate Benefits section. However we need to include Benefits section only if posting has real specific content for it. The posting does have specific benefits listed (medical coverage, 401(k) matching, etc.) but they are already in the agency paragraph. We could still create a Benefits section and list them, but that would duplicate the same sentences. To avoid duplication, we could either not include Benefits section and rely on the agency paragraph to convey benefits, or we could rephrase to avoid duplication. The instruction says preserve all substantive information; we can keep them in the agency paragraph; that's fine. So we may not need a separate Benefits heading. Thus we have only Pay and Schedule sections. 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: "Shift: 8 hours, 40 hours per week." We could also include Start Date, Duration, etc. Those are not under allowed headings but could be placed as a

  before sections. The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests to use those for sections. We could just put metadata as

  without heading. Thus final HTML:

  AHS Staffing is seeking a travel CT Technologist for a travel job in Haverhill, New Hampshire.

  Specialty: CT Technologist

  Discipline: Allied Health Professional

  Start Date: 10/05/2026

  Duration: 13 weeks

  40 hours per week

  Shift: 8 hours

  Employment Type: Travel

  AHS Staffing Job ID #815400.

  Then maybe a paragraph about agency (the long one). Then Pay and Schedule sections. But we must not repeat 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 include Job ID in a short

  . We should remove duplicated lines: The posting includes "Posted job title: CT Tech" which is duplicate of job title; we should drop that. Also "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." Keep. Now ensure we don't include boilerplate like "About AHS Staffing" heading; we just have paragraph. Let's craft final HTML:

  AHS Staffing is seeking a travel CT Technologist for a travel job in Haverhill, New Hampshire.

  Specialty: CT Technologist

  Discipline: Allied Health Professional

  Start Date: 10/05/2026

  Duration: 13 weeks

  40 hours per week

  Shift: 8 hours

  Employment Type: Travel

  AHS Staffing Job ID #815400.

  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.

  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

  Shift: 8 hours, 40 hours per week.

  Check for any duplicated lines: we have "40 hours per week" appears both as a separate

  and in Schedule paragraph. That's duplication. The metadata includes "40 hours per week" as a separate line; schedule also mentions it. We should avoid duplication. We can drop the separate "40 hours per week" line and keep it only in Schedule. Or we can keep both but that's duplication. Better to drop the separate line. Similarly "Shift: 8 hours" appears as separate line and in Schedule. We'll drop separate line. Thus metadata lines: Specialty, Discipline, Start Date, Duration, Employment Type, Job ID. Let's list:

  Specialty: CT Technologist

  Discipline: Allied Health Professional

  Start Date: 10/05/2026

  Duration: 13 weeks

  Employment Type: Travel

  AHS Staffing Job ID