PUBLIC SAFETY EMERGENCY CALL TAKER I/II

We need to output HTML fragment with sections: About the role? Actually the posting includes "About The Position" and "About The Agency". Also "Examples of Work" could be responsibilities. "Qualifications" section. "Additional Information" includes location, conditions, shift hours, etc. We need to include only sections with real content. No Pay, Schedule, Benefits unless stated. There's mention of shift hours (eight, ten, twelve hour rotating shifts) - that's schedule info. Should we include a Schedule section? The rule: include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The posting does have shift hour info: "Have the ability ... to report on time to the primary center ... Be able to work eight (8), ten (10) or twelve (12) hour rotating shifts". Also "Employees in this classification may be assigned to a one of four twelve hour rotating shifts". So we have schedule specifics. So we can include a Schedule section with that info. Benefits: not mentioned. Pay: not mentioned. So omit. We need headings:

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. We need to preserve all substantive info, not invent or summarize away detail. Remove boilerplate etc. We need to decide sections: About The Position (maybe "About the role") and About The Agency (maybe "About the agency")? The rule says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely we should stick to those headings where applicable. So we can map: - About the role: corresponds to "About The Position". Provide prose. - Responsibilities: could be "Examples of Work" list. - Requirements: could be "Qualifications" (minimum qualifications) plus maybe "Additional Information" conditions? But we have separate Qualifications heading. - Qualifications: we already have a Qualifications section. - Skills: maybe not present; we could omit if no specific skills list. - Schedule: we have shift info. We should not repeat job title as heading. We need to include all substantive info: nature and variety of work intro paragraph? The first paragraph about Prince George's County Government etc. That's general intro; maybe we can include as part of About the role? Or maybe a separate "About the role" includes that. We need to preserve all info: The intro about dynamic workplace, bilingual encouraged, Office of Homeland Security seeking PSC Emergency Call Taker I/II, grade P14/P15, upcoming Fall training classes. That's substantive. We also have "About The Position" details: call taker duties. We have "About The Agency": history. We have "Examples of Work": a long list of duties (operate workstation, etc.) That's responsibilities. We have "Qualifications": Minimum qualifications list. We have "Additional Information": includes location, conditions of employment (shift hours, uniform, training requirements, essential employee, etc.). This could be split into Schedule (shift hours) and maybe other info like location, uniform, training, essential employee. Since we don't have headings for location or training, we could put them under About the role or Responsibilities? But better to keep them under a generic section? The instruction says prefer a few substantive sections over many thin ones. So we could combine Additional Information into Schedule and maybe Qualifications? But Qualifications already covers minimum qualifications. Additional info includes conditions like uniform, training, essential employee, location, ability to report to centers, etc. Those are not qualifications but conditions of employment. Could be placed under "About the role" or maybe a new section like "Conditions". But we only allowed headings from the list; we could still use other headings? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. Safer to stick to those. We can place location, uniform, training, essential employee under About the role or Responsibilities? Might be odd. Maybe we can create a section "Requirements" for conditions like uniform, ability to work shifts, etc. But Requirements usually for prerequisites. However we can still use it. Let's think: We have: - About the role: intro + About The Position description. - Responsibilities: Examples of Work list. - Requirements: Minimum Qualifications? Actually Qualifications heading exists. So we can put Minimum Qualifications under Qualifications. - Requirements could be things like "Must be able to work eight, ten, twelve hour rotating shifts", "Must have driver's license or reliable transportation", "Must wear uniform", "Must be essential employee", "Must complete training". Those are more like requirements/conditions. - Skills: maybe not needed. - Schedule: shift hours. But we have overlapping. Better to follow the examples: Use headings exactly as given: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we must only use those headings. If we have content that doesn't fit, we need to fit into one of those. Let's map: - About the role: include introductory paragraph about agency, bilingual encouragement, position description overview. - Responsibilities: list of duties from Examples of Work (the long list). Also maybe the call taker duties from About The Position? But we can include those as responsibilities too. - Requirements: include conditions like ability to work shifts, transportation, uniform, essential employee, training completion, background check, medical exam, drug screen, etc. Also maybe the minimum qualifications? But we have Qualifications heading for that. - Qualifications: minimum qualifications list (HS diploma/GED, age 18, 1 year Windows experience, pass exam and keyboarding test). - Skills: maybe we can list specific skills like listening ability, typing, etc. But those are in About The Position. Could go under Skills. - Benefits: none -> omit. - Pay: none -> omit. - Schedule: shift hours (8,10,12 hour rotating shifts) and maybe mention rotating shifts. We must not create headings with filler. So we will only output those headings that have content. Let's extract content precisely. First, intro paragraph: "Nature and Variety of Work Come join our team! Prince George’s County Government provides a dynamic and inclusive workplace where employees can thrive, learn, and grow across its 30 diverse agencies, all dedicated to serving the County's residents with essential resources and services. Nestled just minutes away from Washington, DC, Prince George's County combines urban vibrancy with serene surroundings, offering an ideal setting to live, work, and enjoy life. Bilingual applicants are encouraged to apply. The Office of Homeland Security is currently seeking qualified applicants to fill Public Safety Emergency Call Taker I/II positions, Grade P14/P15 in the Public Safety Communications (PSC) Division for its upcoming Fall training classes. This role is critical in maintaining and supporting public safety. If you have a desire to help the community, support emergency responses, and are seeking a rewarding career in public safety communications, we invite you to apply today." We can keep that as prose under About the role. Next, About The Position: details about call taker duties. Could go under Responsibilities or About the role. Since we already have About the role for overview, we can put the specific duties under Responsibilities. But we also have Examples of Work list which is a more detailed list of duties. We can combine both under Responsibilities as a list. Let's extract the responsibilities text: From About The Position: "Call Takers receive incoming calls via the 9-1-1 system's emergency or non-emergency lines, enter and transmit appropriate emergency information and codes into the Computer Aided Dispatch (CAD), and simultaneously provide pre-arrival and post-dispatch instructions to distressed or irate callers while recording data in the CAD system. Call Takers are responsible for becoming familiar with emergency and dispatch protocols to effectuate response and transmission of emergency requests in a safe, reproducible, and non-arbitrary manner. Incumbents are expected to exhibit highly skilled listening ability in order to quickly and accurately ascertain from emotional, distraught individuals, the nature of assistance required along with the ability to accurately and quickly type/enter the information in the CAD system. Call Takers must have the tolerance to work under pressure. Work is performed inside a secured, windowless office environment with a specialized low-light system and includes prolonged periods of sitting at a designated workstation monitoring computer screens and entering data. There is limited opportunity for physical movement; rest and meal periods are dependent on workload. Incumbents must be able to perform the following: reaching, fingering, grasping, hearing/listening, seeing/observing, and repetitive motions. Vision abilities required for this job include close vision and the ability to adjust focus; the ability to see with or without corrective lenses, and well enough to read standard text and text displayed on a video display terminal. Work may require constant focus on a computer screen for two or more hours at a time. All personnel in this class of work must work on site and are not eligible for telework or remote work assignments." That's a lot of prose; we could keep as paragraph(s) under Responsibilities. Then Examples of Work list: each sentence starting with a verb. We can turn each into

  . Let's list them: - Operate a workstation comprised of multiple computer systems including Automatic Call Distribution (ACD) 9-1-1 emergency and non-emergency telephone system, geographical mapping tools (GIS and aerial photography), Computer Aided Dispatch, and other repositories for critical information to answer, triage and process incoming emergency and non-emergency calls of service - Initiate calls for service, utilizing appropriate protocols, provides pre-arrival instructions including CPR instructions, when appropriate - Receive incoming requests for emergency and non-emergency assistance, determine the type of service(s) required and initiate calls for service in accordance with emergency dispatch protocols and Public Safety Communication (PSC), Police, Sheriff's, Fire/EMS and other public safety agencies' policies - Receive calls via the radio, 9-1-1 system or telephone while using an issued headset or other computer-based communication equipment and processes/records pertinent information according to agency procedures and protocol - Make computer inquiries and be able to interpret the information that is received from the various agencies via the computer - Operate the various technical systems and equipment necessary to obtain and properly process 9-1-1 calls for service. This includes the deaf teletype system, 9-1-1 system, text to 9-1-1 computer function, language line, mapping programs, and the Computer Aided Dispatch system - Provide emergency pre-arrival and post-arrival instructions to the caller to mitigate or lessen the impact of their emergency prior to arrival of public safety responders - Gather, classify, and supplement pertinent information obtained from caller(s) and enter it into the CAD system, consistent with appropriate protocols - Utilize life support protocols, as authorized under the Maryland Emergency Medical Dispatch license/certification, to provide appropriate instructions to caller - Establish communications with hearing impaired callers through the Maryland Relay 7-1-1 telephone system - Identify non-English speaking callers and utilizes the language translation service as necessary to complete call processing - Utilize the NCIC, METERS, and other related computer data bases to obtain information on criminal history, arrest warrants, missing persons, driver history, stolen property, stolen vehicles, securities and boats, vehicles, firearms, etc. - Identify when it is appropriate to refer callers to other County, State, or Federal agencies or outside jurisdictions and maintains/prepares various logs and records pertinent to operations We could keep as list. Now Requirements section: conditions of employment etc. From Additional Information: - Job Location: Onsite at designated locations