Registered Nurse / RN - Emergency Medicine
Solomon Page · Pasadena, TX · 4 wk ago
On-siteHealthcareContract
We need to output HTML fragment with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Remove boilerplate, navigation, EEO, etc. Must preserve all substantive info.
Let's parse the posting:
- "Our client is looking to add a Registered Nurse to their team." (intro)
- Job Details: Location: Pasadena, Texas; Duration: 13 Weeks; Start Date: 11/02/2026; Shift: 3x12 Days; Estimated Gross Weekly Pay: $2,008; Estimated Weekly Stipend: $1,288
- Qualifications: list bullet points: Current Texas license; Excellent interpersonal skills including patience, empathy, and compassion; Effective communication skills, including active listening, writing, speaking and reading comprehension; Fast and adaptive problem-solving abilities; Ability to stand for long periods of time
- Then: "If you meet the required qualifications and are interested in this role, please apply today." (application instruction - remove)
- Why Work with Us: paragraph about Solomon Page benefits: comprehensive benefits package, travel nurses immediate access to medical coverage and ReviveHealth virtual care; also dental and vision coverage, commuter benefits, a 401(k) plan, flexible spending, referral bonuses, ongoing training, and more. As an ESOP company, offers employee stock ownership plan to all consultants. As a member of traveler community, you will join a nurturing culture that fosters your career goals. Solomon Page can connect you with your next opportunity – whether it is in your hometown, or you are looking to travel to a new destination.
- About Solomon Page Healthcare & Medical Staffing: Accredited by the Joint Commission with the Gold Seal of Approval, Solomon Page prides ourselves in developing long-term relationships with healthcare providers based on trust and respect. Our experienced Healthcare and Medical Staffing experts are committed to providing safe and quality patient care through our wide network of travel nurses, locum tenens, and allied resources. For more information and additional healthcare opportunities, visit: solomonpage.com and connect with Solomon Page on Instagram, Facebook, Twitter, LinkedIn, and TikTok. (This is boilerplate? It's about the company; maybe we keep as "About the company"? But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The "About Solomon Page" could be considered "About the role"? Not exactly. The instruction says use headings for those specific section headings. It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Remove boilerplate, navigation, EEO, etc. Must preserve all substantive info.
Let's parse the posting:
- "Our client is looking to add a Registered Nurse to their team." (intro)
- Job Details: Location: Pasadena, Texas; Duration: 13 Weeks; Start Date: 11/02/2026; Shift: 3x12 Days; Estimated Gross Weekly Pay: $2,008; Estimated Weekly Stipend: $1,288
- Qualifications: list bullet points: Current Texas license; Excellent interpersonal skills including patience, empathy, and compassion; Effective communication skills, including active listening, writing, speaking and reading comprehension; Fast and adaptive problem-solving abilities; Ability to stand for long periods of time
- Then: "If you meet the required qualifications and are interested in this role, please apply today." (application instruction - remove)
- Why Work with Us: paragraph about Solomon Page benefits: comprehensive benefits package, travel nurses immediate access to medical coverage and ReviveHealth virtual care; also dental and vision coverage, commuter benefits, a 401(k) plan, flexible spending, referral bonuses, ongoing training, and more. As an ESOP company, offers employee stock ownership plan to all consultants. As a member of traveler community, you will join a nurturing culture that fosters your career goals. Solomon Page can connect you with your next opportunity – whether it is in your hometown, or you are looking to travel to a new destination.
- About Solomon Page Healthcare & Medical Staffing: Accredited by the Joint Commission with the Gold Seal of Approval, Solomon Page prides ourselves in developing long-term relationships with healthcare providers based on trust and respect. Our experienced Healthcare and Medical Staffing experts are committed to providing safe and quality patient care through our wide network of travel nurses, locum tenens, and allied resources. For more information and additional healthcare opportunities, visit: solomonpage.com and connect with Solomon Page on Instagram, Facebook, Twitter, LinkedIn, and TikTok. (This is boilerplate? It's about the company; maybe we keep as "About the company"? But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The "About Solomon Page" could be considered "About the role"? Not exactly. The instruction says use headings for those specific section headings. It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should only use those headings if they exist. The posting does not have explicit sections like "Responsibilities" or "About the role". It has "Job Details", "Qualifications", "Why Work with Us", "About Solomon Page". We need to map content to allowed headings where appropriate. We cannot invent sections. We should only include a heading if the posting has real, specific content for it. So we need to see if any of those headings match content.
- "About the role": Could map to introductory description: "Our client is looking to add a Registered Nurse to their team." plus maybe location, duration, start date, shift. That seems like role details. So we could create About the role
with that info.
- "Responsibilities": Not explicitly listed. The posting does not give duties/responsibilities. So we should not include Responsibilities section.
- "Requirements": Could be similar to Qualifications? The posting has "Qualifications:" list. Could map to Requirements or Qualifications. Since both are allowed, we need to decide. The posting explicitly says "Qualifications:" So we should use Qualifications
for that list. We could also include Requirements if there is separate content, but there isn't. So we skip Requirements.
- "Skills": The qualifications list includes interpersonal skills, communication skills, problem-solving, ability to stand. Those could be considered skills. But we already used Qualifications heading. We could either combine or split. The instruction: Prefer a few substantive sections over many thin ones. So we should not split into both Qualifications and Skills if they overlap. Since Qualifications heading is present in the posting, we use that. Skills heading would be redundant/thin. So we skip Skills.
- "Benefits": The "Why Work with Us" section describes benefits: comprehensive benefits package, medical coverage, ReviveHealth virtual care, dental and vision coverage, commuter benefits, 401(k), flexible spending, referral bonuses, ongoing training, ESOP, nurturing culture, etc. That's substantive. So we include Benefits
with that content.
- "Pay": The posting includes Estimated Gross Weekly Pay: $2,008 and Estimated Weekly Stipend: $1,288. That's pay info. So we include Pay
with those details.
- "Schedule": The posting includes Shift: 3x12 Days. That's schedule. So we include Schedule
with that.
Also we have Location, Duration, Start Date. Those could go under About the role or maybe separate but we don't have a heading for those. We can include them in About the role paragraph.
We must not include boilerplate like "If you meet the required qualifications and are interested in this role, please apply today." (application instruction). Also remove "Why Work with Us" heading? We'll convert that content to Benefits section. Also remove "About Solomon Page Healthcare & Medical Staffing" etc. That's company description; could be considered part of Benefits? Not really. It's more about the company. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Solomon Page" is not exactly boilerplate but it's company info. However we don't have a heading for company info. Could we include it under About the role? Not appropriate. Could we omit it? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep that info. But we don't have a heading for it. Perhaps we can treat it as part of "About the role"? Not really. Or we could create a generic
About the role
with that info. - "Responsibilities": Not explicitly listed. The posting does not give duties/responsibilities. So we should not include Responsibilities section. - "Requirements": Could be similar to Qualifications? The posting has "Qualifications:" list. Could map to Requirements or Qualifications. Since both are allowed, we need to decide. The posting explicitly says "Qualifications:" So we should useQualifications
for that list. We could also include Requirements if there is separate content, but there isn't. So we skip Requirements. - "Skills": The qualifications list includes interpersonal skills, communication skills, problem-solving, ability to stand. Those could be considered skills. But we already used Qualifications heading. We could either combine or split. The instruction: Prefer a few substantive sections over many thin ones. So we should not split into both Qualifications and Skills if they overlap. Since Qualifications heading is present in the posting, we use that. Skills heading would be redundant/thin. So we skip Skills. - "Benefits": The "Why Work with Us" section describes benefits: comprehensive benefits package, medical coverage, ReviveHealth virtual care, dental and vision coverage, commuter benefits, 401(k), flexible spending, referral bonuses, ongoing training, ESOP, nurturing culture, etc. That's substantive. So we includeBenefits
with that content. - "Pay": The posting includes Estimated Gross Weekly Pay: $2,008 and Estimated Weekly Stipend: $1,288. That's pay info. So we includePay
with those details. - "Schedule": The posting includes Shift: 3x12 Days. That's schedule. So we includeSchedule
with that. Also we have Location, Duration, Start Date. Those could go under About the role or maybe separate but we don't have a heading for those. We can include them in About the role paragraph. We must not include boilerplate like "If you meet the required qualifications and are interested in this role, please apply today." (application instruction). Also remove "Why Work with Us" heading? We'll convert that content to Benefits section. Also remove "About Solomon Page Healthcare & Medical Staffing" etc. That's company description; could be considered part of Benefits? Not really. It's more about the company. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Solomon Page" is not exactly boilerplate but it's company info. However we don't have a heading for company info. Could we include it under About the role? Not appropriate. Could we omit it? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep that info. But we don't have a heading for it. Perhaps we can treat it as part of "About the role"? Not really. Or we could create a genericwithout a heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use for section headings (e.g. those). It doesn't say we cannot have other headings, but we should follow the pattern. However we must not repeat job title as a heading and not put Job ID/requisition numbers as headings. The company description could be placed under a heading like "About the company" but that's not in the list. The instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not an exhaustive list. But later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can create a heading for company info if we think it's substantive. But we need to decide if we should. The instruction also says "Prefer a few substantive sections over many thin ones." So we could combine company info into Benefits or About the role? Might be thin if separate.
Maybe we can include a section "About the company" as About the company
. But the instruction didn't forbid that. It gave examples but not exclusive. However the user likely expects only those headings. The typical pattern in these tasks is to only use those headings. The company description might be considered boilerplate? It's not legal/EEO, but it's promotional. Might be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not those. So we should keep it.
Thus we need to decide where to put it. Could create a section "About Solomon Page" as About Solomon Page
. That seems reasonable.
But the instruction 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 the examples are those. I'd lean to include a heading for company info as it's substantive.
Alternatively, we could incorporate company info into Benefits section as part of "Why Work with Us" already includes benefits and culture. The "About Solomon Page" is more about accreditation and mission. Could be considered part of Benefits? Not exactly. But we could merge it into Benefits as additional details about the company. That would keep sections few.
Let's see: Benefits section currently includes: comprehensive benefits package, medical coverage, ReviveHealth virtual care, dental and vision coverage, commuter benefits, 401(k) plan, flexible spending, referral bonuses, ongoing training, ESOP, nurturing culture, career goals, connecting opportunities. The company accreditation and mission could be added there as well. That would keep sections: About the role, Qualifications, Benefits, Pay, Schedule. That's five sections.
We must not include filler like "commensurate with experience". Not present.
Now we need to output HTML fragment only, no /, no markdown fences.
We'll produce:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not an exhaustive list. But later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can create a heading for company info if we think it's substantive. But we need to decide if we should. The instruction also says "Prefer a few substantive sections over many thin ones." So we could combine company info into Benefits or About the role? Might be thin if separate.
Maybe we can include a section "About the company" as About the company
. But the instruction didn't forbid that. It gave examples but not exclusive. However the user likely expects only those headings. The typical pattern in these tasks is to only use those headings. The company description might be considered boilerplate? It's not legal/EEO, but it's promotional. Might be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not those. So we should keep it.
Thus we need to decide where to put it. Could create a section "About Solomon Page" as About Solomon Page
. That seems reasonable.
But the instruction 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 the examples are those. I'd lean to include a heading for company info as it's substantive.
Alternatively, we could incorporate company info into Benefits section as part of "Why Work with Us" already includes benefits and culture. The "About Solomon Page" is more about accreditation and mission. Could be considered part of Benefits? Not exactly. But we could merge it into Benefits as additional details about the company. That would keep sections few.
Let's see: Benefits section currently includes: comprehensive benefits package, medical coverage, ReviveHealth virtual care, dental and vision coverage, commuter benefits, 401(k) plan, flexible spending, referral bonuses, ongoing training, ESOP, nurturing culture, career goals, connecting opportunities. The company accreditation and mission could be added there as well. That would keep sections: About the role, Qualifications, Benefits, Pay, Schedule. That's five sections.
We must not include filler like "commensurate with experience". Not present.
Now we need to output HTML fragment only, no /, no markdown fences.
We'll produce:
About the role
About the role
Our client is looking to add a Registered Nurse to their team. Location: Pasadena, Texas. Duration: 13 Weeks. Start Date: 11/02/2026. Shift: 3x12 Days.
Qualifications
- Current Texas license
- Excellent interpersonal skills including patience, empathy, and compassion
- Effective communication skills, including active listening, writing, speaking and reading comprehension
- Fast and adaptive problem-solving abilities
- Ability to stand for long periods of time
Benefits
Offering a comprehensive benefits package, travel nurses have immediate access to medical coverage and ReviveHealth virtual care. Additionally, you are offered access to dental and vision coverage, commuter benefits, a 401(k) plan, flexible spending, referral bonuses, ongoing training, and more. As an ESOP company, Solomon Page offers an employee stock ownership plan to all consultants. As a member of our traveler community, you will join a nurturing culture that fosters your career goals. Solomon Page can connect you with your next opportunity – whether it is in your hometown, or you are looking to travel to a new destination. Accredited by the Joint Commission with the Gold Seal of Approval, Solomon Page prides ourselves in developing long-term relationships with healthcare providers based on trust and respect. Our experienced Healthcare and Medical Staffing experts are committed to providing safe and quality patient care through our wide network of travel nurses, locum tenens, and allied resources.
Pay
Estimated Gross Weekly Pay: $2,008. Estimated Weekly Stipend: $1,288.
Schedule
Shift: 3x12 Days.
Check for any duplicated lines: We have not included application instruction. We removed "If you meet the required qualifications and are interested in this role, please apply today." Good. We kept all substantive info: location, duration, start date, shift, qualifications list, benefits