Research Fellow - Wake Forest Institute for Regenerative Medicine (WFIRM)

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 posting. Job title: WFIRM Postdoctoral Research Fellow (but we do not repeat as heading). We need to include metadata like Department, Status, Benefits Eligible, Hours Per Week, Schedule Details/Additional Information, Pay Range, etc. Some of these may go into a short

or drop. We must remove boilerplate: cookie/navigation/legal/EEO etc. There's none explicit. There's a lot about Advocate Health benefits etc. That's benefits content. We need to preserve all substantive information. Let's extract sections: - Job Summary: description of role. - Specific duties: list of duties. - Education/Experience: requirement. - Skills & Qualifications: list. - WORK ENVIRONMENT: description of institute. - Our Commitment To You: benefits description (compensation, benefits, etc.) - About Advocate Health: description of employer. We need to map to headings: About the role (maybe job summary), Responsibilities (duties), Requirements (education/experience), Qualifications (maybe skills), Skills (maybe separate), Benefits (benefits description), Pay (pay range), Schedule (schedule details). Also maybe "Work Environment" could be part of About the role or separate but not in list; we could include as About the role or maybe as a separate section like "Work Environment". But instructions say use headings for those specific ones; we can also include other headings if needed? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. Probably we should stick to those headings only if content exists. Thus we need to decide which sections have content. - About the role: we have Job Summary and maybe Work Environment. Could combine. - Responsibilities: Specific duties list. - Requirements: Education/Experience. - Qualifications: maybe Skills & Qualifications? But we also have Skills section. Could treat Qualifications as education/experience, Skills as skills list. - Benefits: Benefits description (Our Commitment To You includes benefits). Also Benefits Eligible Yes. - Pay: Pay Range $30.70 - $46.05. - Schedule: Hours Per Week 40, Schedule Details/Additional Information Varies. Since schedule details says Varies, which is placeholder; we should not create Schedule section if content is only "Varies" (placeholder). The rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So we should not include Schedule section because the only schedule info is "Varies". However we have Hours Per Week 40 which is specific. Could we include that under a Schedule section? The schedule details says Varies, but hours per week is 40. Might be considered schedule info. But the rule says do not create Schedule section unless posting actually states them. It does state Hours Per Week 40 and Schedule Details/Additional Information Varies. The Varies is placeholder; but we have actual hours. Could we still include Schedule section with the hours? Might be okay. But we need to avoid filler. We could include a

with Hours Per Week 40. But the heading would be Schedule. If we include Schedule heading, we must have substantive content beyond placeholder. We have Hours Per Week 40 (specific). So we can include that. Thus we will include Schedule section with

Hours Per Week: 40.

maybe also mention that schedule details vary? But we should avoid placeholder. Could just state the hours. Now Benefits: we have Benefits Eligible Yes, and a long description of benefits under "Our Commitment To You". That's substantive. Pay: we have Pay Range $30.70 - $46.05. Now About the role: we have Job Summary and Work Environment description. Could combine. Responsibilities: list of duties. Requirements: Education/Experience. Qualifications: maybe Skills & Qualifications? But we also have Skills section. Could treat Qualifications as the bullet list of skills & qualifications? Actually the posting has "Skills & Qualifications" heading with a list. Then after that there is "WORK ENVIRONMENT". So we could map: - Qualifications: the list under Skills & Qualifications (maybe includes experience, background, computer skills, attention to detail, etc.) - Skills: maybe we could split further but we already have that list; we could treat Skills as same as Qualifications? But we need to avoid duplication. Perhaps we treat Qualifications as education/experience, and Skills as the skills list. However the posting lumps them together. Let's decide: Requirements: Education/Experience (Ph.D. with focus...). Qualifications: maybe the bullet list of experience in cell culture etc. (the first set). Then Skills: maybe the later bullet list of computer skills, attention to detail, etc. But the posting has "Skills & Qualifications" heading then a paragraph with multiple sentences each describing experience/skills. It's not clearly split. Given the instruction to prefer few substantive sections over many thin ones, we could combine Qualifications and Skills into one section called Qualifications (or Skills). But we need to follow the heading list; we can include both if we have content for each. However we risk thin sections. Better: Use Qualifications for the bullet list of experience/skills, and Skills for the computer skills, attention to detail, etc. But the posting does not separate them clearly; it's all under Skills & Qualifications. We could split arbitrarily but risk losing nuance. Given the instruction to preserve all substantive information, we can keep them together under one heading, say Qualifications (or Skills). Since we need to output only HTML fragment, we can choose to include either Qualifications or Skills, not both, to avoid thin sections. Which one is more appropriate? The posting includes "Skills & Qualifications". So we could use heading "Qualifications" and put the content there. Or we could use "Skills". The examples include both; we can choose one. I'll choose "Qualifications" for the combined list. Now Benefits: we have Benefits Eligible Yes and the benefits description. We'll include Benefits section with that content. Pay: Pay Range. Schedule: Hours Per Week 40. Now About the role: Job Summary + Work Environment. Let's extract exact text. Job Summary: "The WFIRM Postdoctoral Research Fellow will participate in a research project to develop a new platform to enable the testing of vaccines. The applicant will perform a variety of complex tasks including antigen uptake and presentation, immune cell activation and differentiation, in vitrobiological and functional tests for verification of tissue construct viability and functional assays. Research will be performed in a team environment and the application will be provided with a variety of procedures and techniques previously outlined by established protocols and other scientific data related to the production of tissue engineered constructs." Note: there's a typo "in vitrobiological". We'll keep as is. Work Environment: "The Wake Forest Institute for Regenerative Medicine (WFIRM) is a world leader in the development of technologies and products in the fields of tissue engineering and regenerative medicine. WFIRM is an interdisciplinary institute, with a semi-open laboratory concept aimed towards fostering collaboration in a variety of research areas. WFIRM occupies several floors in the Richard H. Dean Biomedical Building in the Wake Forest Innovation Quarter in Winston-Salem." Our Commitment To You: includes compensation and benefits description. Let's extract: "Advocate Health offers a comprehensive suite of Total Rewards: benefits and well-being programs, competitive compensation, generous retirement offerings, programs that invest in your career development and so much more - so you can live fully at and away from work, including: Compensation Base compensation listed within the listed pay range based on factors such as qualifications, skills, relevant experience, and/or trainingPremium pay such as shift, on call, and more based on a teammate's jobIncentive pay for select positionsOpportunity for annual increases based on performance Benefits And More Paid Time Off programsHealth and welfare benefits such as medical, dental, vision, life, and Short- and Long-Term DisabilityFlexible Spending Accounts for eligible health care and dependent care expensesFamily benefits such as adoption assistance and paid parental leaveDefined contribution retirement plans with employer match and other financial wellness programsEducational Assistance Program Note: Eligibility for programs listed above may depend on your FTE or status (e.g., full-time, part-time, per diem, temporary, etc.); please ask a Recruiter for more information during an interview." We need to keep that as prose. About Advocate Health: description. "Advocate Health is the third-largest nonprofit, integrated health system in the United States, created from the combination of Advocate Aurora Health and Atrium Health. Providing care under the names Advocate Health Care in Illinois; Atrium Health in the Carolinas, Georgia and Alabama; and Aurora Health Care in Wisconsin, Advocate Health is a national leader in clinical innovation, health outcomes, consumer experience and value-based care. Headquartered in Charlotte, North Carolina, Advocate Health services nearly 6 million patients and is engaged in hundreds of clinical trials and research studies, with Wake Forest University School of Medicine serving as the academic core of the enterprise. It is nationally recognized for its expertise in cardiology, neurosciences, oncology, pediatrics and rehabilitation, as well as organ transplants, burn treatments and specialized musculoskeletal programs. Advocate Health employs 155,000 teammates across 69 hospitals and over 1,000 care locations, and offers one of the nation's largest graduate medical education programs with over 2,000 residents and fellows across more than 200 programs. Committed to providing equitable care for all, Advocate Health provides more than $6 billion in annual community benefits." We could include this as maybe "About the Employer" but not in list. Could drop? The instruction says preserve ALL substantive information; we should not drop it. But we don't have a heading for it; we could include it under About the role or maybe as a separate section like "About Advocate Health". Since the instruction only gave examples, we can add other headings if needed. It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings. So we can add a heading "About Advocate Health". That seems appropriate. Now we need to format lists: Use

• for any list of duties/requirements/benefits. We have duties list: antigen uptake and presentation, immune cell activation and differentiation, in vitrobiological and functional tests for verification of tissue construct viability and functional assays. Also "basic and advanced immunological protocols including antigen presentation, T and B cell activation, cell culture and expansion, assembly of 3D constructs using biofabrication techniques, collection and organization of data, and assisting in the preparation of reports and manuscripts." We need to combine into a list. Let's extract all duties: From Job Summary: "antigen uptake and presentation, immune cell activation and differentiation, in vitrobiological and functional tests for verification of tissue construct viability and functional assays." From Specific duties: "basic and advanced immunological protocols including antigen presentation, T and B cell activation, cell culture and expansion, assembly of 3D constructs using biofabrication techniques, collection and organization of data, and assisting in the preparation of reports and manuscripts." We could combine into a single list, but avoid duplication (antigen presentation appears twice). We'll keep as separate items but could deduplicate. The instruction: preserve ALL substantive information; do not invent or summarize away detail. Deduplication might be considered summarizing? It's okay to combine similar items but we risk losing nuance. Safer to keep each distinct statement as separate list items, even if some overlap. Thus list items: - Antigen uptake