Medical Assistant Outpatient Oncology Bilingual

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the job posting. Content: - Intro about company: "Starling Oncology (NASDAQ: STLN) is advancing oncology..." This is about the company, could be "About the role"? Actually "About the role" is about the job, but we could treat as "About the role" or maybe "About the company". The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include "About the role" with description of role purpose and summary. - Job purpose and summary: "The Medical Assistant is adaptable..." That's about role. - Essential duties and responsibilities: list. - Knowledge, skills, and abilities: list. - Experience, education and/or training: list. - Physical working requirements: maybe could be part of Requirements or Qualifications? Could be separate but not in list of allowed headings. Could fold into Requirements or Qualifications. Probably include under Requirements. - Pay: "Pay Transparency for hourly teammates $24—$27.88 USD". That's specific pay range. So include Pay section. - Benefits: Not explicitly mentioned. There's mention of mileage reimbursement, but that's not benefits. No explicit benefits like health insurance etc. So we should not create Benefits section unless posting actually states them. It does not list benefits, so omit. - Schedule: Not mentioned explicitly. There's "willing and able to work assigned shifts at multiple clinic locations". Not a specific schedule. So we should not create Schedule section unless posting actually states them. It does not give schedule details, so omit. - Also there is "SAME DAY INTERVIEWS..." and AI Recruiter assistant etc. Those are boilerplate/application instructions; we should remove. - Also "The estimate displayed represents the typical wage range..." that's part of pay. - Also "Mileage will be reimbursed." That's a benefit? Could be considered a benefit but not typical benefits like health, 401k. The instruction: "Prefer a few substantive sections over many thin ones." We could include mileage reimbursement under Benefits? But they said only include Benefits section if posting actually states them. It does state mileage reimbursement, which is a benefit. So we could include Benefits section with that detail. However they also said "never emit a heading followed by filler/placeholder text". Mileage reimbursement is specific. So we could include Benefits. But we need to decide: The list of allowed headings includes Benefits. So we can include Benefits if there is real content. There is "Mileage will be reimbursed." That's a benefit. Also maybe "Same day interviews" is not a benefit. So we can include Benefits with that bullet. Also there is "AI Recruiter Assistant" etc - remove. Also "The estimate displayed represents the typical wage range..." is part of Pay. Also "BLS and CPR certification preferred." etc. We need to preserve all substantive information; do not invent or summarize away detail. We need to use

• for any list of duties/requirements/benefits, and

  for prose. We need to not repeat the job title as a heading. We need to not put Job ID/requisition numbers as headings. We need to output only HTML fragment. Let's structure:

  About the role

  ... job purpose and summary ... maybe also company description? The "About the role" could include the job purpose and summary paragraph(s). We'll include the paragraph from "JOB PURPOSE AND SUMMARY:" plus maybe the earlier description about the role? The earlier paragraph about "At Starling Oncology, our Medical Assistants play a vital role..." is also about role. We'll combine. We need to preserve all substantive information, so we need to include the company description? That is not about the role but about the company. Could be omitted? The instruction says preserve ALL substantive information; do not invent or summarize away detail. The company description is substantive but not about the role. However we have no heading for "About the company". The allowed headings list does not include About the company. But we could still include it under About the role? Might be misrepresenting. However we could include a

  before any headings that is not under 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 those for section headings. It might be okay to have a

  for introductory prose before any heading. The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

  • for any list of duties/requirements/benefits, and

    for prose." It doesn't say we cannot have other headings, but we should follow the pattern. Probably we should include a brief intro paragraph before the first heading, describing the company. That's permissible as prose. Thus:

    Starling Oncology (NASDAQ: STLN) is advancing oncology by delivering highly specialized, value-based cancer care in the community setting. Formerly known as The Oncology Institute, Starling Oncology offers cutting-edge, evidence-based cancer care to a population of approximately 2.1 million patients, including clinical trials, transfusions, and other care delivery models traditionally associated with the most advanced care delivery organizations. With more than 400 employed and network clinicians and over 100 clinics and network locations of care across five states and growing, Starling Oncology is changing oncology for the better. For more information, visit www.starlingoncology.com.

    Then we can have

    About the role

    with the job purpose and summary. Then

    Responsibilities

    with the essential duties list. Then

    Requirements

    maybe combine Knowledge, Skills, and Abilities and Experience, Education and/or Training and Physical working requirements? But we have separate headings for Qualifications, Skills. The instruction list includes Qualifications, Skills. So we could split: Requirements maybe for experience/education, Qualifications for knowledge/skills/abilities, Skills for specific abilities? However they said "Prefer a few substantive sections over many thin ones." So we might combine into fewer sections. But we need to follow the instruction: Use headings for those categories if we have content. We have content for Knowledge, Skills, and Abilities (list). That's like Skills. We have Experience, Education and/or Training (list). That's like Qualifications. We have Physical working requirements (list). That could be part of Requirements or Qualifications. We could make a section "Requirements" for experience/education/physical. And "Skills" for knowledge, skills, abilities. Or we could have "Qualifications" for experience/education, "Skills" for knowledge/skills/abilities, and maybe omit Requirements if we cover physical under Qualifications. Let's decide. We need to preserve all substantive information. So we need to include all lists. Option: Use

    Qualifications

    for Experience, Education and/or Training and Physical working requirements (maybe combine). Use

    Skills

    for Knowledge, Skills, and Abilities. But we also have "About the role" and "Responsibilities". Then "Pay". Then "Benefits" for mileage reimbursement. Thus sections: About the role, Responsibilities, Qualifications, Skills, Pay, Benefits. Check if any content missing: The "Essential duties and responsibilities" list is under Responsibilities. The "Knowledge, skills, and abilities" list is under Skills. The "Experience, education and/or training" list plus physical working requirements under Qualifications. Pay: we have pay range. Benefits: mileage reimbursement. We need to ensure we don't include filler like "commensurate with experience". Not present. Now we need to format lists as
    • . For prose, use

      . We need to avoid repeating the job title as heading. Not needed. We need to not include Job ID etc. Now let's extract the exact text. Company description paragraph: "Starling Oncology (NASDAQ: STLN) is advancing oncology by delivering highly specialized, value-based cancer care in the community setting. Formerly known as The Oncology Institute, Starling Oncology offers cutting-edge, evidence-based cancer care to a population of approximately 2.1 million patients, including clinical trials, transfusions, and other care delivery models traditionally associated with the most advanced care delivery organizations. With more than 400 employed and network clinicians and over 100 clinics and network locations of care across five states and growing, Starling Oncology is changing oncology for the better. For more information, visit www.starlingoncology.com." We'll keep that as a

      . Then "SAME DAY INTERVIEWS: ..." is boilerplate/application instructions; remove. Then "At Starling Oncology, our Medical Assistants play a vital role in transforming the patient experience. You'll be part of a compassionate care team that helps patients navigate one of the most important journeys of their lives—with dignity, empathy, and hope." This is about role; we can include in About the role paragraph. Then "JOB PURPOSE AND SUMMARY: The Medical Assistant is adaptable, dependable, and eager to advance their clinical careers. As an essential member of the patient care team, the Medical Assistant will provide both administrative and clinical support to ensure the smooth operation of the clinic. The MA should deliver high-quality, compassionate patient care, enhancing clinic efficiency, and contributing to an outstanding patient experience. This position also offers the opportunity to be cross trained in patient registration and medical records support, as needed. Teammates must be willing and able to work assigned shifts at multiple clinic locations and drive between clinics as needed to support patient care and business operations. Mileage will be reimbursed." We need to preserve all that. Note mileage reimbursement appears here; but we also plan to put mileage under Benefits. However it's mentioned here; we should not duplicate. We could keep it in About the role or Responsibilities? It's a benefit. We'll keep it in Benefits section and maybe remove from About the role to avoid duplication? But instruction says preserve ALL substantive information; we can keep it in both places? That would be duplication. Better to keep it once. Since it's a benefit, we can put it under Benefits and not repeat in About the role. However the About the role paragraph currently includes that sentence. We could edit to remove the mileage sentence from About the role, but that would be removing substantive information (the mileage reimbursement). But we will still have it in Benefits, so the information is preserved. However we are removing it from the About the role paragraph, which is also substantive. But we could keep it there and also in Benefits, causing duplication. The instruction says preserve ALL substantive information; duplication is not prohibited but might be considered redundant. It didn't forbid duplication. However they said "do NOT invent or summarize away detail." Duplication is not inventing or summarizing away. It's okay but maybe not ideal. However to keep it simple, we could keep the mileage sentence in About the role and also include Benefits section with mileage reimbursement (maybe just mention it again). That would duplicate but still preserve. However they said "Prefer a few substantive sections over many thin ones." Duplication might be considered thin? Not sure. Better to keep mileage in Benefits and remove from About the role to avoid duplication, but we must ensure we still have the substance elsewhere. Since we will have Benefits section with mileage reimbursement, the information is preserved. The About the role paragraph will lose that sentence, but we could keep the rest. Is that considered summar