Project Manager, General Surgery (Remote Opportunity)

The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and apply the rules. First, I need to identify the sections: - About the role (introductory paragraph) - Responsibilities (Core Duties listed) - Requirements/Qualifications (Desired Qualifications, Minimum Education And Experience Required, Knowledge, Skills And Abilities, Certificates And Licenses Required) - Benefits? Not explicitly stated - there's "About Us" but that's more company description - Pay? Not mentioned - Schedule? Mentioned: "standard work week is 40 hours, with flexibility required during critical project phases" and "remote work environment" and "occasional travel" - Skills? Could be part of qualifications Rules: - Use

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

• for lists - Use

  for prose - Do NOT repeat job title as heading - Do NOT put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove boilerplate (EEO, equal opportunity, scam warnings, application instructions, cookie/navigation/legal) - Include section ONLY when real specific content exists - Never emit heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits sections unless posting actually states them - Prefer few substantive sections over many thin ones - Output ONLY HTML fragment, no /, no markdown code fences Let me parse the content: 1. Introductory paragraph: "This position can operate within a remote work environment. The role may require occasional travel to clinical sites or partner facilities. The standard work week is 40 hours, with flexibility required during critical project phases. The Division of General Surgery is seeking a strategic and results-oriented Project Manager to support initiatives within the Canary Center, Division of General Surgery, and Cancer Clinical Trials Office at Stanford University School of Medicine. Under faculty and research leadership, this role will develop, implement, and coordinate strategic programs focused on precancer research, clinical initiatives, and operational excellence. The Project Manager will lead cross-functional projects from inception through completion, coordinate clinical, research, and administrative stakeholders, and ensure the timely and successful delivery of program goals." This is "About the role" content. 2. Desired Qualifications: list of qualifications including Master's degree, Doctoral preferred, 5 years experience, regulatory knowledge, analytical skills, communication, tools proficiency. This is a list. 3. Responsibilities: Core Duties listed as bullet points (though in text they're separated by line breaks). Should be

  • . 4. Minimum Education And Experience Required: Bachelor's degree and three years relevant experience, etc. 5. Knowledge, Skills And Abilities: list of abilities. 6. Certificates And Licenses Required: for teaching jobs, advanced degree or certification may be required. 7. About Us: company description - but this is boilerplate? It's specific to Stanford but generic. The rule says remove boilerplate, but "About Us" might be considered company info. However, the rule says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The "About Us" section is not exactly boilerplate but it's generic. The rule also says "include a section ONLY when the posting has real, specific content for it". This is generic Stanford mission statement. I think we should omit it as it's not specific to the role. 8. The last paragraphs: "The job duties listed are typical examples... Employees may also perform other duties as assigned. Consistent with its obligations under the law... Stanford is an equal employment opportunity..." This is legal/EEO boilerplate - remove. Also note: "Schedule" info is in the first paragraph: remote work, occasional travel, 40 hours week with flexibility. That's specific schedule info. Should we create a Schedule section? The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state schedule info. But it's brief. Could include in About the role or separate Schedule section. Since it's specific, maybe include a Schedule section. Similarly, Benefits? Not mentioned. Pay? Not mentioned. Skills? The "Knowledge, Skills And Abilities" section is essentially skills. Could be a Skills section. Qualifications vs Requirements: The posting has "Desired Qualifications" and "Minimum Education And Experience Required". Could combine into a "Requirements" or "Qualifications" section. The rule says use headings like "Requirements, Qualifications". I'll use "Qualifications" for desired and "Requirements" for minimum? But better to combine into one "Qualifications" section with sub-lists? However, the rule says use

    for section headings. Could have one "Qualifications" heading with multiple lists. But the rule says "Use

    • for any list of duties/requirements/benefits". So we can have multiple
      under one heading. But the rule also says "Prefer a few substantive sections over many thin ones." So maybe combine all qualification-like content into one "Qualifications" section. Let's structure: - About the role (prose) - Responsibilities (list) - Qualifications (multiple lists: Desired Qualifications, Minimum Education and Experience, Knowledge Skills Abilities, Certificates and Licenses) - Schedule (prose from first paragraph) But the first paragraph also includes remote work and travel. That's schedule-related. Could put in Schedule section. Let's extract schedule info: "This position can operate within a remote work environment. The role may require occasional travel to clinical sites or partner facilities. The standard work week is 40 hours, with flexibility required during critical project phases." That's specific. So create a Schedule section. Now, the "About Us" and legal paragraphs: remove. Now, write HTML. We'll have:

      About the role

      ... (the introductory paragraph minus schedule info? Actually the introductory paragraph includes both role description and schedule. I'll keep the role description in About the role, and move schedule info to Schedule section. But the paragraph is mixed. I'll split: first three sentences are schedule, rest is role. So in About the role, include from "The Division of General Surgery is seeking..." onward. In Schedule, include the first three sentences. But the rule says preserve ALL substantive information. So we must include all. We'll split. Let's write. First, About the role:

      The Division of General Surgery is seeking a strategic and results-oriented Project Manager to support initiatives within the Canary Center, Division of General Surgery, and Cancer Clinical Trials Office at Stanford University School of Medicine. Under faculty and research leadership, this role will develop, implement, and coordinate strategic programs focused on precancer research, clinical initiatives, and operational excellence. The Project Manager will lead cross-functional projects from inception through completion, coordinate clinical, research, and administrative stakeholders, and ensure the timely and successful delivery of program goals.

      Schedule:

      Schedule

      This position can operate within a remote work environment. The role may require occasional travel to clinical sites or partner facilities. The standard work week is 40 hours, with flexibility required during critical project phases.

      Responsibilities:

      Responsibilities

      • Develop and manage research programs by conducting research activities, including outreach to varied stakeholders within the program, assigning resources and making program improvement recommendations that impact policies and programs.
      • Identify, recommend and implement opportunities for new research.
      • Source, collect and analyze data, create reports, review and explain trends; formulate and evaluate alternative solutions and/or recommendations to achieve the goals of the program or function.
      • Teach and/or assist in the teaching and administration of courses. Develop curriculum. Develop curriculum-rating survey, detailed feedback on courses and make recommendations for preliminary overview and changes.
      • Write and/or edit complex content for proposals, research grants, peer-reviewed publications, and other program activities.
      • Contribute to and inform on strategic program/entity planning and related funding and financial sustainability.
      • May advise students and/or coach/mentor clients.
      • Develop or contribute to outreach strategy related to program communications, development, partnerships, and fundraising/funding.
      • Coach and mentor program staff.
      Qualifications:

      Qualifications

      Desired Qualifications

      • Master's degree in cancer research or a cancer-related field. A Doctoral degree is preferred.
      • Minimum of 5 years of project management and regulatory experience in national and international oncology clinical trials.
      • Experience working with multidisciplinary research teams, patient engagement teams and multi-stakeholder panels; facilitating large-scale, multi-site grant submissions; and developing/maintaining national and international collaborations.
      • Regulatory Knowledge: Familiarity with HIPAA, other healthcare regulations governing data security and patient care, and external regulatory processes. Proven expertise in undertaking complex regulatory tasks: Submitting IRB applications/amendments; Compiling multi-site national/international Data Use Agreements (DUA) and Material Transfer Agreements (MTA); Clinical trial reporting (clinicaltrials.gov).
      • Analytical and Problem-Solving: Strong analytical, organizational and project management skills with the ability to synthesize and interpret research findings, manage budgets, and solve complex operational challenges. Demonstrated ability to navigate complex clinical trial organizations, including cooperative group infrastructure, NIH organization, and structure of other trial sponsors and funders.
      • Communication: Exceptional written and verbal communication skills, with the ability to translate clinical needs into actionable project plans and integrate within an interdisciplinary research team. Strong presentation skills including dissemination of knowledge products at national and international meetings.
      • Tools Proficiency: Experience with relevant medical research databases and software.

      Minimum Education and Experience Required

      • Bachelor's degree and three years of relevant experience or combination of education, training, and relevant experience.
      • Advanced degree may be required for some programs.
      • For jobs with financial responsibilities, experience managing a budget and developing financial plans.

      Knowledge, Skills and Abilities

      • Ability to develop program partnerships and funding sources.
      • Excellent oral, written, and analytical skills, exhibiting fluency in area of specialization.
      • Ability to oversee and direct staff.
      • Basic knowledge of managing budgets and developing financial plans.

      Certificates and Licenses Required

      • For teaching jobs, advanced degree or certification may be required for some programs.
      But the rule says use

      for section headings. It doesn't mention

      . But we can use

      for subsections? The rule says "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid

      . But to be safe, maybe keep all as

      ? But then we'd have multiple

      for each sub-qualification. That might be okay. However, the rule says "Prefer a few substantive sections over many thin ones." So maybe combine all qualifications under one

      Qualifications

      and use
      for each category but without subheadings? But the categories are distinct. Could use labels within list items? But better to use

      for subsections. The instruction doesn't forbid

      . It says "use

      for section headings". It doesn't say you cannot use other heading levels. I think using

      for subsections is fine. But the output should be only HTML fragment. No markdown. Let's produce final HTML. Check for any missing content: The "Desired Qual