NP or MD

We need to output HTML fragment only, with sections for headings where there is real content. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Preserve all substantive info. We need to parse the posting. Content: - Intro: "At Saban we believe in the employee experience, and know you are the heart of our business! Work shouldnt consume your life, we believe in Work-Life-Balance and strive for flexibility through various company perks." This is about employee experience, maybe part of About Us? But we have an "About Us" later. Could be part of "About the role"? Actually "About the role" heading is for description of role. The intro is more about company culture. Could be placed under "About Us" or maybe "About the role"? The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide which sections have content. We have: - Benefits And Perks: list: Free Medical coverage options, We cover all out of pocket expenses! Chiropractor/Acupuncture covered at 100% in-network, HMO and PPO Dental coverage options, Vision, Weekend Shift Differential Pay, 403(b) retirement plans with employer matching, Generous paid time off including 1-Week Holiday closure for Christmas & New Years!, Competitive Wages & Annual Merit Increase. Thus Benefits section. - Pay: "Pay for an MD would be $270k + $15k sign on bonus." Also maybe "Competitive Wages & Annual Merit Increase" but that's more benefits. We have explicit pay figure. So Pay section. - Schedule: "40hrs/wk @ 8405 Beverly Blvd 90048. M-F preferred but open to alternative schedules". Also maybe "Weekend Shift Differential Pay" is part of benefits but schedule info: 40hrs/wk, M-F preferred but open to alternative schedules. So Schedule section. - Duties And Responsibilities: list of duties. - Position Requirements: list of requirements. - Qualifications? The posting includes "Physician or Nurse Practitioner(adults, geriatrics) with eligibility for 103 license and is interested in eventually getting their 104." Also "valid license to practice medicine as a Nurse Practitioner or Physician in the State of California, with no pending or previous disciplinary action from any state licensing entity", "Current DEA license and BLS certificate", "Competency in general adult ambulatory care, family planning, adolescent, and women’s health.", etc. That could be Requirements or Qualifications. The instruction says we have separate headings for Requirements and Qualifications. We need to decide what goes where. Usually Requirements are mandatory, Qualifications are preferred. The posting lumps them together. We could split: Requirements: mandatory items (license, DEA, BLS, competency, ability to relate, etc). Qualifications: preferred items (bilingual Spanish, prior experience, knowledge of regulations, experience with county/state/federal programs). But we need to follow instruction: include a section ONLY when the posting has real, specific content for it. So we can have both Requirements and Qualifications if we can delineate. We also have Skills: maybe "Ability to relate and communicate well to all cultural and ethnic groups in the community, including fluency in written and spoken English. Bi-lingual skills in written and spoken Spanish are preferred." That's a skill. Also "Ability to perform clinical duties within established guidelines in a organized, efficient manner". Could be skill. But we may not need separate Skills if we can incorporate into Requirements/Qualifications. However we have headings for Skills; we could create a Skills section for things like communication, bilingual, etc. But we need to avoid thin sections. Let's see if we have enough distinct content for Skills. We also have "About the role": maybe the introductory paragraph about employee experience and work-life balance could be considered "About the role". Or we could use "About Us" but that's not in allowed headings list. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we must use those. So we need to map content to those. Thus: - About the role: maybe a brief description of the role: "Seeking a Physician or Nurse Practitioner(adults, geriatrics) with eligibility for 103 license and is interested in eventually getting their 104." plus maybe the location and schedule? But schedule is separate. Could include "Provides primary care services to Clinic patients". That's more responsibilities. So About the role could be a summary: "We are looking for a Physician or Nurse Practitioner to provide primary care services..." But we must not invent. We can use the sentence: "Seeking a Physician or Nurse Practitioner(adults, geriatrics) with eligibility for 103 license and is interested in eventually getting their 104." That's specific. Also maybe "Work shouldnt consume your life, we believe in Work-Life-Balance and strive for flexibility through various company perks." That's about company culture, not role. Could be part of About the role? Might be okay but it's not role-specific. However we need to preserve all substantive info; we can include it under About the role as part of company culture? Might be okay. Better: Use About the role to include the introductory statements about Saban's belief in employee experience, work-life balance, etc. That is substantive and not duplicated elsewhere. So we can put that there. - Responsibilities: the Duties And Responsibilities list. - Requirements: mandatory items: Physician or Nurse Practitioner with eligibility for 103 license and interest in 104; valid license to practice medicine as NP or Physician in CA, no pending/previous disciplinary action; Current DEA license and BLS certificate; Competency in general adult ambulatory care, family planning, adolescent, and women’s health; Ability to perform clinical duties within established guidelines in an organized, efficient manner; Ability to relate and communicate well to all cultural and ethnic groups in the community, including fluency in written and spoken English. (maybe language fluency is requirement). Also maybe "Working knowledge of direct outpatient care and management methods and practices in a community clinic setting." Could be requirement or qualification. We'll decide. - Qualifications: preferred items: Bi-lingual skills in written and spoken Spanish are preferred; Prior experience in a similar setting is preferred; Basic knowledge of local, state and federal regulations relating to care of patients in a clinic setting; prior experience with county, state and federal programs such as CHDP, FPACT, EWC, Medi-Cal and Title X is preferred; maybe also "Understanding of current medical, educational and psychosocial intervention procedures" could be qualification. - Skills: maybe we can combine some overlapping but we could create Skills for communication, bilingual, etc. But we already have language in Requirements/Qualifications. Might be redundant. Could skip Skills if no distinct content. But we have "Ability to relate and communicate well..." which is a skill. Could put under Skills. However we already used that in Requirements. Might be better to put under Skills and keep Requirements more about licensure etc. Let's think. We need to avoid thin sections. If we create Skills with just one bullet, it's thin. Better to incorporate into Requirements or Qualifications. Thus we may omit Skills section. Now Benefits: we have list. Pay: we have specific pay figure. Schedule: we have 40hrs/wk, M-F preferred but open to alternative schedules. Now we need to ensure we don't include boilerplate like "Compensation Disclaimer Actual salary offers are considered by various factors..." That's boilerplate but it's about compensation disclaimer. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The compensation disclaimer might be considered legal boilerplate? It's about salary offers being subject to change. Might be considered boilerplate but it's substantive? It's a disclaimer about pay. The instruction says "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." It doesn't explicitly say to remove compensation disclaimer. However earlier: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The compensation disclaimer is legal-ish. Might be considered boilerplate. Safer to drop it? But we need to preserve ALL substantive information; do NOT invent or summarize away detail. The disclaimer is not substantive info about the job; it's a legal disclaimer. I'd drop it. Also the EEO statement at the end: "Saban Community Clinic will consider qualified applicants with criminal history pursuant to the California Fair Chance Act..." and "We are an Equal Opportunity Employer..." That's EEO boilerplate; remove. Also "About Us" paragraph: we could incorporate into About the role? But we have an About Us paragraph describing mission, values, etc. That's substantive about the company. Could be placed under About the role? Might be okay but it's not about the role. However we don't have an About Us heading allowed. So we need to decide where to put it. Could we put it under About the role as a brief description of the organization? The instruction says "About the role" heading for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So About the role likely expects description of the role, not the company. But we have no other heading for company info. However we could treat the About Us content as part of About the role? Might be acceptable but not ideal. However we must preserve all substantive information; we cannot drop it. So we need to include it somewhere. Perhaps we can include it under About the role as a short paragraph about the organization, acknowledging that it's about the company but it's still substantive. The instruction didn't forbid including company info under About the role. It just gave examples of headings. So we can use About the role to include both role and company overview. Alternatively, we could create a separate section 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? It says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It might imply we should use those headings when appropriate, but we could also use other headings? The examples are given; but the instruction says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It seems they expect us to use those headings. It doesn't say we cannot use other headings, but to be safe we should stick to those. Thus we need to fit About Us content into one of those headings. Which one fits best? Maybe "About the role" can include a brief about the organization as context. We'll do that. Now we need to ensure we don't include filler like "commensurate with experience", "not specified", etc. We have specific content. Now we need to output HTML fragment only, no /, no markdown. We'll structure:

About the role

At Saban we believe in the employee experience, and know you are the heart of our business! Work shouldnt consume your life, we believe in Work-Life-Balance and strive for flexibility through various company perks