Travel MRI Technologist - $2,463 per week

We need to output HTML fragment with sections only if there is real specific content. The posting includes: specialty, discipline, start date, duration, hours per week, shift, employment type, job ID, pay package description (based on 8 hour shifts and 40 hours per week, tax-free stipend amount to be determined). Also posted job title: Radiology Tech - MRI. We must not repeat job title as heading. Do not put Job ID as heading. We can fold minor metadata into a short

or drop it. We need to preserve all substantive information. Substantive: specialty, discipline, start date, duration, hours per week, shift, employment type, pay package description (though stipend amount TBD). We must not create sections for Pay/Schedule/Benefits unless posting actually states them. Pay: they mention pay package based on 8 hour shifts and 40 hours per week with tax-free stipend amount to be determined. That's not a specific amount, but it's still some info about pay. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." They do state pay package based on 8 hour shifts and 40 hours per week with tax-free stipend amount to be determined. That's stating something about pay, albeit vague. Should we include a Pay section? It says "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 not a specific number, but it's still pay info. The rule says: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". Here "tax-free stipend amount to be determined" is TBD. So we should not create a Pay section if it would just contain placeholder/TBD. However we could include the statement as prose in a

maybe under a generic section? But we need sections only when posting has real specific content for it. The pay info is not specific amount, but it's still some info. However the rule about filler/placeholder text suggests we should avoid sections that would just contain placeholder like "TBD". The pay package statement includes "tax-free stipend amount to be determined" which is TBD. So maybe we should not create a Pay section. Instead we could incorporate that info into a

under maybe a general "Details" section? But we don't have a heading for Details unless we have content. The allowed headings are specific: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We cannot invent other headings. So we must only use those headings if we have substantive content. If we don't have substantive content for Pay, we should omit Pay section. Similarly Schedule: they give shift: 8 hours, 40 hours per week. That's schedule info. Could we make a Schedule section? The schedule is specific: 8 hour shifts, 40 hours per week. That's substantive. So we can include a Schedule section with that info. Benefits: not mentioned. So omit Benefits. About the role: we could have a paragraph describing the role: "Aequor Allied is seeking a travel MRI Technologist for a travel job in Chicago, Illinois." That's substantive. Responsibilities: not given. Requirements: they list specialty, discipline, start date, duration, etc. Those could be considered requirements. Qualifications: maybe specialty and discipline. Skills: not given. So we need to decide which sections to include. We must preserve all substantive information. Let's extract: - Job posting: Aequor Allied is seeking a travel MRI Technologist for a travel job in Chicago, Illinois. - Specialty: MRI Technologist - Discipline: Allied Health Professional - Start Date: 10/18/2026 - Duration: 13 weeks - 40 hours per week - Shift: 8 hours - Employment Type: Travel - Job ID #1825095 (metadata, can be dropped or folded into short p) - 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. - Posted job title: Radiology Tech - MRI (but we don't repeat as heading) We need to avoid repeating job title as heading. So we can maybe include a

that mentions the posted job title? The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid mentioning it in prose. So we could include it in a paragraph. We need to remove boilerplate etc. There's none. Now decide sections: - About the role: could include the first sentence about seeking a travel MRI Technologist in Chicago, maybe also mention posted job title. - Responsibilities: none. - Requirements: could include specialty, discipline, start date, duration, hours per week, shift, employment type. Those are requirements for the role. - Qualifications: maybe same as requirements? Might be redundant. Better to put requirements. - Skills: none. - Benefits: none. - Pay: we have pay package description but includes TBD stipend. Might be considered placeholder. The rule: avoid sections with filler/placeholder text like "TBD". The pay section would contain that statement, which includes TBD. So better to omit Pay section. - Schedule: we have shift 8 hours, 40 hours per week. That's specific. So we can include Schedule section. Thus we will have sections: About the role, Requirements, Schedule. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. For About the role, we can use

  . For Requirements, we can list items as

  • . For Schedule, we can maybe use

    or

    . Since schedule info is two items: shift length and weekly hours. Could be a list. We must preserve all substantive information. Let's include: About the role:

    Aequor Allied is seeking a travel MRI Technologist for a travel job in Chicago, Illinois. (Posted job title: Radiology Tech - MRI)

    Requirements: list items: - Specialty: MRI Technologist - Discipline: Allied Health Professional - Start Date: October 18, 2026 (or keep as 10/18/2026) - Duration: 13 weeks - Hours per week: 40 hours - Shift: 8 hours - Employment Type: Travel We could also include Job ID? It's metadata, we can fold into short

    or drop. Probably drop. Schedule: list: - Shift length: 8 hours - Weekly hours: 40 hours (based on 8 hour shifts) But note that schedule info duplicates hours per week and shift already in requirements. However we need to preserve all info; duplication is okay if it's in posting. But we might avoid duplication by not repeating in schedule if already in requirements. However schedule section is meant to convey schedule specifics; we can still include but maybe we can note that schedule is 8-hour shifts, 40-hour work week. It's not duplicate if we mention again; but we could keep it. We must not invent or summarize away detail. So we need to keep the exact phrasing where possible. Let's craft:

    About the role

    Aequor Allied is seeking a travel MRI Technologist for a travel job in Chicago, Illinois. (Posted job title: Radiology Tech - MRI)

    Requirements

    • Specialty: MRI Technologist
    • Discipline: Allied Health Professional
    • Start Date: 10/18/2026
    • Duration: 13 weeks
    • 40 hours per week
    • Shift: 8 hours
    • Employment Type: Travel

    Schedule

    • Shift length: 8 hours
    • Weekly hours: 40 hours
    We omitted Pay because it's TBD. We omitted Benefits. We omitted Responsibilities, Qualifications, Skills. Check if any info missing: The phrase "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." We omitted that entirely. Is that substantive? It's about pay but includes TBD. The rule says never emit a 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 the posting actually states them. It does state pay package, but the content includes TBD. If we made a Pay section, we would have to include that statement, which includes TBD. That would be filler/placeholder. So better to omit Pay section entirely. However we might incorporate the pay info into a

    under About the role or Requirements? But that would be adding pay info not under a heading. The instruction: "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 forbid having prose outside sections. So we could add a

      about pay package as prose, not under a Pay heading. That would preserve the info without violating the rule about Pay section. However the rule also says "Prefer a few substantive sections over many thin ones." Adding a prose paragraph about pay is okay. But we must decide if we should include that pay info. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should include the pay package statement somewhere. We can put it in a

      under About the role or as a separate

      before sections. Since we already have About the role paragraph, we could append that info there. Let's include: After the role sentence, add: "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." Thus About the role paragraph becomes two sentences. Now we have preserved pay info. Now check duplication: Schedule section includes shift length and weekly hours, which are also in Requirements. That's okay; we are preserving all info. Could we avoid duplication by moving schedule info to Schedule only and removing from Requirements? But Requirements includes "40 hours per week" and "Shift: 8 hours". Those are substantive requirements. If we remove them from Requirements, we lose that info from Requirements section. But we could keep them in Requirements and also have Schedule; duplication is okay. Now check if we need to include "Posted job title: Radiology Tech - MRI" as part of About the role. We included it in parentheses. Now ensure we didn't include any boilerplate. Good. Now output only HTML fragment. Let's craft final HTML:

      About the role

      Aequor Allied is seeking a travel MRI Technologist for a travel job in Chicago, Illinois. (Posted job title: Radiology Tech - MRI) 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.

      Requirements

      • Specialty: MRI Technologist
      • Discipline: Allied Health Professional
      • Start Date: 10/18/2026
      • Duration: 13 weeks
      • 40 hours per week
      • Shift: 8 hours
      • Employment Type: Travel

      Schedule

      • Shift