UNIV - Staff Scientist I - Department of OBGYN

We need to output HTML fragment with sections: headings

for sections present. Must not repeat job title. Must not include Job ID etc. Must include only sections with real content. Must not include boilerplate like EEO, E-Verify, etc. Must remove cookie/navigation/legal/EEO etc. Must preserve all substantive info. We need to parse the job description. Key sections: - About the role? Not explicit but we have summary: "A position for Staff Scientist 1 is open in the laboratory of Dr. David P. Mysona, MD. He is a Gynecologic Oncologist and surgeon scientist. His specialty administers chemotherapy, immunotherapy, and performs radical surgical procedures. His lab receives patient samples from himself and seven other Gynecologic Oncologists providing unprecedented axis to longitudinal patient tumor and blood samples. His lab is focused on using human specimens to decipher the endometrial cancer immune microenvironment and using this knowledge to develop novel therapies for this disease site." That could be "About the role" or "Job Summary". Use heading

About the role

maybe. - Responsibilities: The "Job Description" paragraph includes duties: self-starter, independent thinker, team player, assist in planning and oversight of research projects, use flow cytometry, etc. Also "Principal duties are to assist in experiments for research projects under supervision of the project head and the PI of the laboratory." Also "Core Competencies Preferred" list. - Requirements: The "Core Competencies Preferred" list includes many skills. - Qualifications: Not explicit but maybe "Core Competencies Preferred" is qualifications. Could also include "Physical Requirements" and "Additional New Requirements". Those could be under "Requirements" or "Qualifications". We need to decide. - Skills: Could be separate but we have many skill lists; maybe combine into "Skills". However we need to avoid thin sections. Perhaps we can have sections: About the role, Responsibilities, Requirements (including core competencies, physical requirements, additional new requirements), Benefits? Not given. Pay? Not given (pay range 0.00 - 0.00 - 0.000 but that's placeholder; we must not create Pay section if it's just placeholder or zero? The instruction: 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. Here pay range is all zeros, which seems placeholder; better to omit Pay section. - Schedule: Scheduled Weekly Hours 40, Work Shift (blank). That's real: 40 hours per week. Could create Schedule section with that info. It's not placeholder. So we can include Schedule. - Benefits: Not mentioned. - Qualifications: Could be separate from Requirements. But we have core competencies, physical requirements, additional new requirements. Could combine into Requirements. We need to avoid duplication. Let's extract substantive content. First, About the role summary paragraph. Second, Responsibilities: The "Job Description" paragraph after "Job Description" heading includes many duties. Also "Principal duties are to assist in experiments for research projects under supervision of the project head and the PI of the laboratory." Also "Core Competencies Preferred" maybe more like qualifications. But we can treat "Job Description" as Responsibilities. Third, Requirements: Could include "Core Competencies Preferred", "Physical Requirements", "Additional New Requirements". Also maybe "Worker Type Employee" etc but that's metadata; we can drop. Fourth, Schedule: "Scheduled Weekly Hours 40 Work Shift". Could phrase as "40 hours per week". We need to output HTML with

headings and

• for lists,

  for prose. We must not include boilerplate: EEO, E-Verify, etc. Also remove "Additional Job Description Physical Requirements:" heading? We'll keep the content under Requirements. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep the specifics: e.g., list of core competencies exactly as given. Let's extract core competencies list: "Core Competencies Preferred 2D and 3D cell culture (especially 3D microfluidic culture of organotypic tumor spheroids)Handling, processing, and culturing primary tumor specimens and peripheral blood mononuclear cellsFlow CytometryCell viability studies (including IncuCyte live cell image analysis)Secreted protein profiling (ELISA, Luminex)Specimen preparation for single cell analysis including transcriptomics, CITEseq, T cell repertoire profiling, and proteomicsFluorescence microscopyEnglish language fluencyGood verbal and written communication skillsAbility to work independently and as member of a teamA passion for science and learning" It appears as a run-on string without punctuation. We need to split into items. Likely each competency separated by something? The original had no commas between some. We need to parse logically: - 2D and 3D cell culture (especially 3D microfluidic culture of organotypic tumor spheroids) - Handling, processing, and culturing primary tumor specimens and peripheral blood mononuclear cells - Flow Cytometry - Cell viability studies (including IncuCyte live cell image analysis) - Secreted protein profiling (ELISA, Luminex) - Specimen preparation for single cell analysis including transcriptomics, CITEseq, T cell repertoire profiling, and proteomics - Fluorescence microscopy - English language fluency - Good verbal and written communication skills - Ability to work independently and as member of a team - A passion for science and learning We'll create

  • for each. Physical Requirements: list many items with frequency descriptors. We need to keep them as is. Could be a
    with each line. Additional New Requirements: list: - Ability to obtain and maintain a valid drivers license. - Computer literacy. - Ability to work rotating shifts as required. - Ability to work overtime as required. - Ability to learn and use new processes, tools and equipment as required. - If you like working with energetic enthusiastic individuals, you will enjoy your career with us! (This is fluff; maybe we can keep as prose? It's not a requirement but a statement. Might be considered boilerplate? It's not EEO; it's a motivational line. Could keep as a

    under Additional New Requirements or maybe under About the role? But it's under Additional New Requirements heading. We'll keep as a

    . Also note: "If you like working with energetic enthusiastic individuals, you will enjoy your career with us!" is not a requirement but a statement; we can keep as prose. Now schedule: "Scheduled Weekly Hours 40 Work Shift". Could be a

    stating 40 hours per week. Now we need to ensure we don't repeat job title. Not include "Staff Scientist 1" as heading. Now produce HTML. Structure:

    About the role

    ... summary paragraph ...

    Responsibilities

    ... responsibilities paragraph ...

    Requirements

    Maybe split into subheadings? But we only allowed

    for section headings. Could have multiple

    sections: Core Competencies, Physical Requirements, Additional New Requirements. But the instruction: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So we can have multiple

    sections each representing a category. We could have separate sections for Core Competencies, Physical Requirements, Additional New Requirements. But they said prefer a few substantive sections over many thin ones. However these are substantive. Could combine into one Requirements section with sublists? But we need to use

    • for any list. Could have a single Requirements section with multiple
      lists each preceded by a

      describing the category. That's acceptable. Thus:

      Requirements

      Core Competencies Preferred:

      ...

      Physical Requirements:

      ...

      Additional New Requirements:

      ...
      But we need to avoid using ? Not prohibited. Could just put a

      heading like "Core Competencies Preferred:" then list. Now schedule:

      Schedule

      Scheduled Weekly Hours: 40 hours per week.

      Now ensure we didn't include boilerplate: Remove EEO, E-Verify, etc. Also remove "Worker Type Employee Worker Sub-Type Research Grant Cost Center ..." etc. Now check for any other substantive info: "Entity Medical University of South Carolina (MUSC - Univ)" maybe we can include in About the role? It's metadata but could be considered part of the role's institution. Might keep as part of About the role: "Position at Medical University of South Carolina (MUSC)". The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

      or drop it. So we can include the entity as a short sentence in About the role. Thus About the role paragraph could be: "A position for Staff Scientist 1 is open in the laboratory of Dr. David P. Mysona, MD, a Gynecologic Oncologist and surgeon scientist at the Medical University of South Carolina (MUSC). His lab receives patient samples from himself and seven other Gynecologic Oncologists, providing unprecedented access to longitudinal patient tumor and blood samples. The lab focuses on using human specimens to decipher the endometrial cancer immune microenvironment and develop novel therapies for this disease." We need to preserve all substantive information; we must not lose details like "His specialty administers chemotherapy, immunotherapy, and performs radical surgical procedures." That is substantive about Dr. Mysona. Include that. Also "His lab is focused on using human specimens to decipher the endometrial cancer immune microenvironment and using this knowledge to develop novel therapies for this disease site." Include. Now Responsibilities: need to capture all duties from the Job Description paragraph. Let's extract that paragraph: "The successful candidate will be a self-starter, independent thinker, and team player, who has a passion for science. They will assist in the planning and oversight of research projects that utilize in vivo, ex vivo, and in vitro model systems to examine the endometrial cancer immune microenvironment and develop novel therapeutic strategies to overcome resistance to immunotherapy in this cancer. The successful candidate will primarily use flow cytometry to analyze the phenotypes of immune cells within the tumor microenvironment and ex vivo patient-derived tumor models (patient-derived organotypic tumor spheroids, PDOTS) to test interventions targeting immune cell phenotypes to decipher mechanisms of response and resistance to immunotherapy in endometrial cancer. The level of complexity of this work is high with requisite knowledge of cancer cell biology, T cell biology, including non-conventional T cells, basic immunology, cancer immunology, and 3D tumor modeling. Further, this position involves project management experience and experience supervising 1 or more research technicians and assisting in the teaching and training of graduate students and other trainees. The candidate is expected to develop new areas of research, conduct experiments and data analysis, assist with the preparation of manuscripts and grants, and present at meetings. Principal duties are to assist in experiments for research projects under supervision of the project head and the PI of the laboratory. Specifically, the lab is part of Medical University of South Carolina & Hollings Cancer Center. The focus is on immunotherapy in endometrial cancer. The primary role of this position is to process patient samples from the clinic and operating room using the lab’s cutting-edge technology to evaluate immune cell phenotypes and their role in response and resistance to immunotherapy in endometrial cancer." We need to preserve all that. We'll put in a

      . Now Requirements: we need to include core competencies list exactly as given (but we split). Ensure we don't lose any. Let's list core competencies items as we identified. Now Physical Requirements list: need to keep each item with its frequency descriptor in parentheses. Let's extract them exactly: - Ability to perform job functions in an upright position. (Continuous) - Ability to perform job functions in a seated position. (Continuous) - Ability to perform job functions while walking/mobile.