Travel Pediatric Emergency Room RN - $1,589 per week
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Also remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to parse the posting. Key info: - Job: travel nurse RN ED - Emergency Department in Kingwood, Texas. - Specialty: ED - Emergency Department - Discipline: RN - Start Date: 10/19/2026 - Duration: 13 weeks (also says 13.14 weeks) - 36 hours per week - Shift: 12 hours, nights - Employment Type: Travel - Summary: Junxion Med Staffing looking for ER RN assignment in Kingwood, Texas. Assignment lasts 13.14 weeks, start Oct 19, 2026. If start date, shift, or pay doesn’t line up, let’s talk. Often multiple openings. Give us a call opt 1 (maybe contact instruction, but we should remove application instructions? The instruction "Give us a call opt 1" is like contact instruction; we should remove application instructions. So we can drop that line. - Job Details: Shift: 12H Nights, Total Weekly Hours: 36, Certifications: ACLS, PALS, TNCC, BLS, Trauma Level: Facility Specific - Required Experience, Skills, and Certifications: list: IV skills, EKG skills, Triage acuity training, ACLS, PALS, TNCC, BLS - Preferred Skills: ENPC, CPI - Preferred Personality Traits: Team player, Flexible with assignments - Benefits: Insurance Plans starting under $175/month for employees, Referral Bonus, Additional contract bonus opportunities, Vacation Incentives, Employee Assistance Program (EAP), 401k with access to financial advisors - Also later: Benefits section repeats: Weekly pay, 401k retirement plan, Referral bonus, Medical benefits, Dental benefits, Vision benefits, Mileage reimbursement - About the Company: Junxion Med Staffing partners with hospitals... goal: provide strong support, transparent communication, assignments that make sense for your career and your life. - About Junxion Med Staffing: founded by former healthcare traveler... specialize in placing travel nurses... etc. Values: Transparent communication, Dedicated support, Competitive pay and benefits, Focus on your success. - Pay package: based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. - Job ID #1390009 (should be folded into short p or dropped). We should not put Job ID as heading; we can include a short p with Job ID maybe but it's minor metadata; we can drop it or include in a p. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can either drop it or include in a p. Probably drop it to keep concise. - Also note: "Estimated weekly pay includes projected hourly wages and weekly meal and lodging per diems for eligible clinicians based on nationally published GSA rates. Actual weekly pay and per diems may differ from the amount shown and may be subject to change during an assignment." This is pay info but not specific amount. Since we should not create Pay section unless posting actually states them. It mentions estimated weekly pay but no actual number. It says "Estimated weekly pay includes projected hourly wages..." but no figure. It's vague. Should we include Pay section? The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "Estimated weekly pay includes projected hourly wages..." but not a specific number. It's still stating something about pay. However the rule also says "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". Here we have no specific number, but it's not exactly placeholder like "varies". It says estimated weekly pay includes projected hourly wages and per diems based on GSA rates. That's somewhat generic but still info. Might be considered placeholder? Not sure. Safer to not create Pay section because no concrete amount. We could include a short p about pay info under maybe About the role? But we need to follow sections: we can include a
about pay details inside a section like About the role or maybe a separate Pay section only if we have concrete. Since we don't have concrete, we should not create Pay section. We can incorporate pay info into a
under About the role or maybe under Benefits? But Benefits section is separate. Schedule: we have shift: 12 hours, nights; 36 hours per week; duration 13 weeks. That's schedule info. We can create a Schedule section with those details. Benefits: we have specific benefits: Insurance Plans starting under $175/month, Referral Bonus, Additional contract bonus opportunities, Vacation Incentives, Employee Assistance Program (EAP), 401k with access to financial advisors, Weekly pay (maybe part of benefits?), 401k retirement plan, Referral bonus, Medical benefits, Dental benefits, Vision benefits, Mileage reimbursement. Some duplicates. We need to preserve all substantive info, not invent. We should combine duplicates but keep info. We'll list unique benefits. Requirements: we have Required Experience, Skills, and Certifications list. Also Certifications: ACLS, PALS, TNCC, BLS (these are also in required). Also Trauma Level: Facility Specific (maybe a requirement). Also Shift: 12H Nights, Total Weekly Hours: 36 (these are schedule). Also Start Date, Duration. Qualifications: maybe we can treat Required Experience, Skills, and Certifications as Requirements/Qualifications. The headings we can use: About the role (summary), Responsibilities (maybe not present), Requirements (list of required skills/certs), Qualifications (maybe preferred skills/traits), Benefits, Schedule, Pay (if we have). But we need to avoid empty sections. We have no explicit Responsibilities section. Could we infer responsibilities from specialty? Not given. So we should not create Responsibilities heading. We have About the role: we can use summary paragraph. We have Requirements: list of required skills/certs. We have Qualifications: preferred skills and personality traits. We have Benefits: list. We have Schedule: shift, hours, duration, start date. We have Pay: maybe we can include a short p about pay inside About the role or Benefits? But we should not create Pay section unless we have concrete. We'll omit Pay section. We also have About the Company/About Junxion Med Staffing: could be part of About the role? Or we could create an About the Company section but not in allowed headings list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Skills is also allowed. We could put required skills under Requirements, preferred skills under Qualifications, maybe also a Skills section? But we already have Requirements and Qualifications covering skills. Skills heading maybe redundant. We'll not create Skills unless we have specific skills list not covered elsewhere. We have required skills list and preferred skills list; we can put them under Requirements and Qualifications respectively. Thus sections: About the role (summary + maybe company description), Requirements (required experience, skills, certifications), Qualifications (preferred skills, personality traits), Benefits, Schedule. We need to ensure we don't repeat info. Let's extract summary: "Junxion Med Staffing is looking for a ER RN to take an assignment in Kingwood, Texas. This assignment lasts 13.14 WEEKS and is scheduled to start on October 19, 2026. If the start date, shift, or pay doesn’t line up with what you're looking for, let’s talk. We often have multiple openings in the same market." We should remove the "Give us a call opt 1" as application instruction. Also remove "If the start date, shift, or pay doesn’t line up..." maybe it's okay to keep as it's substantive? It's more of a call to action but not exactly application instruction. It's okay. We also have "About Junxion Med Staffing" paragraph about mission etc. Could be included in About the role. We need to preserve all substantive info: So we should include the company description paragraphs. Thus About the role could contain: - Junxion Med Staffing is looking for a ER RN to take an assignment in Kingwood, Texas. This assignment lasts 13.14 weeks and is scheduled to start on October 19, 2026. If the start date, shift, or pay doesn’t line up with what you're looking for, let’s talk. We often have multiple openings in the same market. - Junxion Med Staffing partners with hospitals and healthcare systems nationwide to connect experienced clinicians with meaningful opportunities. Our goal is simple: provide strong support, transparent communication, and assignments that make sense for your career and your life. - Junxion Med Staffing was founded by a former healthcare traveler who understands the challenges healthcare professionals face - because we’ve been there. We specialize in placing travel nurses, allied health professionals, physicians, physician assistants, and nurse practitioners in both short-term and permanent roles across a wide range of specialties. Whether you're looking for a travel contract or a long-term fit, we work to ensure the right match between each healthcare professional and facility. At Junxion, we keep it simple: ● Transparent communication. No surprises, no hidden details, just honest conversations so you always know what to expect. ● Dedicated support. From job search to contract negotiations and throughout your assignment, you’ll have a recruiter who’s with you every step of the way. ● Competitive pay and benefits. We advocate for you to be fairly compensated and supported in your goals. ● A focus on your success. When healthcare professionals feel valued and empowered, patient care improves and that’s what it’s all about. You’re not just a number here. You’re part of a team that actually cares. Let’s find your next great opportunity together. We need to preserve bullet points? The original uses ●. We can keep as plain text or convert to
- . Since it's a list, we could use
- . But the rule says use
- for any list of duties/requirements/benefits. This is a list of company values; not duties/requirements/benefits. Could still be a list but not required. Safer to keep as plain sentences. Now Requirements: list required experience, skills, certifications: - IV skills - EKG skills - Triage acuity training - ACLS (Advanced Cardiovascular Life Support) - PALS (Pediatric Advanced Life Support) - TNCC (Trauma Nursing Core Course) - BLS (Basic Life Support) Also Certifications: ACLS, PALS, TNCC, BLS (duplicate). Also Trauma Level: Facility Specific (maybe a requirement). Also Shift: 12H Nights, Total Weekly Hours: 36 (these are schedule). Start Date and Duration also schedule. We'll include required list as above. Also maybe include Trauma Level: Facility Specific as a requirement. Now Qualifications: preferred skills and personality traits: - ENPC (Emergency Nursing Pediatric Course) - CPI (Crisis Prevention Institute training) - Team player - Flexible with assignments Now Benefits: we need to consolidate. From first benefits list: - Insurance Plans starting under $175/month for employees - Referral Bonus - Additional contract bonus opportunities - Vacation Incentives - Employee Assistance Program (EAP) - 401k with
- . But the rule says use