Travel Pediatric OR CST - $1,201 per week
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use - for lists
- Use
for prose
- Do NOT repeat job title as heading (page already shows it)
- Do NOT put Job ID/requisition numbers as headings — fold minor metadata into short
or drop
- Preserve ALL substantive information; do NOT invent or summarize away detail
- Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions
- Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD")
- Never create Pay/Schedule/Benefits sections unless posting actually states them
- Prefer few substantive sections over many thin ones
- Output ONLY HTML fragment — no /, no markdown code fences
Now, let's map the content to appropriate sections.
The job posting has:
- A description of the role (About the role)
- Responsibilities? Not explicitly listed, but there is a description of what they're seeking.
- Requirements: listed as "Requirements:" with bullet points.
- Qualifications? Could be combined with requirements.
- Skills? Not explicitly listed.
- Benefits: listed as "Benefits for Travel Surg Techs:" and also "We Offer:" which includes benefits and perks.
- Pay: there is "Competitive pay" in benefits, and "Pay package is based on 12 hour shifts and 36.0 hours per week... with tax-free stipend amount to be determined." Also "Weekly Pay through Direct Deposits" and "Competitive Compensation". So there is some pay info.
- Schedule: Shift details: "Shift: 12 hours, days", "Shift: 3x12 Days", "36 hours per week". So schedule info exists.
Also there is "About Focus Staff" which is company info, but the rule says use headings like "About the role", "Responsibilities", etc. Not "About the company". However, the user didn't forbid company info, but the example headings are about the role. The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., so we can use other headings if needed? But we should stick to those typical sections. The company description might be considered boilerplate? The user says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The "About Focus Staff" appears twice, and it's company marketing. Might be considered boilerplate. However, it's part of the posting. But the instruction says "Preserve ALL substantive information". The company description is not directly about the job role. But it's part of the posting. I think we should include it as a section maybe "About the Company" but the example headings don't include that. The user says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings, but we should prefer those. However, the company info is duplicated and marketing. I'll include it as a section "About the Company" or maybe fold into a short paragraph? But the instruction says "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." For company info, it's not minor metadata. But it's not about the role. I think we can include a section "About the Company" if it's substantive. But the user says "Prefer a few substantive sections over many thin ones." The company description is long and duplicated. I'll include one "About the Company" section with the unique content.
Also "Other Information" metadata: Job Title, Employment Time, Date Posted, Valid Through, Job City, State, Country, Shift, Job ID, Hiring Organization. These are minor metadata. Should fold into a short
or drop. The instruction says "fold minor metadata into a short
or drop it." So I'll create a paragraph with key metadata: location, start date, duration, shift, employment type, maybe job ID.
EEO statement: "Focus Staff is an EEO/AA (Equal Employment Opportunity and Affirmative Action) Employer." This is boilerplate, remove.
Pay package info: "Estimated pay package based on bill rate at time job was posted. Bill rates can change frequently and without notice. Exact pay package may vary based on several factors, including, but not limited to, guaranteed hours, travel distance, demand, experience, etc." This is a disclaimer, but also there is "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 substantive pay info. So we should include a Pay section with that.
Schedule: shift details are given. So include Schedule section.
Benefits: two lists: "Benefits for Travel Surg Techs:" and "We Offer:" which includes many benefits. Combine into one Benefits section.
Requirements: list.
Qualifications: maybe same as requirements. The posting says "Requirements:" and lists. Also "Valid SC License", "BLS". Could be qualifications. I'll use Requirements heading.
Skills: not explicitly listed.
Responsibilities: not explicitly listed. The description says "The ideal candidate will have at least 1 year of experience in a Surg Tech setting." That's a requirement, not responsibilities. There's no list of duties. So maybe no Responsibilities section.
About the role: we can have a section "About the Role" with the description prose.
Now, let's structure:
1. About the Role: prose describing the job.
2. Schedule: details about shift, hours, duration.
3. Requirements: list.
4. Benefits: list (combine both lists).
5. Pay: details about pay package.
6. About the Company: company description (once).
7. Additional Details: metadata paragraph.
But the user says "include a section ONLY when the posting has real, specific content for it". So we must ensure each section has content.
Let's extract content.
First, the job description: "Focus Staff is seeking a Certified Surg Tech for a travel contract in Charleston, SC. The ideal candidate will have at least 1 year of experience in a Surg Tech setting. Contract Length: 13 Weeks Start Date: 11/09/2026 Shift: 3x12 Days"
Also earlier: "Specialty: Pediatric Surgical Technologist Discipline: Allied Health Professional Start Date: 11/09/2026 Duration: 13 weeks 36 hours per week Shift: 12 hours, days Employment Type: Travel"
We can combine.
Schedule section: include shift, hours per week, duration, start date.
Requirements:
- 1 Year of Experience, 2 Preferred
- Valid SC License
- BLS
- Eligible to work in the United States
Benefits: from "Benefits for Travel Surg Techs:" list:
- Health insurance
- Vision insurance
- Dental insurance
- Life insurance
- Licensure reimbursement
- Travel reimbursement
- Relocation assistance
- 401(k)
- 401(k) matching
- Competitive pay
- Referral bonus
- Holiday bonus
From "We Offer:" list:
- Immediate Openings
- Weekly Pay through Direct Deposits
- Flexible Schedules
- Day and Night Shifts Available
- Competitive Compensation
- Guaranteed Hours (based on employer)
- Travel Assistance
- Dedicated/Responsive Recruiters
- Day One Medical, Dental, Vision and Life Insurance
- Generous Housing Stipend
- 24/7 Support
- Company Provided Housing Options
- Referral Bonus ($600)
- Loyalty Bonus ($1,200)
- Discounts/Coupons to Hotels
- Access to Jobs in all 50 States
- Painless Credentialing Process
- U.S.A.-based Company
- Equal Opportunity Employer
- Joint Commission Certified
- Licensure Reimbursement
- Pet-Friendly
- Access to Discounts, Rewards, and more
Some are duplicates (e.g., Competitive pay/compensation, Licensure reimbursement, Referral bonus). We'll combine and deduplicate.
Pay: "Competitive pay" is in benefits. Also "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." Also "Weekly Pay through Direct Deposits". So Pay section can include that.
Schedule: "Shift: 12 hours, days", "36 hours per week", "Shift: 3x12 Days", "Duration: 13 weeks", "Start Date: 11/09/2026".
About the Company: the "About Focus Staff" section (the second one is more detailed). Use that.
Additional Details: metadata: Job City: Charleston, Job State: SC, Job Country: USA, Employment Type: Travel, Contract Length: 13 weeks, Job ID: a0xVt00000XF3H7IAL, Hiring Organization: Focus Staff, Date Posted: 10/09/2026, Valid Through: 02/08/2027. Fold into a paragraph.
Now, produce HTML.
We'll use
for each section heading.
Sections:
- About the Role
- Schedule
- Requirements
- Benefits
- Pay
- About the Company
- Additional Details
But the user said "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use exactly those headings where appropriate. "About the role" not "About the Role". Case? Probably "About the role". We'll follow the example capitalization: "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". We'll use those.
We don't have Responsibilities, Qualifications, Skills. So we'll only include those we have.
We have "About the role", "Schedule", "Requirements", "Benefits", "Pay". Also "About the Company" not in list, but we can include as "About the Company" or maybe omit? The instruction says "use for section headings (
for prose - Do NOT repeat job title as heading (page already shows it) - Do NOT put Job ID/requisition numbers as headings — fold minor metadata into short
or drop - Preserve ALL substantive information; do NOT invent or summarize away detail - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions - Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") - Never create Pay/Schedule/Benefits sections unless posting actually states them - Prefer few substantive sections over many thin ones - Output ONLY HTML fragment — no /, no markdown code fences Now, let's map the content to appropriate sections. The job posting has: - A description of the role (About the role) - Responsibilities? Not explicitly listed, but there is a description of what they're seeking. - Requirements: listed as "Requirements:" with bullet points. - Qualifications? Could be combined with requirements. - Skills? Not explicitly listed. - Benefits: listed as "Benefits for Travel Surg Techs:" and also "We Offer:" which includes benefits and perks. - Pay: there is "Competitive pay" in benefits, and "Pay package is based on 12 hour shifts and 36.0 hours per week... with tax-free stipend amount to be determined." Also "Weekly Pay through Direct Deposits" and "Competitive Compensation". So there is some pay info. - Schedule: Shift details: "Shift: 12 hours, days", "Shift: 3x12 Days", "36 hours per week". So schedule info exists. Also there is "About Focus Staff" which is company info, but the rule says use headings like "About the role", "Responsibilities", etc. Not "About the company". However, the user didn't forbid company info, but the example headings are about the role. The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., so we can use other headings if needed? But we should stick to those typical sections. The company description might be considered boilerplate? The user says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The "About Focus Staff" appears twice, and it's company marketing. Might be considered boilerplate. However, it's part of the posting. But the instruction says "Preserve ALL substantive information". The company description is not directly about the job role. But it's part of the posting. I think we should include it as a section maybe "About the Company" but the example headings don't include that. The user says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings, but we should prefer those. However, the company info is duplicated and marketing. I'll include it as a section "About the Company" or maybe fold into a short paragraph? But the instruction says "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." For company info, it's not minor metadata. But it's not about the role. I think we can include a section "About the Company" if it's substantive. But the user says "Prefer a few substantive sections over many thin ones." The company description is long and duplicated. I'll include one "About the Company" section with the unique content. Also "Other Information" metadata: Job Title, Employment Time, Date Posted, Valid Through, Job City, State, Country, Shift, Job ID, Hiring Organization. These are minor metadata. Should fold into a short
or drop. The instruction says "fold minor metadata into a short
or drop it." So I'll create a paragraph with key metadata: location, start date, duration, shift, employment type, maybe job ID. EEO statement: "Focus Staff is an EEO/AA (Equal Employment Opportunity and Affirmative Action) Employer." This is boilerplate, remove. Pay package info: "Estimated pay package based on bill rate at time job was posted. Bill rates can change frequently and without notice. Exact pay package may vary based on several factors, including, but not limited to, guaranteed hours, travel distance, demand, experience, etc." This is a disclaimer, but also there is "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 substantive pay info. So we should include a Pay section with that. Schedule: shift details are given. So include Schedule section. Benefits: two lists: "Benefits for Travel Surg Techs:" and "We Offer:" which includes many benefits. Combine into one Benefits section. Requirements: list. Qualifications: maybe same as requirements. The posting says "Requirements:" and lists. Also "Valid SC License", "BLS". Could be qualifications. I'll use Requirements heading. Skills: not explicitly listed. Responsibilities: not explicitly listed. The description says "The ideal candidate will have at least 1 year of experience in a Surg Tech setting." That's a requirement, not responsibilities. There's no list of duties. So maybe no Responsibilities section. About the role: we can have a section "About the Role" with the description prose. Now, let's structure: 1. About the Role: prose describing the job. 2. Schedule: details about shift, hours, duration. 3. Requirements: list. 4. Benefits: list (combine both lists). 5. Pay: details about pay package. 6. About the Company: company description (once). 7. Additional Details: metadata paragraph. But the user says "include a section ONLY when the posting has real, specific content for it". So we must ensure each section has content. Let's extract content. First, the job description: "Focus Staff is seeking a Certified Surg Tech for a travel contract in Charleston, SC. The ideal candidate will have at least 1 year of experience in a Surg Tech setting. Contract Length: 13 Weeks Start Date: 11/09/2026 Shift: 3x12 Days" Also earlier: "Specialty: Pediatric Surgical Technologist Discipline: Allied Health Professional Start Date: 11/09/2026 Duration: 13 weeks 36 hours per week Shift: 12 hours, days Employment Type: Travel" We can combine. Schedule section: include shift, hours per week, duration, start date. Requirements: - 1 Year of Experience, 2 Preferred - Valid SC License - BLS - Eligible to work in the United States Benefits: from "Benefits for Travel Surg Techs:" list: - Health insurance - Vision insurance - Dental insurance - Life insurance - Licensure reimbursement - Travel reimbursement - Relocation assistance - 401(k) - 401(k) matching - Competitive pay - Referral bonus - Holiday bonus From "We Offer:" list: - Immediate Openings - Weekly Pay through Direct Deposits - Flexible Schedules - Day and Night Shifts Available - Competitive Compensation - Guaranteed Hours (based on employer) - Travel Assistance - Dedicated/Responsive Recruiters - Day One Medical, Dental, Vision and Life Insurance - Generous Housing Stipend - 24/7 Support - Company Provided Housing Options - Referral Bonus ($600) - Loyalty Bonus ($1,200) - Discounts/Coupons to Hotels - Access to Jobs in all 50 States - Painless Credentialing Process - U.S.A.-based Company - Equal Opportunity Employer - Joint Commission Certified - Licensure Reimbursement - Pet-Friendly - Access to Discounts, Rewards, and more Some are duplicates (e.g., Competitive pay/compensation, Licensure reimbursement, Referral bonus). We'll combine and deduplicate. Pay: "Competitive pay" is in benefits. Also "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." Also "Weekly Pay through Direct Deposits". So Pay section can include that. Schedule: "Shift: 12 hours, days", "36 hours per week", "Shift: 3x12 Days", "Duration: 13 weeks", "Start Date: 11/09/2026". About the Company: the "About Focus Staff" section (the second one is more detailed). Use that. Additional Details: metadata: Job City: Charleston, Job State: SC, Job Country: USA, Employment Type: Travel, Contract Length: 13 weeks, Job ID: a0xVt00000XF3H7IAL, Hiring Organization: Focus Staff, Date Posted: 10/09/2026, Valid Through: 02/08/2027. Fold into a paragraph. Now, produce HTML. We'll use