Associate Director, Research and Public Health
James Madison University · Harrisonburg, VA · 1 mo ago
HealthcareFull-time
We need to output HTML fragment with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. Preserve all substantive info.
We need to parse the posting.
Key info:
- Opening date: Sep 25 2026 (maybe metadata, could be short p)
- Working Title: Associate Director, Research and Public Health
- State Role Title: N/A (ignore)
- Position Type: Administrative & Professional (Non-teaching Faculty)
- Position Status: Full-Time
- FLSA Status: Exempt: Not Eligible for Overtime
- College/Division: College of Health and Behavioral Studies
- Department: 100498 - Institute for Innovat in HHS
- Pay Band: N/A
- Pay Rate: Commensurate with Experience (should not create Pay section because it's vague "Commensurate with Experience" - rule: never create Pay/Schedule/Benefits sections unless posting actually states them. "Commensurate with Experience" is not a specific amount, it's placeholder. So we should NOT include Pay section.
- Is this a JMU only position? No
- Is this a grant-funded position? Yes. This is a grant-funded position and is contingent upon continued funding.
- Is this a Conflict of Interest designated position? No
- Beginning Review Date: 10/26/2026
- About JMU Mission etc (boilerplate? Might be considered generic but could be kept as "About the role"? Actually "About JMU Mission" is generic about university; but we might include as part of "About the role"? The instruction: include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The "About JMU Mission" is generic but still substantive about the institution. Might be considered appropriate for "About the role"? However they said "About the role" heading for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could put an "About the role" section containing the description of the role from "General Information" etc. The "About JMU Mission" is more about the university; maybe we can incorporate into About the role or drop as boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About JMU Mission" seems like generic boilerplate about the university, but it's not legal/EEO. Might be considered part of the posting but not specific to role. However we could keep it under "About the role" as context. But we need to avoid filler like "commensurate with experience". The mission statement is not filler; it's specific to JMU. Might be okay.
But we need to preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include all substantive info from the posting, except boilerplate like EEO, legal, etc. The "About JMU Mission" is substantive about the university; we should keep it.
We need to decide sections:
- About the role: could include the description from "General Information" paragraph about the Institute, role description, etc. Also maybe the "About JMU Mission" could be part of this or separate? But we only have allowed headings list; we cannot add custom headings. So we must fit content under those headings. Could put university mission under "About the role" as well.
- Responsibilities: from "Duties And Responsibilities" bullet list.
- Requirements: from "Qualifications" (required qualifications). Could also include "Preferred Qualifications" maybe under Requirements or Skills? The headings list includes Requirements, Qualifications, Skills. We need to decide mapping. Usually "Qualifications" could be required qualifications; "Skills" could be skills like Microsoft Excel etc. But we have both "Qualifications" and "Skills" headings allowed. We need to avoid thin sections. Perhaps combine required qualifications and preferred qualifications under "Qualifications". Skills could be separate for technical competencies.
But we must not create a section if content is thin. Let's see what we have:
Required Qualifications:
- Master’s degree in Health Sciences, Public Health, Psychometrics, Nursing, or a related field.
- Experience leading collaborative research projects.
- Strong capacity for research, including data analysis and reporting.
- Strong attention to detail.
- Experienced and organized in project management.
- Demonstrated ability to form positive and productive collaborations.
- Ability to lead and administer grant-funded projects.
- Grant writing experience.
- Experience building and maintaining professional relationships with grant partners and funding agencies.
- A commitment to sustaining and growing research and public health initiatives.
- Ability to mentor faculty and students in the research process, including supporting research, preparing manuscripts, and professional presentations.
- Ability to develop and manage budgets.
- Excellent oral and written communication skills and excellent interpersonal skills.
- A demonstrated ability to work independently and as part of a team, with excellent organizational and time management skills.
- A commitment to cultivating welcoming, supportive workplace environments.
- Competency in Microsoft Excel, Word, Teams, Outlook, survey development tools, and data analysis software.
Preferred Qualifications:
- Doctoral degree in Health Sciences, Public Health, Nursing, Social Work, or a related field is strongly preferred.
Also there is "Additional Posting Information" about IIHHS history etc. That could be under "About the role" maybe.
Also "Conditions Of Employment" includes background check, E-Verify, etc. That's legal/boilerplate? Might be considered boilerplate but it's about employment conditions; maybe we should keep? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Conditions of Employment might be considered legal but it's standard. Might be removed. However we need to preserve ALL substantive information; but they said remove legal boilerplate. So we can drop Conditions Of Employment, EEO Statement, Reasonable Accommodation.
Also "About JMU Mission" etc might be considered boilerplate but it's about the university; not sure. Might keep.
We need to output only HTML fragment, no markdown.
Let's craft:
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. Preserve all substantive info.
We need to parse the posting.
Key info:
- Opening date: Sep 25 2026 (maybe metadata, could be short p)
- Working Title: Associate Director, Research and Public Health
- State Role Title: N/A (ignore)
- Position Type: Administrative & Professional (Non-teaching Faculty)
- Position Status: Full-Time
- FLSA Status: Exempt: Not Eligible for Overtime
- College/Division: College of Health and Behavioral Studies
- Department: 100498 - Institute for Innovat in HHS
- Pay Band: N/A
- Pay Rate: Commensurate with Experience (should not create Pay section because it's vague "Commensurate with Experience" - rule: never create Pay/Schedule/Benefits sections unless posting actually states them. "Commensurate with Experience" is not a specific amount, it's placeholder. So we should NOT include Pay section.
- Is this a JMU only position? No
- Is this a grant-funded position? Yes. This is a grant-funded position and is contingent upon continued funding.
- Is this a Conflict of Interest designated position? No
- Beginning Review Date: 10/26/2026
- About JMU Mission etc (boilerplate? Might be considered generic but could be kept as "About the role"? Actually "About JMU Mission" is generic about university; but we might include as part of "About the role"? The instruction: include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The "About JMU Mission" is generic but still substantive about the institution. Might be considered appropriate for "About the role"? However they said "About the role" heading for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could put an "About the role" section containing the description of the role from "General Information" etc. The "About JMU Mission" is more about the university; maybe we can incorporate into About the role or drop as boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About JMU Mission" seems like generic boilerplate about the university, but it's not legal/EEO. Might be considered part of the posting but not specific to role. However we could keep it under "About the role" as context. But we need to avoid filler like "commensurate with experience". The mission statement is not filler; it's specific to JMU. Might be okay.
But we need to preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include all substantive info from the posting, except boilerplate like EEO, legal, etc. The "About JMU Mission" is substantive about the university; we should keep it.
We need to decide sections:
- About the role: could include the description from "General Information" paragraph about the Institute, role description, etc. Also maybe the "About JMU Mission" could be part of this or separate? But we only have allowed headings list; we cannot add custom headings. So we must fit content under those headings. Could put university mission under "About the role" as well.
- Responsibilities: from "Duties And Responsibilities" bullet list.
- Requirements: from "Qualifications" (required qualifications). Could also include "Preferred Qualifications" maybe under Requirements or Skills? The headings list includes Requirements, Qualifications, Skills. We need to decide mapping. Usually "Qualifications" could be required qualifications; "Skills" could be skills like Microsoft Excel etc. But we have both "Qualifications" and "Skills" headings allowed. We need to avoid thin sections. Perhaps combine required qualifications and preferred qualifications under "Qualifications". Skills could be separate for technical competencies.
But we must not create a section if content is thin. Let's see what we have:
Required Qualifications:
- Master’s degree in Health Sciences, Public Health, Psychometrics, Nursing, or a related field.
- Experience leading collaborative research projects.
- Strong capacity for research, including data analysis and reporting.
- Strong attention to detail.
- Experienced and organized in project management.
- Demonstrated ability to form positive and productive collaborations.
- Ability to lead and administer grant-funded projects.
- Grant writing experience.
- Experience building and maintaining professional relationships with grant partners and funding agencies.
- A commitment to sustaining and growing research and public health initiatives.
- Ability to mentor faculty and students in the research process, including supporting research, preparing manuscripts, and professional presentations.
- Ability to develop and manage budgets.
- Excellent oral and written communication skills and excellent interpersonal skills.
- A demonstrated ability to work independently and as part of a team, with excellent organizational and time management skills.
- A commitment to cultivating welcoming, supportive workplace environments.
- Competency in Microsoft Excel, Word, Teams, Outlook, survey development tools, and data analysis software.
Preferred Qualifications:
- Doctoral degree in Health Sciences, Public Health, Nursing, Social Work, or a related field is strongly preferred.
Also there is "Additional Posting Information" about IIHHS history etc. That could be under "About the role" maybe.
Also "Conditions Of Employment" includes background check, E-Verify, etc. That's legal/boilerplate? Might be considered boilerplate but it's about employment conditions; maybe we should keep? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Conditions of Employment might be considered legal but it's standard. Might be removed. However we need to preserve ALL substantive information; but they said remove legal boilerplate. So we can drop Conditions Of Employment, EEO Statement, Reasonable Accommodation.
Also "About JMU Mission" etc might be considered boilerplate but it's about the university; not sure. Might keep.
We need to output only HTML fragment, no markdown.
Let's craft:
About the role
... content ...
Responsibilities
- ... each duty ...
Qualifications
- ... required qualifications ...
Skills
for technical competencies (Microsoft Excel etc). But those are already in qualifications; we could split: Qualifications for education/experience, Skills for technical competencies. That would avoid thin sections? Let's see. If we put all required qualifications under Qualifications, that's a decent list. Skills could be the competency in Microsoft Excel etc. That's also a list but maybe thin. However we could keep them together under Qualifications to avoid thin Skills section. The instruction: Prefer a few substantive sections over many thin ones. So better to have fewer sections. So we can have About the role, Responsibilities, Qualifications. Possibly also Benefits? No specific benefits mentioned. Pay? Not specific. Schedule? Not specific. So we omit those. We also need to include metadata like opening date, position type, status, etc. Where to put? Could be a shortunder About the role or maybe a separate
before headings? 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 metadata like Opening date, Position type, etc. Not as heading. Thus output:
Opening: Sep 25 2026. Position Type: Administrative & Professional (Non-teaching Faculty). Position Status: Full-Time. FLSA Status: Exempt: Not Eligible for Overtime. College/Division: College of Health and Behavioral Studies. Department: 100498 - Institute for Innovat in HHS. Grant-funded: Yes (contingent upon continued funding). Beginning Review Date: 10/26/2026.
Then