Senior Research Assistant, Center for Surgery and Public Health

We need to output HTML fragment with sections: h3 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, legal, etc. Must not include navigation, cookie, etc. Must preserve all substantive info. We need to parse the posting. Key sections: - Job Summary (the paragraph after "Job Summary"): description of CSPH etc. - Qualifications (first block after "Qualifications"): description of role supporting NIH-funded R01 study, duties etc. - Principal Duties And Responsibilities (list of duties) - Skills/Abilities/Competencies Required (list of skills) - Qualifications (Education etc) Actually there is another "Qualifications" heading later: "Qualifications Education Bachelor's Degree Science required Can this role accept experience in lieu of a degree? Yes Experience relevant research and data management experience 3-5 years required Experience supporting human subjects research, qualitative research methods, and REDCap preferred." We need to decide how to handle duplicate headings. 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. 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. We need to include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. We need to preserve all substantive information. We need to remove boilerplate: EEO statement, legal, competency framework, etc. Also remove "Additional Job Details (if Applicable)" maybe we keep details like Remote Type Hybrid, Work Location, Scheduled Weekly Hours, Employee Type, Work Shift, Pay Range, Grade. Those are substantive: they give schedule, pay, location, etc. So we should include sections for Pay, Schedule, Benefits? Benefits: there is a paragraph about benefits but it's generic: "In addition to competitive base pay, we offer comprehensive benefits, career advancement opportunities, differentials, premiums and bonuses as applicable and recognition programs..." That's somewhat generic but still mentions benefits. However instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state Pay Range and Scheduled Weekly Hours, and mentions benefits. So we can include Pay, Schedule, Benefits sections. But we must not include filler like "commensurate with experience" etc. The Pay Range is specific: $53851.00 - $82,014.40/Annual Grade 6. So we can include Pay section with that. Schedule: "Scheduled Weekly Hours 28 Employee Type Regular Work Shift Day". So we can include Schedule section. Benefits: there is a paragraph about benefits: "In addition to competitive base pay, we offer comprehensive benefits, career advancement opportunities, differentials, premiums and bonuses as applicable and recognition programs designed to celebrate your contributions and support your professional growth." That's somewhat generic but still mentions benefits. It's not filler like "not specified". It's actual statement. So we can include Benefits section with that paragraph. We also have "Remote Type Hybrid Work Location 399 Revolution Drive". That's location info; could be part of a "Location" section but not in allowed headings list. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No Location. So we might incorporate location into a short paragraph under maybe About the role or Responsibilities? But we must not invent headings. Could we add a

  with location info under maybe About the role? The About the role section is not present in the posting; we have Job Summary. The allowed headings include "About the role". We could use that for the Job Summary content. That seems appropriate: "About the role" heading with the Job Summary paragraph. Responsibilities: could map to Principal Duties And Responsibilities. Requirements: could map to Qualifications (the first Qualifications block) or maybe Requirements. Skills: map to Skills/Abilities/Competencies Required. Qualifications: we have Education etc. Could be separate Qualifications section. But we must not repeat headings unnecessarily. We need to decide which sections to include. We have content for: - About the role (Job Summary) - Responsibilities (Principal Duties And Responsibilities) - Requirements (maybe the first Qualifications block about supporting NIH-funded study, duties etc.) Actually that block is more like a description of the role; but we already used About the role for summary. Could treat that as Requirements? Or we could combine. Better: Use sections: - About the role (Job Summary) - Responsibilities (Principal Duties And Responsibilities) - Requirements (Qualifications block about supporting NIH-funded R01 study, etc.) - Skills (Skills/Abilities/Competencies Required) - Qualifications (Education, experience, etc.) - Pay (Pay Range) - Schedule (Scheduled Weekly Hours, Employee Type, Work Shift) - Benefits (benefits paragraph) We must ensure we don't create empty sections. Now we need to format lists. For Responsibilities: list of duties each sentence separated by periods. We'll convert each duty into

• . The duties list: "Conduct research studies as per study guidelines and protocols." "Coordinate facilitated group meetings with participating sites, including scheduling, communications, materials, logistics, and follow-up." "Recruit, screen, and consent study participants across clinical settings." "Collect, manage, and maintain accurate and confidential research data and participant records using REDCap." "Perform data entry, basic quantitative analyses, and routine reporting." "Conduct qualitative coding" "Maintain regulatory documents and IRB as needed." "Assist with drafting annual progress reports and other study documentation" "Collaborate effectively with investigators, research staff, and institutional partners" "Maintain accurate, organized, and confidential study files and records in accordance with applicable policies and ethical research standards." "All other duties as assigned." We'll make each a
• . For Skills: list: "Excellent interpersonal and communication skills are required for working with the study participants." "Good oral and written communication skills." "Proficiency in Microsoft Office applications (Excel, Word, Outlook) and comfort with digital research tools." "Strong organizational skills and ability to manage multiple priorities across concurrent studies." "Demonstrated attention to detail and commitment to data quality." "Professionalism and respect for patient needs, confidentiality, and ethical research conduct." We'll make each a
• . For Requirements (the first Qualifications block): content: "The Senior Research Assistant will support a 5-year NIH-funded R01 study which aims to identify best practices across multiple state trauma systems and identify opportunities to achieve optimal patient outcomes in trauma care at the system-level. They will conduct qualitative coding, provide general project administration, and maintain quality communication within the team to ensure that project milestones and deliverables are completed accurately an on schedule. The role will also support Delphi recruitment and organizing in-person meeting logistics. The Research Assistant may contribute to additional studies or initiatives as they develop, supporting the broader research mission of the team." We can split into sentences as
• maybe. But it's prose; we could keep as

  . The instruction: Use

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

    for prose. So if it's not a list, we keep as paragraph. This block is more like a description; we can keep as

    . For Qualifications (Education etc): content: "Education Bachelor's Degree Science required Can this role accept experience in lieu of a degree? Yes Experience relevant research and data management experience 3-5 years required Experience supporting human subjects research, qualitative research methods, and REDCap preferred." We need to preserve all info. Could format as

    with sentences. We could also split into bullet list: Education, Experience, etc. But it's not explicitly a list; but we could make a list for clarity. However instruction: Use

    • for any list of duties/requirements/benefits. This is not explicitly a list but we could treat as list of qualifications. Safer to keep as

      . For Pay: we have "Pay Range $53851.00 - $82,014.40/Annual Grade 6". Also there is a paragraph about base pay determination. We'll include the Pay Range as

      . Could also include the paragraph about base pay determination but that's generic; maybe we keep just the range. For Schedule: "Scheduled Weekly Hours 28 Employee Type Regular Work Shift Day (United States of America)". Also "Remote Type Hybrid Work Location 399 Revolution Drive". Location maybe we could include in Schedule or a separate paragraph but we don't have a Location heading. Could add to Schedule

      including location and remote type. For Benefits: paragraph: "In addition to competitive base pay, we offer comprehensive benefits, career advancement opportunities, differentials, premiums and bonuses as applicable and recognition programs designed to celebrate your contributions and support your professional growth." We'll output as

      . Now we need to ensure we don't include boilerplate: EEO statement, legal, competency framework, etc. Also remove "Additional Job Details (if Applicable)" heading but we already extracted its content. Now produce HTML fragment. Structure:

      About the role

      Job Summary paragraph...

      Responsibilities

      • ...
      ...

      Requirements

      ...

      Skills

      • ...
      ...

      Qualifications

      ...

      Pay

      Pay Range $53851.00 - $82,014.40/Annual Grade 6

      Schedule

      Scheduled Weekly Hours 28; Employee Type Regular; Work Shift Day; Remote Type Hybrid; Work Location 399 Revolution Drive.

      Benefits

      In addition to competitive base pay, we offer comprehensive benefits, career advancement opportunities, differentials, premiums and bonuses as applicable and recognition programs designed to celebrate your contributions and support your professional growth.

      Check for any duplicated content: Ensure we didn't miss any substantive info like "Established in 2005 as a joint initiative of Harvard Medical School (HMS) and the Harvard School of Public Health (HSPH), The Center for Surgery and Public Health (CSPH) has been at the forefront..." That's in Job Summary. We need to include all of that. Now check for any other substantive info: "We are advancing the science of surgical care delivery by studying effectiveness, quality, equity, and value at the population level and training the most gifted of a new generation of physician-scientists." That's part of Job Summary. Also "Together our efforts are making surgery safer, more patient-centered and more accessible in the U.S. and around the world." Include. Now ensure we didn't include any boilerplate like "We believe that high-performing teams drive groundbreaking medical discoveries and invite all applicants to join us and experience what it means to be part of Mass General Brigham." That's part of the introductory paragraph before Job Summary. Should we include that? It's part of the site description but not specific to the job. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The introductory paragraph about Mass General Brigham mission is generic but still part of the posting. It's not boilerplate like EEO; it's about the organization. Might be considered substantive? It's describing the organization. The instruction says to remove boilerplate, but not