Bilingual (Spanish) Phone Outreach Associate

We need to output HTML fragment with sections: About Us? The instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. We need to include sections only when posting has real specific content. The posting includes "About Us" content, "The Role", "Responsibilities", "Qualifications", "Compensation range", "Our Interview Process" (maybe not needed), "For full-time employees, we offer a comprehensive benefits package". Also schedule: "This role is expected to work from 9:30am-6:30pm CT, and will require flexibility to work overtime." That's schedule. Pay: compensation range $22-$28/hr. Benefits: described. Also maybe "Skills" not explicit; we could omit if not present. "Requirements" maybe same as Qualifications; but we have Qualifications section. Could also have "About the role" heading? The posting has "The Role:" which could be used as About the role. But they said use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content accordingly. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting includes some scam warning at end: "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." That's boilerplate; should be removed. Also "Remote positions are open to candidates in the contiguous US only. Due to operational and compliance requirements, we are unable to hire candidates residing in ND, AL, HI, PR or outside the contiguous US." That's maybe location restriction; is that boilerplate? It's substantive location restriction; maybe keep? It's not a heading; could be placed in a short

maybe under About Us? But instructions: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." This location restriction could be considered metadata; we could fold into a short

maybe under About Us or at end. However they said remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Location restriction is not exactly those; but could be considered operational requirement; maybe keep as a short p. Also "Our Interview Process" details: maybe not needed as a heading; could be omitted as not in list of headings. But we could include as a section? The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". The interview process is specific content; but we don't have a standard heading for it; we could maybe treat as "Requirements"? Not appropriate. Better to omit because not in allowed headings list? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exhaustive; we could still add other headings if needed? It says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are the expected headings; we should stick to those. So we should not create a heading for Interview Process. We could fold that info into a short

maybe under About the role? But it's not about role. Might be considered metadata; we could drop it? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." Interview process is not minor metadata; it's part of hiring process. But maybe we can drop as it's not required? However we must preserve ALL substantive information; we cannot drop substantive info. So we need to include it somewhere. Could we incorporate it under "About the role" as a paragraph? That seems odd. Maybe we can create a section "Requirements" and include interview process there? Not correct. Better approach: Since 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 suggests those are typical. To be safe, we could include a section "Process" but not in list; risk of violating. I'd rather include the interview process details as a

under a generic heading like "About the role" or maybe under "Qualifications"? Not ideal. Alternatively, we could treat "Our Interview Process" as a subsection under "About the role" but still keep the content. The instruction: "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." Interview process is not minor metadata; it's part of the job description. So we should keep it. Perhaps we can create a heading "Process" but it's not in the list; but the examples are not exhaustive. I'd assume it's okay to add other headings as needed, as long as we use

. The instruction says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." indicates examples, not exclusive. So we can add other headings like "Interview Process". That seems fine. Similarly, "About Us" could be a heading; but they didn't list About Us; but we could use "About the role" for the role description, and maybe "About Us" as a heading? Not in examples but could be okay. However they said "Do NOT repeat the job title as a heading". About Us is not job title. So we could include About Us as a heading. But they gave examples of headings; maybe they expect us to use those specific headings only. The phrase "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Usually in such tasks, they want you to use those headings if applicable. If a section doesn't match, you might omit or fold into another. For About Us content, we could fold into "About the role"? Not ideal. But we could create a heading "About Us" as it's substantive. I'd lean to include About Us as a heading. Let's decide: We'll produce sections: - About Us (h3) - About the role (h3) (maybe from "The Role:") - Responsibilities (h3) - Qualifications (h3) - Benefits (h3) - Pay (h3) - Schedule (h3) We could also include "Interview Process" as a section but not required; maybe we can fold into "About the role" or "Qualifications"? Not ideal. But we could add a section "Process" as h3; risk but maybe okay. Given the instruction to preserve ALL substantive information, we need to include interview process details somewhere. If we omit, we violate. So we need to include it. Let's add a section "Interview Process" as h3. Also location restriction: we can fold into a short p under About Us or at end. Now we need to remove boilerplate: the scam warning lines, maybe also the line "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." Remove that. Also remove "Remote positions are open to candidates in the contiguous US only. Due to operational and compliance requirements, we are unable to hire candidates residing in ND, AL, HI, PR or outside the contiguous US." This is location restriction; we could keep as a short p maybe under About Us. Now let's extract content. About Us paragraph: The first paragraph about US maternal outcomes, Nadia Care mission, etc. We'll keep as

. The Role: description: "We are seeking a remote Bilingual (Spanish) Phone Outreach Associate, specialized in engaging new members. This role will be responsible for making calls to potential members and accurately explaining what we do at Nadia Care and how we serve our community. The ideal candidate will be a quick learner who can memorize scripts and adapt when issues arise during a call. As the voice of our company, the Phone Outreach Associate must possess excellent communication and interpersonal skills, as well as be enthusiastic about helping members and driving membership growth for Nadia Care. This role is expected to work from 9:30am-6:30pm CT, and will require flexibility to work overtime. This role will report directly to the Phone Outreach Team Lead, which sits on the Marketing & Member Enrollment team at Nadia Care." We'll separate schedule later. Responsibilities list: bullet points. Qualifications list: bullet points. Compensation: "Compensation range for this position is between $22-$28/hr. The exact amount will depend on direct, relevant experience." Benefits: list of benefits: Time Off That Works for You (with subpoints), Comprehensive Health & Wellness Coverage (with subpoints), Security & Future Planning Options (with subpoints). We'll need to format as

• maybe nested. We need to preserve all substantive information; we can keep subpoints as separate
• inside parent
• or just as separate
• with dash. Simpler: make each benefit category as
• with its details as
  inside. Schedule: "This role is expected to work from 9:30am-6:30pm CT, and will require flexibility to work overtime." Now produce HTML. We must not include or . Just fragment. Let's craft. We'll start with

  About Us

  ...

  Then

  About the role

  ... (excluding schedule sentence)

  Then

  Responsibilities

  ...
  Then

  Qualifications

  ...
  Then

  Benefits

  ...
  Then

  Pay

  ...

  Then

  Schedule

  ...

  Then maybe

  Interview Process

  ...

  Then location restriction as

  ...

  maybe after interview process. Check for any duplicated lines: Ensure we don't repeat. Now write content. About Us text: Combine first two paragraphs? The About Us section includes: "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 journey. We help our members with care navigation, doula support, assistance with lactation, nutrition, housing, transportation and a wide range of other needs. We leverage technology to support our virtual engagement that allows us to meet all our moms where they are.We ensure that our members have trusted sources for support, resources, and information throughout their pregnancy, delivery and well into postpartum.