USDA-ARS Postdoctoral Research Opportunity: Development of Novel Vaccines for Poultry Viral Diseases

We need to produce HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Remove boilerplate, navigation, etc. Must preserve all substantive info. We need to parse the posting. Key info: - Organization: USDA, ARS, location Athens, Georgia. - Description: research opportunity, project details, learning objectives, mentor, start date, appointment length, level of participation, stipend (monthly stipend commensurate with educational level and experience), citizenship requirements (U.S. citizens only), ORISE info, health insurance requirement, etc. - Qualifications: currently pursuing or have received a doctoral degree in relevant fields. - Preferred Skills: highly motivated scientist in virology and vaccine development; strong hands-on techniques in DNA/RNA amplification, molecular cloning, transgene gene expression, virus propagation, cell cultures. - There's also "Point of Contact Janeen Eligibility Requirements">51 ) Citizenship: U.S. Citizen Only Degree: Doctoral Degree. Discipline(s): Life Health and Medical Sciences ..." This seems garbled but we can extract: Citizenship: U.S. Citizen Only; Degree: Doctoral Degree; Discipline(s): Life Health and Medical Sciences (list many subfields). We'll include that under Qualifications maybe. - Application details: deadline 11/20/2026 3:00:00 PM Eastern Time Zone. How to apply: scroll to bottom and click APPLY. Required documents: transcript(s), resume/CV, two recommendations. All docs must be English or include official translation. ORISE GO app mention. This is application instructions; we should remove application instructions per rule: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should not include application instructions. So we exclude "How To Apply", "Application Deadline", etc. However we might keep deadline? The rule says remove application instructions. Deadline is part of application instructions; likely remove. Also "Reference Code" maybe minor metadata; we can fold into short p or drop. Probably drop. - We need to include sections only when there is real specific content. So we can have:

About the role

with description of role, location, mission, project.

Responsibilities

maybe list duties: constructing recombinant Marek's disease virus, learning construction, conducting vaccine efficacy studies, sample collection, viral genome detection, data analysis.

Learning Objectives

maybe could be under Responsibilities or separate? Could be "Training and Learning Objectives". But we have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map content accordingly. - Qualifications: doctoral degree, citizenship, discipline list. - Skills: preferred skills list. - Benefits: stipend (monthly stipend commensurate with educational level and experience) and health insurance requirement (proof of health insurance required, can be obtained through ORISE). Also maybe mention no employment-related benefits. But we should not include vague like "commensurate with experience" if it's not specific? The stipend is described as "monthly stipend commensurate with educational level and experience." That's somewhat vague but it's still specific that there is a stipend. The rule says: 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. The posting does state stipend exists, albeit described as commensurate. That's not a specific number but it's still stating there is a stipend. Is that considered filler? The example includes "commensurate with experience" as filler to avoid. So we should not create a Benefits/Pay section if the only info is "commensurate with experience". However we also have health insurance requirement which is specific. So maybe we can include a Benefits section with health insurance requirement, but not stipend if it's vague. But we could also include stipend as part of Benefits but we risk violating rule. Safer: omit Benefits section entirely because the only substantive benefit is health insurance requirement, which is specific. Actually health insurance requirement is specific: "Proof of health insurance is required for participation in this program. Health insurance can be obtained through ORISE." That's substantive. So we can include Benefits section with that. - Pay: we could omit because stipend is vague. - Schedule: level of participation: full time. That's specific. So we can include Schedule section with full time. - Also we might include "Appointment Length": initially one year, may be renewed. That's also schedule/contract length. Could be under Schedule or maybe a separate section but we only have allowed headings. Could put under Schedule as well. - Mentor info: could be under About the role or Responsibilities. - Learning objectives: could be under About the role or Responsibilities. We need to preserve all substantive info; not invent or summarize away detail. So we need to include details like project description, learning objectives bullet points, mentor contact, appointment length, start date flexible, citizenship, disciplinary list, preferred skills. We must not include application instructions, deadline, reference code, ORISE GO app, etc. We must not repeat job title as heading (the page already shows it). No job title given explicitly but we can ignore. We must not put Job ID/requisition numbers as headings. We must output only HTML fragment. Let's craft sections:

About the role

Opportunity with the U.S. Department of Agriculture (USDA), Agricultural Research Service (ARS) in Athens, Georgia. ARS is the USDA's chief scientific in‑house research agency, tasked with finding solutions to agricultural problems, delivering cutting‑edge tools for farmers, sustaining agroecosystems, and ensuring economic competitiveness of U.S. agriculture. The fellow will join a research team developing recombinant Marek's disease virus vaccines to prevent Marek's disease and other poultry diseases. The project involves constructing recombinant vaccines using a molecularly cloned Marek's disease virus as a vector platform, evaluating efficacy against Marek's disease and targeted poultry diseases, constructing the recombinant virus that expresses foreign antigens, learning construction of recombinant avian herpesvirus vaccines, conducting vaccine efficacy studies, collecting samples from animals, performing viral genome detection, and analyzing data.

Maybe also include mentor:

Mentor: Taejoong Kim (taejoong.kim@usda.gov).

Responsibilities

• Construct recombinant Marek's disease virus expressing foreign antigens.
• Learn and apply techniques to recover infectious avian herpesviruses from DNA transfection.
• Quantify virus infectivity and determine viral titers.
• Modify cloned virus genomes using advanced recombineering technologies.
• Evaluate vaccinal efficacy of Marek's disease virus vector vaccines (experimental design, data collection, analysis).
• Conduct vaccine efficacy studies, including sample collection from animals, viral genome detection, and data analysis.

But note responsibilities may overlap with learning objectives. However we need to preserve all substantive info; we can combine. Learning objectives list: Recovery of Infectious Avian Herpesviruses; Quantification of Virus Infectivity and Titer; Modification of Cloned Virus Genome; Evaluation of Vaccinal Efficacy. We could put them under Responsibilities or maybe under a separate section but we don't have a heading for Learning Objectives. Could incorporate into Responsibilities as bullet points. We also have "Through these learning objectives, you will develop a robust skill set in virology, molecular biology, and vaccine development, contributing to advancements in avian disease prevention and control." Could add as a paragraph.

Qualifications

Applicants must be currently pursuing or have received a doctoral degree in a relevant field. Citizenship: U.S. citizens only. Discipline(s): Life Health and Medical Sciences (including Agricultural Sciences, Agronomy, Anatomy, Animal Behavior, Animal Health and Food Safety, Animal Sciences, Basic Biomedical Sciences, Biochemistry, Bioinformatics, Biology (General), Biophysics, Botany, Cellular and Molecular Biology, Comparative Medicine and Laboratory Animal Medicine, Computational Biology, Developmental Biology, Ecology, Ecosystem Ecology, Emergency and Incident Management, Entomology, Environmental Health, Epidemiology, Evolutionary Biology, Food Sciences and Technology, Genetics, Health Physics, Horticulture, Immunology, Industrial Hygiene, Infectious Diseases and Zoonoses, Kinesiology and Exercise Physiology, Medicine, Microbiology, Neurosciences, Nursing, Nutritional Sciences, Occupational Health, Pharmacology, Pharmacy, Physiology, Plant Sciences, Population and Community Ecology, Population Medicine, Public Health, Structural Biology, Toxicology, Veterinary Sciences, Virology, Wildlife Sciences, Zoology (General)).

That is a huge list; we need to preserve all. Might be long but okay.

Skills

• Highly motivated scientist in virology and vaccine development.
• Strong hands‑on techniques in DNA/RNA amplification, molecular cloning, transgene gene expression, virus propagation, and cell cultures.

Schedule

Appointment is full‑time. Initial appointment length is one year, with possibility of renewal upon recommendation of ARS and contingent on funding availability. Start date is flexible and will be arranged as soon as possible.

Benefits

Proof of health insurance is required for participation; health insurance can be obtained through ORISE. (Note: a monthly stipend is provided, commensurate with educational level and experience.)

We included stipend note in parentheses; but that might be considered filler? It's still mention of stipend but we already said we shouldn't create Benefits section unless posting actually states them. It does state stipend exists, albeit vague. The rule says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state stipend (monthly stipend commensurate with educational level and experience). So we can include Benefits section with stipend mention. However the example of filler includes "commensurate with experience". That is exactly the phrase used. The rule says: 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. So if we include Benefits section, we must avoid filler text. The stipend description is "commensurate with educational level and experience." That's similar to "commensurate with experience". That might be considered filler. To be safe, we could omit stipend mention entirely and just mention health insurance requirement. But then we lose info about stipend. However the rule says we must preserve ALL substantive information. The stipend is substantive, even if vague. But the rule also says not to create a Benefits section if the only content is filler. However we have health insurance requirement which is substantive. So we can have Benefits section with health insurance requirement, and we could also include stipend but maybe phrase it differently to avoid the exact filler phrase? The phrase is exactly from posting; we cannot change it because we must preserve info, not invent or summarize away detail. We could include it as is, but then the section would contain filler text. The rule says "never emit a heading followed by filler/placeholder text (e.g., 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". It doesn't say we cannot have filler text inside a section if there is also other substantive content? It says "never emit a heading followed by filler/placeholder text". That implies if the section's immediate content after heading is filler only, it's not allowed. If we have other substantive content (like health insurance requirement) then the heading is not followed solely by filler. So we can include both. Thus Benefits