Deputy Office Head - Information Advantage Office (Faculty)
The Applied Research Laboratory at Penn State University · University Park, PA · 3 wk ago
On-siteSalesFull-time
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 that have real specific content.
We need to parse the posting.
First, remove boilerplate: application instructions, remote work notice, etc. Also remove EEO, background checks, etc. Keep substantive info: position specifics, description, duties, requirements, benefits.
Let's extract:
Position specifics: "Your working location can be a hybrid of on-site/work from home, on-site location is State College, PA. We are searching for a Deputy Office Head for the Information Advantage Office (IAO) at the Penn State Applied Research Laboratory (ARL). IAO conducts mission-driven research to disrupt adversary capabilities, enable rapid operational adaptation, and secure a decisive information advantage in contested environments. Its work advances C5ISRT and counter-C5ISRT by bridging intelligence, decision-making, and execution to outpace emerging threats. The Office delivers applied RDT&E that transforms information into operational advantage, reshaping the landscape of information superiority. IAO consists of four division: Command, Control, and Communication Innovations (C3I); Joint Mission Integration and Experimentation (JMIE); Cyber, Modeling and Simulation (CMS); and Strategic Systems Operations (SSO). The Deputy Office Head will report directly to the Office Head of the Information Advantage Office. This position will be filled as either Research and Development Engineer, non-tenure Research Faculty, or Technical Engineering Project Manager. ARL is an authorized DoD SkillBridge partner and welcomes all transitioning military members to apply."
Then list of duties: "You will:" followed by bullet-like sentences.
Let's extract each duty:
- Work closely with the Office leadership team to build and maintain trusted relationships with key sponsors and stakeholders
- Work closely with the IAO Office Head and Senior Scientist to ensure the delivery of superior research deliverables to our sponsors
- Support the IAO Office Head in developing and executing strategic initiatives
- Represent the Office in meetings and discussions with sponsors and guests
- Lead, manage, and continuously improve the operations of the Office
- Plan and manage office finances in collaboration with the IAO Program Finance Administrator
- Plan and manage workspace and research facilities and equipment
- Oversee the Office's external web presence, overview briefing, and a library of supporting capability briefings
- Support the Office Head in daily interactions with colleagues in Enterprise Operations - Engineering Services, Business Services, Security Services, Human Resources, Information Technology Services, and Special Programs Security
- Lead, manage, and continuously improve professional development, training, and onboarding
Then: "Non-tenure faculty rank will be commensurate with education level and experience." This is filler? It's generic, but maybe we can include as part of Qualifications? It says "commensurate with education level and experience." That's vague; maybe we should not include as a separate section because it's filler. The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So we should not create a section just for that line. We can incorporate into Qualifications maybe? But it's basically saying rank will be commensurate; not specific. Better to omit.
Then: "Minimally requires a Master's degree in an engineering or science discipline and 10 years' related experience."
Then: "Required skills/experience areas include:" followed by bullet list:
- All aspects of leading individual and portfolios of research projects including developing technical concepts, writing winning proposals, staffing the project, conducting the research, managing budgets, and delivering high quality results
- All aspects of leading a research organization, including planning and managing labor across projects, managing research budgets, presenting department capabilities to sponsors, and hiring, coaching, and mentoring employees
- Superior writing and presentation skills
- Demonstrated success leading a team of engineers/scientists, and collaborating with large teams on multi-organization, multi-disciplinary projects
- Experience and exposure in one or more ares of C5ISRT (typo: ares -> areas)
- Active SECRET government security clearance, TS or above is desired
Then description of ARL purpose: maybe not needed.
Then Benefits section: "Benefits Penn State provides a competitive benefits package for full-time employees designed to support both personal and professional wellbeing. In addition to comprehensive medical, dental, and vision coverage, employees enjoy robust retirement plans. One of the standout benefits is the generous 75% tuition discount, available to employees as well as eligible spouses and children. For more detailed information, please visit our Benefits Page."
Thus we have Benefits content.
Pay: not mentioned. Schedule: not mentioned (though hybrid location mentioned, but schedule not explicit). So we should not create Pay or Schedule sections.
We need sections: About the role (maybe position specifics), Responsibilities (the "You will:" list), Requirements (education/experience), Qualifications (maybe skills/experience areas), Skills (maybe overlapping), Benefits.
We need to avoid duplication. Let's decide:
- About the role: description of IAO, position, reporting, location, etc.
- Responsibilities: the list of duties.
- Requirements: Minimally requires a Master's degree ... and 10 years' related experience.
- Qualifications: maybe the required skills/experience areas list (including leading projects, leading organization, writing, team leadership, C5ISRT experience, security clearance). Could be under Skills or Qualifications. The instruction: use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have both Qualifications and Skills if content distinct. But we can combine if needed. Let's separate: Qualifications: education/experience (maybe same as Requirements). Actually Requirements often includes education/experience. Qualifications could be skills/experience areas. Skills could be specific competencies like superior writing and presentation skills, etc. But we have overlapping.
Better to follow typical: Requirements: education and experience. Qualifications: required skills/experience areas. Skills: maybe not needed if covered. But we can still include Skills if we have distinct items like "Superior writing and presentation skills" etc. However those are already in required skills/experience areas. To avoid duplication, we could put all under Qualifications and omit Skills. Or we could put under Skills the list of specific skills (writing, presentation, leading teams, etc.) and under Qualifications the education/experience. Let's see.
The posting: "Required skills/experience areas include:" then list includes leading projects, leading organization, superior writing and presentation skills, demonstrated success leading team, experience in C5ISRT, active SECRET clearance. So that's a mix of skills and experience. Could treat as Qualifications.
Thus we can have:
- About the role (position specifics)
- Responsibilities (You will list)
- Requirements (Master's degree + 10 years experience)
- Qualifications (Required skills/experience areas list)
- Benefits (benefits description)
We should not include Pay or Schedule.
Now we need to output HTML fragment: use
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the posting.
First, remove boilerplate: application instructions, remote work notice, etc. Also remove EEO, background checks, etc. Keep substantive info: position specifics, description, duties, requirements, benefits.
Let's extract:
Position specifics: "Your working location can be a hybrid of on-site/work from home, on-site location is State College, PA. We are searching for a Deputy Office Head for the Information Advantage Office (IAO) at the Penn State Applied Research Laboratory (ARL). IAO conducts mission-driven research to disrupt adversary capabilities, enable rapid operational adaptation, and secure a decisive information advantage in contested environments. Its work advances C5ISRT and counter-C5ISRT by bridging intelligence, decision-making, and execution to outpace emerging threats. The Office delivers applied RDT&E that transforms information into operational advantage, reshaping the landscape of information superiority. IAO consists of four division: Command, Control, and Communication Innovations (C3I); Joint Mission Integration and Experimentation (JMIE); Cyber, Modeling and Simulation (CMS); and Strategic Systems Operations (SSO). The Deputy Office Head will report directly to the Office Head of the Information Advantage Office. This position will be filled as either Research and Development Engineer, non-tenure Research Faculty, or Technical Engineering Project Manager. ARL is an authorized DoD SkillBridge partner and welcomes all transitioning military members to apply."
Then list of duties: "You will:" followed by bullet-like sentences.
Let's extract each duty:
- Work closely with the Office leadership team to build and maintain trusted relationships with key sponsors and stakeholders
- Work closely with the IAO Office Head and Senior Scientist to ensure the delivery of superior research deliverables to our sponsors
- Support the IAO Office Head in developing and executing strategic initiatives
- Represent the Office in meetings and discussions with sponsors and guests
- Lead, manage, and continuously improve the operations of the Office
- Plan and manage office finances in collaboration with the IAO Program Finance Administrator
- Plan and manage workspace and research facilities and equipment
- Oversee the Office's external web presence, overview briefing, and a library of supporting capability briefings
- Support the Office Head in daily interactions with colleagues in Enterprise Operations - Engineering Services, Business Services, Security Services, Human Resources, Information Technology Services, and Special Programs Security
- Lead, manage, and continuously improve professional development, training, and onboarding
Then: "Non-tenure faculty rank will be commensurate with education level and experience." This is filler? It's generic, but maybe we can include as part of Qualifications? It says "commensurate with education level and experience." That's vague; maybe we should not include as a separate section because it's filler. The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So we should not create a section just for that line. We can incorporate into Qualifications maybe? But it's basically saying rank will be commensurate; not specific. Better to omit.
Then: "Minimally requires a Master's degree in an engineering or science discipline and 10 years' related experience."
Then: "Required skills/experience areas include:" followed by bullet list:
- All aspects of leading individual and portfolios of research projects including developing technical concepts, writing winning proposals, staffing the project, conducting the research, managing budgets, and delivering high quality results
- All aspects of leading a research organization, including planning and managing labor across projects, managing research budgets, presenting department capabilities to sponsors, and hiring, coaching, and mentoring employees
- Superior writing and presentation skills
- Demonstrated success leading a team of engineers/scientists, and collaborating with large teams on multi-organization, multi-disciplinary projects
- Experience and exposure in one or more ares of C5ISRT (typo: ares -> areas)
- Active SECRET government security clearance, TS or above is desired
Then description of ARL purpose: maybe not needed.
Then Benefits section: "Benefits Penn State provides a competitive benefits package for full-time employees designed to support both personal and professional wellbeing. In addition to comprehensive medical, dental, and vision coverage, employees enjoy robust retirement plans. One of the standout benefits is the generous 75% tuition discount, available to employees as well as eligible spouses and children. For more detailed information, please visit our Benefits Page."
Thus we have Benefits content.
Pay: not mentioned. Schedule: not mentioned (though hybrid location mentioned, but schedule not explicit). So we should not create Pay or Schedule sections.
We need sections: About the role (maybe position specifics), Responsibilities (the "You will:" list), Requirements (education/experience), Qualifications (maybe skills/experience areas), Skills (maybe overlapping), Benefits.
We need to avoid duplication. Let's decide:
- About the role: description of IAO, position, reporting, location, etc.
- Responsibilities: the list of duties.
- Requirements: Minimally requires a Master's degree ... and 10 years' related experience.
- Qualifications: maybe the required skills/experience areas list (including leading projects, leading organization, writing, team leadership, C5ISRT experience, security clearance). Could be under Skills or Qualifications. The instruction: use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have both Qualifications and Skills if content distinct. But we can combine if needed. Let's separate: Qualifications: education/experience (maybe same as Requirements). Actually Requirements often includes education/experience. Qualifications could be skills/experience areas. Skills could be specific competencies like superior writing and presentation skills, etc. But we have overlapping.
Better to follow typical: Requirements: education and experience. Qualifications: required skills/experience areas. Skills: maybe not needed if covered. But we can still include Skills if we have distinct items like "Superior writing and presentation skills" etc. However those are already in required skills/experience areas. To avoid duplication, we could put all under Qualifications and omit Skills. Or we could put under Skills the list of specific skills (writing, presentation, leading teams, etc.) and under Qualifications the education/experience. Let's see.
The posting: "Required skills/experience areas include:" then list includes leading projects, leading organization, superior writing and presentation skills, demonstrated success leading team, experience in C5ISRT, active SECRET clearance. So that's a mix of skills and experience. Could treat as Qualifications.
Thus we can have:
- About the role (position specifics)
- Responsibilities (You will list)
- Requirements (Master's degree + 10 years experience)
- Qualifications (Required skills/experience areas list)
- Benefits (benefits description)
We should not include Pay or Schedule.
Now we need to output HTML fragment: use for each section heading, then content:
for prose,
- for lists. We must preserve all substantive information, not invent or summarize away detail. So we need to keep the exact wording? We should preserve substance but can rephrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep the information, not omit details. We can keep the sentences as is, maybe split into paragraphs. We need to avoid boilerplate: remove application instructions, remote work notice, EEO, background checks, etc. Also remove "Notice regarding employment at the Applied Research Laboratory (ARL): Employees must be eligible to obtain a government security clearance, participate in the ARL drug testing program, and comply with electronic and physical monitoring requirements applicable to federal contractors." That's substantive? It's about clearance and drug testing; but we already have security clearance requirement. However it's more about employment requirements. Might be considered boilerplate? It's specific to ARL. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly EEO but it's about employment requirements. Might be considered legal? It's about security clearance, drug testing, monitoring. Could be considered part of job requirements. However we already have security clearance requirement. The drug testing and monitoring might be extra. But to be safe, maybe we keep it as part of Requirements or Qualifications? The instruction says remove legal boilerplate. This seems like legal/employment conditions. Might be considered boilerplate. I'd lean to remove it to stay safe. Also remove "Background Checks/Clearances" section. Also remove "FOR FURTHER INFORMATION on ARL, visit our website at www.arl.psu.edu." That's maybe not substantive? Could be considered extra info but maybe we keep as part of About the role? It's a reference. Might be okay to keep but it's not essential. The instruction says preserve ALL substantive information; does that include a link to website? It's substantive? Possibly yes, but it's just a reference. I'd keep it maybe as a note in About the role. But we need to avoid duplication. There's also "ARL’s purpose is to research and develop innovative solutions to challenging scientific, engineering, and technology problems in support of the Navy, the Intel Community (IC), and other federal government customers." That's substantive about ARL purpose; we could include in About the role. Now let's craft sections. About the role: combine location, position, IAO description, divisions, reporting, position type, DoD SkillBridge, ARL purpose, maybe website. We need to ensure we don't include filler like "Non-tenure faculty rank will be commensurate with education level and experience." We'll omit. Now Responsibilities: list each duty as
- .
Requirements: "Minimally requires a Master's degree in an engineering or science discipline and 10 years' related experience." That's a sentence.
Qualifications: list of required skills/experience areas.
We need to keep the exact phrasing? Let's copy each bullet.
Bullet list:
- All aspects of leading individual and portfolios of research projects including developing technical concepts, writing winning proposals, staffing the project, conducting the research, managing budgets, and delivering high quality results
- All aspects of leading a research organization, including planning and managing labor across projects, managing research budgets, presenting department capabilities to sponsors, and hiring, coaching, and mentoring employees
- Superior writing and presentation skills
- Demonstrated success leading a team of engineers/scientists, and collaborating with large teams on multi-organization, multi-disciplinary projects
- Experience and exposure in one or more ares of C5ISRT (typo: ares). We should preserve as is? Probably keep the typo as it's in the source. But we could correct? The instruction says preserve ALL substantive information; does correcting a typo count as altering? It's still substantive but we might keep original. Safer to keep original text: "Experience and exposure in one or more ares of C5ISRT".
- Active SECRET government security clearance, TS or above is desired
Now Benefits: "Benefits Penn State provides a competitive benefits package for full-time employees designed to support both personal and professional wellbeing. In addition to comprehensive medical, dental, and vision coverage, employees enjoy robust retirement plans. One of the standout benefits is the generous 75% tuition discount, available to employees as well as eligible spouses and children. For more detailed information, please visit our Benefits Page."
We should keep as prose.
Now output HTML.
Structure:
About the role
...
Responsibilities
- ... ...
Requirements
...
Qualifications
- ... ...
Benefits
...
Make sure no extra whitespace? It's fine. Now craft About the role paragraph. We need to include: working location hybrid,