EPA Quantifying the Impact of Chemical Exposure on the Thyroid System of Developing Amphibians

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 where there is real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. We need to parse the posting. Key info: - Organization: U.S. Environmental Protection Agency (EPA) - Reference Code: EPA-OSCPP-2026-0010 (but we should drop minor metadata) - How To Apply: instructions (should be removed as application instructions) - Application Deadline: 11/20/2026 3:00:00 PM Eastern Time Zone (maybe we could include in a short paragraph? The instruction says: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we could include deadline in a paragraph maybe under a generic "About the role"? But we need to decide sections. - Description: includes mission, research project details, training activities, learning objectives, mentor, anticipated start date, appointment length, level of participation, participant stipend (commensurate with educational level and experience), citizenship requirements, security clearance, ORISE info, health insurance, etc. - Qualifications: master's or bachelor's degree in relevant fields, within past 5 years, etc. - Preferred Skills: list. - Point of Contact: Rachel (maybe incomplete). There's also eligibility requirements snippet. We need to produce sections: maybe "About the role" (description of role/research), "Responsibilities" (training activities), "Requirements" (citizenship, security clearance, health insurance?), "Qualifications" (education), "Skills" (preferred skills), maybe "Benefits" (stipend, health insurance, ORISE membership, etc.), "Pay" (stipend commensurate...), "Schedule" (full time, appointment length). However we must only include sections if there is real specific content. Avoid filler like "commensurate with experience" is considered filler? The instruction says: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") . So we cannot have a Pay section with just "commensurate with educational level and experience". That's placeholder. So we should not create a Pay section unless there is actual number. Since it's just commensurate, we should not include Pay section. Similarly Benefits: we have stipend, health insurance, ORISE membership, etc. Those are substantive? The stipend is placeholder though. But health insurance requirement and ORISE membership are specific. However the instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state stipend (though placeholder) and health insurance requirement, ORISE membership. Are those considered "benefits"? Possibly yes. But the stipend being placeholder may be considered filler; but we could still include Benefits section with details about health insurance, ORISE membership, etc., but we must not include placeholder text like "commensurate with educational level and experience". We could omit that sentence or rephrase? We must preserve ALL substantive information; do NOT invent or summarize away detail. So we cannot omit the stipend info entirely because it's substantive (though placeholder). But we cannot include it as filler? The instruction says: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") . So if we include a Benefits section, we must not have filler text. The stipend sentence is placeholder; we could maybe not include that sentence? But that would be omitting substantive info (the stipend exists, albeit unspecified). The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The stipend is substantive (they say they will receive a monthly stipend commensurate with educational level and experience). That's info, albeit not a number. Is that considered filler? The examples of filler include "commensurate with experience". That's exactly what we have. So they consider that filler. So we should not include that sentence? But then we would be omitting the stipend info. However they say "never emit a heading followed by filler/placeholder text". If we include a Benefits section, we must avoid filler. Perhaps we can include Benefits section but only list the concrete benefits: health insurance requirement, ORISE membership, maybe the fact that stipend is provided (without describing amount). But we need to avoid the phrase "commensurate with educational level and experience". We could say "The participant will receive a monthly stipend." That's still vague but not the filler phrase. However that is summarizing away detail? The original detail includes "commensurate with educational level and experience". If we drop that phrase, we are summarizing away detail (the condition). That might be considered summarizing away detail, which is not allowed. But the instruction says do NOT invent or summarize away detail. So we must keep that detail exactly. However that detail is considered filler per examples. There's a conflict. Likely the intention: we should not create a Pay section if the only info is "commensurate with experience". So we should omit Pay section entirely. For Benefits, we could include other benefits like health insurance, ORISE membership, etc., but we must not include the stipend phrase if it's considered filler. However we could still mention that a stipend is provided, but we must keep the exact phrase? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep the exact phrase. But then we would have filler in Benefits section. However maybe they consider that acceptable if it's not under a Pay heading? The filler examples are for headings like Pay, Schedule, Benefits. They said never create Pay/Schedule/Benefits sections unless the posting actually states them. And also never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So if we create a Benefits section, we must not have filler text. The stipend phrase is filler, so we cannot include it. Therefore we must either not include Benefits section, or we must find a way to include benefits without filler. Could we include benefits like health insurance, ORISE membership, but not mention stipend? That would be omitting the stipend detail, which is substantive. But maybe they consider stipend as part of Pay, not Benefits. Since we are not making a Pay section, we could drop stipend entirely? But that would be losing info. However maybe they consider stipend as Pay info, and since it's filler, we should omit Pay section and not mention stipend at all. The instruction says preserve ALL substantive information; but maybe they consider that stipend info is not substantive because it's just placeholder. The examples of filler include "commensurate with experience". So they treat that as not substantive enough to warrant a section. So we can drop it. Thus we will not include Pay or Benefits sections. We'll include sections: About the role (description of research project, mission, location), Responsibilities (training activities list), Requirements (citizenship, security clearance, health insurance requirement?), Qualifications (education), Skills (preferred skills). Possibly also Schedule (appointment length, full time, start date). Schedule specifics: Anticipated Appointment Start Date: September 2026 (flexible). Appointment Length: initially one year, may be renewed three to four additional years. Level of Participation: full time. That's specific info, not filler. So we can include a Schedule section. We must not include Job ID etc. We'll fold minor metadata like reference code into a short paragraph maybe under About the role? Or we could drop it. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include a short paragraph with the reference code maybe. We must remove boilerplate: navigation, legal, EEO, scam-warning, duplicated lines, application instructions (How To Apply, ORISE GO app, etc.), FAQ, point of contact maybe? Point of contact is Rachel (maybe not needed). We'll keep mentor info maybe under About the role or Responsibilities? Mentor is substantive. We'll include mentor under About the role or maybe a separate "Mentor" but not a standard heading. We'll keep it in About the role paragraph. We must preserve all substantive information: description of mission, research project details, training activities list, learning objectives list, mentor, start date, appointment length, participation level, citizenship requirements, security clearance, ORISE info, health insurance requirement, ORISE membership, etc. Some of those may be considered benefits but we are not making Benefits section; we could include them under Requirements or About the role. For clarity, we could put citizenship, security clearance, health insurance under Requirements. ORISE membership maybe under Benefits but we don't have Benefits; we could put under About the role as additional info. We need to use

for section headings. Use

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

  for prose. We must output only HTML fragment. Let's craft:

  About the role

  Research opportunity at the U.S. Environmental Protection Agency (EPA), Office of Chemical Safety and Pollution Prevention (OCSPP), Great Lakes Coastal Environmental Science Laboratory in Duluth, Minnesota. The mission of EPA is to protect human health and the environment...

  (include mission paragraph). Also include research project description, translational process, assay development, etc. Also mention mentor Sigmund Degitz (Degitz.Sigmund@epa.gov). Also mention reference code maybe. We need to ensure we preserve all substantive info from description. That's lengthy. We'll need to include the description paragraphs about mission, research project, translational process, assay development, etc. We'll keep them as prose (

  ). Might be multiple paragraphs. Then Responsibilities: list of training activities (the bullet list starting with "With guidance from the mentor, you may be involved in any or all of the following training activities:" followed by a list). We'll put that as

  • each item. Then Requirements: citizenship requirements (U.S. citizens and Lawful Permanent Residents only), EPA Security Clearance (background investigation), Proof of health insurance required (can be obtained through ORISE). Also maybe mention that participants are not employees, no employment-related benefits. That's more like disclaimer but maybe still requirement. We'll include. Then Qualifications: master's or bachelor's degree in relevant fields, within past 5 years, bachelor's considered with strong lab experience. Then Skills: preferred skills list (experience conducting bioassays, aquatic organisms, molecular biology techniques, prior research experience, writing peer-reviewed articles, science communication, computational skills, omics/HTS data experience). Then Schedule: Anticipated Appointment Start Date: September 2026 (flexible). Appointment Length: initially one year, may be renewed three to four additional years upon EPA recommendation and subject to funding. Level of Participation: full time. We must not include Pay or Benefits sections. We must not include application instructions, ORISE GO app, deadline? The deadline is substantive; maybe we could include it under About the role or a separate section like "Important Dates". But we don't have a heading for that. Could we include it under About the role as a short sentence? The instruction says we can fold minor metadata into a short

    or drop it. The deadline is not minor? It's important. But we don't have a heading for dates. Could we create a section "Important Dates"? Not in allowed headings list. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could put deadline under Schedule? Not exactly schedule but could be considered part of