Certified Nurse Midwife (CNM)
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Include sections only if posting has real specific content. We have content for About the role (the paragraph after "About the role:"), Responsibilities (Key Responsibilities), Requirements (maybe "Desired Experience & Qualifications" includes requirements), Qualifications (maybe same as requirements?), Skills (Preferred Skills), Pay (Salary Range), Schedule (flexible schedule description). Also Benefits: mention "competitive total rewards package which includes base salary, and comprehensive benefits." That's vague but mentions benefits. Should we include Benefits section? It says "comprehensive benefits" but not specifics. The rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits: they say "comprehensive benefits" but no specifics; that might be considered filler? It's vague but still states they offer comprehensive benefits. Might be acceptable to include Benefits with a short paragraph describing that they offer comprehensive benefits (though not detailed). However the rule says avoid filler/placeholder text like "commensurate with experience". "Comprehensive benefits" is not a placeholder but still vague. I'd include Benefits section with a short p.
Pay: they give salary range $118,000 - $150,000 USD. That's specific, so include Pay.
Schedule: they describe flexible schedule, typical schedule includes approx two office days per week, average 24 hours on-call per week, protected post-call day off, etc. That's specific enough. Include Schedule.
Now we need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We must not repeat job title as heading. No Job ID.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can combine similar info.
We need to use - for any list of duties/requirements/benefits. So for Responsibilities list, we need
- . For Requirements/Qualifications maybe also list. For Skills list. For Benefits maybe list if we have items; but we only have generic statement; could just use
. For Pay maybe
. For Schedule maybe
or
if we list items.
We must not include boilerplate like EEO, legal, navigation, cookie, application instructions. So remove those sections.
We need to preserve all substantive info: include description of Oula, About Oula? 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." There's also an "About Oula:" section earlier. Should we include that? The instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The sections we can use are limited to the list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not include an "About Oula" heading because it's not in the allowed list. However we could fold that content into About the role? Probably not; but the instruction says we can only use those headings. So we must omit the About Oula description? But we need to preserve ALL substantive information. However the instruction says we should output only HTML fragment using those headings; if we omit About Oula, we lose substantive info. But maybe we can incorporate About Oula content into About the role section? The About the role section currently is about the role; we could add a brief paragraph about Oula before responsibilities? But the heading is About the role; we could include Oula description as part of that section? Might be okay. However 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 ...)". It might be okay to include other headings if needed, but they gave examples. Safer to stick to those headings only. We could put Oula description in a
before the first heading, as minor metadata? It's not minor; it's substantive. But maybe we can treat it as part of About the role? The About the role heading could contain both role description and company overview. That might be acceptable.
Thus structure:
About the role
[combined Oula description + role description]
Then Responsibilities
- ... each responsibility
Then Requirements
maybe combine licensure, certification, experience, etc.
Or we could list.
Then Qualifications
maybe similar to requirements; but we might combine? However we need separate sections only if posting has real specific content for each. The posting has "Desired Experience & Qualifications". That could be considered both requirements and qualifications. We could split: Requirements: licensure, certification, experience; Qualifications: maybe the "bonus" skills? But they also have "Preferred Skills". So we could treat Requirements as mandatory (licensure, certification, 2+ years experience). Qualifications as preferred/experience items? But the instruction says prefer a few substantive sections over many thin ones. Might be better to have Requirements covering licensure, certification, experience, and Qualifications covering the "bonus" skills and preferred skills? However they also have "Preferred Skills" separate. So we could have Skills for preferred skills. Then Qualifications could be empty? Better to combine Requirements and Qualifications into one section? But we need to follow instruction: include a section ONLY when posting has real specific content for it. If we combine, we might lose distinction but still preserve info. Could have Requirements (mandatory) and Qualifications (preferred) both as sub-sections? But they'd be thin. Maybe we can have Requirements (mandatory) and Skills (preferred). And omit Qualifications heading because content overlaps with Requirements/Skills. But the instruction list includes Qualifications as possible heading; we can omit if not needed.
Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule.
Now we need to extract content.
About Oula description: "Oula delivers maternity care built around our patients—offering comprehensive support before, during, and after pregnancy. With fewer C-sections and higher VBAC success rates, our research-backed approach is delivering better outcomes. Our team of trusted midwives, OBGYNs, and dedicated care navigators ensure our patients get the type of care they need in the moments that matter most. Since launching in 2021, we’ve expanded to include Preconception and Miscarriage Care, Pregnancy Care, Postpartum Support, and Gynecology. We currently have 4 clinics in the tri-state area, with three new clinics opening in 2026! Come join our team of clinicians, innovators, operators, and technologists passionate about setting a new standard in maternity care. Oula is redesigning maternity care from the ground up. Our modern maternity centers combine the best of obstetrics and midwifery care to deliver a more evidence-based and personalized pregnancy experience. From our collaborative medical team and welcoming clinics to our remote care platform, we are setting a new standard for pregnancy that unifies modern medicine and human intuition. Since opening our first tech-enabled, collaborative care clinic in 2021, we have grown across multiple markets and continue to expand."
Role description: "We are looking for a Certified Nurse-Midwife (CNM) to join our growing maternity care practice. We’re searching for someone who is thoughtful and passionate about delivering patient-centric, judgment-free care, and is excited to join a dynamic and innovative team. This is the perfect opportunity for a CNM who is excited to expand their skill set and help define and build a new best-in-class maternity care experience. You will be responsible for delivering full-spectrum perinatal care, as well as helping to shape and refine Oula’s clinical care model. At Oula, midwives lead their own panels within a truly collaborative model — OB-GYNs are integrated members of the same team, not a separate referral tier — and our patients deliver at our partner hospital. With fewer C-sections and higher VBAC success rates, our research-backed approach delivers better outcomes for the communities we serve. This is the autonomy-with-backup practice many midwives are looking for and rarely find. This is a full-time position with a flexible schedule that varies based on market and operational needs. At steady-state staffing, a typical schedule includes approximately two office days per week, an average of 24 hours of on-call coverage per week (with a protected post-call day off where applicable), and dedicated administrative and didactic time. During the launch of new markets or other ramp-up periods, scheduling needs—including on-call responsibilities—may temporarily be greater as the practice grows. Part-time and per-diem arrangements may be available depending on clinic needs."
We can combine Oula description and role description into About the role section.
Now Responsibilities list: from "Key Responsibilities:" bullet points:
- Provides full-scope midwifery care during pregnancy, labor, birth, and postpartum across a variety of settings: our clinics, our partner hospital, and virtually.
- Attends births as the primary delivering clinician for low-risk patients, supporting physiologic labor and birth while recognizing when escalation or consultation is indicated.
- Collaborates with other team members (e.g., obstetricians, nurses, MAs, doulas, coordinators, therapists, etc.) to provide whole-person care.
- Communicates effectively with patients during and between appointments to ensure questions are answered and concerns are addressed by leveraging Oula’s technology.
- Able and excited to educate about and promote the midwifery model of care to current and prospective patients, with a focus on growing Oula’s patient population.
- Works collaboratively with Oula’s product & engineering team to give feedback on the patient portal to create a more personalized, inclusive, and consistent approach to care.
We'll put each as
- .
Now Requirements: mandatory items from "Desired Experience & Qualifications:":
- Must hold active state licensure as required to practice midwifery in the clinic’s state (or be eligible to obtain it before start), and current certification by the AMCB as a Certified Nurse-Midwife or Certified Midwife.
- Two or more years of full-scope clinical midwifery experience preferred; we also welcome strong earlier-career candidates who are approaching that mark.
- Experience caring for diverse communities with a wide variety of needs.
- Great professional references and a reputation for providing exceptional patient care valued by your patients and colleagues.
- Experience with telemedicine or elements of virtual care.
We could also include any extra “bonus” skills or passions that will help us serve our patients (i.e. the ability to communicate with patients in their preferred language, passion for birth equity work, lactation certification, nutrition/diabetes training, etc.) but those are bonus, maybe go to Skills.
Now Skills: "Preferred Skills" list:
- Early pregnancy loss options counseling and medical management
- Familiarity with Perinatal Mental Health
- Basic bedside sonography skills (1st Trimester Viability and positioning confirmation)
Also the bonus skills mentioned earlier could be included here.
Now Benefits: "Oula offers a competitive total rewards package which includes base salary, and comprehensive benefits." Also maybe mention "competitive total rewards package". We'll put a
stating that.
Pay: Salary Range: $118,000 USD - $150,000 USD.
Schedule: description from role: flexible schedule, typical schedule includes approx two office days per week, average 2
- . For Requirements/Qualifications maybe also list. For Skills list. For Benefits maybe list if we have items; but we only have generic statement; could just use
. For Pay maybe
. For Schedule maybe
or
- if we list items.
We must not include boilerplate like EEO, legal, navigation, cookie, application instructions. So remove those sections.
We need to preserve all substantive info: include description of Oula, About Oula? 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
- ... each responsibility
- .
Now Requirements: mandatory items from "Desired Experience & Qualifications:":
- Must hold active state licensure as required to practice midwifery in the clinic’s state (or be eligible to obtain it before start), and current certification by the AMCB as a Certified Nurse-Midwife or Certified Midwife.
- Two or more years of full-scope clinical midwifery experience preferred; we also welcome strong earlier-career candidates who are approaching that mark.
- Experience caring for diverse communities with a wide variety of needs.
- Great professional references and a reputation for providing exceptional patient care valued by your patients and colleagues.
- Experience with telemedicine or elements of virtual care.
We could also include any extra “bonus” skills or passions that will help us serve our patients (i.e. the ability to communicate with patients in their preferred language, passion for birth equity work, lactation certification, nutrition/diabetes training, etc.) but those are bonus, maybe go to Skills.
Now Skills: "Preferred Skills" list:
- Early pregnancy loss options counseling and medical management
- Familiarity with Perinatal Mental Health
- Basic bedside sonography skills (1st Trimester Viability and positioning confirmation)
Also the bonus skills mentioned earlier could be included here.
Now Benefits: "Oula offers a competitive total rewards package which includes base salary, and comprehensive benefits." Also maybe mention "competitive total rewards package". We'll put a
stating that. Pay: Salary Range: $118,000 USD - $150,000 USD. Schedule: description from role: flexible schedule, typical schedule includes approx two office days per week, average 2
or drop it." There's also an "About Oula:" section earlier. Should we include that? The instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The sections we can use are limited to the list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not include an "About Oula" heading because it's not in the allowed list. However we could fold that content into About the role? Probably not; but the instruction says we can only use those headings. So we must omit the About Oula description? But we need to preserve ALL substantive information. However the instruction says we should output only HTML fragment using those headings; if we omit About Oula, we lose substantive info. But maybe we can incorporate About Oula content into About the role section? The About the role section currently is about the role; we could add a brief paragraph about Oula before responsibilities? But the heading is About the role; we could include Oula description as part of that section? Might be okay. However 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 ...)". It might be okay to include other headings if needed, but they gave examples. Safer to stick to those headings only. We could put Oula description in a
before the first heading, as minor metadata? It's not minor; it's substantive. But maybe we can treat it as part of About the role? The About the role heading could contain both role description and company overview. That might be acceptable. Thus structure:
About the role
[combined Oula description + role description]
ThenResponsibilities
Requirements
maybe combine licensure, certification, experience, etc.
Or we could list. ThenQualifications
maybe similar to requirements; but we might combine? However we need separate sections only if posting has real specific content for each. The posting has "Desired Experience & Qualifications". That could be considered both requirements and qualifications. We could split: Requirements: licensure, certification, experience; Qualifications: maybe the "bonus" skills? But they also have "Preferred Skills". So we could treat Requirements as mandatory (licensure, certification, 2+ years experience). Qualifications as preferred/experience items? But the instruction says prefer a few substantive sections over many thin ones. Might be better to have Requirements covering licensure, certification, experience, and Qualifications covering the "bonus" skills and preferred skills? However they also have "Preferred Skills" separate. So we could have Skills for preferred skills. Then Qualifications could be empty? Better to combine Requirements and Qualifications into one section? But we need to follow instruction: include a section ONLY when posting has real specific content for it. If we combine, we might lose distinction but still preserve info. Could have Requirements (mandatory) and Qualifications (preferred) both as sub-sections? But they'd be thin. Maybe we can have Requirements (mandatory) and Skills (preferred). And omit Qualifications heading because content overlaps with Requirements/Skills. But the instruction list includes Qualifications as possible heading; we can omit if not needed. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. Now we need to extract content. About Oula description: "Oula delivers maternity care built around our patients—offering comprehensive support before, during, and after pregnancy. With fewer C-sections and higher VBAC success rates, our research-backed approach is delivering better outcomes. Our team of trusted midwives, OBGYNs, and dedicated care navigators ensure our patients get the type of care they need in the moments that matter most. Since launching in 2021, we’ve expanded to include Preconception and Miscarriage Care, Pregnancy Care, Postpartum Support, and Gynecology. We currently have 4 clinics in the tri-state area, with three new clinics opening in 2026! Come join our team of clinicians, innovators, operators, and technologists passionate about setting a new standard in maternity care. Oula is redesigning maternity care from the ground up. Our modern maternity centers combine the best of obstetrics and midwifery care to deliver a more evidence-based and personalized pregnancy experience. From our collaborative medical team and welcoming clinics to our remote care platform, we are setting a new standard for pregnancy that unifies modern medicine and human intuition. Since opening our first tech-enabled, collaborative care clinic in 2021, we have grown across multiple markets and continue to expand." Role description: "We are looking for a Certified Nurse-Midwife (CNM) to join our growing maternity care practice. We’re searching for someone who is thoughtful and passionate about delivering patient-centric, judgment-free care, and is excited to join a dynamic and innovative team. This is the perfect opportunity for a CNM who is excited to expand their skill set and help define and build a new best-in-class maternity care experience. You will be responsible for delivering full-spectrum perinatal care, as well as helping to shape and refine Oula’s clinical care model. At Oula, midwives lead their own panels within a truly collaborative model — OB-GYNs are integrated members of the same team, not a separate referral tier — and our patients deliver at our partner hospital. With fewer C-sections and higher VBAC success rates, our research-backed approach delivers better outcomes for the communities we serve. This is the autonomy-with-backup practice many midwives are looking for and rarely find. This is a full-time position with a flexible schedule that varies based on market and operational needs. At steady-state staffing, a typical schedule includes approximately two office days per week, an average of 24 hours of on-call coverage per week (with a protected post-call day off where applicable), and dedicated administrative and didactic time. During the launch of new markets or other ramp-up periods, scheduling needs—including on-call responsibilities—may temporarily be greater as the practice grows. Part-time and per-diem arrangements may be available depending on clinic needs." We can combine Oula description and role description into About the role section. Now Responsibilities list: from "Key Responsibilities:" bullet points: - Provides full-scope midwifery care during pregnancy, labor, birth, and postpartum across a variety of settings: our clinics, our partner hospital, and virtually. - Attends births as the primary delivering clinician for low-risk patients, supporting physiologic labor and birth while recognizing when escalation or consultation is indicated. - Collaborates with other team members (e.g., obstetricians, nurses, MAs, doulas, coordinators, therapists, etc.) to provide whole-person care. - Communicates effectively with patients during and between appointments to ensure questions are answered and concerns are addressed by leveraging Oula’s technology. - Able and excited to educate about and promote the midwifery model of care to current and prospective patients, with a focus on growing Oula’s patient population. - Works collaboratively with Oula’s product & engineering team to give feedback on the patient portal to create a more personalized, inclusive, and consistent approach to care. We'll put each as