Emergency Services Coordinator

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 content. We need to parse the job description. We have: - About The Role: paragraph(s) describing role. - Key Responsibilities: list of bullet points. - Why This Role Matters: maybe could be part of About? But we can treat as separate? Not required heading; we could include under About the role or maybe as a separate section "Why This Role Matters". The instructions: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only use those headings if they exist. "Why This Role Matters" is not in list; we could incorporate into About the role or maybe omit. Better to keep content but not as separate heading; we can embed within About the role paragraph. - Working Conditions: includes Hybrid Telework, DMV Pull Program, Conflict of Interest. Not in list; maybe we could put under "Benefits"? No. Could be omitted? The instruction: include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It doesn't say we must include Working Conditions; we can drop it if not matching headings. However we need to preserve ALL substantive information; we cannot drop info. So we need to incorporate that info somewhere else, maybe under a generic

without heading. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

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

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. So we can have prose paragraphs without headings. So we can include Working Conditions as prose paragraphs. - Department Information: also prose. - Desirable Qualifications: list of qualifications; could be under "Qualifications" or "Requirements". The heading list includes Requirements, Qualifications, Skills. We need to decide which to use. The posting has "Desirable Qualifications". That's qualifications. So we can use

  Qualifications

  and list items. - Benefits: there is a Benefits section with list. So we include

  Benefits

  and list. - Pay: not mentioned; we should not include Pay heading. - Schedule: not mentioned explicitly; there is Hybrid Telework but not schedule details. So we should not include Schedule heading. - Responsibilities: we have Key Responsibilities list. So

  Responsibilities

  . - About the role: we have About The Role paragraph(s). So

  About the role

  . - Requirements: maybe we could treat Desirable Qualifications as Requirements? But we already used Qualifications. Could also have Requirements separate but we don't have explicit required qualifications besides maybe experience etc. The Desirable Qualifications list includes experience etc. Could be considered Requirements. But we have only one qualifications list; we can put under Qualifications. The instruction: Prefer a few substantive sections over many thin ones. So we can combine Requirements and Qualifications into one Qualifications section. Or we could have Requirements heading with some content (maybe none). Better to just have Qualifications. Thus sections: About the role, Responsibilities, Qualifications, Benefits. Plus prose paragraphs for Working Conditions, Department Information, maybe also "Why This Role Matters" integrated. We need to preserve all substantive information. Let's extract. About The Role paragraph: "We are seeking a highly motivated Emergency Services Coordinator (ESC) to serve as the interface between state and local government partners. This position plays a critical role in strengthening emergency management capabilities across the state by providing guidance, coordination, and support before, during, and after disasters. During complex, high-impact emergencies—such as wildfires, floods, or earthquakes—staff work alongside local emergency managers to coordinate state resources and share critical information with emergency operations centers across all levels of SEMS. Staff help identify resource gaps, analyze operational challenges, and support solutions that minimize impacts to life, property, and the environment. During non-emergency periods, staff collaborate with counties and cities to strengthen preparedness. This includes reviewing emergency operations plans, supporting training and exercises, and updating policies and procedures based on lessons learned from After Action Reports. Regional staff also help maintain the integrity of the Standardized Emergency Management System (SEMS) by coordinating quarterly Mutual Aid Regional Advisory Committee (MARAC) meetings. These meetings bring together emergency management partners—such as local and county emergency managers, fire, law enforcement, communications, and other local partners—to discuss regulatory changes, system improvements, emerging technologies, funding opportunities, and overall regional readiness. The ideal candidate thrives in a fast-paced and dynamic environment, demonstrates strong independence and leadership, and is committed to supporting communities during emergencies." That's the About The Role. Key Responsibilities list: - Serve as the primary interface between state and local governments on emergency management initiatives. - Provide advisory support and coordination to local and tribal governments, regional staff, and state agencies. - Lead and support emergency management projects and preparedness initiatives. - Respond to disasters and emergencies statewide, including after-hours deployments when required. - Maintain routine program responsibilities while addressing short-term urgent assignments. - Ensure compliance with regulatory requirements and internal deadlines. - Communicate effectively with stakeholders through written reports, briefings, and presentations. - Develop and implement solutions to complex emergency management challenges. Why This Role Matters paragraph: "As an Emergency Services Coordinator, you will play a vital role in helping communities prepare for, respond to, and recover from disasters, ensuring that critical resources and coordination are available when they are needed most. We hope that you will consider a rewarding and challenging career with us! You will find additional information about the job in the Duty Statement." We could incorporate after About the role. Working Conditions: - Hybrid Telework: This position is eligible for a hybrid work schedule. Additional in office days may be required based on the business need. - DMV Pull Program: Participation in the DMV Pull Program is required. The position(s) require(s) a valid Driver’s License (DL). You must answer the questions addressing your DL on your application. Ensure you provide your DL number, class, expiration date, and any endorsements and/or restrictions. - Conflict of Interest (COI): This position is designated under the Conflict of Interest Code and is required to complete Form 700 within 30 days of appointment. Failure to comply with the Conflict of Interest Code requirements may void the appointment. Department Information paragraph(s): "The California Governor’s Office of Emergency Services (Cal OES) is committed to fostering a diverse and inclusive culture by hiring and retaining individuals from a variety of backgrounds and personal experiences. Our employees are empowered with the tools and resources necessary to meet our mission, while continuing to expand equity and inclusion efforts at all levels of the organization. We are committed to the spirit and work required to ensure the safety and resilience of every community in California. The Response Operations leads the State’s incident response efforts and maintains emergency management situational awareness during an incident. Responding to a disaster means addressing the short-term, direct effects of an incident or threat. Response includes immediate actions to save lives, protect property, and meet basic human needs. The Cal OES Response Operations addresses all types of threats and hazards, ranging from accidents, technological hazards, natural disasters, human-caused incidents, pre-planned events, proactive preparedness measures, and mutual aid coordination. The Response Operations reinforces local responses to incident areas by coordinating state-level government, private sector, and nongovernmental roles in support of local governments and other entities. Responses are conducted in accordance with the Standardized Emergency Management System (SEMS). In the event of an emergency, employees may be contacted and requested to report to work in the event of an emergency. This contact may be outside of your normal working hours (evenings/nights, weekends, and holidays). This service may require irregular work hours, work locations other than the official duty location, and may include duties other than those specified in your official position description. Travel requirements in support of emergency operations may be extensive in nature (weeks to months), with little advance notice, and you may be required to relocate to emergency sites. More information may be found here: Response Operations | California Governor's Office of Emergency Services Department Website: http://www.caloes.ca.gov" Desirable Qualifications list: - Experience responding to disasters. - Knowledge of state disaster preparedness and response protocols and procedures and the state’s disaster response structure. - Experience working with local government agencies. - Knowledge of federal, state, and local emergency preparedness and response laws, regulations, policies, and guidelines. - Ability to establish and maintain rapport and collaborative working relationships with highly engaged internal and external partners. - Experience with coordination of multiple multidisciplinary partners. - Ability to maintain a high degree of confidentiality. - Ability to handle multiple competing priorities simultaneously. - Ability to provide actionable, real-time intelligence to support situational awareness and decision-making. - Excellent customer service (interpersonal) skills, including professionalism, tactfulness, flexibility, and open-mindedness. - Excellent written and verbal communication skills. - Ability to meet deadlines in high pressure environments. - Ability to work efficiently and resourcefully as part of a team, or individually. - Ability to provide creative solutions to problems. - Demonstrate initiative. - Strong computer literacy and software skills and ability to quickly learn and adapt to new systems and technologies. - Public speaking/presentation skills. Benefits list: - Excellent CalPERS state pension plan - 401(k) and 457(b) Plans - Flexible Schedules - Generous paid time off - Health, dental & vision insurance for the employee or the employee's family - Investment in careers development - Free Parking - Electric Carport Note: The benefits list includes "Excellent CalPERS state pension plan401(k) and 457(b) PlansFlexible SchedulesGenerous paid time offHealth, dental & vision insurance for the employee or the employee's familyInvestment in careers developmentFree ParkingElectric Carport". Actually the original text had no line breaks; but we can treat each as separate bullet. We'll split by keywords? Better to keep as given but we can separate with commas? The instruction: preserve ALL substantive information; do not invent or summarize away detail. We need to output list items; we can keep each benefit as separate
• . The original string: "Excellent CalPERS state pension plan401(k) and 457(b) PlansFlexible SchedulesGenerous paid time offHealth, dental & vision insurance for the employee or the employee's familyInvestment in careers developmentFree ParkingElectric Carport". It seems missing punctuation; but we can still split where capital letters start after lowercase? Might be ambiguous. Safer to keep as a single
• with the whole string? But that would lose detail of each benefit. However the instruction says preserve ALL substantive information; splitting incorrectly could misrepresent. Better to keep as one paragraph? But they said use
  • for any list of duties/requirements/benefits. So we need to make a list. We could treat each benefit separated by a capital letter after a lowercase? Let's manually parse: "Excellent CalPERS state pension plan" "401(k) and 457(b) Plans" "Flexible Schedules" "Generous paid time off" "Health, dental & vision insurance for the employee or the employee's family" "Investment in careers development" "Free Parking" "Electric Carport" Yes that seems correct. We'll output those as
  • . Now we need to output only HTML fragment, no /, no markdown. We'll structure:

    About the role

    ... (About The Role paragraph + Why This Role Matters maybe)

    Responsibilities