Travel CT Technologist - $2,980 per week
for each section present: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real specific content.
We need to parse the job posting.
Key details:
- Job title: CT Technologist (already shown, not repeated as heading)
- Location: Tacoma, Washington (maybe part of About the role)
- Specialty: CT Technologist
- Discipline: Allied Health Professional
- Start Date: 11/02/2026
- Duration: 13 weeks
- 36 hours per week
- Shift: 12 hours
- Employment Type: Travel
- Agency: MedPro Healthcare Allied Staffing (Joint Commission-certified)
- Requirements: Eighteen months prior experience in a health care setting as a CT Tech; must be ARRT (CT) or ASRT certified; Most states require licensure; Ability to work independently as well as in a team environment.
- Benefits: Weekly pay and direct deposit; Full coverage of all credentialing fees; Private housing or housing allowance; Group Health insurance for you and your family; Company-paid life and disability insurance; Travel reimbursement; 401(k) matching; Unlimited Referral Bonuses up to $1,000.
- Duties/Responsibilities: list of duties (operate CT equipment, positioning patients, setting controls, assisting radiologist, etc.)
- About Agency: description of MedPro Healthcare Staffing.
- Additional Benefits repeated: Day 1 medical, dental, vision benefits; Weekly pay and direct deposit; Unlimited Referral Bonuses starting at $500; On Staff Clinical Support Team; Access to nationwide travel assignments; MPX+ Mobile app; Full coverage of all credentialing fees; Private housing or housing allowance; Tax Free Per Diems, Housing Stipends and Travel Reimbursements; Company-paid life and disability insurance; Travel reimbursement; 401(k) matching; Benefits Weekly pay; Employee assistance programs; Referral bonus.
We need to avoid duplication and boilerplate. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
We need to preserve all substantive information, not invent or summarize away detail.
We need to include sections only when posting has real specific content.
We need to 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.
We must not repeat the job title as a heading.
We must not put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it.
We need to decide which sections to include.
We have:
- About the role: could include location, start date, duration, hours per week, shift, employment type, agency description maybe. But "About the role" could be a short paragraph summarizing the job: travel CT Technologist in Tacoma, WA, start date, duration, hours, shift, travel employment.
- Responsibilities: list of duties.
- Requirements: list of requirements (experience, certification, licensure, ability to work independently/team).
- Qualifications: maybe same as requirements? The posting doesn't separate qualifications; but we could treat requirements as qualifications. However we need to avoid thin sections. If we have both Requirements and Qualifications with similar content, that might be thin. Better to combine into one section: Requirements (or Qualifications). The instruction says use headings for those categories if content exists. We can decide to have Requirements and maybe Qualifications if there is distinct content. The posting mentions "Eighteen months prior experience... must be ARRT (CT) or ASRT certified... Most states require licensure... Ability to work independently as well as in a team environment." That's requirements. There's no separate qualifications list. So we can have a Requirements section.
- Skills: not explicitly listed; maybe implied but not specific. Better to omit Skills section if no specific content.
- Benefits: list of benefits.
- Pay: The posting mentions "Weekly pay and direct deposit" but also says "Weekly payment estimates are intended for informational purposes only and include a gross estimate of hourly wages and reimbursements for meal, incidental, and housing expenses. Your recruiter will confirm your eligibility and provide additional details. MedPro Job ID #a0Fcx00000el27NEAQ. 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." This is somewhat vague but includes mention of weekly pay, tax-free stipend to be determined. However the instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state weekly pay and direct deposit as a benefit, but also mentions pay package based on shifts, tax-free stipend amount to be determined. That is somewhat specific but includes "to be determined". The instruction says: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "tax-free stipend amount to be determined" is similar to TBD. So we should avoid creating a Pay section if it's only placeholder. However we have "Weekly pay and direct deposit" as a concrete benefit. That could go under Benefits. The Pay section might be redundant. Better to not create a Pay section; include pay info under Benefits (since it's a benefit). The instruction says: Prefer a few substantive sections over many thin ones. So we can combine pay into Benefits.
- Schedule: The posting states "36 hours per week", "Shift: 12 hours". That's schedule info. So we can have a Schedule section with those details.
Thus sections: About the role, Responsibilities, Requirements, Benefits, Schedule.
We need to ensure we don't duplicate content.
Let's extract substantive info:
About the role:
- Travel CT Technologist position in Tacoma, Washington.
- Start date: 11/02/2026.
- Duration: 13 weeks.
- Hours: 36 hours per week.
- Shift: 12-hour shifts.
- Employment type: Travel.
- Agency: MedPro Healthcare Allied Staffing (Joint Commission-certified staffing agency) seeking a quality CT Tech for a contract with one of our top healthcare clients.
- Maybe also mention that MedPro Healthcare Staffing is a Joint Commission-certified provider of contract staffing services, placed nursing and allied travelers since 1983.
But "About Agency" could be part of About the role or separate. However we have no separate heading for About Agency; we could incorporate into About the role.
We need to avoid duplication: The "About Agency" paragraph appears later with more detail about MedPro's mission, etc. That is substantive and could be included under About the role or maybe a separate section like "About the Agency". But the allowed headings list does not include About Agency; only About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we must fit agency info into About the role or maybe Benefits? Better to put under About the role.
Thus About the role paragraph will include: MedPro Healthcare Allied Staffing is a Joint Commission-certified staffing agency seeking a quality CT Tech for a contract with one of our top healthcare clients. Since 1983, they have placed nursing and allied travelers in top healthcare facilities nationwide. Provide mission statement etc.
We need to ensure we don't include boilerplate like EEO, scam warning, etc. The posting includes: "MedPro Staffing is an Equal Opportunity Employer. All applicants will be considered for employment without attention to race, color, religion, national origin, age, sex, disability, marital status or veteran status." That's boilerplate EEO; we should remove.
Also "If qualified and interested, please call for immediate consideration." That's application instruction; remove.
Also "Key Words: CT Technologist, CAT Scan Tech, Computerized Axial Tomography, CT Tech" - maybe not needed but could be considered metadata; we can drop.
Also "Posted job title: CT Technologist Imaging: CT Technologist." - duplicate.
Also "MedPro Job ID #a0Fcx00000el27NEAQ." - minor metadata; we can fold into a short p or drop. Probably drop.
Also "Weekly payment estimates are intended for informational purposes only..." - we decided to avoid Pay section; but we could include a note under Benefits that weekly pay and direct deposit is provided, but the estimate is informational. However that sentence includes "informational purposes only" and "tax-free stipend amount to be determined". That's somewhat placeholder. Might be better to omit that sentence entirely, as it's not concrete benefit. But we need to preserve ALL substantive information. Is that substantive? It says weekly pay and direct deposit is a benefit; the rest is about estimates being informational and stipend TBD. The substantive part is "Weekly pay and direct deposit". The rest is not substantive (it's disclaimer). We can keep the phrase "Weekly pay and direct deposit" as part of Benefits list, and omit the disclaimer.
Thus Benefits list: Weekly pay and direct deposit; Full coverage of all credentialing fees; Private housing or housing allowance; Group Health insurance for you and your family; Company-paid life and disability insurance; Travel reimbursement; 401(k) matching; Unlimited Referral Bonuses up to $1,000; Day 1 medical, dental, and vision benefits for you and your family; Unlimited Referral Bonuses starting at $500 (but we already have up to $1,000; need to avoid duplication). Actually there are two mentions: "Unlimited Referral Bonuses up to $1,000" and later "Unlimited Referral Bonuses starting at $500". They are similar but different numbers. We need to preserve ALL substantive information; we cannot invent or summarize away detail. If there are two different statements, we need to keep both? But they are essentially same benefit with different numbers; maybe the posting has inconsistencies. We need to keep both as separate bullet points? That would be duplicative but both are substantive. However we should avoid duplicated lines per instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove duplicated lines. The referral bonus appears twice with slightly different wording; we need to deduplicate. Choose one representation that captures the info: maybe "Unlimited Referral Bonuses up to $1,000". The other says "starting at $500". Which is more specific? The first gives a max; the second gives a starting amount. Both are substantive. Could combine: "Unlimited Referral Bonuses (starting at $500, up to $1,000)". That preserves both numbers without duplication. That seems acceptable as it's not inventing; it's combining info from two statements. However we must be careful not to invent or summarize away detail. Combining is summarizing but not losing detail; we keep both numbers. It's not creating new info. It's okay.
Similarly, "Group Health insurance for you and your family" vs "Day 1 medical, dental, and vision benefits for you and your family". Those are distinct: group health insurance vs medical/dental/vision. Keep both.
Also "Private housing or housing allowance" appears twice; deduplicate.
Also "Travel reimbursement" appears twice; deduplicate.
Also "Company-paid life and disability insurance" appears twice; deduplicate.
Also "401(k) matching" appears twice; deduplicate.
Also "Weekly pay and direct deposit" appears multiple times; deduplicate.
Thus Benefits list will contain unique items:
- Weekly pay and direct deposit
- Full coverage of all credentialing fees
- Private housing or housing allowance
- Group Health insurance for you and your family
- Day
- for any list of duties/requirements/benefits, and
for prose. We must not repeat the job title as a heading. We must not put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. We need to decide which sections to include. We have: - About the role: could include location, start date, duration, hours per week, shift, employment type, agency description maybe. But "About the role" could be a short paragraph summarizing the job: travel CT Technologist in Tacoma, WA, start date, duration, hours, shift, travel employment. - Responsibilities: list of duties. - Requirements: list of requirements (experience, certification, licensure, ability to work independently/team). - Qualifications: maybe same as requirements? The posting doesn't separate qualifications; but we could treat requirements as qualifications. However we need to avoid thin sections. If we have both Requirements and Qualifications with similar content, that might be thin. Better to combine into one section: Requirements (or Qualifications). The instruction says use headings for those categories if content exists. We can decide to have Requirements and maybe Qualifications if there is distinct content. The posting mentions "Eighteen months prior experience... must be ARRT (CT) or ASRT certified... Most states require licensure... Ability to work independently as well as in a team environment." That's requirements. There's no separate qualifications list. So we can have a Requirements section. - Skills: not explicitly listed; maybe implied but not specific. Better to omit Skills section if no specific content. - Benefits: list of benefits. - Pay: The posting mentions "Weekly pay and direct deposit" but also says "Weekly payment estimates are intended for informational purposes only and include a gross estimate of hourly wages and reimbursements for meal, incidental, and housing expenses. Your recruiter will confirm your eligibility and provide additional details. MedPro Job ID #a0Fcx00000el27NEAQ. 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." This is somewhat vague but includes mention of weekly pay, tax-free stipend to be determined. However the instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state weekly pay and direct deposit as a benefit, but also mentions pay package based on shifts, tax-free stipend amount to be determined. That is somewhat specific but includes "to be determined". The instruction says: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "tax-free stipend amount to be determined" is similar to TBD. So we should avoid creating a Pay section if it's only placeholder. However we have "Weekly pay and direct deposit" as a concrete benefit. That could go under Benefits. The Pay section might be redundant. Better to not create a Pay section; include pay info under Benefits (since it's a benefit). The instruction says: Prefer a few substantive sections over many thin ones. So we can combine pay into Benefits. - Schedule: The posting states "36 hours per week", "Shift: 12 hours". That's schedule info. So we can have a Schedule section with those details. Thus sections: About the role, Responsibilities, Requirements, Benefits, Schedule. We need to ensure we don't duplicate content. Let's extract substantive info: About the role: - Travel CT Technologist position in Tacoma, Washington. - Start date: 11/02/2026. - Duration: 13 weeks. - Hours: 36 hours per week. - Shift: 12-hour shifts. - Employment type: Travel. - Agency: MedPro Healthcare Allied Staffing (Joint Commission-certified staffing agency) seeking a quality CT Tech for a contract with one of our top healthcare clients. - Maybe also mention that MedPro Healthcare Staffing is a Joint Commission-certified provider of contract staffing services, placed nursing and allied travelers since 1983. But "About Agency" could be part of About the role or separate. However we have no separate heading for About Agency; we could incorporate into About the role. We need to avoid duplication: The "About Agency" paragraph appears later with more detail about MedPro's mission, etc. That is substantive and could be included under About the role or maybe a separate section like "About the Agency". But the allowed headings list does not include About Agency; only About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we must fit agency info into About the role or maybe Benefits? Better to put under About the role. Thus About the role paragraph will include: MedPro Healthcare Allied Staffing is a Joint Commission-certified staffing agency seeking a quality CT Tech for a contract with one of our top healthcare clients. Since 1983, they have placed nursing and allied travelers in top healthcare facilities nationwide. Provide mission statement etc. We need to ensure we don't include boilerplate like EEO, scam warning, etc. The posting includes: "MedPro Staffing is an Equal Opportunity Employer. All applicants will be considered for employment without attention to race, color, religion, national origin, age, sex, disability, marital status or veteran status." That's boilerplate EEO; we should remove. Also "If qualified and interested, please call for immediate consideration." That's application instruction; remove. Also "Key Words: CT Technologist, CAT Scan Tech, Computerized Axial Tomography, CT Tech" - maybe not needed but could be considered metadata; we can drop. Also "Posted job title: CT Technologist Imaging: CT Technologist." - duplicate. Also "MedPro Job ID #a0Fcx00000el27NEAQ." - minor metadata; we can fold into a short p or drop. Probably drop. Also "Weekly payment estimates are intended for informational purposes only..." - we decided to avoid Pay section; but we could include a note under Benefits that weekly pay and direct deposit is provided, but the estimate is informational. However that sentence includes "informational purposes only" and "tax-free stipend amount to be determined". That's somewhat placeholder. Might be better to omit that sentence entirely, as it's not concrete benefit. But we need to preserve ALL substantive information. Is that substantive? It says weekly pay and direct deposit is a benefit; the rest is about estimates being informational and stipend TBD. The substantive part is "Weekly pay and direct deposit". The rest is not substantive (it's disclaimer). We can keep the phrase "Weekly pay and direct deposit" as part of Benefits list, and omit the disclaimer. Thus Benefits list: Weekly pay and direct deposit; Full coverage of all credentialing fees; Private housing or housing allowance; Group Health insurance for you and your family; Company-paid life and disability insurance; Travel reimbursement; 401(k) matching; Unlimited Referral Bonuses up to $1,000; Day 1 medical, dental, and vision benefits for you and your family; Unlimited Referral Bonuses starting at $500 (but we already have up to $1,000; need to avoid duplication). Actually there are two mentions: "Unlimited Referral Bonuses up to $1,000" and later "Unlimited Referral Bonuses starting at $500". They are similar but different numbers. We need to preserve ALL substantive information; we cannot invent or summarize away detail. If there are two different statements, we need to keep both? But they are essentially same benefit with different numbers; maybe the posting has inconsistencies. We need to keep both as separate bullet points? That would be duplicative but both are substantive. However we should avoid duplicated lines per instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove duplicated lines. The referral bonus appears twice with slightly different wording; we need to deduplicate. Choose one representation that captures the info: maybe "Unlimited Referral Bonuses up to $1,000". The other says "starting at $500". Which is more specific? The first gives a max; the second gives a starting amount. Both are substantive. Could combine: "Unlimited Referral Bonuses (starting at $500, up to $1,000)". That preserves both numbers without duplication. That seems acceptable as it's not inventing; it's combining info from two statements. However we must be careful not to invent or summarize away detail. Combining is summarizing but not losing detail; we keep both numbers. It's not creating new info. It's okay. Similarly, "Group Health insurance for you and your family" vs "Day 1 medical, dental, and vision benefits for you and your family". Those are distinct: group health insurance vs medical/dental/vision. Keep both. Also "Private housing or housing allowance" appears twice; deduplicate. Also "Travel reimbursement" appears twice; deduplicate. Also "Company-paid life and disability insurance" appears twice; deduplicate. Also "401(k) matching" appears twice; deduplicate. Also "Weekly pay and direct deposit" appears multiple times; deduplicate. Thus Benefits list will contain unique items: - Weekly pay and direct deposit - Full coverage of all credentialing fees - Private housing or housing allowance - Group Health insurance for you and your family - Day