Jobs · Healthcare · Texas

Travel MFM Ultrasound Tech - $1,885 per week

CrossMed Healthcare Staffing · Austin, TX · 5 days ago
On-siteHealthcareFull-time
The user wants me to reformat a job posting into clean semantic HTML. Let me analyze the content and apply the rules. First, identify sections: - About the role / Job Description: There's a description about CrossMed and the position. - Responsibilities: Not explicitly listed, but there are details about the job (specialty, discipline, start date, duration, hours, shift, employment type). - Requirements: Not explicitly listed, but there are some details like specialty, discipline. - Qualifications: Not explicitly listed. - Skills: Not explicitly listed. - Benefits: There's a list of benefits. - Pay: There's mention of pay package based on 12 hour shifts, 36 hours per week, tax-free stipend amount to be determined. - Schedule: Shift: 12 hours, nights; FRI-SUN 6:00P-6:30A. Rules: - Use

for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). - Use
  • for lists,

    for prose. - Do NOT repeat job title as heading. - Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it. - Preserve ALL substantive information; do NOT invent or summarize away detail. - Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). - Include a section ONLY when the posting has real, specific content for it — 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. - Prefer a few substantive sections over many thin ones. - Output ONLY the HTML fragment — no /, no markdown code fences. Now, let's parse the content: The posting includes: - "CrossMed is seeking a travel Ultrasound Technologist for a travel job in Austin, Texas." -> This is an intro paragraph. - "Job Description & Requirements" heading in original, but we shouldn't repeat job title. We'll have an "About the role" section. - Specialty: Ultrasound Technologist - Discipline: Allied Health Professional - Start Date: ASAP - Duration: 13 weeks - 36 hours per week - Shift: 12 hours, nights - Employment Type: Travel - CrossMed Job ID #80305724. -> minor metadata, fold into a short

    or drop. I'll include in a meta paragraph. - Pay package is based on 12 hour shifts and 36 hours per week (subject to confirmation) with tax-free stipend amount to be determined. -> Pay info. - Posted job title: CONTRACT - MFM ULTRASOUND TECH (729) - 13 WEEKS - FRI-SUN 6:00P-6:30A -> This is the job title, but we shouldn't repeat as heading. Could include in meta. - About CrossMed: paragraph about company. - Benefits: list of benefits. We need to decide sections: - About the role: includes the intro paragraph and maybe the job details (specialty, discipline, start date, duration, hours, shift, employment type). Could be a list. - Schedule: shift details (12 hours, nights; FRI-SUN 6:00P-6:30A). The posting has specific schedule info, so include Schedule section. - Pay: pay package details (based on 12 hour shifts, 36 hours per week, tax-free stipend amount to be determined). It's specific enough? It says "tax-free stipend amount to be determined" which is a bit placeholder but there is some info. The rule: never create Pay section unless posting actually states them. It does state pay package based on... but amount TBD. Might still include as Pay section with the info given. - Benefits: list of benefits, definitely include. - About the company: "About CrossMed" paragraph. Could be a section "About the company" but not in the predefined headings. The allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About the company" not listed. Could fold into About the role or separate? The rule says use

    for section headings (e.g. About the role, Responsibilities, ...). It says "e.g." so maybe we can use other headings? But better to stick to the list. Could include company info in About the role as a paragraph. - Responsibilities: not explicitly listed. Could infer from job title? But rule: preserve substantive info, do not invent. So no Responsibilities section. - Requirements: not explicitly listed. Could include specialty, discipline as requirements? But they are more job details. Might put in About the role. - Qualifications: none. - Skills: none. Thus sections: About the role, Schedule, Pay, Benefits. Now, structure:

    About the role

    CrossMed is seeking a travel Ultrasound Technologist for a travel job in Austin, Texas.

    • Specialty: Ultrasound Technologist
    • Discipline: Allied Health Professional
    • Start Date: ASAP
    • Duration: 13 weeks
    • Hours per week: 36
    • Shift: 12 hours, nights
    • Employment Type: Travel

    CrossMed Job ID #80305724. Posted job title: CONTRACT - MFM ULTRASOUND TECH (729) - 13 WEEKS - FRI-SUN 6:00P-6:30A

    But the job title is already shown on page, but we can include as meta. The rule: do NOT repeat the 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 in a paragraph. About CrossMed paragraph: could add after the list.

    About the role

    CrossMed is seeking a travel Ultrasound Technologist for a travel job in Austin, Texas.

      ...details...

    CrossMed Job ID #80305724. Posted job title: CONTRACT - MFM ULTRASOUND TECH (729) - 13 WEEKS - FRI-SUN 6:00P-6:30A

    At CrossMed Healthcare Staffing, we aim to create lasting impressions wherever we go. Embark on your healthcare traveler journey with us and discover the CrossMed advantage. We offer competitive pay packages, comprehensive benefits, an in-house clinical team, and dedicated recruiters committed to your success. Our goal is to become the preferred staffing provider by delivering top-notch customer service. Join us and experience the difference firsthand!

    But the About CrossMed is company description, maybe separate section? Not in allowed headings. Could keep in About the role. Schedule section:

    Schedule

    • Shift: 12 hours, nights
    • Schedule: Friday–Sunday, 6:00 PM – 6:30 AM
    Pay section:

    Pay

    Pay package is based on 12‑hour shifts and 36 hours per week (subject to confirmation) with a tax‑free stipend amount to be determined.

    Benefits section:

    Benefits

    • Weekly pay
    • Holiday Pay
    • Guaranteed Hours
    • Continuing Education
    • Company provided housing options
    • Mileage reimbursement
    • Referral bonus
    • Medical benefits
    • Dental benefits
    • Vision benefits
    • License and certification reimbursement
    • Life insurance
    Check for any duplicate or boilerplate: The original has "Benefits" heading and list. Good. Now, ensure no filler. Pay section includes "amount to be determined" which is a placeholder but it's actual info from posting. The rule: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "amount to be determined" is similar to TBD. But the posting says "tax-free stipend amount to be determined." That is a specific statement. The rule says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay package based on... but amount TBD. I think it's okay to include because there is substantive info about pay structure. However, the rule says "never emit a heading followed by filler/placeholder text". The Pay section would have a paragraph that includes "amount to be determined". That might be considered placeholder. But the posting includes that phrase. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we must include that detail. The rule about filler is about not creating a section with only filler. Here we have some info. I'll include Pay section. Similarly, Schedule section has specific times. Now, output only HTML fragment. Let's write the HTML. Use proper escaping for special characters (like &). Use
    • for lists. I'll produce:

      About the role

      CrossMed is seeking a travel Ultrasound Technologist for a travel job in Austin, Texas.

      • Specialty: Ultrasound Technologist
      • Discipline: Allied Health Professional
      • Start Date: ASAP
      • Duration: 13 weeks
      • Hours per week: 36
      • Shift: 12 hours, nights
      • Employment Type: Travel

      CrossMed Job ID #80305724. Posted job title: CONTRACT - MFM ULTRASOUND TECH (729) - 13 WEEKS - FRI-SUN 6:00P-6:30A

      At CrossMed Healthcare Staffing, we aim to create lasting impressions wherever we go. Embark on your healthcare traveler journey with us and discover the CrossMed advantage. We offer competitive pay packages, comprehensive benefits, an in-house clinical team, and dedicated recruiters committed to your success. Our goal is to become the preferred staffing provider by delivering top-notch customer service. Join us and experience the difference firsthand!

      Schedule

      • Shift: 12 hours, nights
      • Schedule: Friday–Sunday, 6:00 PM – 6:30 AM

      Pay

      Pay package is based on 12‑hour shifts and 36 hours per week (subject to confirmation) with a tax‑free stipend amount to be determined.

      Benefits

      • Weekly pay
      • Holiday Pay
      • Guaranteed Hours
      • Continuing Education
      • Company provided housing options
      • Mileage reimbursement
      • Referral bonus
      • Medical benefits
      • Dental benefits
      • Vision benefits
      • License and certification reimburs

Similar jobs