Director, Emergency Management & Business Continuity
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections where posting has real specific content. The posting includes: Job Summary (we can treat as About the role). Responsibilities (detailed). Required Education, Experience, Skills And Certifications (these could be Requirements, Qualifications, Skills). Preferred Qualifications (maybe Qualifications). Supplemental Information includes Institutional Impact, Authority and Decision-Making, Key Relationships, Direct Reports, Important Note about E-Verify, compensation statement, benefits, etc. Benefits are described: "extremely comprehensive benefits program... medical, dental, life insurance, long term disability insurance, tuition remission, generous 403(b) employer contribution, employee assistance program, liberal paid time off policies, performing arts, libraries, bookstores, dining facilities, campus recreation and sporting events". So we can have Benefits section. Pay: they say "competitive compensation program which is commensurate with your qualifications, experience, and contingent upon the departmental budget." That's vague; we should not create Pay section if it's just "commensurate with experience" etc. The rule: 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. For Pay, they say competitive compensation program commensurate with qualifications, experience, contingent upon budget. That's essentially "commensurate with experience" which is placeholder; we should not create Pay section. Schedule: not mentioned; no schedule info. So we omit Pay and Schedule.
Benefits: they give specific benefits list, so we can include Benefits section.
We need to preserve all substantive information, not invent or summarize away detail. Must not repeat job title as heading. Must not put Job ID etc.
We need to use for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We need to decide sections: About the role (Job Summary), Responsibilities, Requirements (maybe combine Education, Experience, Skills And Certifications?), Qualifications (Preferred Qualifications), Skills (maybe separate?), Benefits. Could also have a section for "Key Relationships" etc but not required headings; we can include them under Responsibilities or as separate sections if they have content. However the instruction says use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings only. So we should map content to those headings.
Thus:
- About the role: Job Summary paragraph.
- Responsibilities: list of responsibilities (the bullet points under Job Responsibilities). Use - .
- Requirements: Education, Experience, Required Skills And Certifications (maybe combine). Could be a list.
- Qualifications: Preferred Qualifications (Master's degree, certifications, experience in higher ed/global enterprise, data management, info security awareness). Could be list.
- Skills: maybe we could separate Required Skills And Certifications as Skills? But we already used Requirements for skills. Could also have Skills section for things like communication, collaboration, problem-solving, ability to manage multiple projects. However those are under Required Skills And Certifications. Might be okay to put them under Requirements.
But we need to avoid duplication. Let's think: The posting has sections: Competencies, Education, Experience Required (with subparts Education, Experience, Required Skills And Certifications). Then Preferred Qualifications. Then Supplemental Information (Institutional Impact, Authority and Decision-Making, Key Relationships, Direct Reports, Important Note, compensation, benefits). We could put Institutional Impact etc under About the role? Might be better to create a separate section like "Additional Information" but not allowed headings. Perhaps we can incorporate them into About the role or Responsibilities as prose.
But we must preserve all substantive information. So we need to include those details somewhere.
We could create a section "About the role" that includes Job Summary plus Institutional Impact, Authority and Decision-Making, Key Relationships, Direct Reports, Important Note about E-Verify, compensation statement (though we avoid Pay section). Benefits separate.
Thus About the role will be a longer prose containing multiple paragraphs.
We must not repeat job title as heading.
We must not include boilerplate like EEO etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting includes EEO statement at end: "St. John’s University is an Equal Opportunity Employer...". That's boilerplate; we should remove it.
Also "Any offer of employment is subject to receipt by St. John’s University of satisfactory references, verification of employment and education." That's also boilerplate? Might be considered generic; but it's substantive? It's a condition; but it's typical legal. Might be considered boilerplate; but not explicitly listed as to remove. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The line about offer subject to references is legal; could be considered legal boilerplate. Safer to remove it.
Also "Important Note- St. John’s is NOT an E-Verify Employer" is not EEO; it's a note about E-Verify; we should keep it as it's substantive.
Now let's craft HTML.
We'll have:
About the role
Job Summary paragraph...
Institutional Impact...
Authority and Decision-Making...
Key Relationships...
Direct Reports...
Important Note - St. John’s is NOT an E-Verify Employer
Then Responsibilities:
Responsibilities
- ... each bullet
We need to preserve the percentages? The posting includes percentages like Policies, Plans, and Procedures – 40% etc. Should we keep them? They are substantive. We can include them in the list items.
Responsibilities list items: each bullet from the posting.
Let's extract them:
Policies, Plans, and Procedures – 40%
- Lead stakeholder committees to develop and maintain emergency and continuity plans.
- Conduct multi-disciplinary risk assessments and hazard mitigation planning.
- Create, maintain and update the university-wide Comprehensive Emergency Management Plan (CEMP).
- Tailor Emergency Operations Plans (EOPs) for each campus or center, including international locations.
- Ensure compliance with regulatory and accessibility standards.
- Collaborate with departments and schools to maintain continuity plans that prioritize core missions (teaching, research, housing, and public service).
- Coordinate with Enterprise Risk Management and international campus leaders.
- Establish and maintain a University-wide travel security governance framework that sets institutional standards for University-sponsored travel risk management, including decision authority, risk-tolerance thresholds by destination, and approval and documentation expectations applicable to faculty, staff, and students.
- Oversee an operational travel security program that provides a single intake and tracking mechanism for University-sponsored travel, conducts trip-level risk reviews, delivers pre-departure briefings for elevated-risk locations, and coordinates active traveler communications and emergency response.
- Establish a mandatory travel insurance standard covering emergency medical treatment, medical evacuation, trip disruption, and repatriation; enforce verification as part of the travel registration workflow.
Exercises and Outreach – 20%
- Design and deliver HSEEP-compliant training, exercises, and public preparedness campaigns.
- Maintain a multi-year training and exercise calendar.
- Develop outreach programs for students, faculty, and staff on preparedness and resilience.
- Build partnerships with NYC Emergency Management, regional universities, and professional associations.
Community Education and Engagement – 15%
- Develop and lead campus-wide education and outreach initiatives to promote understanding of emergency management tools, plans, and individual preparedness responsibilities.
- Deliver engaging, accessible content to students, faculty, and staff through workshops, briefings, printed materials, digital campaigns, and orientation programs.
- Ensure emergency plans and continuity tools are not only developed but also understood and embraced by the campus community.
- Partner with Student Affairs, Residence Life, Human Resources, and academic units to embed preparedness education into community life and institutional culture.
- Foster a culture of shared responsibility and proactive risk reduction.
Strategy and Continuous Improvement – 15%
- Serve as a standards champion across departments to build institutional resilience.
- Identify and prioritize innovative risk reduction strategies.
- Track corrective actions and incorporate lessons learned from exercises and incidents.
- Advance the integration of continuity into emergency response planning.
- Implement a travel risk intelligence and monitoring capability with centralized visibility into active University-sponsored trips, automated country/city risk ratings, alerts for emerging global incidents, and direct support for emergency response coordination, with redundant access for Public Safety and program administrators.
Emergency Response – 5%
- Serve as Incident Commander or assist in ICS role assignment during EOC activations.
- Lead operational setup and readiness for all potential EOC sites.
- Deploy to incident locations as needed and support international response operations.
Partnership Development – 5%
- Establish partnerships with peer institutions and private-sector stakeholders.
- Facilitate integration, liaison, and best-practice sharing across continuity communities.
We need to keep the percentages as part of the heading? Could embed them in the list item text.
Now Requirements:
We have Education: Bachelor’s degree in Emergency Management, Public Administration, Business, or related field.
Experience: Minimum of 7 years of emergency management/continuity or program management experience; or 5–7 years with a related graduate degree. Minimum of 5 years in a supervisory capacity.
Required Skills And Certifications:
- Demonstrated expertise in crisis and continuity planning.
- Familiarity with FEMA, NIMS, HSEEP, and regulatory frameworks.
- Familiarity with travel risk management frameworks, including country/destination risk ratings, traveler tracking platforms, pre-departure briefings, and institutional duty-of-care obligations.
- Completion of ICS courses: IS 100, IS 200, IS 700, IS 800.
- Valid driver’s license (or ability to obtain a NY license).
- Strong communication, collaboration, and problem-solving skills.
- Ability to manage multiple projects in a fast-paced, high-stakes environment.
We'll put these in a .
Qualifications (Preferred):
- Master’s degree (MBA or related field).
- Certified Emergency Manager (CEM), CBCP, or FEMA MEP certification.
- Experience in a higher education or global enterprise setting.
- Strong data management and information security awareness.
Now Benefits:
We have: "extremely comprehensive benefits program to meet the diverse needs of our workforce. Along with exceptional benefits such as medical, dental, life insurance, long term disability insurance, tuition remission, generous 403(b) employer contribution, employee assistance program, and liberal paid time off policies, faculty and staff can also enjoy St. John’s performing arts, libraries, bookstores, dining facilities, campus recreation and sporting events"
We'll put that as a list.
Now About the role content: Job Summary paragraph plus Institutional Impact, Authority and Decision-Making, Key Relationships, Direct Reports, Important Note.
Let's extract Job Summary paragraph:
"The Director of Emergency Management and Continuity at St. John’s University is a subject matter expert in all aspects of emergency management—including planning, prevention, response, and recovery—as well as business and operational continuity. Using an all-hazards approach, the Director identifies and mitigates risks that could potentially disrupt university operations at any of St. John’s locations, domestic or international. With a strong operational focus, the Director ensures that emergency management plans are actionable, widely understood, appropriately resourced, and routinely exercised
- for any list of duties/requirements/benefits, and
for prose. We need to decide sections: About the role (Job Summary), Responsibilities, Requirements (maybe combine Education, Experience, Skills And Certifications?), Qualifications (Preferred Qualifications), Skills (maybe separate?), Benefits. Could also have a section for "Key Relationships" etc but not required headings; we can include them under Responsibilities or as separate sections if they have content. However the instruction says use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings only. So we should map content to those headings. Thus: - About the role: Job Summary paragraph. - Responsibilities: list of responsibilities (the bullet points under Job Responsibilities). Use
- .
- Requirements: Education, Experience, Required Skills And Certifications (maybe combine). Could be a list.
- Qualifications: Preferred Qualifications (Master's degree, certifications, experience in higher ed/global enterprise, data management, info security awareness). Could be list.
- Skills: maybe we could separate Required Skills And Certifications as Skills? But we already used Requirements for skills. Could also have Skills section for things like communication, collaboration, problem-solving, ability to manage multiple projects. However those are under Required Skills And Certifications. Might be okay to put them under Requirements.
But we need to avoid duplication. Let's think: The posting has sections: Competencies, Education, Experience Required (with subparts Education, Experience, Required Skills And Certifications). Then Preferred Qualifications. Then Supplemental Information (Institutional Impact, Authority and Decision-Making, Key Relationships, Direct Reports, Important Note, compensation, benefits). We could put Institutional Impact etc under About the role? Might be better to create a separate section like "Additional Information" but not allowed headings. Perhaps we can incorporate them into About the role or Responsibilities as prose.
But we must preserve all substantive information. So we need to include those details somewhere.
We could create a section "About the role" that includes Job Summary plus Institutional Impact, Authority and Decision-Making, Key Relationships, Direct Reports, Important Note about E-Verify, compensation statement (though we avoid Pay section). Benefits separate.
Thus About the role will be a longer prose containing multiple paragraphs.
We must not repeat job title as heading.
We must not include boilerplate like EEO etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting includes EEO statement at end: "St. John’s University is an Equal Opportunity Employer...". That's boilerplate; we should remove it.
Also "Any offer of employment is subject to receipt by St. John’s University of satisfactory references, verification of employment and education." That's also boilerplate? Might be considered generic; but it's substantive? It's a condition; but it's typical legal. Might be considered boilerplate; but not explicitly listed as to remove. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The line about offer subject to references is legal; could be considered legal boilerplate. Safer to remove it.
Also "Important Note- St. John’s is NOT an E-Verify Employer" is not EEO; it's a note about E-Verify; we should keep it as it's substantive.
Now let's craft HTML.
We'll have:
About the role
Job Summary paragraph...
Institutional Impact...
Authority and Decision-Making...
Key Relationships...
Direct Reports...
Important Note - St. John’s is NOT an E-Verify Employer
Then Responsibilities:Responsibilities
- ... each bullet
- .
Qualifications (Preferred):
- Master’s degree (MBA or related field).
- Certified Emergency Manager (CEM), CBCP, or FEMA MEP certification.
- Experience in a higher education or global enterprise setting.
- Strong data management and information security awareness.
Now Benefits:
We have: "extremely comprehensive benefits program to meet the diverse needs of our workforce. Along with exceptional benefits such as medical, dental, life insurance, long term disability insurance, tuition remission, generous 403(b) employer contribution, employee assistance program, and liberal paid time off policies, faculty and staff can also enjoy St. John’s performing arts, libraries, bookstores, dining facilities, campus recreation and sporting events"
We'll put that as a
- list.
Now About the role content: Job Summary paragraph plus Institutional Impact, Authority and Decision-Making, Key Relationships, Direct Reports, Important Note.
Let's extract Job Summary paragraph:
"The Director of Emergency Management and Continuity at St. John’s University is a subject matter expert in all aspects of emergency management—including planning, prevention, response, and recovery—as well as business and operational continuity. Using an all-hazards approach, the Director identifies and mitigates risks that could potentially disrupt university operations at any of St. John’s locations, domestic or international. With a strong operational focus, the Director ensures that emergency management plans are actionable, widely understood, appropriately resourced, and routinely exercised
- .
- Requirements: Education, Experience, Required Skills And Certifications (maybe combine). Could be a list.
- Qualifications: Preferred Qualifications (Master's degree, certifications, experience in higher ed/global enterprise, data management, info security awareness). Could be list.
- Skills: maybe we could separate Required Skills And Certifications as Skills? But we already used Requirements for skills. Could also have Skills section for things like communication, collaboration, problem-solving, ability to manage multiple projects. However those are under Required Skills And Certifications. Might be okay to put them under Requirements.
But we need to avoid duplication. Let's think: The posting has sections: Competencies, Education, Experience Required (with subparts Education, Experience, Required Skills And Certifications). Then Preferred Qualifications. Then Supplemental Information (Institutional Impact, Authority and Decision-Making, Key Relationships, Direct Reports, Important Note, compensation, benefits). We could put Institutional Impact etc under About the role? Might be better to create a separate section like "Additional Information" but not allowed headings. Perhaps we can incorporate them into About the role or Responsibilities as prose.
But we must preserve all substantive information. So we need to include those details somewhere.
We could create a section "About the role" that includes Job Summary plus Institutional Impact, Authority and Decision-Making, Key Relationships, Direct Reports, Important Note about E-Verify, compensation statement (though we avoid Pay section). Benefits separate.
Thus About the role will be a longer prose containing multiple paragraphs.
We must not repeat job title as heading.
We must not include boilerplate like EEO etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting includes EEO statement at end: "St. John’s University is an Equal Opportunity Employer...". That's boilerplate; we should remove it.
Also "Any offer of employment is subject to receipt by St. John’s University of satisfactory references, verification of employment and education." That's also boilerplate? Might be considered generic; but it's substantive? It's a condition; but it's typical legal. Might be considered boilerplate; but not explicitly listed as to remove. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The line about offer subject to references is legal; could be considered legal boilerplate. Safer to remove it.
Also "Important Note- St. John’s is NOT an E-Verify Employer" is not EEO; it's a note about E-Verify; we should keep it as it's substantive.
Now let's craft HTML.
We'll have: