Bilingual (Spanish) Maternal Health Registered Nurse

We need to output HTML fragment with sections: About the role? Actually we have "About Us" content, but we need to reformat job posting into clean semantic HTML. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We must include sections only when posting has real specific content. We have content: About Us (mission, values). That could be "About the role"? Actually "About Us" is about company, not role. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have "The Role" description: a paragraph describing role. That could be "About the role". Then "Responsibilities:" list. Then "Qualifications:" list. Then "Compensation range" is Pay. Then benefits list is Benefits. There's no explicit Skills section separate; qualifications include skills. Could combine? But we can still include Skills if we have content; maybe we can extract skills from qualifications: interpersonal, communication, organized, solutions-oriented, tech-savvy, etc. But we should not invent. Better to not create Skills section if not explicitly labeled. The instruction: "Prefer a few substantive sections over many thin ones." So we could have About the role, Responsibilities, Qualifications, Benefits, Pay. Possibly also Requirements? Qualifications already covers requirements. Could include Requirements as same as Qualifications? Might be redundant. Better to follow headings exactly as given but only if content exists. We have content for About the role (The Role paragraph). Responsibilities (list). Qualifications (list). Benefits (list). Pay (compensation range). No Schedule info. So we omit Schedule. Also we might include Requirements? Not separate; we could treat Qualifications as Requirements. But we have a heading "Requirements" in list; we could map Qualifications to Requirements. However we already have Qualifications heading. The instruction says use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It seems they expect you to pick appropriate headings from that list. So we can use About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. But we have both Requirements and Qualifications content overlapping. The posting has "Qualifications:" list. Could treat that as Requirements. But also there is "Qualifications:" heading already. Might be okay to have both Requirements and Qualifications sections with same content? That would be duplication. Better to map the content to either Requirements or Qualifications, not both. Since the posting uses "Qualifications:" we could use that heading. But the instruction list includes Qualifications as an option. So we can use Qualifications. Then we could omit Requirements. Or we could rename Qualifications to Requirements? The instruction says use those headings; we can choose which to use. I'd use About the role, Responsibilities, Qualifications, Benefits, Pay. Now we need to strip boilerplate: remove About Us? Actually About Us content is substantive about company mission and values. Should we include? The instruction says preserve ALL substantive information; do not invent or summarize away detail. So we should include About Us content somewhere. Where? Could be part of About the role? Or we could add an "About Us" section but not in allowed headings. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. Likely they want us to use those headings only. However we need to preserve About Us content; we could incorporate it into About the role section as introductory paragraph. That would preserve it. So About the role section will contain both the role description and the company mission/values. Thus About the role

About the role

then

containing the About Us paragraph plus The Role paragraph. Now Responsibilities: we have a list with subheadings: Clinical Care & Escalations and Care Quality & Training Support. Each has bullet points. We need to output

• for any list of duties/requirements/benefits. Should we keep the subheadings inside
• ? Probably we can keep them as part of the li text. Eg
• Clinical Care & Escalations: ...
. But we must not invent formatting; we can keep the subheading as plain text inside li. We need to preserve all substantive information: include all bullet points. Qualifications: list of items. We'll output
• each. Benefits: list includes Time Off..., Comprehensive Health & Wellness Coverage with sub-items. We'll output nested lists? The instruction: use
  • for any list of duties/requirements/benefits. So we can have top-level ul for benefits, and inside we can have sub-ul for sub-items. That's fine. Pay: we have compensation range: "$40-$45/hr. The exact amount will depend on years of direct, relevant experience." We'll put that in a

    under

    Pay

    . Schedule: none, omit. Now ensure we don't include boilerplate: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At end there is "Remote positions are open to candidates in the contiguous US only..." and scam warning. Those are boilerplate? They are operational constraints; maybe they are considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The scam warning is likely to be removed. The remote location restriction maybe also considered boilerplate? It's not exactly EEO but it's a hiring restriction. Might be considered boilerplate? Not sure. Safer to keep it? The instruction says remove scam-warning boilerplate. The remote location note is not scam warning; it's a job requirement. Could keep. However it's near the end with "Please note that our recruitment team will only contact candidates via an official company email address..." that's also maybe considered boilerplate? It's about recruitment process. Might be considered application instructions? It's not exactly instructions to apply but contact info. Could be considered boilerplate. Safer to remove that line as well. Also the interview process details: "Below is our standard interview process for this role:" etc. That's application instructions? It's describing interview process; could be considered part of application instructions. The instruction says remove application instructions. So we should remove the interview process bullet list. Also remove the line "At Nadia Care, we value transparency..." leading into interview process. So we will cut that out. Thus final HTML will contain:

    About the role

    About Us paragraph + The Role paragraph.

    Responsibilities

    • Clinical Care & Escalations
      • Conduct telemedicine visits at set points in the postpartum period to identify unmanaged clinical needs and educate members on more complex clinical topics
      • Assess members that report Urgent Maternal Warning Signs or high blood pressure values, and help them navigate to the most appropriate care setting
      • Review blood pressure and Edinburgh Postnatal Depression Scale (EPDS) values and follow-up on irregular values that have not already been escalated
      • Serve as a clinical liaison between Nadia Care and the member’s obstetrics provider or primary care physician, documenting visit summaries and escalating all unmanaged clinical needs reported to the Care team
    • Care Quality & Training Support
      • Help train Maternity Navigators (MNs) on prenatal and postpartum topics to ensure every member receives the same high-quality, evidence-based education
      • Be a voice for the community, bringing insights from your experience working with mothers and families help shape Nadia Care programs that truly meet their needs
      • Foster proactive collaboration between Maternity Navigators and clinicians, including case discussions, knowledge sharing on health education and community resources as needed during care team huddles.

    Qualifications

    • Active compact state Registered Nurse (RN) license in TN or IN, with interest in obtaining licensure in other compact states.
    • Minimum of 5 years of experience in prenatal and postpartum care in outpatient pediatrics, OB/GYN, maternal-fetal medicine, acute care, or a similar setting
    • Native or bilingual fluency in speaking, writing, and reading Spanish, with experience delivering clinical information, patient education, and medical guidance seamlessly in Spanish
    • Exceptional interpersonal and communication skills with the ability to provide compassionate, empathetic, and culturally-informed care
    • Highly organized and solutions-oriented, with the ability to adapt in a fast-paced, evolving environment
    • Comfortable establishing strong relationships with patients virtually
    • Tech-savvy or able to quickly learn systems to document care and communicate with members (e.g., AthenaOne, Spruce, MacOS)

    Benefits

    • Time Off That Works for You
      • Recharge with annual paid holidays off.
      • Full-Time Salaried Employees (Exempt): Enjoy unlimited time off after the 90-day introductory period.
      • Full-Time Hourly Employees (Non-Exempt): Receive three weeks of paid time off after the 90-day introductory period.
    • Comprehensive Health & Wellness Coverage
      • Medical Insurance: Access top-tier healthcare, covering hospital, surgical, and prescription drug benefits. Coverage begins the first of the following month.
      • Dental Insurance: Coverage for preventive care, as well as basic and major procedures.
      • Vision Insurance: Coverage for routine eye exams and eyeglasses.
    • Security & Future Planning Options
      • Stock Option Grant: We believe in shared success.
      • Life Insurance: Financial protection for your beneficiaries.
      • Disability Insurance: Short-term and long-term coverage in case of illness or injury.
      • 401(k) Retirement Plan: Opportunity to save for the future.

    Pay

    Compensation range for this position is between $40-$45/hr. The exact amount will depend on years of direct, relevant experience.

    We need to ensure no extra text outside HTML fragment. No markdown fences. Provide just the HTML. Check for any leftover boilerplate: we removed interview process, scam warning, remote location note, recruitment team note. Also removed "Please note that our recruitment team will only contact candidates via an official company email address ending in @nadiacare.com. Be cautious of scams; Nadia Care will never ask for financial information or payments at any stage of the hiring process." Good. We kept About Us content: "The United States has the poorest maternal and birth outcomes..." etc. We need to include that exactly. Let's copy it. About Us paragraph: "The United States has the poorest maternal and birth outcomes of all developed countries with the underserved, Black, Brown, Indigenous communities disproportionately affected. Nadia Care is working to drastically change the experience of affected communities by reimagining how we deliver meaningful and compassionate care to expectant moms.Nadia Care’s mission is to improve pregnancy, birth and the postpartum journey for women and their families by reimagining how maternity care is delivered. Our team is focused on building trust-based engagement and wrap-around support for expectant moms at home, in person and virtually to ensure they have all the social support they need for a successful and joyful pregnancy